One thing I saw in comments about the removal of xorg server is that some might not see how much work is/was to maintain xorg server. I understand is hard to see from outside, but maintaining xorg server with the standards we have in RHEL is not a small beast. Let me share some:
Autotype is already solved - ydotool, wtype and dotool exists (and possibly others as well).
Screen magnification is already present in KDE (Meta + +, Meta + - to zoom in/out). There’s also a magnifier tool (KMag). There may be similar functionalities in other DEs.
My issue is the lack of an overall GUI automation tool, ie, like AutoHotkey. X11 had PyAutoGUI, but there’s no such AIO equivalent for Wayland yet, and the PyAutoGUI devs don’t seem to be interested in Wayland support - it’s neither on their road map, nor have they even answered any Wayland questions on their Github page, which is disappointing. But this isn’t Wayland’s fault, when other tools have shown that automating the GUI is possible, we just need someone to put together a complete package like PyAutoGUI / AHK.
Autotype is already solved - ydotool, wtype and dotool exists (and possibly others as well).
These tools work by creating a virtual keyboard so they don’t let you send input to a specific window. The input goes to whatever happens to be focused at the moment. This makes them less reliable than the X11 equivalents and unusable for tasks where you need to guarantee that the right window gets the input.
feel free to check out map2, I’m currently working on version 2 which will do lots of the stuff you need when it’s ready, but currently the API might still change and docs are active WIP
still, it can already do most stuff I need it for :)
Autotype is already solved - ydotool, wtype and dotool exists (and possibly others as well).
Screen magnification is already present in KDE (
Meta++,Meta+-to zoom in/out). There’s also a magnifier tool (KMag). There may be similar functionalities in other DEs.My issue is the lack of an overall GUI automation tool, ie, like AutoHotkey. X11 had PyAutoGUI, but there’s no such AIO equivalent for Wayland yet, and the PyAutoGUI devs don’t seem to be interested in Wayland support - it’s neither on their road map, nor have they even answered any Wayland questions on their Github page, which is disappointing. But this isn’t Wayland’s fault, when other tools have shown that automating the GUI is possible, we just need someone to put together a complete package like PyAutoGUI / AHK.
These tools work by creating a virtual keyboard so they don’t let you send input to a specific window. The input goes to whatever happens to be focused at the moment. This makes them less reliable than the X11 equivalents and unusable for tasks where you need to guarantee that the right window gets the input.
KMag doesn’t work on Wayland.
feel free to check out map2, I’m currently working on version 2 which will do lots of the stuff you need when it’s ready, but currently the API might still change and docs are active WIP
still, it can already do most stuff I need it for :)
deleted by creator