On Sunday, December 16, 2012 21:12:18 Bache-Wiig Jens wrote: > > But if you are writing a 100% declarative UI you'd probably wish to > > avoid linking against widgets. So I guess you're saying regular old > > QActions should be exposed just for putting a declarative UI onto > > legacy apps, and also there should be a new QQuick action, which is an > > unrelated class? > > Yes. That is exactly what I am proposing. We will support the parts of > QAction that we can for legacy and portability, but we will introduce a new > QQuickAction class for QML. You can use both with QML but you can only > (directly) use QAction with widgets.
Please not QQuickAction, but QGuiAction. Design it to be UI independent, not tied to a UI implementation (Qt Quick). Thanks, -- Stephen Kelly <[email protected]> | Software Engineer KDAB (Deutschland) GmbH & Co.KG, a KDAB Group Company www.kdab.com || Germany +49-30-521325470 || Sweden (HQ) +46-563-540090 KDAB - Qt Experts - Platform-Independent Software Solutions
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
