[Feature] Wayland Support

[arronium]

Hello, I wanted to look into adding Wayland support for the script, to learn more about Wayland and also avoid switching between X11 and Wayland sessions

but I noticed that there is a os_wayland_backend.py file in .gitignore, so I figured I'd ask it's state before delving in, incase further help isn't necessary, or decisions have been made

[AlexWalp]

Basically I need 3 main functions for wayland to work:

• _find_window_by_name() that returns a window reference/id for a window with "LimbusCompany" name. Currently it cannot find it with my implementation.
• get_virtual_screen_bounds() that gets display params
• screenshot() for the region that is based on window data

Basically, I need a function that returns window geometry data (x, y, w, h) based on window name. So I'm open for any suggestions/implementations on that.

Everything else is very similar to x11 backend.
Oh, btw, I've just found out that my current implementation for x11 is kinda buggy and the window data is just not updated properly sometimes. So I'll also need to fix that.

[Doku1910]

Hi! I was looking before into why Wayland makes things so difficult for a bot. Since Wayland is built for security, it basically "hides" windows from each other, which is why your X11 code can't find Limbus.

I did some digging and here is what I found for those 3 functions:

1 - Finding the window and its size: Wayland doesn't have a universal command for this. You have to ask the desktop directly. If you are on KDE, you can use something called DBus to get the window info. If you are on others like Hyprland or Sway, there are commands (like hyprctl or swaymsg) that give you a list of all open windows and their coordinates in a simple text format.

2 - Screen bounds: This is the easiest part. There are small tools like wlr-randr that tell you the screen size, or you can even check the system files in /sys/class/drm/ to see what resolution the monitor is using.

3 - Screenshots: Most people on Wayland use a tool called grim. It’s great because you can tell it exactly which area to capture (using the x, y, width, and height you got from the first step) and save it as an image for the bot to read.

Since every desktop (GNOME, KDE, Hyprland, etc.) does things differently, maybe don't worry about making it work for everyone. You can select one DE, and you could just make it compatible with that and list it in your notes. One of the best things about Linux is that we can just switch to the desktop that works best for our tools!

Hope this helps! Good luck!