Petri Damst�n wrote:
On Thursday 23 September 2004 19:07, Rob Shortt wrote:I really like your idea of a clean input architecure!
- Define and refine an input architecture for Freevo.
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:First thought:
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.
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
------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php _______________________________________________ Freevo-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freevo-devel
