mainnika/weston
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

README: clarify libweston purpose/goals.

Browse Source 
v2: Rewrap, add a couple of missing words (Pekka).
v3: Use alternative wording (Yong).

Signed-off-by: Emil Velikov <emil.velikov@collabora.com>
Reviewed-by: Pekka Paalanen <pekka.paalanen@collabora.co.uk>
This commit is contained in:
Emil Velikov
2016-07-04 15:23:49 +01:00
committed by Pekka Paalanen
parent ad27693127
commit 99ac6232fa
1 changed files with 10 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README
+10 -10
View File
@@ -73,17 +73,17 @@ http://ometer.com/parallel.html
Libweston design goals Libweston design goals
---------------------- ----------------------
The high-level goal of libweston is that what used to be shell plugins The high-level goal of libweston is to decouple the compositor from
will be main executables. Instead of launching 'weston' with various the shell implementation (what used to be shell plugins).
arguments to choose the shell, one would be launching
'weston-desktop', 'weston-ivi', 'orbital', etc. The main executable
(the hosting program) links to libweston for a fundamental compositor
implementation. Libweston is also intended for use by other projects
who want to create new "Wayland WMs".
The libweston API/ABI will be separating the shell logic and main Thus, instead of launching 'weston' with various arguments to choose the
program from the rest of the "Weston compositor" (libweston shell, one would launch the shell itself, eg. 'weston-desktop',
internals). 'weston-ivi', 'orbital',etc. The main executable (the hosting program)
will implement the shell, while libweston will be used for a fundamental
compositor implementation.
Libweston is also intended for use by other project developers who want
to create new "Wayland WMs".
Details: Details: