[PATCH 00/13] Clean up text protocol and move to wayland

Pekka Vuorela pvuorela at iki.fi
Tue Feb 19 13:31:36 PST 2013

On 19.02.2013 22:11, Jan Arne Petersen wrote:
> On 19.02.2013 20:01, Yichao Yu wrote:
>> On Tue, Feb 19, 2013 at 1:26 PM, Jan Arne Petersen
>> <jpetersen at openismus.com> wrote:
>>> From: Jan Arne Petersen <jpetersen at openismus.com>
>>> This series finalizes the first version of the text protocol and
>>> moves it from Weston to Wayland, so that it can be implemented in
>>> toolkits.
>> Well, the only problem is that this protocol is totally not usable yet
>> and it lacks every single feature a non-layout input method needs.
>> Apart from what I have already mentioned ((more important ones first)
>> tracking input context, cursor following, getting information about
>> im-clients (pid, appname, context), and not really sure about having
>> multiple processes drawing the user interface) there is one more
>> feature that is missing. Is it possible for the im-client to send a
>> key event that is not previously handled by the input method back to
>> text_model (or is wl_text_input the new name...)? At least I haven't
>> found a request on the im-client to send this out... This is really
>> useful when the text model only get input focus after certain key
>> event (see pidgin input window as an example).
> With this series we try to get the text protocol into Wayland (so it can
> be supported by toolkits). The input-method protocol for input methods
> is not ready yet and will be included into Wayland later (when it will
> be ready).

Could perhaps clarify what this means protocol stability-wise. Intention 
to merge into Wayland master, but allowed to still be modified until 
1.1(?) is released, or to be stable already when reaching Wayland?

I do share some concerns with Yichao since this hasn't yet been taken 
into use with a basic CJK setup. Every single feature part, of course, 
being still huge exaggeration.

More information about the wayland-devel mailing list