I agree with all points you listed here. It would be great if some core Qt developers can provide more informations or let's say edification about this "all is QML" stuff. What does it improve - I mean *really* improve. Now it seems it's just less-doing another syntax for widgets. Maybe accelerated over GPU. But enforcing GPU acceleration blocks (as it was said) various virtualization tools etc.
Then imagine that we chose Qt as a GUI toolkit for our product using it with special language bindings (smoke, etc.) and those tools sometimes run over network (X11) from old solaris machine... OK, maybe I'm fearing some non-existing problems but definitely it needs more evangelization. Now I feel like "hey, QML works, it can paint button, throw away qwidgets, let's move all to qml..." On Oct 7, 2011 (Friday), at 2:27 PM, Till Oliver Knoll wrote: > A couple of months ago my impression was that QML will "live happily > in parallel" to QWidgets. They are implemented in a separate "module", > they link to their own required libraries, but that wouldn't concern > me at all as a QWidget desktop application programmer. I would still ... this is what I thought - it will stay forever and QML can be used for some "quick development" (still I cannot imagine myself that coding QML can be quick). cheers, petr P.S.: I don't mean this message as a rude or an un-polite scream... _______________________________________________ Qt5-feedback mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback
