+1 over her on Qml being my favorite UI framework, did crazy think with it
we did render 3D into Qml scene before Qt 3D was there, rendering an
engine into texture into our own declarative engine rendering exposed nodes.
Multiple QQmlEngine for pipeline flow rendering pass (fast rendering into
main GUI thread) other engine into another thread render with more precision
into the background but declare into a declarative way of Qml. Was mostly a
reality, only 1 thing ever stop us from releasing this at large, the Qml
singleton bug from qmldir, this issue was never fixed btw). We could put
rendering progress bar upside the 3D object as they get sharper and better
smoothed and more precise into our CAD software, was very nice to see with the
3D scene still completely fluid and user interactable while the heavy work was
done and could be easily scripted by the high level application dev.
+1 on waiting for 6.2 before any switch can even be possible, will see when it
get there, before it would be just plain huge waste of time.
But I see less and less Qt contract coming our way, client are scare of Qt
license right now, everybody feel like this is a nuclear waste of some kind
that they better to stay away as of now. I cannot really blame them, when the
question always end up check with your lawyer, they don’t they just stroke the
option out or if the answer the price toll depends will depend… they stroke
that option out too!
I did my share of mobile and desktop development for
Windows/Linux/MacOS/iOS/Android and Qt always was my fun ride to write a commun
source code. But I touch it less and less and that make me sad, I do more and
more Xamarin/.Net Standard 2/Unity/Blazor combo code those days. This with
embedded IoT device can go a long way and the cost is predictable… Client like
predictable, they like that too much but they always do…
Jérôme Godbout, B. Ing.
Software / Firmware Team Lead
O: (418) 682-3636 ext.: 114
C: (581) 777-0050
godbo...@dimonoff.com<mailto:godbo...@dimonoff.com>
[signature_1251317868]<https://www.dimonoff.com/>
dimonoff.com<https://www.dimonoff.com/>
1015 Avenue Wilfrid-Pelletier,
Québec, QC G1W 0C4, 4e étage
From: Interest <interest-boun...@qt-project.org> on behalf of ekke
<e...@ekkes-corner.org>
Date: Monday, March 22, 2021 at 11:48 AM
To: interest@qt-project.org <interest@qt-project.org>
Subject: Re: [Interest] The willy-nilly deletion of convenience, methods (was:
Mixing Commercial and Open...)
+1
Qt for me still is the best cross-platform solution for mobile app development
enabling me to build great (and performant) apps from one source.
from time to time looking at Flutter but still feel better using QML for UI and
C++ for the rest.
cannot say much about Qt6 yet because I'm waiting for 6.2 to get all the
modules I need - will start refactoring all the depricated parts next
weeks/months step by step beside my daily work
Am 22.03.21 um 16:22 schrieb Nelson, Michael:
+1 for idea that mobile support has not been the priority in QtCo's mind that I
need it to be.
+1 for idea that filing bug reports and voting for them did not result in my
concerns being addressed. UX with QML across mobile and desktop platforms could
be better but many issues simply sit unaddressed.
Still, cross-platform support is nevertheless strong and QML is indeed a great
language for UI, so I'm still a paying customer, for now. Keeping an eye on
Flutter, though. 😊
Best regards,
MICHAEL NELSON | Sr. Software Engineer
T 703-406-2800, 341
michael.nel...@otthydromet.com<mailto:michael.nel...@otthydromet.com> |
www.otthydromet.com<http://www.otthydromet.com>
--
ekke (ekkehard gentz)
independent software architect
international development native mobile business apps
Qt Mobile: Android, iOS, W10 (former projects: BlackBerry 10)
Qt Champion
BlackBerry Elite Developer
max-josefs-platz 30, D-83022 rosenheim, germany
twitter: @ekkescorner
LinkedIn: http://linkedin.com/in/ekkehard/
_______________________________________________
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
