RFC: KConfig XT (KDE 3.2)
neil at qualityassistant.com
Sun Mar 16 16:36:32 GMT 2003
-----BEGIN PGP SIGNED MESSAGE-----
On Sunday March 16, 2003 12:36, Daniel Stone wrote:
> On Sat, Mar 15, 2003 at 04:38:48PM +0100, Waldo Bastian scrawled:
> > Goals
> > =====
> > * Have the default value for config entries defined in 1 place.
> > Currently it is not uncommon to have them defined in three places:
> > 1) In the application that reads the setting in order to use it
> > 2) In the settings dialog when reading the setting
> > 3) In the settings dialog when selecting "Use defaults".
> > * Provide type-information about config entries to facilate
> > "KConfEdit" like tools. Ideally type-information also includes
> > range-information.
> Bob the Angry flower says: "WRONG WRONG WRONG WRONG WHERE DID YOU LEARN
> THAT WRONG!!".
> Dudes, having a registry is *bad*. You know, we already have KConfEdit -
> KWrite, vim, KVim, whatever.
> I like the "defaults in one place" thing. The registry idea I don't
> like, and IMHO that entire path is wrong, bad, evil, fucked-up and bad.
If by "registry" you mean "an app that reads many KDE text files and
presents them for unified editing," we already have at least two
registries in KDE: File Associations and K Menu Editor.
I see no harm in a System Defaults Editor intended for and aimed only at
system administrators, as long as it is not used as an replacement for and
an excuse to remove KControl functionality.
Neil Stevens - neil at qualityassistant.com
"The shepherd drives the wolf from the sheep's throat, for which the
sheep thanks the shepherd as a liberator, while the wolf denounces him
for the same act as the destroyer of liberty." -- Abraham Lincoln
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
-----END PGP SIGNATURE-----
More information about the kde-core-devel