On Saturday 29 December 2012 02:47:13 Friedrich W. H. Kossebau wrote: > Will kde-frameworks be Qt5-only, so not need to support both Qt4 and Qt5 > and thus to use module-less Qt includes?
At some point it will be, yes. Right now it supports both, so a bunch of QtGui/ was removed in #include statements. > So will projects which refer to the Kdelibs Coding Style need to > add an exception to their rules for the includes, if they want to prepare > for Qt5? > Or does the rule need adaption? Well, for frameworks that intend to be "as close to Qt as possible" they should do the same (for the convenience of developers who don't use qmake/cmake but set up their project configuration in their IDE by hand, for instance Visual Studio). This means re-adding the missing QtWidgets/ in public headers once Qt5 is required in KF5. But for sure this doesn't apply to "projects which refer to the kdelibs coding style". There's no good reason for apps to do this, only porting trouble comes from that. -- David Faure, [email protected], http://www.davidfaure.fr Working on KDE, in particular KDE Frameworks 5
