On Fri, May 8, 2015 at 3:53 PM, Frederik Gladhorn <[email protected]> wrote: > On Friday, May 08, 2015 02:44:53 PM André Somers wrote: >> Frederik Gladhorn schreef op 8-5-2015 om 14:39: >> > Hi, >> > >> > I think the dust has settled quite a bit and the declarative module is >> > becoming better by the day. We have seen it evolve and the new Java Script >> > engine is running smoothly (and actively worked on, sadly it will have one >> > known crasher in the 5.5 beta release which has been fixed in the mean >> > time, so it should be good for everyone with the 5.5 RC). >> > >> > One question is if there is any reason to maintain Qt Quick 1 in the >> > future. It adds burden on maintenance, needs to be patched regularly to >> > move with changes in qtbase etc. >> > >> > Since KDE moved over the Plasma desktop to Qt Quick 2 (on which I'm >> > writing >> > this email), I feel confident that the time has come to move everyone >> > over. >> > For the no opengl acceleration use case, we provide the Qt Quick 2D >> > Renderer as backend. >> > (https://blog.qt.io/blog/2015/01/22/introducing-the-qt-quick-2d-renderer/ >> > ) >> > >> > In short, is there any reason not to remove Qt Quick 1 from Qt 5.6? >> >> Yes, there are reasons. Qt Quick 1 is the entrancepoint to moving your >> Qt 4 Application to Qt 5. > > > Absolutely. But you can migrate to Qt 5.5 which has Qt Quick 1 support and > later to 5.6 and onwards.
Not if you're using the Qt that comes with your Linux distribution (not sure how common that is, i know i am). Cheers, Albert _______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
