After really digging the archives I came across one thread [1] that has a lot of good information on the limits of the Glamo and what has been tried already to get more usefulness out of it. I think it would be good to have some of the information from that thread on the wiki. Any suggestions on a good page for it?<br>
<br>It seems for now, trying to work around the scrolling and clipping graphics as Lally mentioned might be the best course of action. A limited driver supporting OpenGL ES 1.1 at 320x240 resolution would still be nice, but that won't solve any of issues with the user interface.<br>
<br>-Jacob<br><br>[1] <a href="http://lists.openmoko.org/nabble.html#nabble-td19892|a19892">http://lists.openmoko.org/nabble.html#nabble-td19892|a19892</a><br><br><br><div class="gmail_quote">On Sat, Nov 15, 2008 at 12:09 AM, Lally Singh <span dir="ltr"><<a href="mailto:lally.singh@gmail.com">lally.singh@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">The biggest usability issue with the graphical performance on the Moko<br>
is scrolling/clipping graphics.<br>
<br>
If we had the ability to upload an image to the glamo, clip it, and<br>
then pan it in the clip rectangle, a lot of the perceived slowness<br>
wouldn't be a problem. As long as the controls were visually<br>
responsive, they can have old state. People can manage with controls<br>
that show old data, as long as they respond when you interact with<br>
them.<br>
<br>
A few custom GTK widgets that manage the glamo for this sort of thing<br>
(e.g. the large scroll window for applications, etc) would likely<br>
result in worlds of improvement.<br>
<br>
.. or, something fancier... but I think this'd be a great step forward.<br>
<br>
-ls<br>
<div><div></div><div class="Wj3C7c"><br>
On Fri, Nov 14, 2008 at 2:14 PM, Riccardo Centra <<a href="mailto:hiretto@gmail.com">hiretto@gmail.com</a>> wrote:<br>
><br>
> 2008/11/14 Tim Schmidt <<a href="mailto:timschmidt@gmail.com">timschmidt@gmail.com</a>><br>
>><br>
>> On Fri, Nov 14, 2008 at 5:11 AM, Wolfgang Spraul <<a href="mailto:wolfgang@openmoko.com">wolfgang@openmoko.com</a>><br>
>> wrote:<br>
>> > Openmoko actually has learnt a lot from this. First we have learnt to<br>
>> > not trust high-level promises as much as before.<br>
>> > In fact I would go as far as saying that going forward, we will not<br>
>> > trust any promises about 'we will open this up later' anymore.<br>
>> > Either it's open and documented at the time we make the decision to<br>
>> > use those chips, or we look elsewhere.<br>
>> > I believe that's what our customers want.<br>
>><br>
>> Agreed, and awesome.<br>
>><br>
>> > We have a long way to go to come out with kick-ass open phone<br>
>> > hardware, but if our community doesn't loose faith and continues to do<br>
>> > development together with us, we'll get there. The momentum we have<br>
>> > built with the Freerunner is awesome. Please continue to buy<br>
>> > Freerunners and to develop for it, same is happening internally. The<br>
>> > next phones will build on top of the free platform we have built<br>
>> > together, the technology investment will carry over.<br>
>><br>
>> *crosses fingers and hopes*<br>
>><br>
>> > Having said that, if someone wants to seriously develop for the glamo,<br>
>> > please get in touch with me and we will find a legally correct way to<br>
>> > extend the smedia documentation to you.<br>
>> > In fact we have done that in a few cases before already, but I'm not<br>
>> > sure how much actual codes have come out of that. I think very<br>
>> > little ;-)<br>
>> > So we need some really serious coders that don't mind a tough challenge.<br>
>><br>
>> I am not a skilled developer, but I would be more than happy to<br>
>> organize, and participate in a traditional clean room<br>
>> re-implementation of the documentation.<br>
>><br>
>> As a GTA02 owner, as a founding member of the Open Graphics Project,<br>
>> as a Director of the Open Hardware Foundation, I believe I have the<br>
>> resources to accomplish such a task.<br>
>><br>
>> I'd love to try.<br>
>><br>
>> Can we make it happen?<br>
>><br>
>> --tim<br>
>><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>
> Up for this request Wolfgang :)<br>
><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>
><br>
<br>
<br>
<br>
</div></div><font color="#888888">--<br>
H. Lally Singh<br>
Ph.D. Candidate, Computer Science<br>
Virginia Tech<br>
</font><div><div></div><div class="Wj3C7c"><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>
</div></div></blockquote></div><br>