Openmoko Bug #1864: Keyboard needs to have a non-predictive mode

Openmoko Public Trac bugs at docs.openmoko.org
Wed Aug 27 13:56:05 CEST 2008


#1864: Keyboard needs to have a non-predictive mode
-------------------------------------------------+--------------------------
    Reporter:  iknowjoseph                       |        Owner:  openmoko-devel
        Type:  defect                            |       Status:  closed        
    Priority:  normal                            |    Milestone:                
   Component:  unknown                           |      Version:  Om2008.8      
    Severity:  normal                            |   Resolution:  duplicate     
    Keywords:  2008.8, keyboard, predictive, pm  |    Blockedby:                
Reproducible:  always                            |     Blocking:                
-------------------------------------------------+--------------------------

Comment(by zecke):

 Replying to [comment:16 Yorick]:

 >
 > On every phone I know it is possible to turn it of during use. There
 should be a button to enable or disable it withouth having to go to
 exposure.

 Sure, mentioned that to PM in June. But on your phone you probably use "*"
 to switch between modes. What you ask is to have "modes" and "keyboards".
 I think we should only go for keyboards. Which brings the technical
 question how to switch keyboards fast if one is provided by a Gtk+, the
 other by a EFL and a third one with a Qt process. Everything is easy if
 you go to an island and control everything, allow keyboards to be written
 with any language and keyboard requires a lot more effort to get basics
 done.


 If this is not feasable in the short run, even having to set it in
 exposure will make it A LOT more useful (most people will turn it of the
 first time they boot and keep it of I think...).

 Okay, #1764 here...



 > But I keep asking myself: what do you find wrong with Rasters keyboard?

 Nothing. When we decided to go to for the Qtopia keyboard raster's
 keyboard didn't have good prediction, it leaked memory, it had no zoom, no
 selection of different keymaps....One was unable to use it without a
 stylus leave alone a ride in a car. So I was asked to port the Qtopia
 keyboard and roughly spend six hours on it, raster has spend at least
 three weeks working on his keyboard. And using the Qtopia keyboard allowed
 him, or made him, to rewrite his keyboard to be better.


 > It has every functionality the standard 2008.8 has AND MORE.

 It was not back then.

 > Only problem is that the full-qwerty sometimes gets beaten by the
 standard one and we need to reboot, but even then we are not worse of then
 with the standard keyboard.

 I don't follow.


 > Do you use the FreeRunner as your daily phone zecke?

 I'm one of the fews that do. It is my primary phone and I take it with me
 on my travels and rely on it to make "emergency" calls when I'm totally
 lost.

 > Have you tried playing in the terminal?

 I don't use a terminal. My primary use case is to write SMS and that is
 possible. The frustration of zooming and waiting for it to select is
 nothing compared to not being able to write SMS in public transportation
 or the jittering of raster's current zoom widget (experience from raster's
 keyboard).

-- 
Ticket URL: <https://docs.openmoko.org/trac/ticket/1864#comment:19>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac


More information about the devel mailing list