Keysym event in the text protocol

[Bill Spitzak]

Yes I saw that, but it is a file descriptor. My reading was that a 
client machine must have somewhere in it's file system every possible 
keyboard that could be on a remote machine. That is actually what led to 
my question.

I suppose the xkb description can be sent: the local compositor would 
aquire the file the first time it connects to a remote compositor. I 
would then be concerned about loading an interpreted file from an 
untrusted source, but I guess xkb descriptions are simple enough that 
this can be made safe.

What I am really trying to get an answer to is what is special about 
keyboards. Everybody seems to be in agreement that the compositor will 
call libinput and translate raw evdev events from touchpads into 
something more useful. Surely if there is some advantage to the xkb 
scheme it would apply equally to touchpads, and the compositor would 
send raw events and clients would link to libinput and read touchpad 
description files.

On 07/28/2014 10:58 AM, Jasper St. Pierre wrote:
> On Mon, Jul 28, 2014 at 7:44 PM, Bill Spitzak <spitzak at gmail.com
> <mailto:spitzak at gmail.com>> wrote:
>
>     I am just going to have to study this further, because I am still
>     completely stumped as to why so many people think this is an
>     acceptable solution.
>
>     This sounds to me like either the ability to transmit an entire xkb
>     description across the wire is added to the wayland protocol
>
>
> Bill. Please. Can you at least *look* at the current protocol before you
> write your current emails? Because this is why we get frustrated.
>
> http://cgit.freedesktop.org/wayland/wayland/tree/protocol/wayland.xml#n1508