RFC: KConfig XT (KDE 3.2)

Daniel Stone dstone at trinity.unimelb.edu.au
Sun Mar 16 10:06:48 GMT 2003

On Sun, Mar 16, 2003 at 10:42:37AM +0100, Simon Hausmann scrawled:
> On Sun, Mar 16, 2003 at 08:35:42PM +1100, Daniel Stone wrote:
> > On Sun, Mar 16, 2003 at 10:26:49AM +0100, Simon Hausmann scrawled:
> > > Where exactly do you see an attempt of unifying data, of
> > > centralizing it to one 'registry' file, of preventing you from
> > > continuing to edit your config file by hand?
> > 
> > KConfEdit.
> Then I think you misunderstood. Or I did. I thought of KConfEdit as
> a gui frontend to the human-readable meta-data and default values in
> the text config files as Waldo described. I don't see how that
> prevents you from doing things as you did before, I don't see how it
> breaks any sort of backward compatibility in the way config files
> were treated / editable. Do you?

I think the idea of a single, unified GUI frontend to human-readable
metadata (i.e. config files) is wrong, evil, bad, and punishable by
fecaljapan. I think the default values idea is great, but not the

Please, let's not go down this path.

Daniel Stone                                     <dstone at trinity.unimelb.edu.au>
Developer, Trinity College, University of Melbourne
-------------- 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/20030316/7a37722b/attachment.sig>

More information about the kde-core-devel mailing list