Pratik PatelFeb 23

I’m excited to announce the first public release of Terminal Access for NVDA: an add-on focused on improving the NVDA experience when working in terminal/console applications. Inspired by TDSR and Speakup, there's quite a bit of functionality here. I welcome contributions. Issues and PRs welcome. Lots of testing needed.

Open issues on the Github repo at: https://github.com/PratikP1/Terminal-Access-for-NVDA

Get it here: https://github.com/PratikP1/Terminal-Access-for-NVDA/releases/latest

#accessibility #NVDASR

GitHub - PratikP1/Terminal-Access-for-NVDA: This NVDA add-on enables functionality similar to TDSR in NVDA.

This NVDA add-on enables functionality similar to TDSR in NVDA. - PratikP1/Terminal-Access-for-NVDA

GitHub
Show threadPratik PatelFeb 23

I've bumped up the version number for Terminal Access to v1.0.45 with a fix for global keys issue. If you haven't updated it or got to the v1.0.43 release, you can update it here. I've also submited the add-on to the NVDA store. Hopefully, new updates will show up there once approved.

https://github.com/PratikP1/Terminal-Access-for-NVDA/releases/download/v1.0.45/terminalAccess-1.0.45.nvda-addon

Show threadPratik PatelFeb 24

Terminal Access for NVDA 1.0.46 released with better cacheing support and a new configurable output buffer with nvda+alt+n. It automatically speaks newly appended terminal output as it arrives. Coalesces rapid output within a configurable window (default 200 ms). Speaks a concise summary: e.g. "47 new lines". Window monitoring is more efficient and reliable. Settings now give you four new options to control the output buffer.

https://github.com/PratikP1/Terminal-Access-for-NVDA/releases/download/v1.0.46/terminalAccess-1.0.46.nvda-addon

#NVDASR #accessibility

Show threadJoseph Lee
@ppatel The code is very self-explanatory (thank you). One suggestion is to use Python 3.11 assumptions all the way e.g. no need to import typing.Dict and you can use enums for some constants. Let me konw if you would like more detailed reviews and feedback.
Feb 24 at 1:57amWeb
Show threadPratik PatelFeb 24
@joslee Thank you. I'd love to have a conversation with you. The reason why you see a mix of styles is because I'd originally planned to support older versions of NVDA. Because of that, the code needs to be cleaned up. I wanted to focus on the first release and responding to immediate feedback. I'll work on the clean up in the next few days. I'm also iterating since I'm not as confident in my Python skills as other languages. All feedback is welcome, good, bad, or ugly.
Show threadJoseph LeeFeb 24
@ppatel Sure - get something done, and then clean things up when you are ready. I suggest two things: subscribe to NVDA add-ons list hosted on groups.io so you can get more feedback, and learn from reading source code for various NVDA add-ons (including some of mine).
Show threadKaveinthran (no longer here)Feb 24
@joslee @ppatel the add-on list is fun, also the nvda devel list
Show threadPratik PatelFeb 24
@joslee I subscribed to the list last night. I'm getting the feel of the list before I post. I've already looked at quite a few add-ons—definitely yours.