Can I tell you what I envisioned?
I recently saw a new keyboard on the net, it had LCD screens on the keys
(yep, you heard me right). Now what if we were to support stuff like
that out of the box?
Firstly, if we consider this the whole key map problem flies out of the
window. So does the notion of a keyboard (which will hopefully make us
future compliant). The idea comes from my directx days.
In directx all controls are abstracted away and you just deal with
commands like "Jump" and "Move Left,Right".
So a keyboard would be a device with 110 axes. Given that, the typical
events would be "AxisChanged (float delta)". Obviously a keyboard would
report "AxisChanged(1)" for a keydown and "AxisChanged(-1)" for a keyup.
But this is where it gets very interesting. Let's take keyboard
shortcuts for example: the host program would take the OS keymap and
augment it as follows:
Find Ctrl (store as a)
Find C (store b)
Copy = a -> b
Now imagine what would happen with that keyboard. You hit CTRL and then
all the LCDs change to the shortcuts, most notably, a copy icon instead
of C.
VS 2005+ has chords. That is when you hold down Ctrl followed by two keys.
E.g. Fold All Code = ctrl -> m -> o
A mouse would simply be a device with two axes (for the x,y) and 3-many
other axes (for other buttons, the wheel, and the 'tilter' on the new
mice these days).
But in any case, let's just leave keymaps as are until we have drivers.
Because the kernel keymaps will fall away anyway.
--
Jonathan Dickinson
-------------------------------------------------------------------------
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/
_______________________________________________
SharpOS-Developers mailing list
SharpOS-Developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sharpos-developers
