[Compcomm] My ideas (for the record)

[Danny Baumann]

Hi,

> >>> I admit to not having researched grahpical Compiz configuration tools 
> >>> extensively, but at the time I started with compiz-quinnstorm, the most 
> >>> graphical tool available was gconf-editor. And that was confusingly 
> >>> divided into settings for "all screens" versus "screen0". There was no 
> >>> plugin dependency resolution.
> >>>   
> >>>       
> >> You can still use this as a fallback in compiz, but it is not
> >> the only means.
> >>
> >> I think it is very important to have a fallback because there
> >> have been a few notible cases where people are left without
> >> without features because of a bug in the settings manager.

In case you didn't notice yet: The CCS gconf backend directly
edits /apps/compiz, so you can of course also use gconf-editor if you're
using ccs.

> >> Editing libbs config files is not user-friendly.

Huh? How does editing the ini files produced by libccs (one file with
sections) differ from editing ini files produced by the ini plugin
(multiple files without sections) in terms of user-friendliness?

> > An interesting assertion, and you may be right. Though I have edited 
> > libbs and libcompizconfig files with a text editor in the past to work 
> > around some limitations of the configuration tool (such as setting the 
> > same keybinding to more than one action), I imagine it would be more 
> > difficult to unintentionally break something with gconf-editor.
> >   
> 
> Thats for sure...
> 
> I have tried many times to 'break' (read uninstall) gconf
> schemas and its virtually impossible.
> 
> If you slip up and get 3_'s instead of 4 in a libbs config file
> then you are in trouble.

Can you elaborate more on that? Obviously it's easier to break an ini file than to break gconf, but I don't see the reason why it should be easier to break CCS' ini files than to break the ini files of the ini plugin. 

Regards,

Danny