On Sat, Dec 09, 2023 at 01:16:00PM +0100, Ulf Hermann via Interest wrote: > [...] > 3. Clarity: Having dedicated syntax to construct hierarchies of objects is > immensely helpful for building user interfaces. Most user interfaces consist > of some hierarchical construction of graphical elements, and being able to > see that in the code is vital. I have seen some pure C++ constructions that > look kind of similar to QML. If those were public I could discuss them here.
I could offer lines 50-62 in https://code.qt.io/cgit/qt-creator/qt-creator.git/tree/src/plugins/beautifier/generalsettings.cpp for production code. That's the "General" page in the "Beautifier" section of Qt Creator's settings dialog. For a somewhat unrealistic and artifcial example perhaps also https://code.qt.io/cgit/qt-creator/qt-creator.git/tree/tests/manual/layoutbuilder/demo/main.cpp Note that the point here is the "developer facing" "frontend", not the current implementation, which is limited to the single artificial use case there. > We might take them into account when improving qmltc [3]. If we have an > elegant way to express object hierarchies in C++, qmltc might generate that. > You might then opt to instead write the same thing manually. I wouldn't be > opposed to that. I don't think that's worthwhile. The whole thing is basically just syntactic sugar around calling a few setters. Andre' _______________________________________________ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
