From kde-core-devel Fri Aug 01 09:49:39 2003 From: Waldo Bastian Date: Fri, 01 Aug 2003 09:49:39 +0000 To: kde-core-devel Subject: Re: KPrefs status X-MARC-Message: https://marc.info/?l=kde-core-devel&m=105973152930164 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Friday 01 August 2003 01:29, Oswald Buddenhagen wrote: > On Fri, Aug 01, 2003 at 12:45:14AM +0200, Cornelius Schumacher wrote: > > - I added cfgc, the configuration compiler, which creates KPrefs > > subclasses from configuration-description files. Oh wow, excellent. You beat me to it. > > It uses an XML description > > i don't like that part. kconfig xt will solve this differently - and i'd > prefer to have only one config description language (i.e., formalized > config comments) in kdelibs. you could use your experience with this > language to help design the new kconfig stuff, though. > > > and convert this into C++ code. > > fwiw, it might be worth checking, which things (particularily type > checking, enum conversions, etc.) considered for kconfig would be > duplicated in kprefs - i'd prefer not to have any, so it would be strictly > speaking better to implement (or at least design exactly) kconfig xt first. This basically *IS* kconfig xt, this *IS* the new kconfig stuff. The naming of the various classes needs to be a bit streamlined, but basically this is it. The syntax of the config description language is a good point that can probably use some dicussion in particular whether to use a stand-alone XML format or whether to overload the existing config-format. The nice part about having a formal description is that it is always possible to generate one format from the other. Cheers, Waldo - -- bastian@kde.org -=|[ SuSE, The Linux Desktop Experts ]|=- bastian@suse.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE/KjezN4pvrENfboIRAnl0AJ4qz/xH0K+n0yhUL0g1wRSRdBpwXACePhqU QXvO9ivLzwyoztxPnYP4mck= =9GgP -----END PGP SIGNATURE-----