Phone style text input applet (with Source code!)

**Dominik** · 08-26-2004, 09:48 AM

That would be awesome... But would take a bit to write that... Might be enough motivation to rewrite the app in C++ though.

That might be a future project though.. Or maybe Garry will take your advice and integrate it into AIMEE??

**Confused** · 08-26-2004, 09:59 AM

I've already got the basics of the application in AIMEE, no cutting and pasting, it goes into whichever specific text box you want. For GPS applications (which is where it will really be useful), I am going to use AIMEE for entering destination, rather than using whatever application you're using (providing it provides an SDK to allow me to get the list of streets/cities.

It currently will work if the numlock is on, and if it's not, then those keys will (when I code it in to the rest of the application) be able to be used to control AIMEE. Therefore, you can have complete control over AIMEE and entering text

Garry

**keegan** · 08-26-2004, 10:50 AM

I finish resit exams on tuesday and I'll have a go with my tree structure idea, it'll give me something to do and if it works well all the better!

I'll have a go in C# and I'll try to write a VB module once I've got it working for you dominic but my vb is a bit rusty I'm afraid so it might take a while longer

**Confused** · 08-26-2004, 05:54 PM

OK, I got a 44mb JET DB built with 354,982 words in it, using Dominik's theory with 15 characters, (parsed the text file in about 500 seconds on my P4 3.2GHz laptop), gonna now try to incorporate it into this source code and will report findings

Garry

**Dominik** · 08-26-2004, 06:52 PM

Woah! 354,000 words! I have 158,000 and there are alot of junk words in that. I need to trim it down to common words only (otherwise it is tedious going through all the redundant words...)

I'm gonna try interfacing into MS Office's Spell Checker when importing words, so that the DB only gets real words for starters (i have stuff like aaaaaaab etc).

Also, since you seem to be doing it fine on your own; i had to cater for the scenario that the word is longer than the number of letters i had available in my DB (could be a custom word with 30 letters!). In that case i find all words that match the number combinations; and then prune the list as each subsequent letter is added.

I'll continue with my app though (even though i'm sure yours will kick ***!); coz it could be useful for others who dont use AIMEE, or cant wait

**Dominik** · 08-26-2004, 07:01 PM

god _of_cpu, that might be viable (word list only takes up 1.3mb), but its the time that it would take to load it into memory that would hurt

Usually this app will only be called when it is needed, so it needs to start up quickly. In AIMEE this might be feasible though...

Lastly i'm not sure if this would make a difference, but i have indexed the words table to make searches quicker. Not sure if it would be slower searching sequentially through an array in memory (how else would you store it in memory?)

**cheerio** · 08-26-2004, 07:10 PM

t-9 predictive text source codes

http://koti.mbnet.fi/korsu/ft.html

**Confused** · 08-26-2004, 08:15 PM

cheerio,

I found that site, and downloaded the database they have...it's missing so many common things like "i" and "a" and "hi" and "hit" (and those are just the ones i tried).

All I need is a good word list, and the code i've got is working BRILLIANTLY. If a word is more than 15 characters, due to the english language it's a damn good chance that you'll find it by the time you reach 15 characters, or if not then there will only be 1-2 more options

On my laptop, it takes about a second to query and return the necessary rows from the 355k row database.

The biggest hurdle here is having a good word list to start with

Garry

**Confused** · 08-26-2004, 08:35 PM

Just been looking for the past 20 mins and i've not found any decent dictionary yet, i'm calling it a night (it's 1:35am here), if anyone has a half decent dictionary file, let me know where, and I'll give it a try tomorrow, and report back

Garry

**cheerio** · 08-26-2004, 08:58 PM

Originally Posted by Confused

cheerio,

I found that site, and downloaded the database they have...it's missing so many common things like "i" and "a" and "hi" and "hit" (and those are just the ones i tried).

All I need is a good word list, and the code i've got is working BRILLIANTLY. If a word is more than 15 characters, due to the english language it's a damn good chance that you'll find it by the time you reach 15 characters, or if not then there will only be 1-2 more options

On my laptop, it takes about a second to query and return the necessary rows from the 355k row database.

The biggest hurdle here is having a good word list to start with

Garry

ok maby i dunno what your talking about. This is t-9 predictive text. Meaning you press 1 key, 1 time, for each letter. why would you need 'i' and 'a'. I ASSUME T-9 goes by grammar to predict the next word, well not really grammar, buf if the word before it is some sort of word it can determine what kind the next word will be. understand?

http://www.t9.com/learn.html