mirrors/wayland
1
0
Fork 0
mirror of https://gitlab.freedesktop.org/wayland/wayland.git synced 2025-11-01 22:58:40 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions

doc: Capitalize all Wayland occurrences

Browse source 
Signed-off-by: Tiago Vignatti <tiago.vignatti@intel.com>
Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net>

[re-run of search/replace after rebasing]

Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
This commit is contained in:
Tiago Vignatti 2013-04-04 11:28:57 +10:00 • committed by Kristian Høgsberg
parent 4f7f09b4c8
commit 5e014c81cc
5 changed files with 19 additions and 19 deletions
Download patch file Download diff file Expand all files Collapse all files

10
doc/publican/sources/Compositors.xml
View file

@ -77,7 +77,7 @@
</listitem>
<listitem>
<para>
fullscreen X session under wayland
fullscreen X session under Wayland
</para>
</listitem>
</itemizedlist>
@ -92,13 +92,13 @@
Wayland doesn't directly allow this, but clients can communicate GEM
buffer names out-of-band, for example, using D-Bus, or command line
arguments when the panel launches the applet. Another option is to
use a nested wayland instance. For this, the wayland server will have
use a nested Wayland instance. For this, the Wayland server will have
to be a library that the host application links to. The host
application will then pass the wayland server socket name to the
embedded application, and will need to implement the wayland
application will then pass the Wayland server socket name to the
embedded application, and will need to implement the Wayland
compositor interface. The host application composites the client
surfaces as part of it's window, that is, in the web page or in the
panel. The benefit of nesting the wayland server is that it provides
panel. The benefit of nesting the Wayland server is that it provides
the requests the embedded client needs to inform the host about buffer
updates and a mechanism for forwarding input events from the host
application.