Originally posted by devilhorns
View Post
Announcement
Collapse
No announcement yet.
Rasterman: Enlightenment To Have Full Wayland Support
Collapse
X
-
Reason for each desktop to build their own compositors?
This has probably answered before but what's the reason for each desktop to build their own Wayland compositors instead of having them all use and work on the Weston compositor? It seems like there's an awful lot of duplicate work being done across the various projects that could instead be redirected into making Weston awesome?
Comment
-
Originally posted by damg View PostThis has probably answered before but what's the reason for each desktop to build their own Wayland compositors instead of having them all use and work on the Weston compositor? It seems like there's an awful lot of duplicate work being done across the various projects that could instead be redirected into making Weston awesome?
also tech Demo
Comment
-
Originally posted by damg View PostThis has probably answered before but what's the reason for each desktop to build their own Wayland compositors instead of having them all use and work on the Weston compositor? It seems like there's an awful lot of duplicate work being done across the various projects that could instead be redirected into making Weston awesome?
There was an idea discussed that basically came down to there will be one shared system compositor, and then Gnome/Kwin/Enlightenment/etc will implement their own session compositor (mutter/kwin/E...something/etc). Not sure what ever came from that discussion...All opinions are my own not those of my employer if you know who they are.
Comment
-
Originally posted by Ericg View PostWeston isn't meant to be used in production for one... its the developers playground and testbed for protocol support. Its not meant to be the fastest (read: optimizatized) its not meant to be a fully featured desktop. Its a place for the wayland devs to make sure the protocol works as expected.
There was an idea discussed that basically came down to there will be one shared system compositor, and then Gnome/Kwin/Enlightenment/etc will implement their own session compositor (mutter/kwin/E...something/etc). Not sure what ever came from that discussion...
Comment
-
Originally posted by Ericg View PostRaster, I'm assuming you've brought up these concerns with krh and the likes? Changes needed to core is kind of a red flag...
devilhorns == Chris Michael == the guy doing the majority of the Wayland work in E and EFL
Originally posted by Ericg View Post...
There was an idea discussed that basically came down to there will be one shared system compositor, and then Gnome/Kwin/Enlightenment/etc will implement their own session compositor (mutter/kwin/E...something/etc). Not sure what ever came from that discussion...Last edited by Scimmia; 23 July 2013, 06:09 PM.
Comment
-
Originally posted by damg View PostThis has probably answered before but what's the reason for each desktop to build their own Wayland compositors instead of having them all use and work on the Weston compositor? It seems like there's an awful lot of duplicate work being done across the various projects that could instead be redirected into making Weston awesome?
Comment
-
Originally posted by mrugiero View PostThe same duplicated efforts on having several window managers and desktops. Remember a compositor takes the role the window manager had on X.org.
Comment
-
Comment