Reply to thread

Message

Once the keyboard is written, sizing will simply be a skinning issue. So eventually we'll be able to have big ones and small ones. I'm leaning more towards Frodo's thinking with the MSN plugin at the moment, with auto complete there really isn't a need for either an ABC or QWERTY layout BUT we should still offer full support for these.

Regarding auto complete, I've written an app this afternoon using a 137k word dictionary. The dictionary starts of as a plain text file, one word per line and is read into the dictionary builder a word at a time, that word is translated into the corresponding key presses (e.g. 533 for Lee). Once we know the digits we add the word to a hashtable, once the whole dictionary is built the value for entry 533 would look like:

532: lea|kea
533: led|Lee|Jed|ked|kef
534: ...

A couple of words there that I wasn't aware of prior to doing this! My mobile offers Led, Lee, Kee, Lef, Jef and Jee as possible words for 533. It's a garbage in, garbage out situation when it comes to the source dictionary. The hashtable is then serialized once the entire dictionary has been parsed.

There are good open source dictionaries out there and hopefully we can cover all the languages already supported too.

Next job on the auto complete is to store the data in something more memory friendly than a Hashtable (my test app runs at 53mb even though it has two labels on a form). SQLite may be the best bet, our own B-Tree implementation or whatever... back to the getting it skinnable first.

[USER=10344]Ricardoduarte[/USER]: I don't believe that there is a shortcut key, you can however use the keyboard anywhere within MP that using a keyboard is applicable.

Lee.

<blockquote data-quote="Smirnuff" data-source="post: 8921" data-attributes="member: 10545">Once the keyboard is written, sizing will simply be a skinning issue.&nbsp; So eventually we'll be able to have big ones and small ones.&nbsp; I'm leaning more towards Frodo's thinking with the MSN plugin at the moment, with auto complete there really isn't a need for either an ABC or QWERTY layout BUT we should still offer full support for these.Regarding auto complete, I've written an app this afternoon using a 137k word dictionary.&nbsp; The dictionary starts of as a plain text file, one word per line and is read into the dictionary builder a word at a time, that word is translated into the corresponding key presses (e.g. 533 for Lee).&nbsp; Once we know the digits we add the word to a hashtable, once the whole dictionary is built the value for entry 533 would look like:532: lea|kea533: led|Lee|Jed|ked|kef534: ...A couple of words there that I wasn't aware of prior to doing this!&nbsp; My mobile offers Led, Lee, Kee, Lef, Jef and Jee as possible words for 533.&nbsp; It's a garbage in, garbage out situation when it comes to the source dictionary.&nbsp; The hashtable is then serialized once the entire dictionary has been parsed.There are good open source dictionaries out there and hopefully we can cover all the languages already supported too.Next job on the auto complete is to store the data in something more memory friendly than a Hashtable (my test app runs at 53mb even though it has two labels on a form).&nbsp; SQLite may be the best bet, our own B-Tree implementation or whatever... back to the getting it skinnable first.[USER=10344]Ricardoduarte[/USER]: I don't believe that there is a shortcut key, you can however use the keyboard anywhere within MP that using a keyboard is applicable.Lee.</blockquote>

[QUOTE="Smirnuff, post: 8921, member: 10545"] Once the keyboard is written, sizing will simply be a skinning issue. So eventually we'll be able to have big ones and small ones. I'm leaning more towards Frodo's thinking with the MSN plugin at the moment, with auto complete there really isn't a need for either an ABC or QWERTY layout BUT we should still offer full support for these. Regarding auto complete, I've written an app this afternoon using a 137k word dictionary. The dictionary starts of as a plain text file, one word per line and is read into the dictionary builder a word at a time, that word is translated into the corresponding key presses (e.g. 533 for Lee). Once we know the digits we add the word to a hashtable, once the whole dictionary is built the value for entry 533 would look like: 532: lea|kea 533: led|Lee|Jed|ked|kef 534: ... A couple of words there that I wasn't aware of prior to doing this! My mobile offers Led, Lee, Kee, Lef, Jef and Jee as possible words for 533. It's a garbage in, garbage out situation when it comes to the source dictionary. The hashtable is then serialized once the entire dictionary has been parsed. There are good open source dictionaries out there and hopefully we can cover all the languages already supported too. Next job on the auto complete is to store the data in something more memory friendly than a Hashtable (my test app runs at 53mb even though it has two labels on a form). SQLite may be the best bet, our own B-Tree implementation or whatever... back to the getting it skinnable first. [USER=10344]Ricardoduarte[/USER]: I don't believe that there is a shortcut key, you can however use the keyboard anywhere within MP that using a keyboard is applicable. Lee. [/QUOTE]