if its internal, as they said, its not as intended? as the described it, its designed for compositors. which implies, an application using it could lead to conflicting behaviors with the compositor and WM.
This is probably why they’re like “we cant support that” because it’d conflict with what mutter is doing.
doesn’t make it any less a mess but the GNOME devs probably have a point.
This interface should be suitable for the implementation of many desktop shell components, and a broad number of other applications that interact with the desktop
Suitable. Not strictly, and certainly not private. Everyone else, KDE included, have managed to make this work fine.
I might add that I’m quite well aquianted with this protocol as it comes up in a lot of projects I’m involved with.
Ah yes, API abuse. Which is when you use the API as intended and written.
Gnome devs are completely out of touch.
if its internal, as they said, its not as intended? as the described it, its designed for compositors. which implies, an application using it could lead to conflicting behaviors with the compositor and WM.
This is probably why they’re like “we cant support that” because it’d conflict with what mutter is doing.
doesn’t make it any less a mess but the GNOME devs probably have a point.
https://wayland.app/protocols/wlr-layer-shell-unstable-v1
Suitable. Not strictly, and certainly not private. Everyone else, KDE included, have managed to make this work fine.
I might add that I’m quite well aquianted with this protocol as it comes up in a lot of projects I’m involved with.