RonnyPfannschmidt wrote:
>
> On 10 Okt., 15:27, Rodrigo Ferreira de Souza <[EMAIL PROTECTED]>
> wrote:
>
>> the third characteristic will be the dbus things, ok?
>>
> yeah, i'll use dbus signals for tracking changes to options (each
> change will notify all clients)
>
>
With dbus signal
On 10 Okt., 15:27, Rodrigo Ferreira de Souza <[EMAIL PROTECTED]>
wrote:
> the third characteristic will be the dbus things, ok?
yeah, i'll use dbus signals for tracking changes to options (each
change will notify all clients)
>
> On 10/10/2008 10:24, RonnyPfannschmidt wrote:
>
> > Hi,
>
> > sin
the third characteristic will be the dbus things, ok?
On 10/10/2008 10:24, RonnyPfannschmidt wrote:
> Hi,
>
> since gconf is a mess thats pretty unportable im proposing a simple
> dbus based store (which may use json/xml/other shit as storage
> backend)
>
> The basic characteristics will be:
>
>
Hi,
since gconf is a mess thats pretty unportable im proposing a simple
dbus based store (which may use json/xml/other shit as storage
backend)
The basic characteristics will be:
1. config paths will be abstracted via object paths
2. the properties interface will be used for local key-value par
