5 ms·
Can you tell me why do you feel QML is superior to Qt Widgets for desktop applications? I tried QtQuick 1 and was underwhelmed (so much glue code to link C++ a
by lultimouomo 10y ago
Can you tell me why do you feel QML is superior to Qt Widgets for desktop applications?
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...
- distances 10y agoMy experience is indeed more on the embedded and mobile side of things, where hardware acceleration and animations are indeed a major selling point. 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.
- mlvljr 10y ago1) Ease of complete control over visuals and behavior of the "items" and 2) the automated reevaluation of (functional, let's name things what they are) "bindings" of arbitrary structure -- are the main selling points, I'd say (C++ interop will be not a burden, if business logic stays in the backend, making the interop logic rather compact).