toggle quoted messageShow quoted text
I respectfully disagree: although English is sort of a de facto language used to design programming languages, folks write code in all sorts of languages. Although the add-on may help folks read code fragments in a more efficient manner, consider that folks do review source code comments (developers are no exception). Also, I think it would be helpful to think carefully about saying that camel case and identifiers with underscores are exclusive to English, because it might be that developers might be writing identifiers using a language other than English.
I know I'm coming across as a really critical critic, but I'm saying all this to remind folks that we may wish to expand our assumptions a bit based on data we haven't thought about (apologies if I do sound very harsh tonight).
From: email@example.com <firstname.lastname@example.org> On Behalf Of Tony Malykh
Sent: Monday, December 14, 2020 9:18 PM
Subject: Re: [nvda-addons] New WordNav add-on - review requested
One more thing to add: I see WordNav is a tool primarily for software developers. It improves word navigation in cases when you need to deal with camelCaseIdentifiers and underscore_separated_identifiers, and also with long file paths. All of which tend to be exclusively in English.
On 12/14/2020 7:15 PM, Joseph Lee wrote:
One major thing to resolve: what would happen if a user defines multiple virtual desktops on Windows 10 and wish to move amongst them quickly without opening Task View? Another thing to look into is the fact that certain languages do not have definable "word boundary".
<email@example.com> On Behalf Of Tony Malykh
Sent: Monday, December 14, 2020 7:05 PM
To: nvda-addons <firstname.lastname@example.org>
Subject: [nvda-addons] New WordNav add-on - review requested
I present my new add-on WordNav and I would like to have it reviewed.
WordNav improves word navigation commands (Control+Left/Right arrows)
in NVDA. It works in both editables and browse mode. It provides 4
different version of word navigation commands, depending on how do we
define a word, and allows them all to be assigned to either
control+arrows or control+windows+arrows commands. Those different
• Left Control+Arrows: Notepad++ definition, that treats alphanumeric characters as words, and adjacent punctuation marks are also treated as words. This should be the most convenient word definition for the majority of users.
• RightControl+Arrows: Fine word definition splits camelCaseIdentifiers and underscore_separated_identifiers into separate parts, thus allowing the cursor to go into long identifiers.
• LeftControl+Windows+Arros: Bulky word definition treats almost all punctuation symbols adjacent to text as part of a single word, therefore it would treat paths like C:\directory\subdirectory\file.txt as a single word.
• RightControl+Windows+Arros: Multiword definition, that groups several words together. The amount of words is configurable.
Another issue that WordNav is trying to fix is inconsistency between NVDA word definition and word definition in applications. There have been multiple issues of that nature, when the program moves cursor according to one definition, and NVDA assumes another, and that leads to either words being pronounced twice, or some words being skipped. Since wordNav doesn't send Control+Arrows gesture to applications, but it instead parses the whole line itself, it serves as a workaround for this type of issues.