[PATCH RFC] Add language and text-direction to text protocol

Yichao Yu yyc1992 at gmail.com
Fri Feb 1 05:25:45 PST 2013


On Fri, Feb 1, 2013 at 8:06 AM, Jan Arne Petersen
<jpetersen at openismus.com> wrote:
> On 01.02.2013 13:46, Yichao Yu wrote:
>> On Fri, Feb 1, 2013 at 3:18 AM, Jan Arne Petersen
>> <jpetersen at openismus.com> wrote:
>>> On 31.01.2013 23:39, Weng Xuetian wrote:
>>>> And, IMHO, those hint should be set in a key-value map, instead of everytime
>>>> we add some new API, hence the API would be much more flexible and easier to
>>>> be backward compatible. And maybe also reduce IPC round trip between input
>>>> method and application.
>>>
>>> No a key-value map is not really helpful, we would need to add a key
>>> specification so that not every toolkit and every input method uses
>>> different keys, different types of values etc.
>>
>> It will be useful as long as you define some keys you need, language
>> and text-direction in this case, just like wl_display::global event,
>> although the event may not necessarily sent out directly by the
>> compositor.
>
> Why should I reinvent the Wayland protocol on-top of a key-value map and
> not just use it as it is?

In order to easily add new stuff? Or is it possible to add a event
without a abi breaking?

>
> --
> Jan Arne Petersen
> Openismus GmbH
> http://www.openismus.com
> _______________________________________________
> wayland-devel mailing list
> wayland-devel at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/wayland-devel


More information about the wayland-devel mailing list