Hi, Beurk this thread is just about people ranting never tried to use QML or thought about using it as a real alternative or don't even let time for the technology to mature. I write down this date and we will see in 1-2 years when QML will spread a bit, when Qt Components will be mature and released. C++/QML lives very well together, you can almost do all your ugly hack in C++ that you have in your code. Custom painting -> custom items that you export so you can use them in QML.
4 years ago you guys ranted about QGraphicsView, it matured, it's stable (It has its flaws for sure) and now many people use it, work on it and have stuff based on it. N9 UI, Plasma, and many more. Half of this thread is FUD. Of course if you don't want to change any of your code and expect to get Qt5 for free, this is not going to happen like almost any of major upgrades. Now for the ease of the move QWidget was let as a separate library which is good. You can move to QML when you feel QML is ready for your project. And yes I make a desktop app on QML. On Mon, Oct 10, 2011 at 7:28 AM, Konstantin Tokarev <[email protected]> wrote: > > > 10.10.2011, 14:18, [email protected]: >> I would again like to stress that the widget stack is not going away in Qt 5 >> and as of this thread we also clarified that we will not force it on top of >> OpenGL. It will in fact stay there and be the correct and best solution for >> many project also in Qt 5. When it comes to desktop development, I want to >> make sure that people choose Qt Quick because they feel it benefits their >> project and not because they feel forced into using it. Anything else would >> be insane. > > BTW, currently folks who need WebKit 2 are actually forced to use QML because > no Qt/C++ API exists. This is bullshit based again on not checking out stuff. Dude, git clone WebKit trunk and look the h files are exported, the method public, and everything is there. What we promised is a good QML API but we let around the C++ (which is the one our QML plugin use also btw). By good API in QML I mean a property based one which in some cases is less convenient in C++ but *still there*. QWidget is there, it's not gonna move, your app can use it, it will not get major improvements, so you can start using QML and fix it if something is missing. > > -- > Regards, > Konstantin > _______________________________________________ > Qt5-feedback mailing list > [email protected] > http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback > -- Alexis Menard (darktears) Software Engineer INdT Recife Brazil _______________________________________________ Qt5-feedback mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback
