From: Thomas W. <tw...@us...> - 2004-09-24 06:43:56
|
Petri Damstén wrote: >On Thursday 23 September 2004 19:07, Rob Shortt wrote: > > >> - Define and refine an input architecture for Freevo. >> >> I really like your idea of a clean input architecure! This would simplify the installation because one more dependency is out of the way. >This might be good place to re-think about mouse support in freevo. I think >that most of the input devices can be put either of these groups: > >1. Arrow keys + buttons >- Keyboards, Joysticks, Remotes, Mobile phones, ... >2. Pointer + buttons >- Mouse, Touchscreen, Trackball, Touchpad, ... > >Group one works nicely with freevo now, but group two would need some work. >Maybe something like that detached player for extra buttons and ability to >select items with cursor would be enough. Well atleast it might be good idea >to think about this if the input architecture is rewritten. > > First thought: Are there really users which want to use a mouse when they are sitting in their livingroom?? Second thought: Still, it might be a good idea to have generic mouse support in the architecture. Imagine a web browser plugin (gecko engine in a custom frame or just a skinned firefox), it would be certainly annoing to use up/down buttons to reach the links, for example. Third thought: You are right, we should think of it :-) Greetings, -- Thomas |