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

List:       kde-devel
Subject:    Re: KConfig again - "resident in memory" format discussions
From:       Harri Porten <porten () tu-harburg ! de>
Date:       1999-05-16 20:54:32
[Download RAW message or body]

pbrown@redhat.com wrote:
> 
> On Sun, 16 May 1999, David Faure wrote:
> 
> >
> > This solution looks very good for .kderc, because it contains global settings
> > that most apps (via kdecore & kdeui) need.
> > But isn't it too much to put the config for ALL applications in XProperties ?
> > Well, it probably takes the same space in X that it would take in the process itself.
> > Is that right ? (i.e. won't apps copy the values locally ?)
> > (if not, how long is it for an app to get a value from X ? Memory saving is good
> > but we have to think about performance as well)
> > And is there a limitation in the memory used by XProperties ?
> 
> These are all valid points.  .kderc is a special beast, and it is really
> what has started this whole mess anyway.
> 
> Maybe we should store .kderc stuff as XProperties on the root window, and
> keep the app-specific stuff in a system a la scheme #1 (QCache/QMap).  I
> think it sounds like the best of both worlds.

You've got my vote for that approach.

Harri (who probably has to completely rewrite kppp since it stores all
its data in KConfig and reads it on thy fly ;)

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