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!
Anyway, I starred the project and I'm very curious about the kind of traction QML can get.
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.
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.
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.
It supports much more OSes, a proper separation between view and businesses language at language barrier and is fully native code.
edit: interesting, github shows two different dates. I guess the commit date and author date are very different for the latest commit.
