On Wednesday, February 16, 2011, David Jarvie wrote: > There would be a major benefit from splitting KConfig etc out of kdecore: > Qt developers could use the stripped down library confident in the > knowledge that they could use any class in it without having to worry > about whether they might accidentally introduce a dependence on platformy > stuff.
it just introduces a new complexity: which of these bazillion libraries do i use and what's the overhead of having so many of them? (not to mention the complications for us actually making that library). QtCore isn't a bazillion libraries either. what i do agree with, however, is that kdecore (as example) does need: * to be properly documented from a higher level than it is now * should have KDE platform features separated out from app dev framework features which begs the question: "is KConfig (as ane exmple) platform or app dev"? fun conversations to be had and digging to be done :) -- Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 KDE core developer sponsored by Qt Development Frameworks
signature.asc
Description: This is a digitally signed message part.
