From ca658c15afd82301ff66a93d9b9516963d58ddf8 Mon Sep 17 00:00:00 2001 From: Peter Hutterer Date: Thu, 19 Jul 2018 11:06:50 +1000 Subject: [PATCH] doc: break up the "what is libinput" page with two sections Signed-off-by: Peter Hutterer --- doc/what-is-libinput.dox | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/doc/what-is-libinput.dox b/doc/what-is-libinput.dox index f361f0a..fd0f5b1 100644 --- a/doc/what-is-libinput.dox +++ b/doc/what-is-libinput.dox @@ -5,6 +5,8 @@ This page describes what libinput is, but more importantly it also describes what libinput is **not**. +@section what_libinput_is What libinput is + libinput is an input stack to be used by those applications that need full input device processing by commonly used input devices. That includes mice, keyboards, touchpads, touchscreens and graphics tablets. libinput handles @@ -26,6 +28,8 @@ touchpad in the Lenovo T440 and similar devices. While there may be use-cases for providing top software buttons on other devices, libinput does not do so. +@section what_libinput_is_not What libinput is not + libinput is **not** a project to support experimental devices. Unless a device is commonly available off-the-shelf, libinput will not support this device. libinput can serve as a useful base for getting experimental devices -- 2.7.4