Date   

Admin notice: if your address is bouncing as a result of Google services failure yesterday #AdminNotice

 

Hi all,

Members of various Groups.IO forums reported that they are not receiving messages from forums. Turns out it is an effect of Google services failure and owners of affected forums are investigating, including sending bounce probes. If you are not getting messages from this forum, don’t worry – I’ll send a bounce probe, and the message you will get includes a link you can click to unbounce yourself.

Cheers,

Joseph


Re: New WordNav add-on - review requested

 

Hi,
Don't worry.
Cheers,
Joseph

-----Original Message-----
From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of William Wong
Sent: Tuesday, December 15, 2020 12:34 AM
To: nvda-addons@nvda-addons.groups.io
Subject: Re: [nvda-addons] New WordNav add-on - review requested

Joseph, I feel sorry that I have made wrong description about Korean.

Joseph Lee 於 15/12/2020 12:27 寫道:
Hi,
Actually, Korean does have clearly defined word boundaries (similar in idea to English and others where individual words can be distinguished).
Cheers,
Joseph

-----Original Message-----
From: nvda-addons@nvda-addons.groups.io
<nvda-addons@nvda-addons.groups.io> On Behalf Of William Wong
Sent: Monday, December 14, 2020 8:20 PM
To: nvda-addons@nvda-addons.groups.io
Subject: Re: [nvda-addons] New WordNav add-on - review requested

the fact that certain languages do not have definable "word boundary".

Yes Joseph, Language like Chinese, Korean, Japanese dont havespaces
between words

Joseph Lee 於 15/12/2020 11:15 寫道:

Hi,
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".
Cheers,
Joseph

-----Original Message-----
From: nvda-addons@nvda-addons.groups.io
<nvda-addons@nvda-addons.groups.io> On Behalf Of Tony Malykh
Sent: Monday, December 14, 2020 7:05 PM
To: nvda-addons <nvda-addons@nvda-addons.groups.io>
Subject: [nvda-addons] New WordNav add-on - review requested

Hello,
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
control+word
deinitions are:
• 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.

Download:
https://github.com/mltony/nvda-word-nav/releases/latest/download/word
N
av.nvda-addon
Website:
https://github.com/mltony/nvda-word-nav/

Best regards
Tony


















Re: New WordNav add-on - review requested

Samuel Kacer
 

Hi Tony,

another great idea for making lives of blind developers such as myself easier. This is particularly great for code editors like VS code, where word navigation is messy. I have some thoughts about the default configuration and about the behavior as well:

- I think the ctrl + windows +arrows should be unassigned by default, since I would imagine many people like to use virtual desktops and at first I was puzzled why switching between them was funny
- I think if this addon changes behavior for word navigation, it should also change behavior for word selection (i.e. using ctrl + shift + left/right arrow)
- namely it is confusing/frustrating that ctrl + right arrow moves caret forward by x amount, but ctrl + shift + right arrow selects by y amount
- would it be possible to have an app inclusion list instead of an app exclusion list? since I would only want to use this for some code editors, but I don't like making seperate profiles because they get out of sync over time

Kind Regards,
Sam

On Tue, Dec 15, 2020 at 4:04 AM Tony Malykh <anton.malykh@...> wrote:
Hello,
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 word
deinitions  are:
• 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.

Download:
https://github.com/mltony/nvda-word-nav/releases/latest/download/wordNav.nvda-addon
Website:
https://github.com/mltony/nvda-word-nav/

Best regards
Tony







Re: New WordNav add-on - review requested

Cyrille
 

Some additional comments:
* You have an unexpected file left in the bundle of the add-on: manifest (Конфликтующая копия с компьютера Tony’s MacBook Air 2019-12-08).ini
* Could you please use the CSS from the last add-on template? This CSS is optimized for visually impaired people using color inversion. You may also update your other add-ons with this CSS when making new releases. Thanks.

Cheers,

Cyrille
 
De : "Cyrille via groups.io"
A : nvda-addons@nvda-addons.groups.io
Envoyé: mardi 15 Décembre 2020 10:44
Objet : Re: [nvda-addons] New WordNav add-on - review requested
 
Hello

This add-on is a good idea. Thanks Tony.

Here are some feedback on the add-on and the previously written messages:
* In the setting panel, visually, all the edit field are incorrectly located and overlap the first checkbox instead of being located below the "Right Control+Windows behavior:" item.
* The assumption ‌that the paths are mainly in English is wrong. On a computer, it is common to have some files or folders with names in the local language.

Cheers,

Cyrille
 
De : "Tony Malykh"
A : nvda-addons@nvda-addons.groups.io
Envoyé: mardi 15 Décembre 2020 06:18
Objet : 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:
> Hi,
> 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".
> Cheers,
> Joseph
>
> -----Original Message-----
> From: nvda-addons@nvda-addons.groups.io On Behalf Of Tony Malykh
> Sent: Monday, December 14, 2020 7:05 PM
> To: nvda-addons
> Subject: [nvda-addons] New WordNav add-on - review requested
>
> Hello,
> 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 word
> deinitions are:
> • 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.
>
> Download:
> https://github.com/mltony/nvda-word-nav/releases/latest/download/wordNav.nvda-addon
> Website:
> https://github.com/mltony/nvda-word-nav/
>
> Best regards
> Tony
>
>
>
>
>
>
>
>
>
>
>




 


Re: New WordNav add-on - review requested

Cyrille
 

Hello

This add-on is a good idea. Thanks Tony.

Here are some feedback on the add-on and the previously written messages:
* In the setting panel, visually, all the edit field are incorrectly located and overlap the first checkbox instead of being located below the "Right Control+Windows behavior:" item.
* The assumption ‌that the paths are mainly in English is wrong. On a computer, it is common to have some files or folders with names in the local language.

Cheers,

Cyrille
 
De : "Tony Malykh"
A : nvda-addons@nvda-addons.groups.io
Envoyé: mardi 15 Décembre 2020 06:18
Objet : 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:
> Hi,
> 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".
> Cheers,
> Joseph
>
> -----Original Message-----
> From: nvda-addons@nvda-addons.groups.io On Behalf Of Tony Malykh
> Sent: Monday, December 14, 2020 7:05 PM
> To: nvda-addons
> Subject: [nvda-addons] New WordNav add-on - review requested
>
> Hello,
> 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 word
> deinitions are:
> • 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.
>
> Download:
> https://github.com/mltony/nvda-word-nav/releases/latest/download/wordNav.nvda-addon
> Website:
> https://github.com/mltony/nvda-word-nav/
>
> Best regards
> Tony
>
>
>
>
>
>
>
>
>
>
>




 


Re: New WordNav add-on - review requested

Brian's Mail list account
 

I've come across a surprising number of keyboards on laptops which have no right hand control key though.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal E-mail to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users

----- Original Message -----
From: "Joseph Lee" <joseph.lee22590@gmail.com>
To: <nvda-addons@nvda-addons.groups.io>
Sent: Tuesday, December 15, 2020 5:22 AM
Subject: Re: [nvda-addons] New WordNav add-on - review requested


Hi,
Regarding the second item: one more thing to consider is that some keyboard layouts do NOT let you use right Control+arrows for things. This is the case in Korean IME where right Control key is used to convert Korean text (Hangul) into Hanja (Chinese character representation). Of course one can unassign this gesture from the add-on side (via input gestures dialog), but consider that not all users who will meet this add-on are familiar with this step.
Nevertheless, I will submit a basic review.
Cheers,
Joseph

-----Original Message-----
From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of Tony Malykh
Sent: Monday, December 14, 2020 9:16 PM
To: nvda-addons@nvda-addons.groups.io
Subject: Re: [nvda-addons] New WordNav add-on - review requested

what would happen if a user defines multiple virtual desktops on Windows
10 and wish to move amongst them quickly without opening Task View?

Then that user can leave Control+Windows+Arrows unassigned.


Another thing to look into is the fact that certain languages do not have
definable "word boundary

Then no need to use WordNav.. Or optionally there is a way to leave for example native behavior for Left Control+Arrows, and redefine Right Control + arrows if such user wants to use only some features of WordNav.

On 12/14/2020 7:15 PM, Joseph Lee wrote:
Hi,
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".
Cheers,
Joseph

-----Original Message-----
From: nvda-addons@nvda-addons.groups.io
<nvda-addons@nvda-addons.groups.io> On Behalf Of Tony Malykh
Sent: Monday, December 14, 2020 7:05 PM
To: nvda-addons <nvda-addons@nvda-addons.groups.io>
Subject: [nvda-addons] New WordNav add-on - review requested

Hello,
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
control+word
deinitions are:
• 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.

Download:
https://github.com/mltony/nvda-word-nav/releases/latest/download/wordN
av.nvda-addon
Website:
https://github.com/mltony/nvda-word-nav/

Best regards
Tony











Re: New WordNav add-on - review requested

William
 

Joseph, I feel sorry that I have made wrong description about Korean.

Joseph Lee 於 15/12/2020 12:27 寫道:

Hi,
Actually, Korean does have clearly defined word boundaries (similar in idea to English and others where individual words can be distinguished).
Cheers,
Joseph

-----Original Message-----
From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of William Wong
Sent: Monday, December 14, 2020 8:20 PM
To: nvda-addons@nvda-addons.groups.io
Subject: Re: [nvda-addons] New WordNav add-on - review requested

the fact that certain languages do not have definable "word boundary".

Yes Joseph, Language like Chinese, Korean, Japanese dont havespaces between words

Joseph Lee 於 15/12/2020 11:15 寫道:

Hi,
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".
Cheers,
Joseph

-----Original Message-----
From: nvda-addons@nvda-addons.groups.io
<nvda-addons@nvda-addons.groups.io> On Behalf Of Tony Malykh
Sent: Monday, December 14, 2020 7:05 PM
To: nvda-addons <nvda-addons@nvda-addons.groups.io>
Subject: [nvda-addons] New WordNav add-on - review requested

Hello,
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
control+word
deinitions are:
• 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.

Download:
https://github.com/mltony/nvda-word-nav/releases/latest/download/wordN
av.nvda-addon
Website:
https://github.com/mltony/nvda-word-nav/

Best regards
Tony

















Re: New WordNav add-on - review requested

 

Hi,
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).
Cheers,
Joseph

-----Original Message-----
From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of Tony Malykh
Sent: Monday, December 14, 2020 9:18 PM
To: nvda-addons@nvda-addons.groups.io
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:
Hi,
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".
Cheers,
Joseph

-----Original Message-----
From: nvda-addons@nvda-addons.groups.io
<nvda-addons@nvda-addons.groups.io> On Behalf Of Tony Malykh
Sent: Monday, December 14, 2020 7:05 PM
To: nvda-addons <nvda-addons@nvda-addons.groups.io>
Subject: [nvda-addons] New WordNav add-on - review requested

Hello,
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
control+word
deinitions are:
• 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.

Download:
https://github.com/mltony/nvda-word-nav/releases/latest/download/wordN
av.nvda-addon
Website:
https://github.com/mltony/nvda-word-nav/

Best regards
Tony











Re: New WordNav add-on - review requested

 

Hi,
Basic review results;
* License and copyright: pass
* Documentation: pass
* User experience: pass (with comments)
* Security: pass(with comments)

Comments:
* I think it would be great to look at user interface messages as at least one message says "SentenceNav".
* When logging information, can you guarantee that the Dropbox path does exist on a user's system?
* In the readme, I think it would be helpful to point out that you should turn off Control+Windows+arrow keys if you are planning to use virtual desktops on Windows 10.

Based on what we have, if UI messages can be improved, it should be good to go (also keep the original concerns folks raised, too). Further testing and comments from others are appreciated.
Cheers,
Joseph

-----Original Message-----
From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of Joseph Lee via groups.io
Sent: Monday, December 14, 2020 9:23 PM
To: nvda-addons@nvda-addons.groups.io
Subject: Re: [nvda-addons] New WordNav add-on - review requested

Hi,
Regarding the second item: one more thing to consider is that some keyboard layouts do NOT let you use right Control+arrows for things. This is the case in Korean IME where right Control key is used to convert Korean text (Hangul) into Hanja (Chinese character representation). Of course one can unassign this gesture from the add-on side (via input gestures dialog), but consider that not all users who will meet this add-on are familiar with this step.
Nevertheless, I will submit a basic review.
Cheers,
Joseph

-----Original Message-----
From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of Tony Malykh
Sent: Monday, December 14, 2020 9:16 PM
To: nvda-addons@nvda-addons.groups.io
Subject: Re: [nvda-addons] New WordNav add-on - review requested

> what would happen if a user defines multiple virtual desktops on Windows 10 and wish to move amongst them quickly without opening Task View?

Then that user can leave Control+Windows+Arrows unassigned.


> Another thing to look into is the fact that certain languages do not have definable "word boundary

Then no need to use WordNav.. Or optionally there is a way to leave for example native behavior for Left Control+Arrows, and redefine Right Control + arrows if such user wants to use only some features of WordNav.

On 12/14/2020 7:15 PM, Joseph Lee wrote:
Hi,
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".
Cheers,
Joseph

-----Original Message-----
From: nvda-addons@nvda-addons.groups.io
<nvda-addons@nvda-addons.groups.io> On Behalf Of Tony Malykh
Sent: Monday, December 14, 2020 7:05 PM
To: nvda-addons <nvda-addons@nvda-addons.groups.io>
Subject: [nvda-addons] New WordNav add-on - review requested

Hello,
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
control+word
deinitions are:
• 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.

Download:
https://github.com/mltony/nvda-word-nav/releases/latest/download/wordN
av.nvda-addon
Website:
https://github.com/mltony/nvda-word-nav/

Best regards
Tony











Re: New WordNav add-on - review requested

 

Hi,
Regarding the second item: one more thing to consider is that some keyboard layouts do NOT let you use right Control+arrows for things. This is the case in Korean IME where right Control key is used to convert Korean text (Hangul) into Hanja (Chinese character representation). Of course one can unassign this gesture from the add-on side (via input gestures dialog), but consider that not all users who will meet this add-on are familiar with this step.
Nevertheless, I will submit a basic review.
Cheers,
Joseph

-----Original Message-----
From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of Tony Malykh
Sent: Monday, December 14, 2020 9:16 PM
To: nvda-addons@nvda-addons.groups.io
Subject: Re: [nvda-addons] New WordNav add-on - review requested

> what would happen if a user defines multiple virtual desktops on Windows 10 and wish to move amongst them quickly without opening Task View?

Then that user can leave Control+Windows+Arrows unassigned.


> Another thing to look into is the fact that certain languages do not have definable "word boundary

Then no need to use WordNav.. Or optionally there is a way to leave for example native behavior for Left Control+Arrows, and redefine Right Control + arrows if such user wants to use only some features of WordNav.

On 12/14/2020 7:15 PM, Joseph Lee wrote:
Hi,
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".
Cheers,
Joseph

-----Original Message-----
From: nvda-addons@nvda-addons.groups.io
<nvda-addons@nvda-addons.groups.io> On Behalf Of Tony Malykh
Sent: Monday, December 14, 2020 7:05 PM
To: nvda-addons <nvda-addons@nvda-addons.groups.io>
Subject: [nvda-addons] New WordNav add-on - review requested

Hello,
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
control+word
deinitions are:
• 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.

Download:
https://github.com/mltony/nvda-word-nav/releases/latest/download/wordN
av.nvda-addon
Website:
https://github.com/mltony/nvda-word-nav/

Best regards
Tony











Re: New WordNav add-on - review requested

Tony Malykh
 

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:
Hi,
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".
Cheers,
Joseph

-----Original Message-----
From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of Tony Malykh
Sent: Monday, December 14, 2020 7:05 PM
To: nvda-addons <nvda-addons@nvda-addons.groups.io>
Subject: [nvda-addons] New WordNav add-on - review requested

Hello,
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 word
deinitions are:
• 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.

Download:
https://github.com/mltony/nvda-word-nav/releases/latest/download/wordNav.nvda-addon
Website:
https://github.com/mltony/nvda-word-nav/

Best regards
Tony










Re: New WordNav add-on - review requested

Tony Malykh
 

what would happen if a user defines multiple virtual desktops on
Windows 10 and wish to move amongst them quickly without opening Task View?

Then that user can leave Control+Windows+Arrows unassigned.


Another thing to look into is the fact that certain languages do not
have definable "word boundary

Then no need to use WordNav.. Or optionally there is a way to leave for example native behavior for Left Control+Arrows, and redefine Right Control + arrows if such user wants to use only some features of WordNav.

On 12/14/2020 7:15 PM, Joseph Lee wrote:
Hi,
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".
Cheers,
Joseph

-----Original Message-----
From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of Tony Malykh
Sent: Monday, December 14, 2020 7:05 PM
To: nvda-addons <nvda-addons@nvda-addons.groups.io>
Subject: [nvda-addons] New WordNav add-on - review requested

Hello,
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 word
deinitions are:
• 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.

Download:
https://github.com/mltony/nvda-word-nav/releases/latest/download/wordNav.nvda-addon
Website:
https://github.com/mltony/nvda-word-nav/

Best regards
Tony










Re: New WordNav add-on - review requested

 

Hi,
Actually, Korean does have clearly defined word boundaries (similar in idea to English and others where individual words can be distinguished).
Cheers,
Joseph

-----Original Message-----
From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of William Wong
Sent: Monday, December 14, 2020 8:20 PM
To: nvda-addons@nvda-addons.groups.io
Subject: Re: [nvda-addons] New WordNav add-on - review requested

the fact that certain languages do not have definable "word boundary".

Yes Joseph, Language like Chinese, Korean, Japanese dont havespaces between words

Joseph Lee 於 15/12/2020 11:15 寫道:

Hi,
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".
Cheers,
Joseph

-----Original Message-----
From: nvda-addons@nvda-addons.groups.io
<nvda-addons@nvda-addons.groups.io> On Behalf Of Tony Malykh
Sent: Monday, December 14, 2020 7:05 PM
To: nvda-addons <nvda-addons@nvda-addons.groups.io>
Subject: [nvda-addons] New WordNav add-on - review requested

Hello,
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
control+word
deinitions are:
• 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.

Download:
https://github.com/mltony/nvda-word-nav/releases/latest/download/wordN
av.nvda-addon
Website:
https://github.com/mltony/nvda-word-nav/

Best regards
Tony











Re: New WordNav add-on - review requested

William
 

the fact that certain languages do not have definable "word boundary".

Yes Joseph, Language like Chinese, Korean, Japanese dont havespaces between words

Joseph Lee 於 15/12/2020 11:15 寫道:

Hi,
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".
Cheers,
Joseph

-----Original Message-----
From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of Tony Malykh
Sent: Monday, December 14, 2020 7:05 PM
To: nvda-addons <nvda-addons@nvda-addons.groups.io>
Subject: [nvda-addons] New WordNav add-on - review requested

Hello,
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 word
deinitions are:
• 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.

Download:
https://github.com/mltony/nvda-word-nav/releases/latest/download/wordNav.nvda-addon
Website:
https://github.com/mltony/nvda-word-nav/

Best regards
Tony










Re: New WordNav add-on - review requested

 

Hi,
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".
Cheers,
Joseph

-----Original Message-----
From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of Tony Malykh
Sent: Monday, December 14, 2020 7:05 PM
To: nvda-addons <nvda-addons@nvda-addons.groups.io>
Subject: [nvda-addons] New WordNav add-on - review requested

Hello,
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 word
deinitions are:
• 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.

Download:
https://github.com/mltony/nvda-word-nav/releases/latest/download/wordNav.nvda-addon
Website:
https://github.com/mltony/nvda-word-nav/

Best regards
Tony


New WordNav add-on - review requested

Tony Malykh
 

Hello,
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 word deinitions  are:
• 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.

Download:
https://github.com/mltony/nvda-word-nav/releases/latest/download/wordNav.nvda-addon
Website:
https://github.com/mltony/nvda-word-nav/

Best regards
Tony


Help with using an online API?

Meisam Amini <meisamamini21@...>
 

Hello everyone.

I'm a beginner, so sorry for the ignorant question.

I'm trying to use an online api in a global plugin. It's a simple one,
just a get request and the response is a JSON object that contains all
the necessary info.

I know how to use Requests module, so tried to use it. But after
copying its many dependencies finally I encountered a problem with
http.cookies module not being there.

Nothing I did worked. I figured up that NVDA doesn't have the
cookies.py module in the http package, so I added the path to the Lib
folder of my Python installation to the beginning of sys.path so NVDA
could get the cookies module from there, but no luck.

Then tried to use urllib.request, but it gives me 403 http error for
that URL. Don't know why, it opens just fine in my browser and with
requests module.

I appreciate if someone helps me to either solve the problem with
requests module or do the job using another module.

Thanks in advance.


Re: Quick Dictionary with automatic switching of synthesizers for selected languages #addonrelease

Oleksandr Gryshchenko
 

Hi friends,

Joseph, I am very grateful to you for the review!

> * I think it would be best to separate instructions on building the add-on into its own document, as the readme file content will be used  as basis for the add-on entry on community add-ons website.
I agree with you that the add-on help should be issued as a separate document because it has become quite voluminous. Tomorrow I will separate the help page from ReadMe.

> * Can we possibly do a deeper review (if requested) on online services?
Yes of course, I would like the community to conduct a more in-depth review of all my add-ons.

> * Do you expect the add-on to be used in secure mode (logon screen adn so on)? If not, I think it would be best to let the add-on do nothing if NVDA is running in secure mode.
Yes, tomorrow I will add this code to the add-on.

> A suggestion: I think it would be helpful to add wiki-based sources such as Wiktionary provided that API’s to interact with them exists.
Yes, this is a good resource - thanks for the advice!
As far as I know, there used to be a pretty messy API... But I hope that in a few years everything has changed.
I will learn how this can be done.

> There are certain code fragments that could be improved (notably the global plugin constructor and script definitions), but these won’t be done unless the author requests deeper reviews from the community.
I would be very grateful for any advice on improving the code.
I'm still learning to be a developer and would appreciate any recomendations.

@Paul
Thanks for the information.
There really was a error - I have already corrected it and will publish an updated release tomorrow.

Best wishes!
Oleksandr


Re: Add-on Updater 20.12.1 patch released, preparing the add-on for future NVDA releases #addonrelease

Brian's Mail list account
 

Maybe a Christmas Wrapper?
OK sorry.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal E-mail to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users

----- Original Message -----
From: "Joseph Lee" <joseph.lee22590@gmail.com>
To: <nvda-addons@nvda-addons.groups.io>
Sent: Monday, December 14, 2020 2:15 AM
Subject: [nvda-addons] Add-on Updater 20.12.1 patch released, preparing the add-on for future NVDA releases #AddonRelease


Hello all,



Add-on Updater 20.12.1 is now available. This patch prepares the add-on to
support future NVDA releases, specifically changes around Windows version
compatibility checks for add-ons. As always, Add-on Updater can be updated
using Add-on Updater (no bruh, I'm not a rapper).

Cheers,

Joseph






Re: Add-on Updater 20.12.1 patch released, preparing the add-on for future NVDA releases #addonrelease

Matthew Dyer <matthew.dyer83@...>
 

Just grabbed  it this morning.  I  had to run the updater manially for some reason.  I am running the latest master snapshot of nada.  Just thought I would point that out.  Thanks.

Matthew



On Dec 13, 2020, at 9:15 PM, Joseph Lee <joseph.lee22590@...> wrote:

Hello all,
 
Add-on Updater 20.12.1 is now available. This patch prepares the add-on to support future NVDA releases, specifically changes around Windows version compatibility checks for add-ons. As always, Add-on Updater can be updated using Add-on Updater (no bruh, I’m not a rapper).
Cheers,
Joseph

2881 - 2900 of 17054