From 1ba6403c630da1fd7db26815cd56ebe077ab0d31 Mon Sep 17 00:00:00 2001 From: Mattias Andrée Date: Mon, 4 May 2015 00:02:37 +0200 Subject: info: wby not wayland MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Mattias Andrée --- doc/info/mds.texinfo | 44 +++++++++++++++++++++++++++++++++++++++++++- 1 file changed, 43 insertions(+), 1 deletion(-) (limited to 'doc') diff --git a/doc/info/mds.texinfo b/doc/info/mds.texinfo index d643f0a..ead66d5 100644 --- a/doc/info/mds.texinfo +++ b/doc/info/mds.texinfo @@ -6759,7 +6759,7 @@ Circles (bing) @kbd{ "p" "c"} composes the character presenting the back of a playing card. -Jokers and thumps are composed using the playing +Jokers and trumps are composed using the playing card back and two additional characters. @table @asis @@ -8409,6 +8409,7 @@ output servers, and even windowing servers. @menu * Server Architecture:: Discussion on fundamental design choices. * Fixing X.org Issues:: Can we avoid the problems X.org has? +* Why Not Wayland:: Why Wayland Won't Cut It. * Desktop Environments:: What are desktop environments' relationship to mds? @end menu @@ -8880,6 +8881,47 @@ in the server. +@node Why Not Wayland +@section Why Not Wayland + +Development of @command{mds} started out of +concern that Wayland would not meet our needs, +and the knowledge that X does not. We are now +however aware that Wayland meets our needs even +less than X.@footnote{Not even counting that +the documentation for Wayland is way more lacking +that X's documentation.} + +Wayland only has protocols for drawing onto a +buffer and input devices, and some very limited +output protocols. Wayland is inherently inflexible. +If anyone was to add additional functionally must +do so in the compositor --- the window manager --- +and publish to protocol. It is then up to all +other compostors (window managers) to implement +the protocol. + +It should be noted that Wayland does not even +have an official protocol for applying gamma +corrects. Some compositors (window managers) +choose to implement it by using @command{colord}. + +Additionally, screenshooting, screen recording +and global hotkeys must be implemented in the +compositor (window manager). Why? Because of +security. In Wayland, security always trumps +useability and usefulness. + +Another huge limitation of Wayland is that it +does not have any network protocol. For it to +be network, the compositor must implement a +network protocol --- and there is no official +network protocol. When this is all done, a +compositor proxy must be written that can +communicate with it. + + + @node Desktop Environments @section Desktop Environments -- cgit v1.2.3-70-g09d2