New input handling framework

[nvaccessAuto]

Reported by jteh on 2010-03-19 02:42
NVDA needs a new, flexible input handling framework.

• It must handle input from sources other than the keyboard; e.g. Braille displays.
  • Multiple variants of a single source should be handled also; e.g. desktop and laptop keyboard layouts.
• It should allow input from all sources to execute scripts, as well as facilitating keyboard/input help.
• There should be an input gesture class hierarchy. All input gestures will create an input gesture instance.
• Scripts should receive an input gesture instance instead of a key press.
• It should allow scripts common to multiple targets (e.g. say all) to be specified in a single mapping.
• Users should be able to override all entries without having to edit builtin maps.
• It should be possible to re-send the gesture for sources which support it. This would be used instead of sendKeyPress.
• Bindings for all input sources should be specified in the same map file.
  Blocking Trigger execution of scripts in response to keys on braille displays #209, In the keyboard settings dialog, the content of the "keyboard layout" list is not translatable #558, shift+page up and shift+page down to select text on webpages? #639, Support for entry of computer braille via a braille keyboard #808, In some applications, particular NVDA shortcuts should be localized #810, Caps Lock Alert or Prevention #939, Keyboard/input help doesn't speak punctuation keys when speak punctuation is disabled #977

[nvaccessAuto]

Comment 3 by jteh on 2010-03-25 04:43
Bzr branch: http://bzr.nvaccess.org/nvda/inputFramework/
As of rev 3411, keyboardHandler has been changed to use input gestures. However, work hasn't yet begun on the new mapping system.

[nvaccessAuto]

Comment by jteh on 2010-04-08 13:48
(In #620) Already fixed as part of the work on the new input framework (#601).

[nvaccessAuto]

Comment by jteh on 2010-05-04 02:24
(In #639) This is easy to do. We should also implement shift+ctrl+up/down, since there are ctrl+up/down.

Let's do this after inputFramework, as it will cause merge conflicts otherwise.

[nvaccessAuto]

Comment 6 by jteh on 2010-05-04 02:25
Probably want to get this into 2010.2, not least because merging it later will be painful.
Changes:
Milestone changed from 2010.3 to 2010.2

[nvaccessAuto]

Comment 7 by jteh on 2010-07-14 06:48
Changes:
Milestone changed from 2010.2 to 2010.3

[nvaccessAuto]

Comment by jteh on 2010-07-15 00:43
(In #558) Done as part of input framework.

[nvaccessAuto]

Comment 13 by jteh on 2010-10-12 02:54
As of inputFramework rev 3449, functionality should be equivalent to that in main. Work has not yet begun on the new map file format nor braille input gestures.

[nvaccessAuto]

Comment 15 by jteh (in reply to comment description) on 2010-10-14 05:04
Merged inputFramework in 062be1b.

The new mapping system hasn't yet been implemented. This means that the following features still aren't present:
Replying to jteh:

• It should allow scripts common to multiple targets (e.g. say all) to be specified in a single mapping.
• Users should be able to override all entries without having to edit builtin maps.
• Bindings for all input sources should be specified in the same map file.

However, the core framework (gestures, etc.) is done. Therefore, I'm closing this ticket as fixed. I'll open new tickets/hijack other tickets for features based on this framework.
Changes:
State: closed