<div>Finger Splash looks very cool and useful.</div>
<div>Imho a cool idea.</div>
<div><font color="#000000">@<span id="_user_openmoko@mauve.plus.com" style="COLOR: #b90038"><font color="#000000"><a href="mailto:openmoko@mauve.plus.com">openmoko@mauve.plus.com</a>: You are right, abcde... keyboards can be used for blind typing. But not on a only-touchscreen-phone.
</font></span></font></div>
<div><span style="COLOR: #b90038"><font color="#000000">I used a Nokia 7710 for about 1.5 years and typing blind was simply impossible.</font></span></div>
<div><font color="#000000"><span style="COLOR: #b90038"><font color="#000000">Theres no feedback at all.</font></span><br><br> </font></div>
<div><span class="gmail_quote">2007/5/30, Ben Burdette <<a href="mailto:bburdette@comcast.net">bburdette@comcast.net</a>>:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"><br>> Dasher is only really information efficient considering the input only.<br>> The output stream needs to be quite dense.
<br>><br>> This pretty much means that you have to stare at the display all the time<br>> when inputting text.<br>> Sure - in theory, dasher may approach arithmetic coding in terms of<br>> information input.
<br>> But unless you can do the coding in your head, you've got to stare at the<br>> screen, making it less useful for environments where you've got vibration,<br>> sunlight, walking down the street, or less likely for a phone, if you're
<br>> blind. (Hmm. /me ponders dasher with audio prompting)<br>> T9 or even abc def ... you can use blind.<br>> Even qwerty with real hardware keys. (I think on-screen keyb would be<br>> optimistic :) )<br>>
<br>><br><br>To me, it looks like Dasher has a some drawbacks:<br><br>one, it seems to be CPU intensive - there's a lot of animation going on<br>during text entry. Not a problem for PCs, but it might not be optimal
<br>on a low power device.<br><br>two, its storage intensive. You have to have a dictionary of some sort<br>available for it to do its prediction. Or, several dictionaries, each<br>for a different type of text entry (like english and japanese, or
<br>english and C++ programming).<br><br>three, it takes up a lot of screen space. If you are just doing pure<br>text entry without needing to look at something else, that's ok. But<br>I'd rather it didn't take up the whole screen so that I can't see an IM
<br>that I'm replying to, or several lines of the website form I'm filling<br>out.<br><br>That's not to say I'm against Dasher. But I'd like to see a lot of<br>flexibility available in openmoko text entry so that I can change to
<br>dasher, or some other text entry method when needed, or just to try<br>things out. I hope someone will implement it for openmoko, together<br>with several other alternatives for doing text entry.<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">http://lists.openmoko.org/mailman/listinfo/community
</a><br></blockquote></div><br>