40 ms·
To be clearer, as each wayland desktop pretty much creates their own incompatible wayland compositor (because wayland protocol is minimal and not feature comple
by superkuh 10mo ago
To be clearer, as each wayland desktop pretty much creates their own incompatible wayland compositor (because wayland protocol is minimal and not feature complete) this is just a guide to fixing the hyperland broken wayland desktop. Not all waylands' broken desktops.
- ChocolateGod 10mo agoWhat protocol is missing from Wayland? Yes Wayland doesn't have a printer protocol like Xorg, I know.
- singron 10mo agohttps://gitlab.freedesktop.org/wayland/wayland-protocols/-/tree/main?ref_type=heads https://gitlab.freedesktop.org/wayland/wayland-protocols/-/t... This is an incomplete list of protocols that aren't part of core Wayland. Compositors implement additional protocols that aren't even part of this process (e.g. wlr-screencopy-unstable). See the wlroota protocols here: https://gitlab.freedesktop.org/wlroots/wlroots/-/tree/master/protocol?ref_type=heads https://gitlab.freedesktop.org/wlroots/wlroots/-/tree/master...
- ChocolateGod 10mo agoRight but there's the xdg-portal for screen capture which runs through Pipewire and supports sand-boxing (because its negotiated over dbus), which all the main compositors support. Just because a protocol isn't part of Wayland, doesn't mean a standard protocol does not exists.
- deleted 10mo ago[deleted]
- superkuh 10mo agoThe big ones missing for me are accessibility support (ie, screen readers) and mouse/keyboard input support for basic things like keyboard sharing.