Option to type using myWin2.2 (and Key Magic keyboards)

[GoogleCodeExporter]

Issue 65 will require us to add a virtual typing system for lookup, and we
will use myWin2.2 for that. It shouldn't take much additional effort to
allow users to type exclusively in myWin2.2. And why not allow them to?
--the virtual keyboard seems like a great way to teach users how to type
using a layout, and the keyboard specification is Open Source. 

Original issue reported on code.google.com by seth.h...@gmail.com on 24 Feb 2009 at 7:00

• Blocking: #89

[GoogleCodeExporter]

Separated out the logic for typing as a "help" keyboard and typing as a
"letter-based" one. Haven't tested it yet.

Original comment by seth.h...@gmail.com on 8 Feb 2010 at 7:59

[GoogleCodeExporter]

Changed the title to be more descriptive. Regarding progress:

   1) myWin2.2 appears to work fine. Extensive testing to be done after I separate 
out the logic for KeyMagic (it'll just be 2 or 3 function calls & a bunch of 
overrides.)

   2) KeyMagic keyboards load, and the "variables" and "replacements" arrays appear
fine. However, the occasional entry is missing; moreover, I haven't fully 
validated
all lines of text. 

Also to-do: document our nifty format online and describe how searches will be
performed using this method.

Original comment by seth.h...@gmail.com on 23 Mar 2010 at 6:49

• Changed title: Option to type using myWin2.2 (and Key Magic keyboards)
• Changed state: InProgress

[GoogleCodeExporter]

Verified all variables, and most (unique) replacements. Time to document.

Original comment by seth.h...@gmail.com on 24 Mar 2010 at 8:28

• Added labels: Priority-High
• Removed labels: Priority-Low

[GoogleCodeExporter]

All validated. Most behavior works. Still leaving this open for now, at least 
until
we have an Ayar demo out.

Original comment by seth.h...@gmail.com on 11 Apr 2010 at 6:32

[GoogleCodeExporter]

Key Magic keyboards now cache into a binary format. This format is simple 
enough to
declare "stable" --indeed, the primary bug I found was actually in the source 
text
reader. 

Original comment by seth.h...@gmail.com on 14 Apr 2010 at 9:20

[GoogleCodeExporter]

Status update:

 * KeyMagic keyboard work.
 * Ayar support is complete. (Now just bug-fixing).
 * Help Keyboard has been re-enabled, uses a generic "Input Method".
 * Help Keyboard input method works even if Roman/Display/HelpInput are in different encodings.

Next Ayar demo will have the Help Keyboard & won't allow you to switch layouts. 
Then we can focus on allowing layout switches.

Original comment by seth.h...@gmail.com on 20 Jun 2010 at 10:33

[GoogleCodeExporter]

Marking as fixed; all remaining Key Magic bugs have their own tickets.

Help keyboards with arbitrary layouts will certainly require their own tickets.

Original comment by seth.h...@gmail.com on 18 Aug 2010 at 7:00

• Changed state: Fixed