On Saturday 26 April 2014 11:57:24 Christoph Feck wrote: > > [...] The reason behind is that the KF5/Qt5 porting creates > > quite disruptive changes (QtQuick1 to QtQuick2; port away from > > QGraphicsScene). Thus any new feature merges from the Qt4 > > branches > > > are very painfull. > > Note that Qt5 includes both QtQuick1 as well as QGraphicsScene. In > other words, an initial KF5 port should not need disruptive changes. > > Please do not rush to remove all Qt4/KDE4Support code, because that > may cause breakage that could lead to bad publicity. Like we did with > removing dependency on Qt3Support, that can come slowly and gradually > in the coming years.
Sure, an initial port even for QtQuick1 and QGraphicsScene is not hard and can be done/should be done this way. However, given the expected timeframe until a KF5-based applications release will happen, there is enough time to complete porting away from them and also guarantee a decent stability of those ports. With that in mind it is probably a very individual decision for every application, by judging where the main benefit for the appliciation is: early porting to new techniques like QtQuick2 or working on (existing/new) features. Going the path of using new techniques yet make it hard to also add features to the Qt4 branches. Cheers, Andreas
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
