MCS design proposal
jannis at xfce.org
Mon Jul 9 23:12:53 CEST 2007
Am Mon, 9 Jul 2007 23:02:24 +0200
schrieb "Stephan Arts" <stephan at xfce.org>:
> On 7/9/07, Jannis Pohlmann <jannis at xfce.org> wrote:
> > Am Mon, 09 Jul 2007 22:41:58 +0200
> > schrieb Harold Aling <h.aling at home.nl>:
> > > What about including some specification file (xml?) and upon
> > > removal of that file, purge the settings from the store?
> > >
> > > Example: "/etc/xconf/xconf.d/xfwm4" which contains the
> > > configuration specification (and defaults) for xfwm4. Upon
> > > install, XConf sees the file, adds it to the store and upon
> > > deletion, XConf removes the entries from the store...
> > You're missing one of the points of this discussion. GConf has these
> > kind of specifications - the design we're talking about has not.
> > IMHO we should keep it lightweight and thus avoid stuff like this.
> Then how about adding a remove function to the API? Combined with the
> option to list all nodes, it is theoretically possible to clean up the
> settings by hand (or a shell-script).
Once there is a function for getting a list (or a tree) of
all properties this is a trivial task. But I don't think this should be
made part of the system.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 189 bytes
Desc: not available
More information about the Xfce4-dev