[Qt-components] QML component APIs and techniques

Bache-Wiig Jens Jens.Bache-Wiig at digia.com
Fri Jan 11 13:10:29 CET 2013


> 
> - Page and PageStack. Are you generally agreeing on these? Page is almost unnecessary as items can be pushed but feels natural in a "pagestack" and will allow some custom margins/styling as well as a status property. But the "tools" property and orientation properties seem dubious and Meego specific.
> 
> As for ApplicationWindow the basic API might end up like this:
> - ApplicationWindow {  // A QtQuick.Window obviously so has "title" etc
>    toolBar: ToolBar { … }
>    statusBar: StatusBar { …} 
>    initialPage: MyPage{ } 
> }
> For desktop it is essentially a replacement for QMainWindow but the way it is defined makes it suitable for hybrid mobile/touch development as well. I see that Ubuntu doesn't have it. Does SailFish define something similar?

Forget the part about having initialPage/pageStack included in the ApplicationWindow. There are many use cases where you want to move the pageStack somewhere else so it is anyway better only as an optional component for now.

Jens




More information about the Qt-components mailing list