Initial prototype for using UITextChecker as a predictions generator.
Changes include:
Use of promises for child specifications. Introduction of a ready property which can be tracked to render the box once the specifications are obtained.
A completions predictor based on the original predictor which uses CaptiveWebView commands to access the native UITextChecker functionality.
A new 'highlight' group used to visually track boxes with a weight assigned as a result of a prediction.
What needs to be reviewed:
Asynchronous model for child specifications. Promises are used but I do wonder the impact in the rendering process.
Things that could be improved:
Cache existing predictions as to prevent trips to the native side if a prediction for a prefix is already available.
Initial prototype for using UITextChecker as a predictions generator.
Changes include:
What needs to be reviewed:
Things that could be improved: