The QT classes for this purpose can also be implemented on top of Elektra's methods. Check this diagram: <a href="http://www.libelektra.org/presentation/img46.html" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)"> http://www.libelektra.org/presentation/img46.html </a> Elektra was written in pure C (but it is object oriented in design) and does not depend on any other libraries. This guarantees cross platform availability (Elektra can be used on any other OS, and on Windows its keys are mapped and stored on WinReg keys) and also very simple programs (as /sbin/init) can link to Elektra. Check this: <a href="http://www.libelektra.org/presentation/img5.html" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://www.libelektra.org/presentation/img5.html</a> Regards, Avi <div>On 3/28/07, Thiago Macieira <<a href="mailto:thiago@kde.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">thiago@kde.org</a>> wrote:<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> Avi Alkalay wrote: >So KConfig and GConf will have (actually have already) an Elektra > backend and there is no need to change applications. Avi, In this case, Marius was thinking of sharing that data down to the toolkit level. KConfig, for instance, is a KDE class, so it cannot be used from Qt. -- Thiago Macieira - thiago (AT) <a href="http://macieira.info" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)"> macieira.info</a> - thiago (AT) <a href="http://kde.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">kde.org </a>   PGP/GPG: 0x6EF45358; fingerprint:   E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358</blockquote></div> -- <a href="http://avi.alkalay.net/blog" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)"> http://avi.alkalay.net/blog</a>