Hi,

> I think I have a solution to the settings problem.
> >
> > I'm sure we can add some stuff to LibCompizConfig-python-bindings to
> > allow LibCompizUtil to work. The idea is :
> >
> > Use LibCompizConfig to store settings offline, but in the directories
> > that the GConf and INI plugins store thier stuff. Then when compiz is
> > opened, we just read the settings using special 'Compiz is online'
> > plugins. That way, we don't need to read the metadata all the time as
> > the plugin load order will will be stored in the INI, GConf and KConf
> > files. Also, we will store the plugin list in a separate file too.
> > That way, we only need to parse the metadata on the time when CWS or
> > CCSM loads.
> >
> > This is just an idea. Please tell me the flaws. Thanks
> >   
> I think this is basically the same as my idea, I am
> waiting to hear the flaws myself.
> 
In short:
- No offline support
- Compiz doesn't parse the full metadata when it starts, only defaults and restrictions.
- When plugin metadata is requested over dbus, it's parsed on-the-fly, so there will be no performance advantage. Given that, using dbus will only increase overhead without adding gain.

Regards,

Danny