Elektra backend for KDE
thiago at kde.org
Tue Feb 21 18:13:24 GMT 2006
Avi Alkalay wrote:
>I don't know exactly what this means, since I don't know what KDEDIR etc
KDEDIR is a deprecated variable. It points to the KDE's installation
KDEHOME is where the user's settings are stored. By default, this is
$HOME/.kde. The configuration is stored there too, but this is not
necessary if the backend uses in its own storage.
KDEDIRS, however, is a lot more complicated. It lists the many different
directories that should be searched for configuration. It defaults to the
KDE installation prefix. The storage backend MUST allow loading the
configuration from different trees and merge them in the order they were
declared in KDEDIRS, respecting the Immutable setting.
This applies to configuration as well as menus and icons (though those two
are supplanted by XDG_DATA_DIRS). Conceivably, the storage backend could
use XDG_DATA_DIRS too and we'd be done with KDEDIRS, but this has to be
To add insult to injury, this setting must be done per-application,
unless /etc/kderc makes the list constant (Kiosk mode). This means that,
if there is a daemon that handles all requests, this daemon must be told
the path list that each application expects its settings to be loaded
>I'm ready to write the backend, but right now I still don't know where
>to start write it. If it is in the playground code, or in the
Since this is KDE4 code, use branches/work/kde4/playground/libs.
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
PGP/GPG: 0x6EF45358; fingerprint:
E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358
1. On frumscafte, hwonne time_t wæs náht, se scieppend þone circolwyrde
wundorcræftlíge cennede and seo eorðe wæs idel and hit wæs gód.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: not available
More information about the kde-core-devel