Wait, does this work on Linux with wayland?
Actually, this is false. This used to be the case in the 70s, but after the Wassenaar Agreement[1], this was removed from nearly all collective bargaining agreements[2]. Some have salary grades that increase…
“Putting everything in the compositor” isn’t mandated by Wayland at all, and I think only gnome does it. If you implement the protocols defined by Kwin, you can reuse everything in KDE without using it. Yes, it’s a lot…
Actually, xdotool is the wrong place for this kind of automation. IMO, the optimal place to implement this is in the toolkits, to make it possible to read text and properly click buttons and menus.
Not all statically typed languages. Using it in QT is great, and using it in GTK in C is not more difficult than showing a window. I also recently came across zbus in rust (https://docs.rs/zbus/1.8.0/zbus/) and it looks…
Wait, does this work on Linux with wayland?
Actually, this is false. This used to be the case in the 70s, but after the Wassenaar Agreement[1], this was removed from nearly all collective bargaining agreements[2]. Some have salary grades that increase…
“Putting everything in the compositor” isn’t mandated by Wayland at all, and I think only gnome does it. If you implement the protocols defined by Kwin, you can reuse everything in KDE without using it. Yes, it’s a lot…
Actually, xdotool is the wrong place for this kind of automation. IMO, the optimal place to implement this is in the toolkits, to make it possible to read text and properly click buttons and menus.
Not all statically typed languages. Using it in QT is great, and using it in GTK in C is not more difficult than showing a window. I also recently came across zbus in rust (https://docs.rs/zbus/1.8.0/zbus/) and it looks…