Thank you Olivier! As I understand it, Wayland compositors are already compositing window managers. What aspect requires working outside of the protocol in this case? Absolute positions?
Thanks again, Joseph On Tue, Sep 5, 2017 at 8:51 PM, Olivier Fourdan <four...@gmail.com> wrote: > Hi, > > Xwayland is basically an X server, like any X server, it requires an X11 > Window manager for the users to manipulate the windows on screen (size, > location, stacking etc.) > > And since those X11 windows go along with Wayland native surfaces, it makes > a lot of sense to have that X11 window manager in the Wayland compositor. > > Cheers, > Olivier > > > On 5 September 2017 at 19:51, Joseph Burt <caseo...@gmail.com> wrote: >> >> Most Wayland compositors, Weston and WLC-based ones included, carry >> around a bit of XWM code, essentially a protocol extension, to deal >> with Xwayland. Why? What is lacking in Xwayland? >> >> Thanks, >> Joseph >> _______________________________________________ >> wayland-devel mailing list >> wayland-devel@lists.freedesktop.org >> https://lists.freedesktop.org/mailman/listinfo/wayland-devel > > _______________________________________________ wayland-devel mailing list wayland-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-devel
