input server

Howdy,

I just started playing with Prex. Mainly just playing around, though I do have some
dreams about what I might do with it in the future. :)

Anyway, I've been reading through the code, and was pleased by how easy it was to
follow over all. I've been trying to find something fairly straight forward to
implement to get more comfortable with the code base, and it occured to me that keyboard
and mouse input might be better off if only a bare hardware interface was implemented in
the driver, and an input server was used to convert that to a character based on key mapping,
and to handle keeping track of mos position and button mapping and that sort of thing. getchar()
would then be switched around to communicate with the input server instead of reading from the
keyboard device.

Does this sound like a good way of handling input, or does it feel to heavy? I like that it moves
functionality out of the drivers, but I don't know how I feel about adding a layer of indirection
with the input server acting as a middle man.

Anyway, at the very least iI'll add a queue to the mouse driver. :)

Alex

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/