[compiz] re-work option initialization

[Mike Dransfield]

Dennis Kasprzyk wrote:
> Additions to the CompOption struct:
> char * group/char * subgroup : Ability to group sets of options and to give 
> this sets a name.
>   

I think that subgroup (and probably group) are excessive
and they lead to the plugin writer designing the UI which
is not right.  From what I can see of the implementation in
beryl, plugin developers just put what they like here.

> char *hints : A semicolon separated list of string that inform the 
> configuration tool to handle this option in a special way. A string value 
> could have a hint "image" or "file" to inform the configuration tool to open 
> a file dialog when the user wants to set this option. We all could workout 
> here a set of hints, that all configuration tools would understand.
>   

Again, this is another one which is blank 99% of
the time and only actually applies to maybe 5
options overall.

Maybe it would be better to add CompOptionTypeImage
which could provide information about the image to
compiz (or even extend to file)?

I do not think that the internals of compiz should have
any more information than they need about the options.

> Additions to the plugin vTable:
> char* category: A plugin can define to belong to a category like "effects" 
> or "accessibility", so that a configuration tool can group plugins together. 
> We could workout possible categories later here.
>
>   

Again, this puts UI design in the hands of the programmer
one persons accessibility is another persons effects.

Couldn't you just maintain a list of each plugins options and
how to group them?  All of these requests just seem to be
making compiz hang onto some values for other applications.

I think in the long term, the autogenerated settings managers
will be replaced with hard coded user friendly ones, this will
leave all of these extra attributes with nowhere to go.