-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Friday 09 January 2004 09:06, Charles de Miramon wrote:
> I think the idea of isolating the kcm code in a ad hoc directory for each
> application is a good one. The more structured the cvs is, the easier it is
> to somebody new to the code to find his way. 

agreed, but i'm wondering at what, if any, added complexity this will create 
in managing/coding kcms that share code / headers with the programs they are 
associated with. it also makes moving apps around more difficult in the 
future as they are framented into several pieces. personally, i'd be more 
inclined to see a structure like:

<module>/<application-name>/kcm

e.g.:

kdebase/kwin/kcm/
kdemultimedia/kmix/kcm/

this would allow kcms to be found easily with a quick `tree -ifd | grep kcm` 
while preserving the relationships between the kcms and their respective 
applications.

i personally find kdebase/kcontrol/kicker to be less intuitive than 
kdebase/kicker/kcm/ would be =)

- -- 
Aaron J. Seigo
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43
while (!horse()); cart();
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux)

iD8DBQE//xDo1rcusafx20MRAm/pAJ9JaDCfRjtuioq9GoPkYacBLD1GcACfYFrg
ewNz6F1WKKIj8/m+19LJK3Q=
=0m8j
-----END PGP SIGNATURE-----
_______________________________________________
kde-usability mailing list
kde-usability@kde.org
https://mail.kde.org/mailman/listinfo/kde-usability