From: Jan Arne Petersen
Add a struct weston_keyboard, to handle the input method grab.
Signed-off-by: Jan Arne Petersen
---
src/compositor.c| 29 +++--
src/compositor.h| 9 -
src/shell.c | 10 --
src/text-backend.c | 48
From: Jan Arne Petersen
Add a struct weston_keyboard, to handle the input method grab.
Signed-off-by: Jan Arne Petersen
---
src/compositor.c | 29 +++--
src/compositor.h | 9 -
src/shell.c| 10 --
src/text-backend.c | 48
On 11/27/2012 09:11 PM, Kristian Høgsberg wrote:
> On Sun, Nov 18, 2012 at 07:06:41PM +0100, Jan Arne Petersen wrote:
>> From: Jan Arne Petersen
>>
> text: Rename and extend text_model key event
I'm holding off on this one and the remaining patches. I think you're
right that it's
On 11/28/2012 03:50 AM, Kristian Høgsberg wrote:
> On Tue, Nov 27, 2012 at 03:11:17PM -0500, Kristian Høgsberg wrote:
>> On Sun, Nov 18, 2012 at 07:06:41PM +0100, Jan Arne Petersen wrote:
>>> From: Jan Arne Petersen
>>>
>> text: Rename and extend text_model key event
> I'm holding off on
On Tue, Nov 27, 2012 at 03:11:17PM -0500, Kristian Høgsberg wrote:
> On Sun, Nov 18, 2012 at 07:06:41PM +0100, Jan Arne Petersen wrote:
> > From: Jan Arne Petersen
> >
> > >>> text: Rename and extend text_model key event
> > >> I'm holding off on this one and the remaining patches. I think you
On Sun, Nov 18, 2012 at 07:06:41PM +0100, Jan Arne Petersen wrote:
> From: Jan Arne Petersen
>
> >>> text: Rename and extend text_model key event
> >> I'm holding off on this one and the remaining patches. I think you're
> >> right that it's better to just add the events to text_model, but
> >
From: Jan Arne Petersen
>>> text: Rename and extend text_model key event
>> I'm holding off on this one and the remaining patches. I think you're
>> right that it's better to just add the events to text_model, but
>> there's more to it than that. We need a better approach to modifiers
>> than
It appears that both the input method and the client have to do the xkb
decoding from hardware events to keysyms and shift information. And that
the method used by the input method to produce "other" keys is to, in
effect, run xkb backwards to produce fake hardware events from the
desired resul
On 11/15/2012 11:29 AM, Jan Arne Petersen wrote:
> My current idea would be to add a modifier_names event to text_model, so
> that an input method sends an array of known modifier names (which would
> be the same used by xkb_keymap_mod_get_index). The mapping to a bitmask
> is than just done by th
From: Jan Arne Petersen
>> text: Start input method from configuration
> I'm happy to see this functionality land, but there's few comments on
> the patch.
I fixed the comments on this patch.
>> text: Rename and extend text_model key event
> I'm holding off on this one and the remaining pa
On Mon, Nov 05, 2012 at 03:26:38AM +0100, Jan Arne Petersen wrote:
> From: Jan Arne Petersen
>
> Hardware keyboard input allows input methods to grab the keyboard
> and process hardware key events to generate text events (with
> pre-edit) over the same text_model interface we use
From: Jan Arne Petersen
Hardware keyboard input allows input methods to grab the keyboard
and process hardware key events to generate text events (with
pre-edit) over the same text_model interface we use for the virtual
keyboard. This allows input methods which compose multiple key
events for
Hi!
On 08/15/2012 02:45 AM, Bill Spitzak wrote:
> Does the proposed input methods support clients being able to show
> intermediate results? This is certainly useful to make "dead keys" less
> "dead", and I am under the impression that it is very useful for some
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012年08月15日 08:45, Bill Spitzak wrote:
> Does the proposed input methods support clients being able to show
> intermediate results? This is
certainly useful to make "dead keys" less "dead", and I am under the
impression
Does the proposed input methods support clients being able to show
intermediate results? This is certainly useful to make "dead keys" less
"dead", and I am under the impression that it is very useful for some
Asian entry systems.
X11 tried to do this with an input-metho
Hi Jan,
I'm still slowly getting the hang of how wayland works, but I think
I've spotted a problem: only one client at a time should bind to the
input_method global. Else we don't know who we send events to.
This has the consequence that the create_text_model request has to be
moved somewhere els
nking about trying to implement a simple composing
input method (like for example pinyin). I read
http://blog.jpetersen.org/2012/06/20/text-input-method-support-in-wayland/
and https://wiki.maliit.org/Wayland_Input_Method_System_Proposal but I
didn't manage to understand how composing input m
t-method-support-in-wayland/
>> and https://wiki.maliit.org/Wayland_Input_Method_System_Proposal but I
>> didn't manage to understand how composing input methods are supposed
>> to work, specifically there is no mention about how keyboard input is
>> going to be hand
but I
didn't manage to understand how composing input methods are supposed
to work, specifically there is no mention about how keyboard input is
going to be handled. I'm not sure if I overlooked something, or if
this part is not specified yet.
The handling of keyboard input is not de
ge to understand how composing input methods are supposed
to work, specifically there is no mention about how keyboard input is
going to be handled. I'm not sure if I overlooked something, or if
this part is not specified yet.
I thought about the problem a bit and in my opinion the cleanest
solution wo
20 matches
Mail list logo
