Swype Keyboard
Root / Submissions / [.]
Download:JRTE3KNV
Version:Size:
Swype has been updated to make amends for the problems it had the last runaround. The algorithm is now faster and can easily handle larger libraries (the library in this update has 10k words).
I've added comments throughout the code to make everything more understandable. You can easily port this over into your own programs, so long as you're careful with copying over all the functions and the global variables too. This also includes a custom keyboard function—which itself is fairly flexible—because the default keyboard will not work for this.
This may be the only update I give for this, unless I get some JN brainblast sort-o-thing to help me figure out how to introduce the touch-vector observation/analyzation necessary for higher right-return accuracy.
Replying to:
SwanBot
SwanBotI was saddened to see no iteration of the word "cake" in there.
Get me the word cake and I'll thumbs up.
Yay
Replying to:
amihart
amihartThis is pretty cool concept. I don't know if the library is just small or if it's just buggy but half the words I try don't work. The other half work pretty well though.
Thanks! It might just be buggy. My current working version is pretty stable with 10k words. The most prominent troubles I'm coming across are misreadings. Often "quote" vs "quite", "people" vs "pierre", that kind of thing.
Replying to:
snail_
snail_It would be really interesting if this worked with the built-in keyboard, which is theoretically possible.
*theoretically not possible. Try swiping across that keyboard, perhaps run a little while loop and observe the keyboard output. The keyboard likes to find button repeats and it acts pretty weird because of that.
Replying to:snail_
snail_It would be really interesting if this worked with the built-in keyboard, which is theoretically possible.
You could use TOUCH, and just treat the keyboard as a background "image"
though at that point I'm not sure what the benefits would be...
Replying to:snail_
snail_It would be really interesting if this worked with the built-in keyboard, which is theoretically possible.
Yeah, that was thought of as well. I had actually wrote some code that automatically mapped out the dimensions of each key by wiggling the stylus across each key horizontally and vertically, observing when the return was either the key or an empty string. The result was an output of data containing each rectangular key's boarder.
It was a fun gimmick, but I think I'm going to try to take this idea somewhere else, so I wrote my own keyboard to supplement.
Cool work! I wonder if someone would do it in another language or maybe built-in a game.
Replying to:
GamerCymreig
GamerCymreigCool work! I wonder if someone would do it in another language or maybe built-in a game.
Just translate the keyboard's dictionary for another language. You can also impliment it in a game by replacing the INPUT call(s) with calls to this keyboard program.
Perhaps you're right.