[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: RFC: KConfig changes for 3.0
From:       Martijn Klingens <mklingens () yahoo ! com>
Date:       2001-07-25 14:46:28
[Download RAW message or body]

On Wednesday 25 July 2001 16:02, Simon Hausmann wrote:
> On Wed, Jul 25, 2001 at 03:19:12PM +0200, Martijn Klingens wrote:
> > On Wednesday 25 July 2001 14:48, Simon Hausmann wrote:
> > > Ohh, right. I see your point now. Hm hm. There's one disadvantage with
> > > always writing out configuration values: They get written into the
> > > local config and if you do that for each and every entry you
> > >
> > >  a) get full blown config files in the user directory, containing
> > > redundant information
> > >
> > >  b) loose the ability for a system administrator to change global
> > > values, because the global changes never get applied to the apps as for
> > > each field there is an entry in the local file.
> >
> > Well... We have both these problems already, as soon as you change some
> > settings most apps write _all_ settings and not just the changed
> > settings. This is current tense, this is _now_ ;-)
>
> But that's after the user decided to customize the configuration, it's not
> done by default.

Well... not exactly. If I change my JavaScript settings I do not want Konq to 
to automatically hardcode the proxy settings as well. Then the sysadmin 
cannot change the proxy config either.

What is needed is a 'default' _per setting_ instead of _per app_. This is all 
of course just IMO , my 2 cents and bla bla blah...

Martijn

[prev in list] [next in list] [prev in thread] [next in thread]