Re: [Tracker] about Tracker Preferences

[Martyn Russell <martyn imendio com>]

Ivan Frade wrote:
> Hi Tshepang, all

Hi

> El jue, 22-05-2008 a las 12:21 +0200, ext Tshepang Lekhonkhobe escribiÃ:
> > Hi,
> >
> > Is there any reason why TP is using its own config library instead of
> > src/libtracker-common/tracker-config.[ch] or does it just need some
> > work?

Actually, both works were added to libtracker-common at the same time.
> From what I can see, we only need to use one of them (but that was last
time I looked, I am not totally sure on this).

>  At some point, we must put some order in the configuration options. We
> must choose what options are available, which ones requires to restart
> the daemon, and which ones can change in runtime.
>
>  My idea is that trackerd should load the options from the config file,
> and write the options when it finish (for example). In the middle, TP
> can read/write the values of the options using a DBus Interface. The
> daemon could also throw a signal saying "Some option have changed!" and
> TP can ask again the values of the options.

I have thought this for some time. We already have a separate API for
the daemon to set certain configuration options. It would be simpler to
just put the TrackerConfig object on the bus and with the "notify"
signal GObject supports, changes are automatically signalled to those
listening.

We would simply have to decide which options to make publicly available
and write the .xml file for the interface.

>  Definetly, TP shouldn't read/write directly the cfg file.

We should be doing this all in one place really. Another job on the list
to do :)

-- 
Regards,
Martyn