Payload size and text.xml in weston
Elvis Lee(KwangWoong Lee)
kwangwoong.lee at lge.com
Sun Dec 15 18:52:30 PST 2013
> On Thu, 2013-12-12 at 18:23 -0600, Jason Ekstrand wrote:
> > Elvis,
> > On Dec 12, 2013 2:08 AM, "Elvis Lee(KwangWoong Lee)"
> > <kwangwoong.lee at lge.com> wrote:
> > > While using text protocol in Weston, we encountered some cases which
> > exceeds the limitation.
> > >
> > > For example, "set_surrounding_text" carries a string which is longer
> > than 1024 bytes.
> Surround text is usually the current paragraph or sentence. Use-case is
> text prediction via text n-grams for instance, which only needs a few
> neighboring words to work out.
> I'd be curious to know which use-cases you tried to implement to hit the
> buffer limit. That is, if you can disclose them of course.
I just started to feel that something is wrong on our implementation.
Anyway let me explain current state.
'set_surrounding_text' carries whole text of input box(UX). Now it's used to support an action 'clear all' with Maliit virtual keyboard.
'Clear all' means to delete whole text in the input box. So the IME(VKB) needs to know whole length of the contents in the box.
I just looked the input-method protocol, but it seems that there is no way to notify the whole length of text to compositor except 'set_surrounding_text'
Also I thought(felt) that 'set_surrounding_text' is for text selection. If it is, what happens when user drags whole text in an input box?
I don't know well about this input-method protocol. So I can still imagine some cases in which set_surrounding_text needs to carry whole text.
Please let me know what I misunderstood.
> > > 1. Restricts input size of text box in UX.
> That's a property of the text editor, not necessarily the input method.
> Read: client-side decision/controlled by UI toolkit.
I didn’t get this part. - Read: client-side decision/controlled by UI toolkit.
Is it a document?
More information about the wayland-devel