4 ms·
Right, the shift away from X doesn't mean the death of using GUI apps remotely, it just means moving to a Remote Desktop model instead of telling apps that thei
by Spivak 6y ago
Right, the shift away from X doesn't mean the death of using GUI apps remotely, it just means moving to a Remote Desktop model instead of telling apps that their render target is your X server through a tunnel.
- pmoriarty 6y agoCould you flesh this out a bit? What is the official Wayland model for doing "Remote Desktop"?
- Spivak 6y agoI hesitate to call it an official model but the short version of the current direction is that the compositor acts as the glue -- providing the final rendered scene and the final merged audio stream to the client over some protocol (like VNC but doesn't have to be) and providing inputs and events to itself and the client applications. How all of this works on the backend is a combination of PipeWire to multiplex video sources and PulseAudio to multiplex audio sources. There's nothing outright preventing something like X forwarding and https://mstoeckl.com/notes/gsoc/blog.html https://mstoeckl.com/notes/gsoc/blog.html is a really cool project that makes it work. From that author: > The main difficulty in producing such a tool is that Wayland protocol messages primarily include control information, and the large data transfers of graphical applications are implemented through shared memory. waypipe must then identify and serialize changes to the shared memory buffers into messages to be transferred over a socket.
- donio 6y agoWhat if I don't want a remote desktop though? 99% of the time I only want a the remote application I am interested in to seamlessly display on my screen, why do I have to bring along a full desktop? Seems like such a fundamental use case that should be made simple but is ignored (or made very difficult) by modern systems.
- freeone3000 6y agoWhat implementation of a remote desktop model currently exists for Wayland?
- Spivak 6y agoThe "big two" have implementations. Definitely not mature but it's getting there. https://wiki.gnome.org/Projects/Mutter/RemoteDesktop https://wiki.gnome.org/Projects/Mutter/RemoteDesktop https://docs.kde.org/trunk5/en/kdenetwork/krfb/krfb-configuration.html https://docs.kde.org/trunk5/en/kdenetwork/krfb/krfb-configur... You most likely won't see an implementation "for Wayland" because that's like asking for a websocket implementation "for HTTP" the actual compositors that speak Wayland need to implement remote desktop capabilities and then expose an API for managing remote desktop sessions (org.freedesktop.portal.RemoteDesktop) to programs that want to leverage it.
- deleted 6y ago[deleted]
- spear 6y agoI haven't tried it, but there's also this one for wlroots-based compositors (eg. sway): https://github.com/any1/wayvnc https://github.com/any1/wayvnc