KDE4 Libs components

[Aaron J. Seigo]

On Sunday 05 March 2006 02:30, Olivier Goffart wrote:
>  What we should do IMO is doing like what Qt does: In the same library,
>  separate the source in several directories (like qtcore/kernel ,
>  qtcore/global , qtcore/tools)

this would certainly be at least one step forward =)

as a concrete example:

i'd like to see kconfig classes all bundled up in one directory so it's clear 
just by looking at the source tree what constitutes the "kconfig technology". 
it would include kconfig itself, backends that we provide (some may be 
optional plugins), kconfigskeleton and the kconfigxt stuff. unit tests and 
documentation would also be found in there

if it were ever decided to create a separate library out of this, it would be 
a bit easier to do so at that point. (including for 3rd parties outside of 
kde)

-- 
Aaron J. Seigo
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

Full time KDE developer sponsored by Trolltech (http://www.trolltech.com)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20060306/456a6ca1/attachment.sig>