Draft
Conversation
Collaborator
|
Impressive! I think we will likely not want to bundle the dictionaries but load them from the internet on user request, like how many Android keyboards handle dictionary downloads. The dictionaries could be in We can also implement a UI for the user to pick the desired word, as well as a way to render a trail line (@oo8dev might have ideas about the latter) |
Collaborator
|
Yup, I've implemented |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I found this new library a few days ago which supports swipe to type for rust, so Ive forked it here, adding some improvements to the prediction selection alg, and laying the groundwork for multi language support.
You can see a some debug output showing the predictions based on the swipe data here:
for example the output
is showing that I swiped over the keys "tyuiopoiuytre" in that order and its correctly predicting that I meant to type the word "type"
Before I continue to implement it properly with the gui and stuff I have a question:
Ive currently implemented the library such that it precompiles word counts and word bigrams into binaries for each language (currently only english) in the crate itself, so the engine can load faster at runtime. its too big for crates.io so it has to be installed via git. This also means the builds will be substantially larger for example the release build binary is now 70mb, compared to 43mb before. I estimate this will increase by about ~30mb per language added. is this acceptable?