diff options
| author | Peter Hutterer <peter.hutterer@who-t.net> | 2018-07-26 09:18:29 +1000 |
|---|---|---|
| committer | Peter Hutterer <peter.hutterer@who-t.net> | 2018-07-27 09:35:00 +1000 |
| commit | d6d208ab1a549fe1d50121b51a316baece9fc432 (patch) | |
| tree | 6a819430a146f86ac50188f9a3675c069da2e83a /README.md | |
| parent | 6d8b10153c5e6a187585adef00b25b1029213d14 (diff) | |
| download | libinput-d6d208ab1a549fe1d50121b51a316baece9fc432.tar.gz | |
doc: move the Architecture blurb to the 'what is libinput' page
The vast majority of ppl reading the README is unlikely to care about this,
but they do care about the Wayland vs X.Org situation so let's split this up.
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 25 |
1 files changed, 0 insertions, 25 deletions
@@ -22,31 +22,6 @@ and the instructions on [reporting bugs](https://wayland.freedesktop.org/libinput/doc/latest/reporting_bugs.html). -Architecture ------------- - -libinput is not used directly by applications. Think of it more as a device -driver than an application library. It is used by the xf86-input-libinput -X.Org driver or Wayland compositors. The typical software stack for a system -running Wayland is: - -@dotfile libinput-stack-wayland.gv - -The Wayland compositor may be Weston, mutter, KWin, etc. Note that -Wayland encourages the use of toolkits, so the Wayland client (your -application) does not usually talk directly to the compositor but rather -employs a toolkit (e.g. GTK) to do so. The Wayland client does not know -whether libinput is in use. - -The simplified software stack for a system running X.Org is: - -@dotfile libinput-stack-xorg.gv - -libinput is not employed directly by the X server but by the -xf86-input-libinput driver instead. That driver is loaded by the server -on demand, depending on the xorg.conf.d configuration snippets. The X client -does not know whether libinput is in use. - Source code ----------- |