[compiz] removing string restrictions

[Quinn Storm]

With an easy metadata setup, this sounds like a very good idea in my opinion.  
Restricted string options are a pain especially for i18n, as obviously the 
restricted values are in C/en_US but we need to display to the end user the 
proper i18n'd value, which would be far easier in this method, as the value 
in this method is the int and the text is merely pretty-printing.  (it 
seriously cleans up the API to any relevant settings library such as libccs)

On Thursday 10 May 2007 15:24:02 David Reveman wrote:
> We've previously discussed if we should add some sort of selection
> option type and not use string options and string restrictions for that
> purpose.
>
> I don't think we need a new option type for this. The integer type
> should do just fine. The attached patch changes the blur plugin's filter
> option from string to integer type and adds the relevant metadata. I
> suggest that we change all existing options that use string restrictions
> in a similar way and remove the string restrictions completely.
>
> Questions? Does it sounds OK?
>
> - David