[yjftsjthsd-h]

>> Occasionally, I've enjoying playing around with window management and hacking with WMs, using stuff like this and/or xdotool and wmctrl.

Ydotool readme:

> Currently implemented command(s):

> type - Type a string

> key - Press keys

> mousemove - Move mouse pointer to absolute position

> click - Click on mouse buttons

So... No.

[shmerl]

For what xdotool does - pretty much a substitute. For anything else you need a compositor specific tool.

KWin scripts or something might work for KDE: https://develop.kde.org/docs/plasma/kwin/

[yjftsjthsd-h]

> For what xdotool does - pretty much a substitute.

No; for just the input functions, and that only if you're not using `--window`, it's a substitute. But xdotool is a lot more than that.

> For anything else you need a compositor specific tool.

Yes, exactly. For the things that were asked for, your best hope is do see if your particular compositor deigned to provide the API surface, and then if it did, write something that uses those non-portable APIs to do what you want.

[shmerl]

Makes perfect sense for it to be something that interacts with the compositor. So KWin does expose such API. But that's not part of Wayland itself or its protocols.

Want to make it easy? Use KDE which cares about flexibility and write scripts for it. Otherwise - probably tough luck, not sure how much other compositors even care about such things.

[yjftsjthsd-h]

Or I could just use X11, where this is a solved problem using a single API that works on arbitrary window managers / desktop environments. The only problem is people keep showing up to tell me that I need to stop using it and use their feature-poor alternative.

[shmerl]

You couldn't really since it's DOA. Otherwise you'd be stuck with unsupported path.