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?

  • kehet@sopuli.xyz
    link
    fedilink
    arrow-up
    10
    arrow-down
    1
    ·
    9 hours ago

    There’s probably a PR or a thread somewhere with a bunch of very angry nerds fighting over whether this is even a useful feature and there’s no API because they can’t reach a compromise. There is no design.

    • L_Acacia@lemmy.ml
      link
      fedilink
      arrow-up
      9
      arrow-down
      1
      ·
      edit-2
      7 hours ago

      Gnome board members most likely blocking it while embezzling donations