How does "move cursor one word to the right" work in zwp_text_input_unstable_v3?

[Filip Filmar]

Hi folks!

I am exploring the features of the v3 text input API as seen at
https://wayland.app/protocols/text-input-unstable-v3.

I am curious, how does this API then implement operations such as "move
cursor one word to the right" or "move cursor to the end of the line" or
"move cursor to the end of the field"?

I ask because, IIUC, the wayland side of this API does not know the entire
string being edited - it can only instruct adding or removing the text
surrounding the cursor position.

Any info on this is appreciated.

Thanks,
F

General question about new API introduction in Wayland

[Filip Filmar]

Hi folks!

Thanks for helping me out with my text input v3 API question

.

If I may, I'd like to ask a few orienting questions about the API lifecycle
and implementation in Wayland.

To wit, the text input is an unstable API.  I take it to mean that it can
change abruptly. What happens then with the implementers of this API? When,
or why would they (ever) want to update the client side to match the latest
and greatest Wayland APIs?

Further, what is the general approach when a client finds a wayland API is
found to be lacking functionality?  I understand that if there is general
interest in the feature, it might make sense to contribute an
implementation.

But, in a case where it's a niche interest of a client, what can a client's
owner do?

In the case of a text input API, it seems that when it changes, the entire
universe of Wayland-supporting clients would need to implement the
client-side changes. Who is (ever) motivated to do that? How does that
usually play out in the Wayland world?

Thanks for your time!

F

Re: General question about new API introduction in Wayland

[Filip Filmar]

On Tue, Dec 20, 2022 at 2:22 AM Pekka Paalanen  wrote:

> Hi,
>
> have you seen
>
> https://gitlab.freedesktop.org/wayland/wayland-protocols/-/blob/main/README.md
> already? It explains the general change procedure and sets expectations.
>

Hi, thank you for your explanation and the link.

I have read the README.md. It describes the mechanics of a protocol change,
which is very useful in itself.

However, my questions were mostly around the circumstances in which an idea
about a new protocol, or a protocol change may arise, and what decides how
that change then propagates to implementations.

Which you inferred, and explained in the rest of your message. So I think I
got the answer that I was after.

Thanks,
F