Schedule: Fixing X input
| Speakers | |
|---|---|
|
Daniel Stone |
| Schedule | |
| Day | Sunday |
| Room | H.2213 |
| Start time | 12:00 |
| End time | 13:00 |
| Duration | 01:00 |
| Info | |
| Event type | Podium |
| Track | X.org |
| Language | English |
X input is currently a horrible tangled mess. It's primarily comprised of three components: core input, which doesn't believe in multiple input devices or different layouts; XKB, which does everything for keyboards except mapping keys, and XInput, which enables applications to actually deal with input devices separately. XKB is a hacked-together mess that only the maintainer understands, and XInput is only used by one application. Input in X is currently undergoing a huge cleanup, and also growing to become useful, as with the multi-pointer X work.
X input is currently a horrible mess of spaghetti code that is conceptually broken. But that's okay, because the implementation is also abysmal. At linux.conf.au, our fearless input ninjas (Daniel Stone and Petter Hutterer of MPX fame) sat down at a pub and devised a back-of-a-coaster plan to actually properly fix input once and for all, and make it even remotely understandable.
This talk will present the current problems, and the plan for moving forward.