Elektra backend for KDE

[Avi Alkalay]

Thomas, how far is this new API from being accepted in the official source ?

As a side note, on Elektra there are no config files. So maybe this methods
should be renamed to something like retrieveConfigResource() and
saveConfigResource().
A filename can be a configuration root, etc, so we can use them the way they
are today anyway.

I'll have future concerns about Kiosk mode, and how to implement that on
Elektra. I already have some ideas for that, and we'll discuss it here.

Regards,
Avi

On 2/20/06, Thomas Braxton <brax108 at cox.net> wrote:
>
> On Monday 20 February 2006 05:32, Adriaan de Groot wrote:
> > On Mon, 20 Feb 2006, Avi Alkalay wrote:
> > > It is time to write an alternative Elektra (http://libelektra.org)
> > > backend to KDE, in place of the INI files, and I decided to start this
> > > work.
> >
> > Aaron Seigo recently did some work on LDAP backends (or was it Samba
> > backends? - Something different anyway), check his blog
> > (aseigo.blogspot.com) for some musings about that.
> >
> > > - Is KConfig 100% backend-independent ?
> >
> > Less than one might hope, was what he found.
> >
> > [ade]
>
> You can find it at branches/work/kde4/playground/libs/kconfig/
> It doesn't work yet, but I'm planning on committing today the last bits
> that
> should make it mostly compatible with current KConfig.
> With the new api there are only 2 functions that need to be implemented in
> the
> backend:
> virtual bool parseConfigFile(const QString& filename,
>                                             KEntryMap& pWriteBackMap,
>                                             bool bGlobal, bool bDefault) =
> 0;
> virtual bool writeConfigFile(const QString& filename, KEntryMap& entryMap,
>                                           bool bGlobal, bool bMerge) = 0;
>
> Thomas
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20060220/e8d2bae3/attachment.htm>