On Tuesday 11 January 2011 03:24:48 you wrote: > I hinted at it there, but more clearly put the QtQuick Timer is GUI > oriented because it synchronizes with the animation timer. It "can" be > used GUI-less but, like the models in QtQuick as well, it is specifically > designed for use in GUI creation. The big-picture of using QML in non-UI > situations will involve not basing it off the Qt UI Creation Kit module.
Thanks for all the comments in the thread, it is a lot more clear now - the question arose primarily as the elements contain many (at least on a first glimpse seemingly) non-GUI related utility elements/classes. While it is perfectly clear what the original goal of QtQtuick is, I would like to keep as close as possible (but not closer than that :) ) to existing classes and documentation for obvious reasons of compatibility and ease of learning. I wonder if at some point (just theorizing) it would make sense to spin off the utility classes into a QtQuickCore or similar (implicitly included by 'regular' QtQuick), just like Qt itself has a separate QtCore and QtGui even though it is/was a primarily UI toolkit. Best regards, Attila Csipa _______________________________________________ Qt-qml mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt-qml
