Looking for Wayland experts

[Flohack]

My company is looking for Wayland expertise:

Are there any Linux experts out there that have tried/experience with simulated input and manipulating windows (move/resize/focus/close/get title/get class etc.) on Wayland sessions? (With X11 this seems to be trivial.)
What I found so far is that mouse/keyboard input is possible by writing to /dev/uinput (how ydotool does it) or in Gnome (Mutter) by a shell extension. There is also a Wayland protocol zwp_virtual_keyboard_v1 for compositors that impelemnt it (what wtype uses), and KDE (KWin) has this org_kde_kwin_fake_input protocol, but those are still unstable I guess.

@alan_g do you have any idea who could help here? Eventually it will be paid but I cannot say this for sure now.

[alan_g]

To some extent it depends on the actual goal. Is this intended as a test harness for an app in a controlled environment? Or as a means of automation on a desktop?

Faking udev ought to work across different compositors. The virtual keyboard extensions might work for some compositors but different compositors support different protocol extensions. (E.g. Mir supports virtual_keyboard_unstable_v1 but not org_kde_kwin_fake_input.)

If this is just for an application test harness, then it should be possible to test against a specific, even a bespoke, compositor.

This could be complicated for most people I know as they have employers, and work (especially paid) outside that raises contract concerns.

Maybe ask on the wayland-devel mailing list?