Commit 99ac6232 authored by Emil Velikov's avatar Emil Velikov Committed by Pekka Paalanen
Browse files

README: clarify libweston purpose/goals.



v2: Rewrap, add a couple of missing words (Pekka).
v3: Use alternative wording (Yong).
Signed-off-by: Emil Velikov's avatarEmil Velikov <emil.velikov@collabora.com>
Reviewed-by: Pekka Paalanen's avatarPekka Paalanen <pekka.paalanen@collabora.co.uk>
parent ad276931
......@@ -73,17 +73,17 @@ http://ometer.com/parallel.html
Libweston design goals
----------------------
The high-level goal of libweston is that what used to be shell plugins
will be main executables. Instead of launching 'weston' with various
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
program from the rest of the "Weston compositor" (libweston
internals).
The high-level goal of libweston is to decouple the compositor from
the shell implementation (what used to be shell plugins).
Thus, instead of launching 'weston' with various arguments to choose the
shell, one would launch the shell itself, eg. 'weston-desktop',
'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:
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment