Reported by on 2011-12-26 19:42
Braillenote is a wellknown notetaker from Pulsedata, now humanwhare that supports a braille terminal mode.
There are models with 18 and 32 cells and with braille and qwerty keyboards. There are many generations of the braillenote (classic, mPower, Apex and maybe more). I have only access to a Braillenote bt 32, that is, the classic model with 32 cells and a braille keyboard. The device communicates through the serial port. newer models have USB ports too but I didn't find any information about protocol changes and such. The only description is found in BRLTTY source package for the serial protocol used by the brailleNote classic bt. Maybe newer models work with the same protocol but I'm not sure... Also no idea about what keys the qwerty keyboard units return.
BrailleNote website: http://www.humanware.com/en-usa/products/blindness/braillenotes
The braillenote implementation of its own protocol have some bugs, one is that when pressing dot7 or dot8 the unit reports that was pressed space+dot7 or space+dot8. Moreover many key combinations are intersepted by the unit and are not sent to the computer.
The attached driver works very well with my Braillenote unit. Cursor routing keys and thumb keys are mapped to NVDA functions as close as possible to the braillenote ones. Braille keyboard keys are mapped to keyboard key presses simulating many navigation tasks: arrows, pageup up and down, end, home, tab, shift tab, showGui and such. pressing H activates and deactivates keyboard help and default combinations can be tested.
Keynames used are the following:
- tprevious, tback, tadvance, tnext for the four thumb keys (from left to right).
- d1...d8 to braille keyboard dots (backspace is d7 and enter d8).
- Space to spacebar.
Gesture.ini changes work with these names.
More testing is needed I think. However I supose it is stable to be included in snapshots for testing purposes, if you think this is to be included in NVDA main distribution. If there is a serial communications error the driver stops communicating so NVDA is not flooded with errors. Tested with main-4852.
Hope this helps someone.
Comments and sugestions are wellcome.
Rui Batista
Blocked by #426
Blocking #2857
Reported by on 2011-12-26 19:42
Braillenote is a wellknown notetaker from Pulsedata, now humanwhare that supports a braille terminal mode.
There are models with 18 and 32 cells and with braille and qwerty keyboards. There are many generations of the braillenote (classic, mPower, Apex and maybe more). I have only access to a Braillenote bt 32, that is, the classic model with 32 cells and a braille keyboard. The device communicates through the serial port. newer models have USB ports too but I didn't find any information about protocol changes and such. The only description is found in BRLTTY source package for the serial protocol used by the brailleNote classic bt. Maybe newer models work with the same protocol but I'm not sure... Also no idea about what keys the qwerty keyboard units return.
BrailleNote website: http://www.humanware.com/en-usa/products/blindness/braillenotes
The braillenote implementation of its own protocol have some bugs, one is that when pressing dot7 or dot8 the unit reports that was pressed space+dot7 or space+dot8. Moreover many key combinations are intersepted by the unit and are not sent to the computer.
The attached driver works very well with my Braillenote unit. Cursor routing keys and thumb keys are mapped to NVDA functions as close as possible to the braillenote ones. Braille keyboard keys are mapped to keyboard key presses simulating many navigation tasks: arrows, pageup up and down, end, home, tab, shift tab, showGui and such. pressing H activates and deactivates keyboard help and default combinations can be tested.
Keynames used are the following:
Gesture.ini changes work with these names.
More testing is needed I think. However I supose it is stable to be included in snapshots for testing purposes, if you think this is to be included in NVDA main distribution. If there is a serial communications error the driver stops communicating so NVDA is not flooded with errors. Tested with main-4852.
Hope this helps someone.
Comments and sugestions are wellcome.
Rui Batista
Blocked by #426
Blocking #2857