[SHR] illume predictive keyboard is too slow

[Carsten Haitzler (The Rasterman)]

On Thu, 05 Feb 2009 15:57:41 +0100 Helge Hafting <helge.hafting at hist.no> said:

> Carsten Haitzler (The Rasterman) wrote:
> 
> >> Surely, when there is a kayboard anyway, a couple of extra keys won't
> >> cost much. Not if they are on all phones, instead of only "adapted" 
> >> ones. The americans can use the extras as application hotkeys.
> > 
> > oh its not the extra keys - its the variations in production. 
> I know. Which is why I suggest one single keyboard for all, with
> the maximum amount of keys instead of the minimum. That way, every
> language (at least every latin-based language) can have a normal keyboard.
> 
> No problem for the english - it will work fine. Their extra keys can be 
> blank, or used as hotkeys. Users with other languages can add whatever 
> they need - and in the correct location too.

that's not practical. have you SEEN all the accented characters available? its
moe than going to double the # of chars in a kbd. otherwise you then need a
compose mode where multiple keystrokes gives you æ or ø or ü or ñ etc. and its
a combo you need to learn. you still need to offer all the accents then on such
a kbd. like ~^'`",* (ãâáàäąå) which drastically will cramp the keyboard or make
it yet another row bigger for everyone. (in addition to some form of compose
key and specific compose logic).

i am not saying to do it - but to me that seems he job of specialised keyboards
per language, not a universal one.

> > just a change in printing whats on the keys is not free. software keyboards
> > are
> A project like openmoko have the option of leaving that to the users.
> Supply a sheet with small letter stickers for all languages, and a 
> printed sheet with where each letter normally go for the 
> software-supported languages.
> [...]
> 
> > it sucks. but "english" is the lowest common denominator and thus most
> > things tend to be built to support it - as   it tends to keep more people
> > happier than  some other setup. if there was enough volume to make enough
> > units for a particular language/locale/country - it'd be different. :)
> 
> I understand that there is little interest in making a phone 
> specifically for Norway, when the volumes are low. That doesn't mean the 
> lowest common is the best way. A keyboard with several extra blank keys,
> and the english qwerty printed on the keytops will work fine for the 
> large group of english-language users.  Norwegians like me will simply 
> put the "ø" and "æ" stickers on the 2 keys to the right of "l", and the 
> "å" sticker on the key to the right of "p".
> 
> Those who want a radically different layout, such as dvorak, take the 
> lid off and carefully rearrange the keytops. Same for azerty-layouts.
> 
> Programmable is better, but if someone wants real keys that depress with 
> a click, then this is possible too.

this would be the best solution - if its a hardware keyboard. a software
keyboard is always the most flexible... but its currently also probably the
least usable and not just because of software, but the fact a resistive screen
only accepts  touch at a time and typing will mean commonly 2 touches at a time
(as you press the new key before you release your finger on the old one). :(


-- 
------------- Codito, ergo sum - "I code, therefore I am" --------------
The Rasterman (Carsten Haitzler)    raster at rasterman.com