<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
--></style>
</head>
<body class='hmmessage'>
Hi All...<div><br></div><div>See comment/question below....</div><div><br></div><div>Caryl<br><br>> From: wad@laptop.org<br>> Date: Thu, 3 Jun 2010 17:27:12 -0400<br>> To: cscott@cscott.net<br>> CC: marketing@lists.sugarlabs.org; tomeu@sugarlabs.org; iaep@lists.sugarlabs.org; rafael@sugarlabs.org<br>> Subject: Re: [IAEP] [Marketing] OLPC rules out Windows for XO-3<br>> <br>> <br>> After spending some time with touch based devices,<br>> I have to agree with Scott. Yes, you can "bolt on"<br>> support for single touch to many activities, but doing<br>> a good job of supporting multitouch is typically a complete<br>> UI redesign.<br>> <br>> We are trying to get an accelerometer into the design<br>> as well as touch, better supporting these new UIs.</div><div><br></div><div><p style="margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Helvetica"><br></p>
<p style="margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Helvetica; min-height: 14.0px"><br></p>
<p style="margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Helvetica"><span class="Apple-style-span" style="font-size: 10pt; "><font class="Apple-style-span" face="Verdana">An accelerometer huh? Does this mean XO-3 users will be able to participate in this international "Quake Catcher Network"? That would be very neat! (Said "wearing my retired-science-educator-hat")</font></span></p>
<p style="margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Helvetica; min-height: 14.0px"><span class="Apple-style-span" style="font-size: 10pt; "><font class="Apple-style-span" face="Verdana"><br></font></span></p>
<p style="margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Helvetica"><a href="http://scienceforcitizens.net/project/239/"><span class="Apple-style-span" style="font-size: 10pt; "><font class="Apple-style-span" face="Verdana">http://scienceforcitizens.net/project/239/</font></span></a></p>
<p style="margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Helvetica; min-height: 14.0px"><span class="Apple-style-span" style="font-size: 10pt; "><font class="Apple-style-span" face="Verdana"><br></font></span></p>
<p style="margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Helvetica"><br></p></div><div><br></div><div><br>> <br>> On Jun 3, 2010, at 1:45 PM, C. Scott Ananian wrote:<br>> <br>> > I strongly encourage the Sugar team to consider rethinking the Sugar<br>> > UI from the ground up for touch. The "simple" port is likely to yield<br>> > a very unsatisfactory experience; "fat fingers" are just not precise<br>> > pointing devices, and a lot of gestures which seem intuitive for a<br>> > mouse don't really work for touch. In the same vein, there are many<br>> > finger gestures which are intuitive which aren't being exploited in<br>> > the mouse-based UI. And, of course, the whole "pop up a keyboard" to<br>> > type thing is weird now; keyboard shortcuts and special "home", "view<br>> > source", etc, keys don't work as well. Everything needs a place on<br>> > screen.<br>> > <br>> > My suggestion would be to first convene a "ground up rethink" of what<br>> > a touch-based Sugar could be. Then, realizing that the best is the<br>> > enemy of the good and the realistic limits on Sugar development, draw<br>> > up a "from here to there" plan concentrating on grabbing the<br>> > lowest-hanging fruit first (perhaps a redesign of the home screen, or<br>> > rethinking palette menus, or whatever) and embarking on an incremental<br>> > strategy to adapt.<br>> > <br>> > Software engineers like to think in terms of generalities, and "what<br>> > can we do that's not too hard", but I'm suggesting that's *not* the<br>> > most fruitful way to approach adaptation to touch. The engineering<br>> > thinking should be *second*. Design and user experience should be<br>> > first. Every designer should probably be required to have spent<br>> > serious time with an iPhone or iPad or touchscreen phone (preferably<br>> > from a variety of different touch-based OSes) to be sure we're not<br>> > just mapping mouse onto touch. Ideally, take some time to give an<br>> > iPad to a 3-6 yr old and watch and learn. The result should be a<br>> > *book*, which describes the ideal UI. That will be the long term<br>> > (think, next decade!) goals for Sugar.<br>> > <br>> > I'd personally like to see the Sugar team come up with bold ideas that<br>> > go *beyond* what we're seeing in Android and iPhone OS; in particular,<br>> > how to best enable *content creation*. We've always said we'd like to<br>> > see a movie editing application in Sugar. Concentrating on what<br>> > Record or Etoys or TurtleArt might look like with a touch-based UI<br>> > would be bold thinking that would radically advance Sugar's mission.<br>> > What does it mean to have the entire environment written in Python, if<br>> > Python is clumsy and hard to use with a touch-based interface? Maybe<br>> > the direct-manipulation model of Etoys is a more natural fit? What<br>> > does "view source" mean in a touch-enabled world?<br>> > <br>> > I look forward to exciting times and crazy great ideas!<br>> <br>> Yep!<br>> <br>> Cheers,<br>> wad<br>> <br>> --scott<br>> > <br>> > -- <br>> > ( http://cscott.net/ )<br>> > _______________________________________________<br>> > IAEP -- It's An Education Project (not a laptop project!)<br>> > IAEP@lists.sugarlabs.org<br>> > http://lists.sugarlabs.org/listinfo/iaep<br>> <br>> _______________________________________________<br>> IAEP -- It's An Education Project (not a laptop project!)<br>> IAEP@lists.sugarlabs.org<br>> http://lists.sugarlabs.org/listinfo/iaep<br></div>                                            </body>
</html>