Input device design
krahn at niehs.nih.gov
Wed Aug 31 14:20:08 PDT 2005
An "input device library" in this case would essentially be an X-Server
module interface. That should be easy to implement, and very useful for
debugging input modules.
I also think it would not become "mush" as long as the library client is
willing to see input events described the way X clients see them.
Brian Paul wrote:
> I really don't know much about input devices and the issues for the X
> server, but one thing is on my mind. Would it be possible to create
> an "input device library" that could be used both by the X server and
> other programs which don't use X?
> Consider that when we get the extended EGL stuff working, we'll have
> an OpenGL environment that can be used independently of the X server.
> It would be nice to have a complementary input library.
> The upsides for such a library are obvious: reusability, modularity,
> portability, versatility, etc.
> The downside is it could be over-engineered to the point where it's a
> big, over-generalized, ambiguous pile of mush.
> Is something like this feasible?
> Looking at the big picture, an X server layered on EGL/OpenGL and such
> an input library might not contain any device-specific code at all.
> xorg mailing list
> xorg at lists.freedesktop.org
More information about the xorg