On Tuesday 02 July 2013 21:37:03 Alexander Neundorf wrote: > Another question: the libraries as they are now in tier1/ and staging/ are > partly really tiny. kinterprocesswindowing consists of 2 cpp files, > kplotting is 4 cpp files. > > Isn't that a bit too fine grained ?
As Sune pointed out we might want to reevaluate some of the smallest ones later on indeed. > E.g. kplotting and kwidgets have the same dependencies. I wouldn't mind > having kplotting as part of kwidgets. This one is IMO not the best example though. Yes they have similar dependencies, but I'd rather keep kplotting separate for two reasons: * It has a clearly identified aim while to be honest KWidgets still looks like a dumping groung (although a much smaller one than kdeui); * There's other plotting engines available for Qt, so puts it on the same foot for third parties use (they can compare kplotting vs qwt for instance, they won't even put kwidgets in the picture). In other words: some of the lines for those splits are not purely based on dependencies, there's also a product definition aspect (and how each framework inserts itself in the wider Qt ecosystem). Regards. -- Kévin Ottens, http://ervin.ipsquad.net Sponsored by BlueSystems and KDAB to work on KDE Frameworks
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
