Thanks Helge, this is very helpful. I agree with all the feature requests. Could you please put them on the wiki [1]? <br><br>About the crashes. My experience is that in only (and always) crashes when there's an error from FSO. So I'll upgrade the GUI to display the FSO error instead of crashing, and then we will be able to work on finding the problem. Some of the crashes I've already identified and they will be fixed in todays release.<br>
<br>[1] <a href="http://wiki.openmoko.org/wiki/Litephone">http://wiki.openmoko.org/wiki/Litephone</a><br><br>Michal<br><br><br>2009/7/30 Helge Hafting <span dir="ltr"><<a href="mailto:helge.hafting@hist.no">helge.hafting@hist.no</a>></span><br>
<div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">KaZeR wrote:<br>
[...]<div class="im"><br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I believe that the style_sheet part isn't needed anymore, and instead you<br>
can use other parameters (like demo, etc).<br>
I simply ran litephone, in my case and it worked.<br>
</blockquote>
<br></div>
Thanks, that worked.<br>
<br>
My impressions after testing a bit:<br>
<br>
* Looks good, is responsive<br>
<br>
* The contact list doesn't have finger scrolling. It jumps when I<br>
select a message close to the bottom though.<br>
<br>
Finger scrolling is even easier. Just put the finger on the screen<br>
and drag up or down as necessary.<br>
<br>
* Calling and receiving works, but is fragile. Once, litephone didn't<br>
notice that the other end hung up. The call was terminated, and when<br>
the other side called back, litephone still was stuck with the<br>
screen for the previous call.<br>
<br>
I could not reproduce this though, further calls worked<br>
as expected.<br>
<br>
* Entering unicode text into a message doesn't work, I get<br>
garbage text instead. Strange, because<br>
stored unicode messages show up fine in the viewer. Most of the<br>
world uses more than ascii. The shr messaging app has no problems<br>
with this.<br>
<br>
* There seems to be no way to forward a message to others. Shr messaging<br>
also lack this, you have the chance to be first. :-)<br>
<br>
* Messages cannot be deleted. (Not implemented yet?)<br>
Please note that the inbox can accumulate lots of messages quickly.<br>
Deleting one-by-one is fine for deleting a few messages, but<br>
cumbersome for many. This is a typical problem with many<br>
phones - click once to select, click once to delete, then wait<br>
as deletion happens, then click to select, click to delete, wait ...<br>
Still - you're better than shr with its 3-click deletion.<br>
<br>
Mass deletion is very useful. One way is to have a little checkbox<br>
at the end of each message in the list. One can then check<br>
several messages quickly, and hit "delete" to get rid of<br>
them all. This way, the user don't have to wait for<br>
each deletion. If deleting 50 messages is slow, then the<br>
user simply pockets the phone or play a game while waiting. :-)<br>
<br>
<br>
<br>
===========<br>
Crashes:<br>
<br>
I tried to save my changes to a contact, and litephone died.<br>
(The contact name contained parentheses, I hope that<br>
didn't crash it.)<br>
Restarting it worked.<br>
<br>
After sending myself some messages, litephone crashed and<br>
can no longer be started on my phone. I get:<br>
INFO: refresh msgs<br>
FATAL: main.cpp: 236 : void PhoneWindow::refreshMessages(): check failed: messages.getRow(i).getValue("Content", &content):<br>
Deleting the messages through shr-messages did not help.<br>
I'll try again when there is an updated version.<br><font color="#888888">
<br>
<br>
Helge Hafting<br>
<br>
</font></blockquote></div><br>