[RFC] Input design

[Dan Nicholson]

On 4/19/07, Daniel Stone <daniel at fooishbar.org> wrote:
> On Fri, Apr 20, 2007 at 09:42:08AM +0930, Peter Hutterer wrote:
> > so how do we specify "all devices"? This is non-trivial.
> > The kernel puts all devices into /dev/input. that's nice, and we can
> > get hal to send us events when a new device comes in. However, this
> > falls short for at least two applications:
> > - bluetooth mice connected with hidd don't cause hal events.
> > this may be fixed in a newer release of hal (I'm still on dapper),
> > but it's annoying nevertheless. In the worst case, this could mean
> > that we can't enable bluetooth input devices because the server never
> > heard about it. this is...not good.
>
> HAL bug. :)

I'm not a hal developer, just lurk there, but work is ongoing on the
BlueZ hal addon. I don't know how good it is yet, but here's some
info:

http://wiki.bluez.org/wiki/HAL

> > and in addition, if there's multiple servers running on one box
> > (multiseat comes to my mind), we have two definitions of "all devices"
>
> Yep, this is the tricky bit.

This is another piece of ongoing work in hal. In tandem with
ConsoleKit, I think the plan is to have this work soon. I know that
multiseat/fast-user-switching has been something that David Zeuthen
has been striving for for a while. I think this is closer to reality
than you'd expect.

--
Dan