So still the same "do your own QML mimic of native widgets"?
So still the same "do your own QML mimic of native widgets"?
https://blog.qt.io/blog/2016/06/10/qt-quick-controls-2-0-a-n...
So from 5.4. up to 5.8 little seems to have changed from that comment.
Nowadays I just use Native OS UI language + C++ or Xamarin, both are easier for me to write portable native apps with direct support for native widgets than using QML.
I tried QtQuick 1 and was underwhelmed (so much glue code to link C++ and QML; the awkwardness of JS without the huge amount of libraries that save your day in web development). In the last couple of years I have seen a lot of renewed hype about QML but I keep wondering what it's buying you over the traditional widgets in non-embedded envs (where you might want to profit from OpenGL acceleration for performance reasons).
Am I missing something? I would love to love QML, as I love Qt and I see that widgets are clearly on their way out...
I'd let others with more experience on desktop QML vs. widgets to judge their respective strengths, my comment was more about Qt vs. non-Qt frameworks. That makes QML the topic as it's currently the main UI development story for Qt.
Because of this, I'm a bit disappointed that Qt 5.8 alpha doesn't have anything interesting for Qt Widgets users. Qt Widgets is the best cross-platform UI framework out there, but Qt Quick is, at least from my perspective, a bit mediocre.
The last attempt was a small mobile app for Android/WP that I ended up rewriting in Java,C++/CX + C++11, because of the issues I had with Qt 5.4.
However I still follow the announcements and get the feeling that they are trying to re-purpose Qt in the same way that JavaFX, WPF/XAML and mobile OS UI stacks have done, but it is still catching up with their feature sets.
QT looks and feels like QT and takes a lot of it's cues from Windows (near as I can tell) so no QT app feels like it belongs on a Mac at all.