Re: Questions and thoughts about input method protocol

On 02/04/2013 11:20 PM, Daniel Stone wrote: What? Compose keys in X can only be implemented through input methods. GTK+ does it using its own internal input method (which is more than capable of doing pre-edit, what with it being part of core GTK+ and all), but xterm and all the other core app

Re: Questions and thoughts about input method protocol

On 05.02.2013 08:20, Daniel Stone wrote: > On 4 February 2013 17:59, Bill Spitzak > 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

Re: Questions and thoughts about input method protocol

On 4 February 2013 17:59, Bill Spitzak wrote: > I think what happened is that because writing an input method was not easy > and required huge amounts of support code that was not needed to support > simple compose or pick-character-by-number operations, these were instead > implemented in X usin

Re: Questions and thoughts about input method protocol

On 02/03/2013 05:14 AM, Yichao Yu wrote: I suspect because preedit was a pain to support under X it was never tried. Not at all, especially if you are using im-module or if you don't need cursor following. Yes, preedit can be used in some input method/layout but other features that I mentioned

Re: Questions and thoughts about input method protocol

On Sun, Feb 3, 2013 at 2:56 AM, Bill Spitzak wrote: > On 02/02/2013 09:12 PM, Yichao Yu wrote: > >> E.g. for non-cjk input method, there is likely to be only one per >> language (which is likely to be a keyboard layout). They normally >> never need cursor following window, don't have dozens of int

Re: Questions and thoughts about input method protocol

On 02/02/2013 09:12 PM, Yichao Yu wrote: E.g. for non-cjk input method, there is likely to be only one per language (which is likely to be a keyboard layout). They normally never need cursor following window, don't have dozens of internal states. Even the use of preedit is not that common. Act

Re: Questions and thoughts about input method protocol

On Fri, Feb 1, 2013 at 3:40 AM, Jan Arne Petersen wrote: > On 01.02.2013 09:21, Pekka Paalanen wrote: >> On Thu, 31 Jan 2013 17:45:25 -0500 >> Yichao Yu wrote: >> >>> On Thu, Jan 31, 2013 at 5:19 PM, Pekka Vuorela wrote: Problem with window titles and all is that they are information not me

Re: Questions and thoughts about input method protocol

On Sat, Feb 2, 2013 at 4:49 AM, Pekka Vuorela wrote: > On 01.02.2013 21:53, Yichao Yu wrote: >> >> On Fri, Feb 1, 2013 at 1:48 PM, Pekka Vuorela wrote: >>> >>> On 01.02.2013 00:45, Yichao Yu wrote: On Thu, Jan 31, 2013 at 5:19 PM, Pekka Vuorela wrote: > > I was talking abo

Re: Questions and thoughts about input method protocol

On 01.02.2013 21:53, Yichao Yu wrote: On Fri, Feb 1, 2013 at 1:48 PM, Pekka Vuorela wrote: On 01.02.2013 00:45, Yichao Yu wrote: On Thu, Jan 31, 2013 at 5:19 PM, Pekka Vuorela wrote: I was talking about input method _automatically_ changing to one layout or another based on what was used in

Re: Questions and thoughts about input method protocol

On Fri, Feb 1, 2013 at 6:36 PM, Yichao Yu wrote: > On Fri, Feb 1, 2013 at 6:15 PM, Bill Spitzak wrote: >> Will simple input methods that have no state have to do anything about this, >> or is it trivial to support? >> >> What I am wondering is if an input method that does not use the context id >

Re: Questions and thoughts about input method protocol

On Fri, Feb 1, 2013 at 6:15 PM, Bill Spitzak wrote: > Will simple input methods that have no state have to do anything about this, > or is it trivial to support? > > What I am wondering is if an input method that does not use the context id > for anything will still need to keep track of what cont

Re: Questions and thoughts about input method protocol

Will simple input methods that have no state have to do anything about this, or is it trivial to support? What I am wondering is if an input method that does not use the context id for anything will still need to keep track of what context id's were allocated and freed? Or can it just throw th

Re: Questions and thoughts about input method protocol

On Fri, Feb 1, 2013 at 1:48 PM, Pekka Vuorela wrote: > On 01.02.2013 00:45, Yichao Yu wrote: >> >> 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: > > >>> I was

Re: Questions and thoughts about input method protocol

On 01.02.2013 00:45, Yichao Yu wrote: 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: I was talking about input method _automatically_ changing to one layout or another based on what was

Re: Questions and thoughts about input method protocol

On 31.01.2013 19:54, Weng Xuetian wrote: On Wednesday 30 January 2013 23:09:20，Pekka Vuorela : I would try to find better ways to achieve targeted goals. One feature I've myself been thinking is virtual keyboard used with messaging app knowing what language, or type of language, the recipient

Re: Questions and thoughts about input method protocol

terminal, may or may not set the window >> > title to their own random things. >> >> You are right about the terminal, although that's not the most >> important case for this: few people uses input method a lot in a >> terminal. > > No, it's a tri

Re: Questions and thoughts about input method protocol

uot;bash" anywhere. There is no keyword you could match. > > Also, other apps that run in the terminal, may or may not set the window > > title to their own random things. > > You are right about the terminal, although that's not the most > important case for this: few p

Re: Questions and thoughts about input method protocol

On Fri, Feb 1, 2013 at 3:21 AM, Pekka Paalanen wrote: > On Thu, 31 Jan 2013 17:45:25 -0500 > Yichao Yu wrote: > >> On Thu, Jan 31, 2013 at 5:19 PM, Pekka Vuorela wrote: >> > Problem with window titles and all is that they are information not meant >> > to >> > input method. Those are meant for

Re: Questions and thoughts about input method protocol

On Fri, Feb 1, 2013 at 2:51 AM, Jan Arne Petersen wrote: > 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 protoco

Re: Questions and thoughts about input method protocol

On 01.02.2013 09:21, Pekka Paalanen wrote: > On Thu, 31 Jan 2013 17:45:25 -0500 > Yichao Yu wrote: > >> On Thu, Jan 31, 2013 at 5:19 PM, Pekka Vuorela wrote: >>> Problem with window titles and all is that they are information not meant to >>> input method. Those are meant for the user and can ch

Re: Questions and thoughts about input method protocol

On Thu, 31 Jan 2013 17:45:25 -0500 Yichao Yu wrote: > On Thu, Jan 31, 2013 at 5:19 PM, Pekka Vuorela wrote: > > Problem with window titles and all is that they are information not meant to > > input method. Those are meant for the user and can change any time and to > > anything. And using those

Re: Questions and thoughts about input method protocol

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

Re: Questions and thoughts about input method protocol

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

Re: Questions and thoughts about input method protocol

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

Re: Questions and thoughts about input method protocol

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

Re: Questions and thoughts about input method protocol

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 still have some questions ab

Re: Questions and thoughts about input method protocol

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 the protocol (and it's limitation). 1, Is there any plan to support xway

Questions and thoughts about input method protocol

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 the protocol (and it's limitation). 1, Is there any plan to support xwayland? I believe it is important to supp