Registry editor

[Ralf Nolden]

On Saturday 27 April 2002 07:15, Kevin Puetz wrote:

I would keep the name but I would definetly *not* install a .desktop file for 
that program in the K menu :) as well as *not* making it a kcontrol module 
(though, can it be used as root over password questioning and editing the 
base configuration files plus add config options which have no entry ?)

I think this tool would help people who set up large installations a lot. If 
you're a network admin and you know what you're doing, this would make your 
life *much* easier than using a demo user and configure all those 
applications until you have a setup that you think should be the default for 
all your users. So, I would like to have it and extend it :))  
(comes up the question: how do we add comments into the rc files for all the 
options so that you know what you're changing with which value when you're 
using the regedit program to change settings ?)

Ralf
> Zack Rusin wrote:
> > Hi,
> >
> > please no punching, spitting or biting. Yesterday, I found myself going
>
> /me hisses, you didn't ban that :-)
>
> > ...
> > Xdefaults, and ability to export and import configurations but someone
> > would actually have to find a need for it, because it already does what
> > I personally wanted. Let me know what you think. Oh, and of course a
> > mandatory "how does it look like" thingy:
> > http://vortex.bd.psu.edu/~mus11/kregedit.png
>
> The import and export functionality could be nice. Even though it doesn't
> add any real functionality over copying the rc files, for the average user
> I bet it would be less scary then messing around in files that they don't
> know much about, it could also hook in with something along the lines of
> kconf_update to properly merge prefs into apps instead of wholly replacing
> them. That would be a fair bit of work though, to come up with a good way
> for apps to tell it what needed to be done.
>
> For it's main purpose I don't see a lot of point, since it would just
> encourage options with no entry in the app GUI for them (and those are bad,
> since they're hard to find). There are almost never any of them that aren't
> for developmental/obsolete features that are either going away soon, or
> about to get a GUI pref.
>
> Oh, and I'd rename it, though I'm not sure to what. It's not the registry
> here, so the name kregedit doesn't really fit :-) Maybe kconfedit or
> something.

-- 
We're not a company, we just produce better code at less costs.
--------------------------------------------------------------------
Ralf Nolden
nolden at kde.org

The K Desktop Environment       The KDevelop Project
http://www.kde.org              http://www.kdevelop.org