The Following 3 Users Say Thank You to ragnar For This Useful Post: | ||
![]() |
2009-09-28
, 11:32
|
|
Posts: 1,589 |
Thanked: 720 times |
Joined on Aug 2009
@ Arlington (DFW), Texas
|
#92
|
![]() |
2009-09-28
, 11:40
|
Posts: 341 |
Thanked: 607 times |
Joined on Dec 2008
|
#93
|
Word completion happens after the fact, i.e. based on if I've typed "drea", it can predict "dreams" or "dreary" or whatever.
The other type of prediction happens before the fact, i.e. based on if I've typed "drea", it predicts that pressing "m" or "r" is than for instance "n" ("drean?"), and therefore updates...
... you can think of it updating the size of the "m" key to be virtually much larger than the "n" key, so if you hit the edge of the "n" key it corrects it (initially) to the "m" key. Think of like an invisible button on top of every real button that you see. The sizes of these invisible buttons change after every key press.
![]() |
2009-09-28
, 11:57
|
|
Posts: 4,384 |
Thanked: 5,524 times |
Joined on Jul 2007
@ ˙ǝɹǝɥʍou
|
#94
|
The Following 4 Users Say Thank You to ysss For This Useful Post: | ||
![]() |
2009-09-28
, 12:03
|
Posts: 337 |
Thanked: 160 times |
Joined on Aug 2009
@ München, DE
|
#95
|
Yes, by a predictive engine I didn't mean a word completion engine, but an engine that predicts what you were intending to press and adjusts your input accordingly. That's what enables smaller than thumb sized keys in portrait mode: even though you type slightly off, the predictive engine guides and tries to match your clicks with reasonable keys in the nearby area. Sometimes you actually touch "q", but it interprets it initially as "w", for instance.
![]() |
2009-09-28
, 12:11
|
Posts: 1,950 |
Thanked: 1,174 times |
Joined on Jan 2008
@ Seattle, USA
|
#96
|
The Following 2 Users Say Thank You to GeraldKo For This Useful Post: | ||
![]() |
2009-09-28
, 12:18
|
|
Posts: 270 |
Thanked: 195 times |
Joined on Aug 2009
@ Finland
|
#97
|
Said Mandibela:
"Creating two interfaces for any app is mandatory if system-wide-ASR is implemented."
Not so. Devs have the option, just like on the N95/97/N900, to support it, just as Mobitubia doesn't support portrait on the N97, which has system wide ASR.
The Following 3 Users Say Thank You to Mandibela For This Useful Post: | ||
![]() |
2009-09-28
, 12:45
|
Posts: 459 |
Thanked: 669 times |
Joined on Sep 2007
@ The DMV
|
#98
|
<passing.opinion>
If you're too busy to free up both of your hands, you are too busy to
type on your device.
</passing.opinion>
The Following User Says Thank You to klinglerware For This Useful Post: | ||
![]() |
2009-09-28
, 12:54
|
|
Posts: 1,743 |
Thanked: 1,231 times |
Joined on Jul 2006
@ Twickenham, UK
|
#99
|
The Following 2 Users Say Thank You to anidel For This Useful Post: | ||
![]() |
2009-09-28
, 17:56
|
|
Posts: 1,589 |
Thanked: 720 times |
Joined on Aug 2009
@ Arlington (DFW), Texas
|
#100
|
This is getting pointless. Unless you learn how to do ASR on the N900 yourself, let the community do it in due time. What you're doing, is spreading bad vibes. EVERYONE knows that Chris would like to have ASR on the N900.
![]() |
Tags |
chris vs landscape mode |
|
The other type of prediction happens before the fact, i.e. based on if I've typed "drea", it predicts that pressing "m" or "r" is than for instance "n" ("drean?"), and therefore updates...
... you can think of it updating the size of the "m" key to be virtually much larger than the "n" key, so if you hit the edge of the "n" key it corrects it (initially) to the "m" key. Think of like an invisible button on top of every real button that you see. The sizes of these invisible buttons change after every key press.