[Development] Qml/Quick Designe Decision Wiki or how to avoid generating work for other stakeholders
Marco.Bubke at digia.com
Tue Jul 2 11:42:10 CEST 2013
The ApplicationWindow encapsulates a completely different concept compared to normal items and trying to treat them as the same in the design tool makes very little sense.
Is sense, logic not very context depend? I think our argument network, which is designer centric, is different from yours, which is run time centric. Like I have written ApplicationWindow is a hybrid of a window and a item but it is not a item in the sense of duck typing. It is different and that is hurting us. And for the menus you don't need a WYSIWYG editor.
The ApplicationWindow floats stand alone in the windowing system, it may have menu bar, status bar and toolbar, all of which require dedicated support from the designer to be designable. And the code generated does not go into a QQuickView, but needs to be created as via QQmlComponent::create() as it creates the window itself.
Actually what is the advantage to have the menu bar, status bar and toolbar designable? And we do not create the items from text because we need more control over them. I don't want to argument about that again and
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Development