From 99ac6232fa1189debce10ace04c46f4304a92be7 Mon Sep 17 00:00:00 2001 From: Emil Velikov Date: Mon, 4 Jul 2016 15:23:49 +0100 Subject: [PATCH] README: clarify libweston purpose/goals. v2: Rewrap, add a couple of missing words (Pekka). v3: Use alternative wording (Yong). Signed-off-by: Emil Velikov Reviewed-by: Pekka Paalanen --- README | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/README b/README index 789755dc..1265ad19 100644 --- a/README +++ b/README @@ -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: