XfconfChannel support for plugins.

[Nick Schermer]

2008/10/14 Brian J. Tarricone <bjt23 at cornell.edu>:
> Nick Schermer wrote:
>> Yeah that's probably 99% of the plugins, so it would be nice for reading the
>> plugin settings, but for writing you still need to xfconf channel, with the
>> property_base if you write everything to a single channel.
>> So IMHO it's not convering enough of the problem.
>
> No, no, I guess I wasn't clear.  You don't expose *anything* relating to
> the details of config storage to the plugins themselves.  They don't
> know about xfconf or anything.

I did understand that, but IMHO a hashtable is not a friendly way of
storing/loading settings. Missing the _get_ and _set_ functions here
and I'm pretty sure nobody is going to use it if they have to convert
GValues.

> Or, maybe really the most flexible solution is for the panel to ONLY
> provide xfce_panel_plugin_get_unique_id(), and let the plugin do
> whatever the hell it wants with it, whether it's opening an XfceRc file,
> or linking directly to libxfconf and creating its own XfconfChannel, or
> something else.

We if the property_root idea is implemented in XfconfChannel, the
panel could provide xfce_panel_plugin_get_property_root() (or
something like that). Something similar as the
xfce_panel_plugin_save_location functions for XfceRc support.

Nick