**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 #209, #558, #639, #808, #810, #939, #977**
Reported by jteh on 2010-03-19 02:42
NVDA needs a new, flexible input handling framework.
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