4 ms·

I think QML is used for Qt Quick and not compatible with desktop-style Qt Widgets. Qt Widgets .ui files are human-unreadable, and when edited in Qt Designer, us

I think QML is used for Qt Quick and not compatible with desktop-style Qt Widgets. Qt Widgets .ui files are human-unreadable, and when edited in Qt Designer, usually lead to incorrect tab order (see LMMS's settings screen). All of these seem somewhat conceptually similar to Audacity ShuttleGUI (https://wiki.audacityteam.org/wiki/ShuttleGui https://wiki.audacityteam.org/wiki/ShuttleGui) Or the Python context-manager-based declarative GUI (wrapping PyQt) I wrote for my relatively small program corrscope (https://github.com/jimbo1qaz/corrscope/blob/master/corrscope/gui/view_mainwindow.py https://github.com/jimbo1qaz/corrscope/blob/master/corrscope...)

jcelerier 7y ago
> I think QML is used for Qt Quick and not compatible with desktop-style Qt Widgets. yes, but it does not prevent you to make desktop apps with it. See e.g. Kirigami UI which is based on QtQuick : https://kde.org/products/kirigami/ https://kde.org/products/kirigami/ (and for "large" desktop apps made with QtQuick, look at the Blizzard launcher, or Substance Designer which is as much a desktop app as one can aspire to be : https://cdn.studiodaily.com/wp-content/uploads/2019/05/substance-designer-screenshot.png https://cdn.studiodaily.com/wp-content/uploads/2019/05/subst... ) QML has a fundamental difference with the links you showed : it is able to create bindings according to variables used in expressions / functions / etc. e.g. if you do MyWidget { width: { if(y > 50) return f(height) + x; else return otherItem.height / height; } } then whenever any of the properties used in the expression changes, the width is recomputed.