RFC: KConfig XT (KDE 3.2)
bastian at kde.org
Sun Mar 16 17:17:43 GMT 2003
On Sunday 16 March 2003 17:07, Maks Orlovich wrote:
> > Instead of relying on the defaults that are hard-coded in the
> > application, rely on default configuration files being installed in
> > $KDEDIR. The technical changes required for this are very minimal, it is
> > mostly a change in policy.
> One thing that is kind of worrisome is the potential for an increase in
> number of keys KConfig may need to store in its maps (from the profiling I
> did, I doubt comments would matter much, since the KConfig time is
> dominated by the map storage -- with the parser being blindingly fast),
> inducing a startup time penalty. I doubt it'd be anything to worry about,
> since we've been making enough across-the-board improvements to probably
> cover it, but I am just wondering whether anyone has any good ideas on how
> to assess the effect of something like this w/o spending a ton of time
> implementing things, so we have the numbers in front of us...
> Other than that, I think this is a great plan and goal.
MAKE A BACKUP OF $KDEHOME/share/config FIRST!!
There, I said it.
Then copy your config files from $KDEHOME to $KDEDIR and measure the
Note that KConfig does not write settings to $KDEHOME that were already
defined under $KDEDIR, so after running an application you will most likely
end up with an empty (non-existing?) file in $KDEHOME.
It might also be interesting to add 3 lines of comments for every config key
and see what that does to parsing speed.
bastian at kde.org -=|[ SuSE, The Linux Desktop Experts ]|=- bastian at suse.com
More information about the kde-core-devel