On Friday 09 September 2011 06:40:52 BRM wrote: > 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.)
QWidget != (Q)Painter. Very important difference. > 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. The footprint talk is mostly pointless given there is no real way to publicly measure it. The only thing somewhat certain is that desktop and mobile(/embedded) userbases are in the millions, which kind-of makes the point of (not so) primary uses fairly moot. Best regards, Attila _______________________________________________ Qt5-feedback mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback
