I wrote some similar entries on my blog (<a href="http://mobiphil.com">http://mobiphil.com</a>), unfortunately I share those observations/opinions. Maybe I am inpatient, but I am not happy to spend time from my life to wait for a phone having done some trivial functions. I think carrying Xwindows is the biggest mistake. I personally encourage QT or new start with gtk on top of <span style="visibility: visible;" id="main"><span style="visibility: visible;" id="search"><cite><a href="http://www.directfb.org/">www.directfb.org/</a>, </cite></span></span>so that gtk based interfaces can be reused... By the way did anybody consider gtk with directfb as direction? Or I am wrong and the bottleneck is not really Xwindows?<br>
<br>About the phone's price: you may find for equivalent of 200 euros the glofiish eten m800, and there is a port of openmoko kernel etc (<span style="visibility: visible;" id="main"><span style="visibility: visible;" id="search"><cite><b>gnufiish</b>.org/ ) </cite></span></span>The eten m800 has a decent keyboard, and this weekend I booted a debian distro. Honestly screen and filesystem on the sd card seem to be a bit faster... If I have time I will do some I/O measurement.<br>
<br>Well my plan is to have a vim phone top of directfb console with a keyboard... that will do all the trick... you can have then very fast phone book, todo list etc. ... al in one file :) .. is anybody interested in this particular approach ? :) (it is not a joke, but myself I am smiling about the idea..)<br>
<br><br>regards<br>Mobiphil<br><br><br><br><br><div class="gmail_quote">On Mon, Jun 22, 2009 at 8:35 AM, Ben Wong <span dir="ltr"><<a href="http://lists.openmoko.org">lists.openmoko.org</a>@<a href="http://wongs.net">wongs.net</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;"><div class="im">On Sat, Jun 20, 2009 at 1:38 PM, Joerg Lippmann<<a href="mailto:jl_lists@donalbain.de">jl_lists@donalbain.de</a>> wrote:<br>
>> > Then the Freerunner is not for you.<br>
>> > It may sound harsh, but it's definitely *not* suitable for daily use.<br>
>> > Period.<br>
>><br>
</div>>> I must respectfully disagree with Joerg's advice to you. [...]<br>
<div class="im"><br>
> OK, maybe I should explain. My mail should not be taken as FUD.<br>
<br>
</div>I hope I didn't give the impression that I thought Joerg's message was<br>
FUD. I think calling "FUD" can too often be an ad hominem attack.<br>
Although I disagree with some of Joerg's statements, it's clear that<br>
he's trying to help and is being honest about the Freerunner's value<br>
to him, personally.<br>
<br>
I want to thank Joerg for taking the time to give a clear list of<br>
reasons why a person might consider the Freerunner unsuitable as a<br>
phone. I think it'd be helpful if these and other points were put on<br>
the wiki so that potential buyers can see the arguments against the<br>
Freerunner, and what the community response is. (E.g., Solved?<br>
Kludged? In progress? Unfixable?)<br>
<font color="#888888"><br>
--Ben<br>
</font><div><div></div><div class="h5"><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><br clear="all"><br>-- <br>being mobile, but including technology<br><a href="http://mobiphil.com">http://mobiphil.com</a><br>