Mihail Naydenov wrote: > There is nothing in QML by design that prevents it for using it for > desktop. > > And I mean core QML, not the implemented widgets and Items so far, which > are biased towards the mobile clearly.
Right. QML the language might be useful on desktop, but existing components in QtQuick are biased towards mobile, not desktop. Those existing components have influenced the whole framework though of course. Imagine people sitting around last year deciding whether to put feature X (useful for mobile) or feature Y (useful for desktop) into the framework. The design and implementation of the framework is influenced by the code that uses it. The move to QML being the first port-of-call for implementing new stuff on desktop is happening fast (Qt5 is scheduled for next year). I'm wondering if there needs to be re-design work with that in mind, or is the current design sufficient and flexible enough. I haven't tried the scene graph stuff or looked at the code, so I don't know the answer to that question and I don't know if work on that is already underway. If the answer is that the declarative framework is already flexible enough and doesn't make undue compromises baised against towards mobile and can handle the features people want from a desktop framework, then I'd be interested to know that. If not, we can start to list what's hard/missing. Thanks, Steve. _______________________________________________ Qt5-feedback mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback
