Xorg Input Hotplugging

[Rob Taylor]

Daniel Stone wrote:
> On Mon, Dec 03, 2007 at 07:15:21PM +0100, ext Nicolas Mailhot wrote:
>> Le lundi 03 décembre 2007 à 19:59 +0200, Daniel Stone a écrit :
>>> On Mon, Dec 03, 2007 at 06:53:26PM +0100, ext Nicolas Mailhot wrote:
>>>> Le lundi 03 décembre 2007 à 19:37 +0200, Daniel Stone a écrit :
>>>>>         <merge key="input.xkb.layout" type="string">gb,ru</merge>
>>>>>         <merge key="input.xkb.variant" type="string">,winkeys</merge>
>>>> Is the , before winkeys needed?
>>> Yes, otherwise you'll have gb(winkeys) and ru; not gb and ru(winkeys).
>> That is seriously broken and user-unfriendly XML :(. Has it been written
>> by gconf developers? Is it not possible to do something more intuitive
>> like
>>
>> <merge sys="input.xkb"/>
>>    <layout value="gb"/>
>>    <layout value="ru">
>>       <variant value="winkeys"/>
>>    </layout>
>> </merge>
>>
>> ie something that actually uses XML hierachical nature to describe
>> hierarchies? I mean what's the point of inflicting tags on users if
>> they're not even used to tokenise properties properly.
> 
> Right now, it merely maps one to one to the existing XKB properties of
> the same name.  I agree that a better hierachical mapping would be more
> than welcome (especially with model-specific layouts), and am definitely
> happy to take patches. :)
> 

Wouldn't a strlist be at least a bit better?

Rob
-- 
Rob Taylor, Codethink Ltd. -  http://codethink.co.uk