I have mixed feelings about QML.
It somewhat looks like a new flash engine, except for mobile devices, and it became old the day React-Native appeared.
But I like the design, and the way the UI is built (descriptive ui language with javascript, integrated event management, bridged with c++).
Anyway, I starred the project and I'm very curious about the kind of traction QML can get.
QML is amazing for desktop apps as well. The only problem with QML on mobile is that stuff just won't look native or match native themes. Not the end of the world though.
It is worse than that. Up until 5.3, the common dialogs would render like on desktop OSes, just tinier, instead of being adapted to the mobile OSes concepts.
As far as I know it is still the case. One needs to reimplement the common dialogs in QML when doing mobile development with Qt.
QML will never become old unless someone improves upon its UX, because React is still the same old Frankenstein of turning a document language into an application framework, you are just doing it all in Javascript.
QML is also all Javascript, but it knows better than to treat its declarative language like verbatim JS. The property system of QML is not something to underestimate, and is IMO by far the most developer friendly way to design a UI today, period. The hardware acceleration on all platforms is just a cherry on top of a usability pie.
I keep having lucid dreams of QML gaining native browser support as a web application development platform, rather than us continuing to try to shoehorn desktop program design into a document markup language more akin to Microsoft Office than Microsoft Visual Basic.
I also see insanity like <script type=text/python> and other delusions probably brought on from traumatic experience with current web tech.
Imagine it - http://coolprogram.stuff/main.qml working would make me cry tears as the strain on my brain as my migrane rapidly unswells and an unholy weight is lifted from my shoulders.
qmlweb, in the meantime, does the work of angels trying to bridge the gap. It is a great project to check up on to try to maintain some hope in the long run, and fake sanity when needed!
14 comments
[ 5.2 ms ] story [ 42.4 ms ] threadAnyway, I starred the project and I'm very curious about the kind of traction QML can get.
http://blog.qt.io/blog/2015/11/23/qt-quick-controls-re-engin...
They already have Holo, they just need Material for newer Android handsets, and those changes are going in 5.7 coming out in a few months.
Now Xamarin is free to indies and they use native controls, not themes that look somehow like native.
As far as I know it is still the case. One needs to reimplement the common dialogs in QML when doing mobile development with Qt.
Why do you think so? Could you expand on this a bit?
I'd prefer QML myself since it means I can have a single UI codebase across platforms, plus with the qml compiler the apps can be fast.
QML is also all Javascript, but it knows better than to treat its declarative language like verbatim JS. The property system of QML is not something to underestimate, and is IMO by far the most developer friendly way to design a UI today, period. The hardware acceleration on all platforms is just a cherry on top of a usability pie.
It supports much more OSes, a proper separation between view and businesses language at language barrier and is fully native code.
I also see insanity like <script type=text/python> and other delusions probably brought on from traumatic experience with current web tech.
Imagine it - http://coolprogram.stuff/main.qml working would make me cry tears as the strain on my brain as my migrane rapidly unswells and an unholy weight is lifted from my shoulders.
qmlweb, in the meantime, does the work of angels trying to bridge the gap. It is a great project to check up on to try to maintain some hope in the long run, and fake sanity when needed!
edit: interesting, github shows two different dates. I guess the commit date and author date are very different for the latest commit.