hey, I was also quite against qt5 at the beginning. But now, after porting of some apps, and using qt5 in real life - I find it pretty cool library set. And now, with kde frameworks it offers really great opportunity to make cool desktop.
remember - solid backend ;) cheers, petr On 05/09/14 19:17, Jerome Leclanche wrote: > Yes, it's certain we'll drop qt4 support once 0.8 is out. > > Paulo, thanks for working on this. The KWindowSystem port is really > cool and we've been talking about it for a while but nobody stepped up > to do it until now :) > Please keep in mind it won't make 0.8 however. But we should be > releasing that any time now. > J. Leclanche > > > 2014-09-05 18:53 GMT+02:00 PCMan <pcman...@gmail.com>: >> On Sat, Sep 6, 2014 at 12:22 AM, Paulo Lieuthier >> <paulolieuth...@gmail.com> wrote: >>> Hello developers and contributors, >>> >>> I'm porting LXQt to KWindowSystem, and it's lookg nice so far, even though >>> KWindowSystem is not 100% complete. I've ported lxqt-panel entirely, except >>> for the keyboard indicator and the system tray. >>> >>> I'll soon send a WIP PR to get comments and help. Now what I want to ask is >>> whether Qt4 will still need to be supported when the move to KWindowSystem >>> happens. If it is agreed to drop it, it'll make the work a little easier for >>> I'm trying to get rid of all xcb/Xlib calls. >>> >>> So, what do you guys think of it? >>> >>> Paulo Lieuthier >> My vote is for dropping Qt4 and supporting Qt5 only. with some exceptions: >> >> 1. qtxdg (this can still be very useful for most qt4 programs) >> 2. pcmanfm-qt (well, I'm willing to maintain that.) >> >> KDE 5 already moved to Qt5, so all new distros shipping KDE should have Qt5. >> Previously I suggest keep Qt4 because Qt5 is very buggy. >> However, we already found workarounds for all of the critical bugs. >> So now everything works as usual in Qt 5. >> Moreover, Qt developers are working on fixing the bugs I've reported. >> One of the most critical bug will be fixed before Qt 5.4. >> So basically LXQt can run on Qt5 without significant problems. >> Maintaining two code paths is time-consuming as this doubles the time >> of testing. >> I'd say Qt5 only. >> Others? >> >> ------------------------------------------------------------------------------ >> Slashdot TV. >> Video for Nerds. Stuff that matters. >> http://tv.slashdot.org/ >> _______________________________________________ >> Lxde-list mailing list >> Lxde-list@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/lxde-list > ------------------------------------------------------------------------------ > Slashdot TV. > Video for Nerds. Stuff that matters. > http://tv.slashdot.org/ > _______________________________________________ > Lxde-list mailing list > Lxde-list@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/lxde-list ------------------------------------------------------------------------------ Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ _______________________________________________ Lxde-list mailing list Lxde-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxde-list
