inlined<br><br><div class="gmail_quote">On Tue, Jul 21, 2009 at 2:08 AM, Dr. H. Nikolaus Schaller <span dir="ltr"><<a href="mailto:hns@computer.org">hns@computer.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div style="word-wrap:break-word"><br><div><div>Am 21.07.2009 um 10:52 schrieb steven mosher:</div><div class="im"><br><blockquote type="cite"><br><br><div class="gmail_quote">On Tue, Jul 21, 2009 at 12:34 AM, Dr. H. Nikolaus Schaller <span dir="ltr"><<a href="mailto:hns@computer.org" target="_blank">hns@computer.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-color:rgb(204, 204, 204);border-left-style:solid;padding-left:1ex"> <div style="word-wrap:break-word">
Ouch!<div><br></div><div>So you need to connect a mouse that is larger than the device to position any scrollbars or press buttons? Or does it have a large enough trackpad somewhere?</div> </div></blockquote><div><br></div>
<div> There is a 4 way key that can be used for up/down/right/left. etc . And an additional</div><div> key for up and down. ( or vol+- ) </div><div><br></div><div> Not sure where you got the mouse idea. </div></div>
</blockquote><div><br></div></div>That is "my own view" (TM) what is needed to make it useable.</div></div></blockquote><div><br></div><div> useable as? </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div style="word-wrap:break-word"><div></div><div><br></div><div>Have you ever tried to operate a UI with the mouse-pointer paradigm through arrow keys?</div></div></blockquote><div><br></div><div> Yup. Size of the screen plays a role in this as does the application.</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div style="word-wrap:break-word"><div></div><div><br></div><div>So I expect that someone needs to write is a complete UI stack for arrow-key-only operation. Plus applications. No compatibility to most FOSS. Unless we restrict the Non-G-UI to commandline and ncurses.</div>
</div></blockquote><div><br></div><div> not so sure about that. I tend not to underestimate the creativity of software developers.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div style="word-wrap:break-word"><div><div class="im"><blockquote type="cite"><div class="gmail_quote"> <blockquote class="gmail_quote" style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-color:rgb(204, 204, 204);border-left-style:solid;padding-left:1ex">
<div style="word-wrap:break-word"><div><div><div><br></div><div>What I wonder is how it will compare to this one:</div> <div><br></div><div><span style="white-space:pre"> </span><a href="http://en.wikipedia.org/wiki/Zipit_Wireless_Messenger_(Z2)" target="_blank">http://en.wikipedia.org/wiki/Zipit_Wireless_Messenger_(Z2)</a></div>
<div><br> </div> <div>and its community project - it appears also to be quite open - but not free(dom):</div><div><br></div><div><span style="white-space:pre"> </span><a href="http://linux.zipitwireless.com/" target="_blank">http://linux.zipitwireless.com/</a></div>
</div></div></div></blockquote><div><br></div><div> And it locks you into a service plan. Not much point in comparing apples and oranges. </div></div></blockquote><div><br></div></div><div>Hint: they have approx. 3 or 4 years experience with this device class and users of such devices. And they may have an (economic) reason to offer that with a service plan...</div>
</div></div></blockquote><div><br></div><div> Yes, of course. But I think it serves no useful purpose to compare devices that are sold</div><div> on a different basis for different reasons. Service plans, as we all know, help to subsidize</div>
<div> the hardware. So for example, I have to live with my ATT phone for 2 years before I can upgrade</div><div> it. For me an unlocked feature phone is superior to locked smart phone. Why? because</div><div> my principles put freedom ahead of technology. </div>
<div><br></div><div> Let me put it another way.. What Qi hardware is about is changing</div><div> the way design is done, just as you encouraged us to.. We start with the NanoNote and then we open that device, the hardware</div>
<div> the schematics, the roadmap. So, in essence we are not just selling a device. Not merely</div><div> putting linux on a device and calling it open. We too are selling a service. That service is</div><div> open hardware and open roadmap. We are doing everything the community asked us</div>
<div> to do while we were at OM. These are our important check boxes: GPL the code, open</div><div> the schematics,upstream the kernel, Open the roadmap process. Those aren't product features, those are service guarantees. As members of the community when we start down the path of comparing closed devices to open devices and partially open devices to open devices we get our principles out of order. </div>
<div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><br>_______________________________________________<br>
Openmoko community mailing list<br>
<a href="mailto:community@lists.openmoko.org">community@lists.openmoko.org</a><br>
<a href="http://lists.openmoko.org/mailman/listinfo/community" target="_blank">http://lists.openmoko.org/mailman/listinfo/community</a><br>
<br></blockquote></div><br>