<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Dec 14, 2010, at 3:55 PM, Jason Grossman wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">
<div style="background-color: rgb(255, 255, 255); position: static; z-index: auto; ">
<span style="display:none"> </span>
<div id="ygrp-text"><p><br>
On 15/12/2010, at 1:51 AM, Jan-Paul Bultmann wrote:<br>
<br>
> The other thing is, maybe we should pick a device and make it the main supported platform for self.<br>
> I was thinking about something like this <br>
> <a href="http://www.alwaysinnovating.com/products/touchbook.htm">http://www.alwaysinnovating.com/products/touchbook.htm</a><br>
<br>
It might be good to focus on one platform, but I don't think it should be a touchpad. Self would have to change a LOT to be useable without a mouse.</p></div></div></div></div></blockquote>I think the opposite is the case.</div><div>You can easily simulate a 3 button mouse with gestures, even if it is as simple as counting the fingers :).</div><div>The size constraints as mentioned in the article could be easily solved by some zooming work.</div><div><br></div><div>We could then gradualy move the interface to be more touch friendly.</div><div><br></div><div><br></div><div><br></div><div><br></div><div><blockquote type="cite"><div style="background-color: rgb(255, 255, 255); position: static; z-index: auto; "><div id="ygrp-mlmsg" style="position:relative;"><div id="ygrp-msg" style="z-index: 1;"><div id="ygrp-text"><p> See <a href="http://arstechnica.com/microsoft/news/2010/07/ballmer-and-microsoft-still-doesnt-get-the-ipad.ars">http://arstechnica.com/microsoft/news/2010/07/ballmer-and-microsoft-still-doesnt-get-the-ipad.ars</a> for some examples of how an environment has to be designed for touch interaction. This is something Apple's been able to (and had to) put a bazillion person-hours into for the iPad OS.<br>
<br></p></div></div></div></div></blockquote><div>And c'mon it's obvious why microsoft won't get close to the ipad :D they still do things like this ( <a href="http://www.pcmasters.de/fileadmin/news/Microsoft/Microsoft-Windows-Phone-7.jpg">http://www.pcmasters.de/fileadmin/news/Microsoft/Microsoft-Windows-Phone-7.jpg</a> )</div><div>which designer had the idea of leaving 1/5 of the screen unused so you can display a round button in the top right corner ... that will lead you to a list of everything on the phone that you can't even sort (like on the macbook wheel). :)</div><div><br></div><div>So my point is, as long as we don't do dumb shit we will be ok :)</div><div><br></div><div>UI2 is already a lot like multitouch interfaces for touch tables just take a look at things like</div><div>PyMt <a href="http://pymt.eu/">http://pymt.eu/</a></div><div>and the demo reels at nuigroup</div><div><a href="http://nuigroup.com/tv/">http://nuigroup.com/tv/</a></div><div><br></div><div>The only things that are a bit different are the popup style menus in self, but that is nothing that a circular menu couldn't sovle :).</div><div><br></div><blockquote type="cite"><div style="background-color: rgb(255, 255, 255); position: static; z-index: auto; "><div id="ygrp-mlmsg" style="position:relative;"><div id="ygrp-msg" style="z-index: 1;"><div id="ygrp-text"><p>
Jason</p>
</div>
<!-- end group email -->
</blockquote></div>I think the hard thing about this is not the design of the multitoch capable morphs.<div>It is rather the rework of self's rendering system, that we should do before.</div><div><br></div><div>Cheers Jan</div></body></html>