IMHO the user input should be ABSTRACTED unlike in traditional OSes. An average application should receive "user actions" from the OS rather than directly the key strokes, unless it needs to. Having more keyboards, mices etc. should be possible too. ATM such abstraction is not necessary (or even possible), but we'll probably need to rethink on it later on. Once we have more sophisticated kernel with some runtime support, coding the rest will be a lot of fun, more OO and .NET way.
Just a floating thought: the key to the performance for a long run in such a system is the memory manager, even if you got a 10 GHz CPU and a perfectly optimized scheduler it will perform like a junk when everything stops to GC for 1 second every 5 or everything got swapped in and out from HDD all the time. Happy new year to everyone :) Dennis Hayes wrote: > Nice, but I think more inportiant is getting stuff working. > If you have a basic English keyboard working, I would advise moving on > to other things. > Most people will either be using English, or can use it, and will be > used to badly written software requiring it. > Later maybe another volunteer will add mapping and stuff for other > languages. > > I don't want to be a bigot here, I am just pointing out that getting > other devices/commands/functionality/etc. working is more importiant > than planing ahead for weird devices, or even more common devices like > non-english keyboards. > > It will be very imnportiant to suport other languages, and the sooner > the better, but with limited resources, we (umm you) need to keep > tight priorities. > > > Thanks, > Dennis > > > */Jonathan Chayce Dickinson <[EMAIL PROTECTED]>/* wrote: > > 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 > > > ------------------------------------------------------------------------ > Looking for last minute shopping deals? Find them fast with Yahoo! > Search. > <http://us.rd.yahoo.com/evt=51734/*http://tools.search.yahoo.com/newsearch/category.php?category=shopping> > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------- > 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 > ------------------------------------------------------------------------- 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
