Gaia/Team/Taipei: Difference between revisions

Line 439: Line 439:


===== Input Management & Keyboard =====
===== Input Management & Keyboard =====
* {{bug|1124150}} - Remove dead code & data structure from xml2dict.py, Write documentation regarding dictionary blob and predictions | landed
* {{bug|1138343}} - [UserDictionary] Instantiate and store an ArrayBuffer instead of a TypedArray during dictionary binary blob generation in KeyboardSettingsApp | landed


===== Review/Feedback/Assistance =====
===== Review/Feedback/Assistance =====


==== > Current Progress ====
==== > Current Progress ====
* Write documentation.


===== Input Management & Keyboard =====
===== Input Management & Keyboard =====
* {{bug|1102835}} - [UserDictionary] Let Keyboard App use User-Dictionary | f? and ui-r?, First iteration
* {{bug|1102835}} - [UserDictionary] Let Keyboard App use User-Dictionary | f? and ui-r?
** I decided to forgo any kind of optimization (caching, async handling) in the first iteration and come up with a usable result first, and then to improve on that result.
** I decided to forgo any kind of optimization (caching, async handling) in the first iteration and come up with a usable result first, and then to improve on that result.
** Patch is ready for UX review and initial code feedback.
** Patch is ready for UX review and code review.
** Will continue on writing unit tests while waiting for feedback.
* {{bug|1138782}} - validChars() in predictions.js should consider different casing | r?
* {{bug|1138782}} - validChars() in predictions.js should consider different casing | r?
** Need to rethink validChars() to reject less chars because user dictionary's character table has less chars defined in dictionary, but we can't reject those non-UD chars if they can be corrected to UD words.
** Need to rethink validChars() to reject less chars because user dictionary's character table has less chars defined in dictionary, but we can't reject those non-UD chars if they can be corrected to UD words.
Line 460: Line 459:


===== Keyboard User Dictionary =====
===== Keyboard User Dictionary =====
* We're one big step left: let the actual prediction engine use the second dictionary, and this is my main focus right now. Major todo on that {{bug|1102835}}:
* Address any review comments
** ui-r?omega and f?timdream
* Will need to adjust prediction merging (from built-in dictionary and user dictionary) mechanism according to omega's feedback, if any
** Adjust prediction merging (from built-in dictionary and user dictionary) mechanism according to omega's feedback
** Writing unit tests
* I still need to consult UX feedback on how we handle non-latin characters in the word list.
* I still need to consult UX feedback on how we handle non-latin characters in the word list.
* In Mar. 6's sync-up, Bruce expressed his expectation that acceptable performance should be: reasonably responsive for a user dictionary of 100 words. I think that includes prediction & dict blob generation.
* In Mar. 6's sync-up, Bruce expressed his expectation that acceptable performance should be: reasonably responsive for a user dictionary of 100 words. I think that includes prediction & dict blob generation.
Confirmed users
346

edits