From f8a2729d7fc7096be9753996e3796e921e3d8f03 Mon Sep 17 00:00:00 2001 From: Peter Hutterer Date: Tue, 25 Aug 2020 14:30:17 +1000 Subject: [PATCH] README: add a graphic to illustrate how XWayland looks like Signed-off-by: Peter Hutterer --- README.md | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) diff --git a/README.md b/README.md index 2282513..b77a80d 100644 --- a/README.md +++ b/README.md @@ -231,6 +231,25 @@ connecting it to a `libeis` context in the compositor (PoC with Weston). This allows Xwayland to intercept XTEST events and route those through the compositor instead. +``` + +--------------------+ +------------------+ + | Wayland compositor |---wayland---| Wayland client B | + +--------------------+\ +------------------+ + | libinput | libeis | \_wayland______ + +----------+---------+ \ + | | +-------+------------------+ + /dev/input/ +---brei----| libei | XWayland | + +-------+------------------+ + | + | XTEST + | + +-----------+ + | X client | + +-----------+ +``` +Of course, XWayland is just another Wayland compositor, so the connection +between libei and libeis could be handled through a portal. + ### Short-lived applications **libei** is not designed for short-lived fire-and-forget-type applications