Questions and thoughts about input method protocol

[Jan Arne Petersen]

On 05.02.2013 08:20, Daniel Stone wrote:
> On 4 February 2013 17:59, Bill Spitzak <spitzak at gmail.com
> <mailto:spitzak at gmail.com>> wrote:
>     It would be really nice if Wayland input methods were designed so
>     that compose key apis were done with this instead of somehow
>     defining the keyboard. The keyboard api should be limited to
>     producing keysyms based on the current set of keys held down, and
>     not handle sequences at all. I think this will require that they be
>     fairly easy to write, and that we have an example compose-key input
>     method from day 1 so nobody is tempted to put it into the keyboard.
> 
> 
> Oh, for the love of god - this is what already happens.  wl_keyboard (go
> have a look at it some day) gives clients the keysyms resulting from
> pressing one keycode at a time.  There's no composition or filtering, we
> just pass it all down to the client, and leave composition up to the
> input methods.  This is why weston-terminal (go try it some day) doesn't
> support compose keys.  It would've taken all of five seconds to try, and
> would've handily shown you that pretty much every single sentence in
> this mail was wrong and/or based on fiction.

I completely agree with Daniel Stone. In addition you could also just
look at the code (it is open source). Just check weston-simple-im.c for
the compose-key input method which is already there for some months now.

-- 
Jan Arne Petersen
Openismus GmbH
http://www.openismus.com