kdeui splitup (widgets)

David Faure faure at kde.org
Fri May 4 08:17:32 UTC 2012


On Thursday 03 May 2012 23:19:38 John Layt wrote:
> Speaking of K4Support, how is that planned to be done?

See kdelibs/staging/kde4support, it already exists :-)

> Will we be renaming 
> classes, giving them a different Namespace / library, or using different
> names in KF5?  

At least until now, this was about entire classes that disappeared (e.g. 
KTemporaryFile moved there, because the new recommended class is 
QTemporaryFile). No name clash -> no renaming necessary.

> How many of the old classes will we have in there, i.e.
> would we have K4DatePicker in K4Support and KDatePicker in KF5?

You're thinking of a different case, where we want to reuse the class name and 
yet change its whole API. This will require a '4' in the class name indeed.
I prefer that rather than a namespace. E.g. searching on lxr.kde.org is only 
possible with a different classname, while using a namespace would just put 
them all into the same search.

> I'd think we would need all the locale and date classes in K4Support?

Can't really answer that before seeing what the porting effort from the old to 
the new locale stuff will be. If it's not much, then maybe you want to break SC 
rather than offer the complete whole stack. Otherwise, yes, this might be an 
option.

-- 
David Faure, faure at kde.org, http://www.davidfaure.fr
Sponsored by Nokia to work on KDE, incl. KDE Frameworks 5



More information about the Kde-frameworks-devel mailing list