I’m working on a window switching tool for Wayland that’s kinda like Alt-Tab. However, it seems like there’s no compositor agnostic way to do things like:
- List all currently open windows
- Ask which window is currently focused
- Focus a specific window
Therefore, if I want my tool to support multiple compositors, I have to re-implement this logic for each compositor.
Is the motivation security through program isolation? That doesn’t quite make sense to me since programs still can do the above things, they just have to do it compositor specifically: hyprctl clients on Hyprland, niri msg windows for Niri, etc. Also, you could just have a Wayland API that requires elevated privileges for doing these things, which the user would have to opt-in to for a specific program.
I feel like this design of Wayland causes a lot of fragmentation. There are a lot of tools that are for example Hyprland-only.
Could you please enlighten me on why Wayland has this design?
why don’t you? you seem bothered by it and maybe op stumbled upon something worth looking into.
I already answered that. I don’t think wayland should exist let alone be fixed and even if I wanted to I described the development environment around it as sclerotic and sycophantic.
then why do you care so much? just use x11.
I do whenever possible. If you’ll remember, I replied to the ops query about why wayland is the way it is.
A better question is why are you replying to me over and over again asking circular questions?