Originally posted by Scimmia
View Post
Announcement
Collapse
No announcement yet.
Enlightenment 0.19 Lands Full Wayland Support, Its Own Compositor
Collapse
X
-
Originally posted by devilhorns View PostThank You
When I get the XWayland support (for legacy applications) pushed into git (maybe this or next week), but Yes it is the first DE to run using Wayland (and not rely on Weston compositor) as far as I know.
This time xwayland wouldn't have a specific compositor interface and would be a real wayland client, so it's simpler for the compositor.
I remember everytime a change to the shell interface code in weston was merged, xwayland for weston got new bugs (fullscreen broken, bad stacking, etc).
So this change will simplificate life.
Comment
-
Originally posted by jern View Post
Comment
-
Originally posted by mannerov View PostI advise you to wait a bit, because they're rewritting how xwayland is handled.
This time xwayland wouldn't have a specific compositor interface and would be a real wayland client, so it's simpler for the compositor.
I remember everytime a change to the shell interface code in weston was merged, xwayland for weston got new bugs (fullscreen broken, bad stacking, etc).
So this change will simplificate life.
Comment
-
Originally posted by erendorn View PostNo, I think kwin intends to be a weston plugin, but gnome are using their own compositor.
Originally posted by KDE Wiki (What is Wayland)The display server is directly moved into the Compositor (that is KWin) and clients connect to this server through a Unix socket.
And from the same page:
Originally posted by KDE Wiki (Plasma Support in Wayland)The most complex task is to implement Wayland support in KWin, KDE Plasma's Compositor and Window Manager. Since 4.11 KWin has some initial Wayland support. It is not yet able to manage Wayland Clients but can use another Wayland compositor as a rendering target instead of X. This is the beginning of a Wayland session compositor running on top of a Wayland system compositor. Instructions on how to test it can be found in this blog post.
Comment
-
Originally posted by Nobu View PostNope:
And from the same page:
I still don't think KDE is at the point where they've finished deciding all that, but that was certainly their original plan. We'll see if they stick to it after they start implementing everything. The whole idea of a "system compositor" has kind of gone away, but they've replaced it with something largely equivalent.
Comment
-
Originally posted by smitty3268 View PostCalling it a "plugin" was probably wrong, but what you quoted is exactly what he meant - KWin would render into a system compositor, a.k.a. Weston, which is what would then talk to DRM, so that KWin wouldn't have to.
I still don't think KDE is at the point where they've finished deciding all that, but that was certainly their original plan. We'll see if they stick to it after they start implementing everything. The whole idea of a "system compositor" has kind of gone away, but they've replaced it with something largely equivalent.
From what I understood, they planned to implement the system compositor in the session manager (kdm, gdm, lightdm, etc.), which would make sense to me. Weston would be more of a stop-gap solution, to be used (for debugging/testing) until the DMs are "ready".
Comment
Comment