Re: multitouch + audio feedback linux dev -> XO-2?

2009-01-27 Thread Wade Brainerd
On Mon, Jan 26, 2009 at 11:57 PM, wrote: > On Mon, 26 Jan 2009, Wade Brainerd wrote: > > Here's to staying focused, >> > > agreed, but I don't see how you can do a keyboard and not have some > multi-touch stuff (shift keys to start with) > > I am in the group that has serious doubts about the cur

Re: multitouch + audio feedback linux dev -> XO-2?

2009-01-26 Thread david
On Mon, 26 Jan 2009, Wade Brainerd wrote: > My (unasked for) opinion is that multitouch should not be a focus of OLPC's > development efforts. The real benefit will just come from being able to > touch the screen in the first place. > > Writing a decent multitouch interface requires massive UI de

Re: multitouch + audio feedback linux dev -> XO-2?

2009-01-26 Thread Wade Brainerd
My (unasked for) opinion is that multitouch should not be a focus of OLPC's development efforts. The real benefit will just come from being able to touch the screen in the first place. Writing a decent multitouch interface requires massive UI design and coding efforts that we frankly cannot muste

Re: multitouch + audio feedback linux dev -> XO-2?

2009-01-26 Thread david
On Tue, 27 Jan 2009, Carlos Nazareno wrote: > 1) Are there any existing hooks/systems for Linux for multi-touch? > That's the only proper way you can get a virtual keyboard to work for > a double-touchscreen clamshell device (the feasibility of which is not > sold to me because of the power consum

Re: multitouch + audio feedback linux dev -> XO-2?

2009-01-26 Thread Nate Ridderman
On Mon, Jan 26, 2009 at 7:22 PM, Nirav Patel wrote: > 1) Are there any existing hooks/systems for Linux for multi-touch? >> That's the only proper way you can get a virtual keyboard to work for >> a double-touchscreen clamshell device (the feasibility of which is not >> sold to me because of the

Re: multitouch + audio feedback linux dev -> XO-2?

2009-01-26 Thread Nirav Patel
> 1) Are there any existing hooks/systems for Linux for multi-touch? > That's the only proper way you can get a virtual keyboard to work for > a double-touchscreen clamshell device (the feasibility of which is not > sold to me because of the power consumption of running a 2nd screen vs > a keyboard