News for hackers. Stuff that matters.
Re:When XML Beats JSON: UI Layouts by forgottenpass on Wednesday October 30, 2019 @12:58PM (#21399870)
I think qt widgets (not-qml, it's different and I haven't used it) uses XML without many of those problems.

Layouts are trees of widgets. Layouts are themselves widgets so repetition in the tree can be reduced.

You use XML, C++, or both to define a widget. The UI Compiler will turn that XML into C++.

That means further code reuse can leverage the C++ type system. All widgets are QWidgets, and MyProgressBar inherits from QScrollBar.

And you (or, at least I) never write .ui files by hand, they've got a GUI designer tool. And the tool supports your custom widgets by treating them the same as the known widget type it inherits from.

Accessing XML-defined widgets from code is the same as C++ defined widgets, because the compilation step means they are. Class member names come straight from the XML file.

The QObjects are constructed in a way that understands the UI hierarchy, and you can programmatically walk that hierarchy using the variable names. (You do have to tell objects their own names in the non-XML-generated code.)

Re:When XML Beats JSON: UI Layouts by Pmop on Wednesday October 30, 2019 @04:27PM (#21402239)
Qt is really good for doing UI, in my opinion, both QML and non-QML. They do a really good job at keeping things coherent and concise, which really helps first-time users, specially after learning the basics.