----- Original Message ----- > From: Peter Kuemmel <[email protected]> > To: Thomas McGuire <[email protected]>; [email protected] >> No one sane would use an unmaintained library, which Qt4 will be once Qt5 >> is >> there. >> People will not use Qt4 in these cases, they will just use an entirely >> different library. >> >> And frankly, I don't buy the argument that everyone will use QML in the > >> future. Nokia is focused on QML and mobile use cases right now, so they >> probably see it as important. Touch interfaces will indeed be much more >> important in the future, especially with the advance of tablets, still >> there > > And there is still no mainstream device which uses Qt (only some > "beta" quality MeeGo tablets). So QML is a Nokia/Symbian only story, > and in some years there are only low-end phones with Symbian and smartphones > with Windows. Maybe then QML is not interesting any more to Nokia and is > dropped.
When talking about Mobile, yes. QML to my understanding is used quite a bit for KDE4, especially in Plasma. I could be wrong though. Though, of course, while Nokia may be pursuing WP7 while Elop is in charge, there is nothing in the agreement from preventing them from moving to Android or back to Meego once he leaves. (Some of his lieutenants might..but that's a different issue.) So don't count on Nokia being WP7 only, especially with the abysmal adoption of WP7 that is out there - which isn't going to improve. Whoever replaces Elop would be suicidal not to move away from WP7 and to MeeGo or Android. (Elop has too much interesting in Microsoft succeeding to do that, and should be fired for conflict of interest alone; but that's diverting from the discussion.) >> will always be traditional widget-based applications, and I think a huge >> number of Qt developers are either ignoring or underestimating their >> importance. > >> I have used QML in embedded touch-based projects and I think it is a >> really >> nice fit for them, and I enjoy working with QML. However, I don't think >> QML is >> a good fit for traditional applications. >> Are you porting QtCreator to QML? If not, why not? > > Without fully supporting QML for desktop applications, there always will be > widget-based apps. The best way to promote QML would have been to provide > great desktop QML elements, but Nokia only drops widgets and thinks this > is the best way to convince desktop-app developers. Even with full support for QML for desktop applications there will still be a need for QWidget/QGraphicsWidget based applications. QML doesn't meet the needs of certain functionalities - like drawing to the widget pixel by pixel; nor is that really a good use-case for QML either - since those applications typically need to be high performing too (more performant than JS would allow), and you typically need to be accessing data structures that are not easily transferred to a JS environment (since JS has no concept of byte alignment, etc.) >> There will be many people still wanting to develop widget-based >> applications. >> With people talking about deprecating everything widget-related and moving >> the >> QML interpreter to QtCore, I fear the widget part of Qt is being >> neglected. > > Isn't desktop support still a creative Friday project? ;) Desktop and Embedded are the two primary uses of Qt. Between KDE and the extensive embedding of Qt in all kinds of everyday appliances they are probably pretty equal. Mobile has no where near the same foot print. Ben > _______________________________________________ Qt5-feedback mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback
