> That’s called “interface builder” and it falls short at edge (or just non-trivial) cases in all frameworks ever created. Qt, gtk, whatever-tk, any windows, mac, phone ui.
That's interesting, I've used those a fair amount of time generally with success for e.g. config UIs, etc.
e.g. look at the amount of Qt-based UI dialog merely on github : https://github.com/search?q=extension%3Aui+language%3AXML+QD...
If it’s different this time, then I would like to see that authors know about the shortcomings and problems that usually arise. E.g. restructuring of a container set without losing inner constraints; injecting two subitems where one was without resizing arounds; temporary places outside of main template; viewing full hierarchy with artifical borders to select an interested level; having auto-dummies in boxes to prevent a new subitem to fill all space, making it easy to reason on half-done design. I could go on.
But all introduction videos just show us how they drop an item into an empty vbox. Thanks, but yawn.