ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput
<danieldg>
eyeris: I don't think there is one; all the foreign ones are about child windows (not embedded)
<danieldg>
I'm not sure wayland wants to do that either, but maybe you could propose such a protocol if you have a good use for it
<shegeley>
I'm a newbie on wayland and I have a question on how text-input protocol works. Is that true that by creating new text-input object and attaching a listener to it, I'd be able to track global (system-wide) context of text-input events? Or I'll be able to track it only in surfaces I create?
nerdopolis has joined #wayland
<kennylevinsen>
shegeley: text-input allows you to use a compositor input method. It is per wl_seat - somewhat similar to a keyboard, except it can send and edit strings instead of just keys.
<kennylevinsen>
You only get text input when focused and when the compositor sends it.
<shegeley>
I mean is it "program -> compositor"? So I can only get input context from the programm I've written and not across all the windows of the current display?
Avenaire has quit [Ping timeout: 480 seconds]
<kennylevinsen>
It's compositor -> program. You receive user input while the surface is focused, I.e. after enter and before leave
<kennylevinsen>
The "set_xyz" tell the compositor to current state of your input field, and the compositor in turn sends you changes to that input field
tesjhg has joined #wayland
mbalmer has joined #wayland
<shegeley>
<kennylevinsen>, thanks a lot for your help. but i still not getting the answer I exepect. let me rephrase: how can I (in my programm) track the global context of text-input events? is text-input protocol suitable for this? i was said that only zwp_input_method can help
<shegeley>
global context: catching the text-input events across all the displays, seats and etc
<kennylevinsen>
text input protocol is for clients to accept strings as input from the compositor.
<kennylevinsen>
input method protocol allows a client to become an input method for other clients that use the text-input protocol - "enter simplified Chinese by writing pinyin"/"Japanese kanji by writing romaji"/etc.
<shegeley>
When using smartphones there is a way smartphone know there is "text-input-possibility" when you being focused on some text-input field and it shows you virtual keyboard. How do I track that context globally using my desktops with Wayland
lbia has joined #wayland
mblenc has quit [Quit: leaving]
<kennylevinsen>
Good question. input-method will report if a text-input field is active, but it will not work for simpler clients just accepting regular keyboard input the normal way. You also need to be the one dealing with foreign language inputs as you're registering yourself as the IME.
tesjhg has quit [Ping timeout: 480 seconds]
junaid has joined #wayland
Moprius has joined #wayland
mblenc has joined #wayland
<shegeley>
"... simpler clients just accepting regular keyboard input the normal way ..." Coult you please elaborate on this part?
Moprius has quit []
mblenc1 has quit [Ping timeout: 480 seconds]
<kennylevinsen>
You normally get a wl_keyboard from your wl_seat, which accept simple keypresses without any concept of "text fields" - just input.
<kennylevinsen>
Because it is just keypresses, it cannot be used for input methods that require contextual information and the ability to edit text field content arbitrarily.
<shegeley>
Did you meant that only Weston seems to support input-method for now?
<kennylevinsen>
No
<kennylevinsen>
No idea what implementation status is, but my point is that input-method pairs with text-input, but text-input is optional and the normal keyboard input method is wl_keyboard