Moving KPrefs from libkdepim to kdelibs

[Ingo Klöcker]

On Tuesday 22 July 2003 14:10, Benjamin Meyer wrote:
> On Monday 21 July 2003 6:54 pm, Ingo Klöcker wrote:
> > On Monday 21 July 2003 18:26, Benjamin Meyer wrote:
> > > Please correct me if I am wrong (I haven't looked at KPref's code
> > > sense March) but KPrefs main reason for being was it set _one_
> > > place for the default values.  If I were to move all of my
> > > default values for an application to my applications global
> > > config and remove them all from the binary I could achieve the
> > > same result.  Any time I needed a entry I could just call
> > > config->readEntry("foo") without the default value because I knew
> > > that the default value was in the global list.
> >
> > Maybe I'm missing something but I don't think that this will work
> > for objects like KMail's accounts, transports, identities, and all
> > other config information which is available for multiple objects
> > because obviously the application's global config file can't
> > contain any default values for an uncountable number of accounts,
> > transports, identities, etc..
>
> I think you are confusing the applications global config with the
> kdeglobal config.  An applciation can not modify its global config,
> but it can modify the kdeglobal config.  Or put it this way: If you
> can't do it in the applications global config how do the kmail
> developers currently do it in the binary?  The user accounts etc are
> stored in their local configs, not the binary or global config.

I was talking about the following: We store the settings of the accounts 
in
[Account 1]
server=...
...

[Account 2]
server=...
...

I don't see how you want to move the default values for the accounts to 
the application's global config and remove them all from the binary in 
order to achieve the same result as with KPrefs.

Furthermore there are certain default values, e. g. the default email 
address, which are generated dynamically. It's impossible to put this 
into a global config file but it's perfectly alright to generate these 
default values in KPrefs.

Regards,
Ingo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 192 bytes
Desc: signature
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20030724/a99dc5ed/attachment.sig>