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

List:       kde-devel
Subject:    Re: Gconf2
From:       Michael Pyne <pynm0001 () comcast ! net>
Date:       2003-08-13 7:19:12
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> The problem though at the moment is it's still all stored in a whole bunch
> of textfiles in the $HOME/.kde directory. A registry style system would be
> heaps faster, and more robust. Maybe gconf2 isn't the solution, but
> something similiar would be.

If you mean some sort of binary/database solution, I am certain it would be 
faster, but I am not sure it would necessarily be more robust.  On the other 
hand, you lose the easy accessibility of the stored options in case your 
registry editor were to be unavailable for any reason.

And if you're talking about a text-based registry solution, then I doubt that 
it would be either faster or more robust. :P

In this case, faster isn't even necessarily better anyways.  An application 
that had a lot of settings to load (Mozilla would be a good example if it 
were for KDE) could enter a link to the actual binary settings into the 
KConfig entry, and read from there.  Other than that, it's pretty much a 
two-time deal (once to read on startup, once to save on shutdown), and I am 
sure that the KDE developers have much better things to optimize.

 - Michael Pyne
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE/OeZwqjQYp5Omm0oRAuEoAJ9u7o3pXFoI/K1YyjmRGoVrvFWZcQCfXkTu
0PauuYen+t/HxS2FqgXdmzw=
=jpB8
-----END PGP SIGNATURE-----
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

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