Bug: 13514349
Change-Id: If4c9db12b0ab5be676f7a2f72715f469066ee537

Bug: 8636060
Change-Id: I169618b50532df68e973e14b3f114c6c19714c84

Bug: 8636060
Change-Id: I088be9a7555265ca097667523defd73be4cbe37f

Bug: 13622107
Bug: 13406701
Change-Id: I0023b398c4451253f9f717e2bd990b8a054004bc

Bug: 13406701
Change-Id: I490574b7ca4b953f67dd2c0ef97401297fade0a4

Change-Id: I165ec4a24f5b1334d55c14948e4d942ec40eb33b

Change-Id: Ie5da6c73d4df4553067c58cd0dce9abb34534250

Bug: 13406701
Change-Id: I4696f145478afdd132314b7d3c148c3a9ca11c9c

Bug: 13406701
Change-Id: I3b9f75de9283f76366d1bef7e14a8f22f2186669

Bug: 8636060

Change-Id: I55332c22897e97148621cbd367acf5175b5b3d04

The event interpreter should intervene later, after decoding.
Decoding should happen first, and then the Event should
be passed to the InputLogic.

For the time being, we will leave the (unused) EventInterpreter
class and its friends, because we'll use them again later.

Bug: 13406701
Change-Id: I7582d486724311e39e6692e606cca50c78800643

Bug: 13406701
Change-Id: I9ecd2709c8f1c678a85b0cfaf7c5ed4f78459821

Bug: 13406701
Change-Id: I0a0e4e0b3357f116e1b915c548dee4575e300c92

Bug: 13406701
Change-Id: Id82e9aab6544ca308e6ac6dee2cfa018b9ce2d8f

The combining framework will be more generic than previously
thought. We don't need to handle dead keys as a special type
of event, as all events can be combined arbitrarily.

Bug: 13406701
Change-Id: I8137fdb186c4d70eaa71808c5a1430b1559db1ae

A transaction should always operate with a consistent set
of settings. It's better to have it reference them than to
always pass them along.

Bug: 8636060
Change-Id: I3c642dfea6be30712fc6cbb279c64f3185895791

Bug: 8636060
Change-Id: Icdf87995dedec410b54c306e8d312ba7ec25cea6

We probably can't put this off any longer

Bug: 8636060
Change-Id: I1e5d3cf62d719f4d064ced3282bebf2e822f6baa

Change-Id: I1c5b27c8edf231680edb8d96f63b9d04cfc6a6fa

This unifies the software and hardware keyboard code
under a single decision process that works.

Bug: 8129303
Bug: 8152758
Change-Id: I7574c563d5f957d57bfe62fe5e3eec59a519d335

Bug: 7969231
Change-Id: I581212093df6f16fa9304e0b3e5b46714a7acdb3

Bug: 5037589
Change-Id: I9e1ff92df7d0c58eb7a0f33603adebc9efb86585

Change-Id: If2fe6f0f4f88a6ae1f22664ded61cec6942c18b9

Change-Id: I750a07c0c564a95ceac734afa873ca3da9626a7f

Essentially this does activate auto-correction with a hardware
keyboard, although a lot of things are still left to implement.
No proximity is used yet which means only missing and excessive
letters are considered. Dead keys are not handled. No combiner
is supported. No suggestions are displayed. Resuming suggestions
does not work correctly with a hardware key (because the view
holds a temporary hardware event 'onKeyPreIme' and the event
from the IME won't be handled until this is handled which won't
happen until after the IME said that it did handle the event).

Bug: 5037589
Change-Id: Idcb5c7b26d56717ed772d53c062362807f11cdae

Bug: 5037589
Change-Id: I829f70a258de58ef8d2b836a9b435198a226e37f

Bug: 5037589
Change-Id: I0a4926f94ef8d1caa17669801608608648b697b9

Bug: 5037589
Change-Id: Id8eea0e2bd00dd339a1efb4b0542e4c091a84195