<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Good point about T9 kimaidou, but as far as I know the T9 itself is a
patented technology, and would not be able to appear on Moko
officially...<br>
<br>
kimaidou wrote:
<blockquote
cite="mid:40cd9ce40901060050o710d1ab5o7ac7284261587cb6@mail.gmail.com"
type="cite">Hi all,<br>
<br>
I am glad people (re-)start to talk about keyboards.<br>
<br>
2 points:<br>
<br>
* Another great improvement compared to the iphone, illume, etc. ones,
would be to have a transparent keyboard, using the whole screen, but
allowing to see through it. Of course we need the transparency % to be
changed by the user. What about the technical feasibility of that ?
Would it be possible ? I thing for example about the Qwo keyboard ( <a
moz-do-not-send="true" href="http://www.opkg.org/package_84.html">http://www.opkg.org/package_84.html</a>
) which would be very finger friendly in full screen (like the other
one)<br>
<br>
* I don't get how the dictionnary (illume and qtopia) actually helps to
write some word. In mobile phones, on which you have only 9 numbers to
type, so 3 letters by number, the "T9" dictionnary was really helpfull,
because it showed a list of words possible with the combination of the
letters entered. I could actually write sms faster with only 9 keys
than now with a complete qwerty keyboard because the buttons were much
bigger and I had only 9 button to search among. Here with the FR, the
"eyes and brain" must locate the desired letter among much more and
much smaller keys. And furthermore, I don't see the point with the
dictionnary. The dictionnary only shows words with the same number of
letters as the ones entered. So it does not provide a way to easily
choose a word (for example, when I type "for" it must show "for",
"forest", force", etc., but with the illume keyboard it only shows
"for" and other useless words like :"big", "fit", die", but",
etc.--> not very related to "for" ) People using OpenOffice Writer
with the autocompletion activated will understand what I am trying to
explain with my limited english skills..<br>
<br>
My 2 cents :) , of course in a constructive way<br>
<br>
Kimaidou<br>
<br>
<div class="gmail_quote">2009/1/6 The Rasterman Carsten Haitzler <span
dir="ltr"><<a moz-do-not-send="true"
href="mailto:raster@rasterman.com">raster@rasterman.com</a>></span><br>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">On
Tue, 6 Jan 2009 11:08:41 +0530 "Shashank Bharadwaj" <<a
moz-do-not-send="true" href="mailto:shanka.mns@gmail.com">shanka.mns@gmail.com</a>><br>
babbled:<br>
<div class="Ih2E3d"><br>
> On Tue, Jan 6, 2009 at 10:47 AM, The Rasterman Carsten Haitzler
<<br>
> <a moz-do-not-send="true" href="mailto:raster@rasterman.com">raster@rasterman.com</a>>
wrote:<br>
><br>
> > On Tue, 06 Jan 2009 02:46:15 +0000 Jan Henkins <<a
moz-do-not-send="true" href="mailto:jan@henkins.za.net">jan@henkins.za.net</a>><br>
> > babbled:<br>
> ><br>
> > > Hello there,<br>
> > ><br>
> > > Pascal d'Hermilly wrote:<br>
> > > > With 2008.12 release, a well working
finger-friendly keyboard is the<br>
> > > > most critical missing feature for me.<br>
> > > > I've made a mockup of a keyboard that I think would
make things a lot<br>
> > > > easier to type.<br>
> > > > <a moz-do-not-send="true"
href="http://dhermilly.dk/pascal/openmoko/keyboard%20mockup.png"
target="_blank">http://dhermilly.dk/pascal/openmoko/keyboard%20mockup.png</a><br>
> ><br>
><br>
> I think, the current Raster's Keyboard great for potrait mode. For
landscape<br>
> mode(i.e holding neo sideways) however, the keyboard does not
utilize the<br>
> extra space. What we need is, imho, a keyboard that would increase
in size<br>
> to take up the extra space in this landscape mode. That way we'll
be able to<br>
> type even faster. If we could add that fuctionality to raster's
keyboard,<br>
> then it'd be just great.<br>
<br>
</div>
that's a matter of just fixing the code to handle resizing
appropriately.<br>
<div class="Ih2E3d"><br>
--<br>
------------- Codito, ergo sum - "I code, therefore I am" --------------<br>
</div>
<div class="Ih2E3d">The Rasterman (Carsten Haitzler) <a
moz-do-not-send="true" href="mailto:raster@rasterman.com">raster@rasterman.com</a><br>
<br>
<br>
</div>
<div>
<div class="Wj3C7c">_______________________________________________<br>
Openmoko community mailing list<br>
<a moz-do-not-send="true" href="mailto:community@lists.openmoko.org">community@lists.openmoko.org</a><br>
<a moz-do-not-send="true"
href="http://lists.openmoko.org/mailman/listinfo/community"
target="_blank">http://lists.openmoko.org/mailman/listinfo/community</a><br>
</div>
</div>
</blockquote>
</div>
<br>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
Openmoko community mailing list
<a class="moz-txt-link-abbreviated" href="mailto:community@lists.openmoko.org">community@lists.openmoko.org</a>
<a class="moz-txt-link-freetext" href="http://lists.openmoko.org/mailman/listinfo/community">http://lists.openmoko.org/mailman/listinfo/community</a>
</pre>
</blockquote>
<br>
</body>
</html>