On 31.01.2013 23:26, Pekka Vuorela wrote:
> On 31.01.2013 22:18, Jan Arne Petersen wrote:
>> On 31.01.2013 16:38, Yichao Yu wrote:
>>> On Thu, Jan 31, 2013 at 9:52 AM, Jan Arne Petersen
>>> wrote:
From: Jan Arne Petersen
Another series of input method support patches. Mostly some
>
On 29.01.2013 03:49, Yichao Yu wrote:
> With the comment on the recent patches for the input method protocol,
> it seems that we are finally on the way to support cursor following.
> However I still have some questions about the protocol (and it's
> limitation).
>
> 1, Is there any plan to support
On Thu, Jan 31, 2013 at 5:39 PM, Weng Xuetian wrote:
> On Thursday 31 January 2013 17:44:02，Jan Arne Petersen :
>> From: Jan Arne Petersen
>>
>> The proposed API allows to send the language and text-direction for
>> inserted text from an input-method to an application.
>>
>> It also allows an app
On Thursday 31 January 2013 20:50:00，Jan Arne Petersen :
> On 31.01.2013 18:00, Yichao Yu wrote:
> > On Thu, Jan 31, 2013 at 11:44 AM, Jan Arne Petersen
> >
> > wrote:
> >> From: Jan Arne Petersen
> >>
> >> The proposed API allows to send the language and text-direction for
> >> inserted text fro
On Thu, Jan 31, 2013 at 5:19 PM, Pekka Vuorela wrote:
> On 31.01.2013 02:54, Yichao Yu wrote:
>>
>> Hi,
>>
>> On Wed, Jan 30, 2013 at 4:09 PM, Pekka Vuorela wrote:
>>>
>>> On 29.01.2013 04:49, Yichao Yu wrote:
Hi,
With the comment on the recent patches for the input metho
On Thursday 31 January 2013 17:44:02，Jan Arne Petersen :
> From: Jan Arne Petersen
>
> The proposed API allows to send the language and text-direction for
> inserted text from an input-method to an application.
>
> It also allows an application to specify a preferred language for
> the input. This
On 31.01.2013 22:18, Jan Arne Petersen wrote:
On 31.01.2013 16:38, Yichao Yu wrote:
On Thu, Jan 31, 2013 at 9:52 AM, Jan Arne Petersen
wrote:
From: Jan Arne Petersen
Another series of input method support patches. Mostly some
cleanups in the protocol:
* Remove some unused requests events (s
On Thu, Jan 31, 2013 at 4:19 PM, Bill Spitzak wrote:
>
>
> Yichao Yu wrote:
>>
>> On Thu, Jan 31, 2013 at 2:20 PM, Bill Spitzak wrote:
>>>
>>> On 01/31/2013 10:42 AM, Michael Hasselmann wrote:
>>>
You need to place your cursor at the left or right end of a text entry
(actually, right or
On 31.01.2013 02:54, Yichao Yu wrote:
Hi,
On Wed, Jan 30, 2013 at 4:09 PM, Pekka Vuorela wrote:
On 29.01.2013 04:49, Yichao Yu wrote:
Hi,
With the comment on the recent patches for the input method protocol,
it seems that we are finally on the way to support cursor following.
However I stil
Yichao Yu wrote:
On Thu, Jan 31, 2013 at 2:20 PM, Bill Spitzak wrote:
On 01/31/2013 10:42 AM, Michael Hasselmann wrote:
You need to place your cursor at the left or right end of a text entry
(actually, right or left of the possibly already existing text, on
focus-in). An explicit text direc
On Thu, Jan 31, 2013 at 4:00 PM, Yichao Yu wrote:
> On Thu, Jan 31, 2013 at 3:18 PM, Jan Arne Petersen
> wrote:
>> On 31.01.2013 16:38, Yichao Yu wrote:
>>> On Thu, Jan 31, 2013 at 9:52 AM, Jan Arne Petersen
>>> wrote:
From: Jan Arne Petersen
Another series of input method suppor
On Thu, Jan 31, 2013 at 3:18 PM, Jan Arne Petersen
wrote:
> On 31.01.2013 16:38, Yichao Yu wrote:
>> On Thu, Jan 31, 2013 at 9:52 AM, Jan Arne Petersen
>> wrote:
>>> From: Jan Arne Petersen
>>>
>>> Another series of input method support patches. Mostly some
>>> cleanups in the protocol:
>>>
>>>
On 31.01.2013 16:38, Yichao Yu wrote:
> On Thu, Jan 31, 2013 at 9:52 AM, Jan Arne Petersen
> wrote:
>> From: Jan Arne Petersen
>>
>> Another series of input method support patches. Mostly some
>> cleanups in the protocol:
>>
>> * Remove some unused requests events (set_preedit etc)
>>
>> * Add a
On Thu, Jan 31, 2013 at 3:06 PM, Jan Arne Petersen
wrote:
> On 31.01.2013 20:59, Yichao Yu wrote:
>> On Thu, Jan 31, 2013 at 2:50 PM, Jan Arne Petersen
>> wrote:
>>> Currently the context is state-less but even when we add state there, in
>>> Qt, for example, there is currently just one input con
On Thu, Jan 31, 2013 at 2:59 PM, Yichao Yu wrote:
> On Thu, Jan 31, 2013 at 2:50 PM, Jan Arne Petersen
> wrote:
>> On 31.01.2013 18:00, Yichao Yu wrote:
>>> On Thu, Jan 31, 2013 at 11:44 AM, Jan Arne Petersen
>>> wrote:
From: Jan Arne Petersen
The proposed API allows to send the
On 31.01.2013 20:59, Yichao Yu wrote:
> On Thu, Jan 31, 2013 at 2:50 PM, Jan Arne Petersen
> wrote:
>> Currently the context is state-less but even when we add state there, in
>> Qt, for example, there is currently just one input context per
>> application not one per widget.
>
> The whole point
On Thu, Jan 31, 2013 at 2:50 PM, Jan Arne Petersen
wrote:
> On 31.01.2013 18:00, Yichao Yu wrote:
>> On Thu, Jan 31, 2013 at 11:44 AM, Jan Arne Petersen
>> wrote:
>>> From: Jan Arne Petersen
>>>
>>> The proposed API allows to send the language and text-direction for
>>> inserted text from an inp
On 31.01.2013 18:00, Yichao Yu wrote:
> On Thu, Jan 31, 2013 at 11:44 AM, Jan Arne Petersen
> wrote:
>> From: Jan Arne Petersen
>>
>> The proposed API allows to send the language and text-direction for
>> inserted text from an input-method to an application.
>
> Can't really see why text-directi
On Thu, Jan 31, 2013 at 2:43 PM, Jan Arne Petersen
wrote:
> On 31.01.2013 20:20, Bill Spitzak wrote:
>> On 01/31/2013 10:42 AM, Michael Hasselmann wrote:
>>
>>> You need to place your cursor at the left or right end of a text entry
>>> (actually, right or left of the possibly already existing text
On Thu, Jan 31, 2013 at 2:20 PM, Bill Spitzak wrote:
> On 01/31/2013 10:42 AM, Michael Hasselmann wrote:
>
>> You need to place your cursor at the left or right end of a text entry
>> (actually, right or left of the possibly already existing text, on
>> focus-in). An explicit text direction event
On 31.01.2013 20:20, Bill Spitzak wrote:
> On 01/31/2013 10:42 AM, Michael Hasselmann wrote:
>
>> You need to place your cursor at the left or right end of a text entry
>> (actually, right or left of the possibly already existing text, on
>> focus-in). An explicit text direction event makes it eas
On 31.01.2013 19:25, Michael Hasselmann wrote:
> On Thu, 2013-01-31 at 15:52 +0100, Jan Arne Petersen wrote:
>> From: Jan Arne Petersen
>>
>> Allows for atomic state changes. Updated surrounding text, content type
>> and micro focus is taken into account all at once at commit.
>
> Does this enfor
On 01/31/2013 10:42 AM, Michael Hasselmann wrote:
You need to place your cursor at the left or right end of a text entry
(actually, right or left of the possibly already existing text, on
focus-in). An explicit text direction event makes it easier than having
to wait and parse for the input meth
On Thu, 2013-01-31 at 09:33 -0800, Bill Spitzak wrote:
> On 01/31/2013 08:44 AM, Jan Arne Petersen wrote:
> > From: Jan Arne Petersen
> >
> > The proposed API allows to send the language and text-direction for
> > inserted text from an input-method to an application.
>
> Can't direction be determ
On Thu, 2013-01-31 at 15:52 +0100, Jan Arne Petersen wrote:
> From: Jan Arne Petersen
>
> Allows for atomic state changes. Updated surrounding text, content type
> and micro focus is taken into account all at once at commit.
Does this enforce the atomicity of state changes or does it rely on
wel
On Thu, Jan 31, 2013 at 12:00 PM, Yichao Yu wrote:
> On Thu, Jan 31, 2013 at 11:44 AM, Jan Arne Petersen
> wrote:
>> From: Jan Arne Petersen
>>
>> The proposed API allows to send the language and text-direction for
>> inserted text from an input-method to an application.
>
> Can't really see why
On Wednesday 30 January 2013 23:09:20，Pekka Vuorela :
> On 29.01.2013 04:49, Yichao Yu wrote:
> > Hi,
> >
> > With the comment on the recent patches for the input method protocol,
> > it seems that we are finally on the way to support cursor following.
> > However I still have some questions about
On Thu, Jan 31, 2013 at 12:33 PM, Bill Spitzak wrote:
> On 01/31/2013 08:44 AM, Jan Arne Petersen wrote:
>>
>> From: Jan Arne Petersen
>>
>> The proposed API allows to send the language and text-direction for
>> inserted text from an input-method to an application.
>
>
> Can't direction be determ
On 01/31/2013 08:44 AM, Jan Arne Petersen wrote:
From: Jan Arne Petersen
The proposed API allows to send the language and text-direction for
inserted text from an input-method to an application.
Can't direction be determined by using Unicode rules on the new text,
with direction override cha
On Thu, Jan 31, 2013 at 11:44 AM, Jan Arne Petersen
wrote:
> From: Jan Arne Petersen
>
> The proposed API allows to send the language and text-direction for
> inserted text from an input-method to an application.
Can't really see why text-direction (of the input window) is useful,
shouldn't that
From: Jan Arne Petersen
Signed-off-by: Jan Arne Petersen
---
clients/editor.c | 20 -
clients/keyboard.c | 54 ++
clients/weston-simple-im.c | 54 ++
protocol/input-method.x
From: Jan Arne Petersen
The proposed API allows to send the language and text-direction for
inserted text from an input-method to an application.
It also allows an application to specify a preferred language for
the input. This could be used by an application to set a language
by context or to r
On Thu, Jan 31, 2013 at 9:52 AM, Jan Arne Petersen
wrote:
> From: Jan Arne Petersen
>
> Another series of input method support patches. Mostly some
> cleanups in the protocol:
>
> * Remove some unused requests events (set_preedit etc)
>
> * Add a commit request to allow to batch different state
>
From: Jan Arne Petersen
Add an extra cursor_position, which also allows to change the anchor
(for slections). Change the index type to int to allow setting it before
the beginning of a commited string.
The cursor should not be moved as a direct repsonse to this event but
atomically on the next c
From: Jan Arne Petersen
Rename set_micro_focus to set_cursor_rectangle to make more clear, what
it refers to.
Signed-off-by: Jan Arne Petersen
---
protocol/text.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/protocol/text.xml b/protocol/text.xml
index b20f00e..749c8c2
From: Jan Arne Petersen
Put them back in, when we know what arguments they will have.
Signed-off-by: Jan Arne Petersen
---
clients/editor.c | 21 -
protocol/text.xml | 4
src/text-backend.c | 7 ---
3 files changed, 32 deletions(-)
diff --git a/clients/editor
From: Jan Arne Petersen
Allows for atomic state changes. Updated surrounding text, content type
and micro focus is taken into account all at once at commit.
Signed-off-by: Jan Arne Petersen
---
clients/editor.c | 2 ++
clients/keyboard.c | 35
From: Jan Arne Petersen
Allows to show/hide the input panel (virtual keyboard) more independent
of focus (some applications might to require additionaly click on a
focused entry to show the input panel).
Signed-off-by: Jan Arne Petersen
---
clients/editor.c | 30 +
From: Jan Arne Petersen
Another series of input method support patches. Mostly some
cleanups in the protocol:
* Remove some unused requests events (set_preedit etc)
* Add a commit request to allow to batch different state
changes on application side together. That needs some more
documentat
On Thu, 31 Jan 2013 14:43:03 +0100
abhishek jain wrote:
> I am using weston only.Could you please tell me Where I have to grep for
> weston_output_init.?
The Weston sources, since you are going to look at the Weston backends'
code.
Thanks,
pq
> On Thu, Jan 31, 2013 at 2:09 PM, Pekka Paalanen
On Thu, 31 Jan 2013 13:57:57 +0100
abhishek jain wrote:
> Hello,
>
> I am new for wayland API. I got stuck in output event handling.
>
> I am using this API.
> wl_outpu::geometry and wl_output::mode . But both gives me the same value
> for both physical_width in mm and width in pixel.
What yo
Hello,
I am new for wayland API. I got stuck in output event handling.
I am using this API.
wl_outpu::geometry and wl_output::mode . But both gives me the same value
for both physical_width in mm and width in pixel.
Thanks in advance.
Regards,
Abhishek Jain
On Thu, Jan 31, 2013 at 1:53 PM,
42 matches
Mail list logo
