[PATCH weston 1/4] README: clarify libweston purpose/goals.
emil.l.velikov at gmail.com
Fri Jun 3 13:27:36 UTC 2016
From: Emil Velikov <emil.velikov at collabora.com>
v2: Rewrap, add a couple of missing words (Pekka).
Signed-off-by: Emil Velikov <emil.velikov at collabora.com>
README | 22 +++++++++++-----------
1 file changed, 11 insertions(+), 11 deletions(-)
diff --git a/README b/README
index 110a14b..76be7b9 100644
@@ -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
+The high-level goal of libweston is to decouple the compositor from
+the the shell logic (what used to be shell plugins).
+Thus the instead of having a single 'weston' launched with various
+arguments to choose the shell, one would be launching 'weston-desktop',
+'weston-ivi', 'orbital', etc. The main executable (the hosting program)
+will implement the shell, while libweston will be used for a fundamental
+Libweston is also intended for use by other projects who want to create
+new "Wayland WMs".
More information about the wayland-devel