wayland backend

[Antoine Martin]

We should be able to plug into wayland and provide remote access for it.

Reading ​this freerdp implementation, it doesn't look too hard.
The main difficulty may be in glueing the C api with our (mostly) python server code.

What makes this now more interesting than before is the availability of ​sub-surfaces - which would allow us to get YUV data for window's sub-regions (like an embedded video player in a browser), without effort.

[Antoine Martin]

Milestone renamed

[Antoine Martin]

More links:

• ​libweston-desktop: The goals of libweston-desktop are to make it easier to bring-up compositors and also to make it easier to support future versions of XDG_Shell.
• ​swc: A library for making a simple Wayland compositor
• ​wlc: Wayland compositor library
• ​tutorials: wayland-compositor: minimal wayland compositor
• ​https://fedoraproject.org/wiki/Wayland_features#remote_display: remote display for wayland

[Antoine Martin]

Milestone renamed

[Antoine Martin]

Recent discussion on ​wayland-devel with links:

• ​Remote display with 3D acceleration using Wayland/Weston: Therefore no support for hardware accelerated OpenGL gets advertised to clients, and clients fall back to software GL.. The hardest part in adding the support to the RDP-backend is implementing the buffer content access efficiently
• ​Remote display with 3D acceleration using Wayland/Weston: but Waltham does no good if you are already going to use VNC protocol or RDP or any other existing protocol.
• ​waltham: Waltham IPC Library : Waltham is a network IPC library designed to resemble Wayland both protocol and protocol-API wise. - probably not useful for us.

[Antoine Martin]

Out of time again.

[Antoine Martin]

New wiki: ​Wayland Remoting. It looks nowhere near ready yet.

[Antoine Martin]

This would also solve #510

See ​Writing a Wayland Compositor, Part 1: Hello wlroots