dec05eba
kiwifarms.net
- Joined
- Jul 27, 2022
There will never be wayland protocols to deal with my issues (especially on gnome) so my software will never be able to work properly on wayland. This is intentional because the wayland philosophy is incompatible with some software. The goal of wayland has never been to work with all software. The goal is instead for software to be designed for the specific wayland compositors. So for gnome for example you're only meant to run gnome-styled software, and so on. KDE has gone against this a bit by "breaking" the wayland protocol. It's a mess.Holy crap i just realized you're the guy from the tech over tea episode with brodie.
I can understand what your issues are with wayland, however in terms of specs, are there any particular ones you're actually eager for in order to stop working around hacks?
Here is another fun hack specific to kde: https://git.dec05eba.com/gpu-screen-recorder-ui/tree/tools/gsr-kwin-helper/gsrkwinhelper.js
I have to create a javascript file and then use dbus to ask kde to load it (as an extension). My application then sets up a dbus interface and the kde extension sends a dbus message to my application with the title of the focused application. The irony is that this makes the application less secure on wayland. The flatpak requires permission to load arbitrary extensions on the host kde system.
Last edited: