RFC: KConfig XT (KDE 3.2)
nolden at kde.org
Sun Mar 16 15:50:35 GMT 2003
-----BEGIN PGP SIGNED MESSAGE-----
On Sunday 16 March 2003 11:06, Daniel Stone wrote:
> 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.
Did you ever have a look at kdenonbeta/kconfedit ? It works for everyone just
fine if you know what you're doing and it doesn't even have a desktop entry
that makes it show up in the menu :-)
It's a *lot* easier to use if you want to modify the settings in config files
because it prevents typos in many places where you change something because
it uses combo boxes for values that are easy to detect (like true/false)
Other than that it just works like using vi.
We're not a company, we just produce better code at less costs.
nolden at kde.org
The K Desktop Environment The KDevelop Project
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
-----END PGP SIGNATURE-----
More information about the kde-core-devel