<br><br><div><span class="gmail_quote">On 6/7/07, <b class="gmail_sendername">Michael 'Mickey' Lauer</b> <<a href="mailto:mickey@openmoko.org">mickey@openmoko.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Tomasz Zielinski wrote:<br>> If with GTK/Matchbox we cannot achieve such rich, fluid and, erm...,<br>> fluid GUI as iPhone, maybe it's not too late to drop GTK and choose<br>> other framework, designed for mobile devices and running quick
<br>> framebuffer operations? GameBoy provided nice full-screen animations<br>> in 1989, eighteen years ago.<br><br>I feel your pain. Trust me, it hurts me as well...<br><br>> I'm 100% sure nobody will cry after pure-X11 applications we loose
<br>> this way. Almost every GTK application would require rewriting/porting<br>> to fit OpenMoko capabilities, so it's not great loss too. Not to<br>> mention font and other DPI-aware issues.<br><br>Interesting. Can I hear more supportive or counter arguments?
<br>What do the others think?</blockquote><div><br>
I'm only interested in graphic effects if they improve the ease and speed of my interactions with the phone. Most of graphic effects don't fit in that category on computers, and my gut feeling is that the smaller the screen, the worse it gets.
<br>
<br>I want something:<br><br>- fast. Don't wan't to wait 1 second everytime I open a menu in order to get it half transparent (and therefore less legible BTW). Maybe I don't want a menu-based UI at all, actually.
<br><br>- easily and deeply configurable: because even *I* can't tell what's the perfect UI for myself without a lot of experimenting. Empowering the users is not only about giving them the sources, it's also about making them as easy to change as possible, so the rapid prototyping abilities of the whole framework are extremely important.
<br><br>And actually, I might want it bad enough to implement it. I'd bet on some tiny, X11-less GUI for responsiveness, plus a layer of Lua bindings for the rapid prototyping aspects. Anyway, AFAIK the widgets implemented in the common, big open-source toolkits have been designed for big screen + mouse, so it's more important to easily write new widgets than having loads of unadapted, XVGA-oriented ones.
<br><br>Note that this approach is not incompatible with the heavier, GTK-based one: once an interesting user experience is found on a lightweight and easy to tweak UI, it can be transposed on the <br>heavy one(s).<br></div>
</div>