Date   

Vocalizer version 2 ready for Python 3 and speech refactoring!

Rui Fontes
 

Hello all!

To start the adaptation of Vocalizer from Tiflotecnia, we here invite all licensed users to test the Beta version of the driver!

It is available here:
https://www.dropbox.com/s/7sv75j5016pbpla/vocalizer-driver-2.1.0-ALPHA1-1.nvda-addon?dl=1
This version is only compatible with Alpha versions of NVDA running on Python 3...

Best regards,

Rui Fontes
Tiflotecnia, Lda.


Re: Debug Helper 1.0: new stable add-on released #addonrelease

Cyrille
 

Hello Luke

At home Win 10 1903, NVDA 2019.2, installation OK.
At work:
* NVDA 2019.2
* Win 10 but do not remember the exact version, surely not 1903, maybe something like 16xx
* The addon installation has failed the first time, and succeeded the second time
* Trying to install again on the previously installed version, it has failed at the third time and succeeded at the 4th time.
Sorry, I did not capture the log. If you do not get one until then, I will try to get a log on next Monday.

Cheers,

Cyrille

-----Message d'origine-----
De : nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> De la part de Luke Davis
Envoyé : vendredi 23 août 2019 20:28
À : nvda-addons@nvda-addons.groups.io
Objet : Re: [nvda-addons] Debug Helper 1.0: new stable add-on released #addonrelease

Would one or two others be willing to test this please? I am not seeing any problems on Win 10 1903 64bit, NVDA beta or alpha, and some earlier versions.

If you do test, please report your Windows and NVDA versions.

Again, the URL is:
https://github.com/XLTechie/debugHelper/releases/download/1.0/debugHelper-1.0.nvda-addon

Luke

On Fri, 23 Aug 2019, Ján Kulik wrote:

Hi, installation of the add-on has failed, it cannot be installed _.


Re: Debug Helper 1.0: new stable add-on released #addonrelease

Luke Davis
 

Would one or two others be willing to test this please? I am not seeing any problems on Win 10 1903 64bit, NVDA beta or alpha, and some earlier versions.

If you do test, please report your Windows and NVDA versions.

Again, the URL is: https://github.com/XLTechie/debugHelper/releases/download/1.0/debugHelper-1.0.nvda-addon

Luke

On Fri, 23 Aug 2019, Ján Kulik wrote:

Hi, installation of the add-on has failed, it cannot be installed _.


ToolbarsExplorer updated for 2019.2, no py3 support yet

Alberto Buffolino
 

Hi all,
sorry if I disappeared, they are not great times.
I updated the add-on in subject for 2019.2, because various users reported problems about it.
Dev version is identical to stable, at the moment, but I hope to release soon a version ready for py3/2019.3.
Alberto


Re: Debug Helper 1.0: new stable add-on released #addonrelease

Luke Davis
 

Can you provide some more information please? What version of Windows? What version of NVDA?
It has so far installed fine in all tests that I have run.

Thank you.

Luke

On Fri, 23 Aug 2019, Ján Kulik wrote:

Hi, installation of the add-on has failed, it cannot be installed


Re: Error sometimes in focus highlight add on

Brian's Mail list account
 

Thanks, not sure how much of an issue it is. Nothing actually broke but I do find the add on very handy when I need a set of eyes over to try to tie up what I'm hearing with what is on the screen.
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: "Takuya Nishimoto" <nishimotz@gmail.com>
To: <nvda-addons@nvda-addons.groups.io>
Sent: Friday, August 23, 2019 9:35 AM
Subject: Re: [nvda-addons] Error sometimes in focus highlight add on


Thank you for the report.
The issue is filed as follows.

https://github.com/nvdajp/focusHighlight/issues/20

--
Takuya Nishimoto
nishimotz@gmail.com

2019年8月23日(金) 17:23 Brian's Mail list account via Groups.Io
<bglists=blueyonder.co.uk@groups.io>:


When typing into a message or edit field at apparently random times we get
the error sound in the latest beta of nvda.

IO - speech._speakSpellingGen (09:11:05.130):
Speaking character u'o'
DEBUG - queueHandler.registerGeneratorObject (09:11:05.130):
Adding generator 203
DEBUG - queueHandler.pumpAll (09:11:05.137):
generator 203 finished
ERROR - queueHandler.flushQueue (09:11:05.246):
Error in func update from eventQueue
Traceback (most recent call last):
File "queueHandler.pyc", line 53, in flushQueue
File "C:\nvda test
folder\userConfig\addons\focusHighlight\globalPlugins\focusHighlight.py",
line 600, in update
File "C:\nvda test
folder\userConfig\addons\focusHighlight\globalPlugins\focusHighlight.py",
line 482, in updateLocations
File "C:\nvda test
folder\userConfig\addons\focusHighlight\globalPlugins\focusHighlight.py",
line 341, in updateFocusLocation
File "C:\nvda test
folder\userConfig\addons\focusHighlight\globalPlugins\focusHighlight.py",
line 321, in locationAvailable
TypeError: object of type 'NoneType' has no len()
IO - inputCore.InputManager.executeGesture (09:11:05.428):
Input: kb(desktop):n
IO - speech._speakSpellingGen (09:11:05.440):
Speaking character u'n'
DEBUG - queueHandler.registerGeneratorObject (09:11:05.441):
Adding generator 204

I do not think its destructive but I cannot actually see what the screen is
doing of course, myself.

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




Re: Debug Helper 1.0: new stable add-on released #addonrelease

Ján Kulik
 

Hi, installation of the add-on has failed, it cannot be installed


Re: Error sometimes in focus highlight add on

Takuya Nishimoto
 

Thank you for the report.
The issue is filed as follows.

https://github.com/nvdajp/focusHighlight/issues/20

--
Takuya Nishimoto
nishimotz@gmail.com

2019年8月23日(金) 17:23 Brian's Mail list account via Groups.Io
<bglists=blueyonder.co.uk@groups.io>:



When typing into a message or edit field at apparently random times we get
the error sound in the latest beta of nvda.

IO - speech._speakSpellingGen (09:11:05.130):
Speaking character u'o'
DEBUG - queueHandler.registerGeneratorObject (09:11:05.130):
Adding generator 203
DEBUG - queueHandler.pumpAll (09:11:05.137):
generator 203 finished
ERROR - queueHandler.flushQueue (09:11:05.246):
Error in func update from eventQueue
Traceback (most recent call last):
File "queueHandler.pyc", line 53, in flushQueue
File "C:\nvda test
folder\userConfig\addons\focusHighlight\globalPlugins\focusHighlight.py",
line 600, in update
File "C:\nvda test
folder\userConfig\addons\focusHighlight\globalPlugins\focusHighlight.py",
line 482, in updateLocations
File "C:\nvda test
folder\userConfig\addons\focusHighlight\globalPlugins\focusHighlight.py",
line 341, in updateFocusLocation
File "C:\nvda test
folder\userConfig\addons\focusHighlight\globalPlugins\focusHighlight.py",
line 321, in locationAvailable
TypeError: object of type 'NoneType' has no len()
IO - inputCore.InputManager.executeGesture (09:11:05.428):
Input: kb(desktop):n
IO - speech._speakSpellingGen (09:11:05.440):
Speaking character u'n'
DEBUG - queueHandler.registerGeneratorObject (09:11:05.441):
Adding generator 204

I do not think its destructive but I cannot actually see what the screen is
doing of course, myself.

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




Re: Re : [nvda-addons] Debug Helper 1.0: new stable add-on released #addonrelease

Luke Davis
 

Hi Cyrille

Thank you, I will definitely look at incorporating some or all of these!
Particularly, as you say, I can already think of times I could have used debugTool, so I really like the idea of bringing that in.

I'll be in touch off list next week.

Luke

On Fri, 23 Aug 2019, Cyrille via Groups.Io wrote:

Hello Luke
I have some scripts that I use for debug purpose. All these scripts are in the following repo :
https://github.com/CyrilleB79/NVDAScripts
The doc for these scripts is in the readme that appears on the main page of the repo.
* debugTool : https://raw.githubusercontent.com/CyrilleB79/NVDAScripts/master/globalPlugins/debugTool.py
Allows to activate and de-activate a stack trace log each time NVDA speaks something. Useful if you want to know which function has made NVDA speak. This
script also contains instructions if you want to trigger stack trace log on an other output function ; an example with braille is commented.
* beepError : https://raw.githubusercontent.com/CyrilleB79/NVDAScripts/master/globalPlugins/beepError.py
This script activate the beep on error NVDA feature even on NVDA stable releases. Useful if you want to track bugs in environments where you do not want to
install alpha or beta version of NVDA such as work's computer, shared computer (with NVDA shared with other users...)
* windowutil: https://github.com/CyrilleB79/NVDAScripts/raw/master/globalPlugins/windowutil.py
A script to get quickly info on an object, such as name, role, value, window control ID, python class mro(), etc.
If you feel these scripts could be integrated in your addon, feel free to copy, rework and/or integrate them partially or entirely. I think that integrating
debugTool (stack trace log on speech) could be the most interesting to integrate.
If you prefer, I may also provide PR  once you have agreed on a feature. However, I do not know when I will be able to make this/these PR(s).
Cheers,
Cyrille
----- Mail d'origine -----
De: Luke Davis <luke@newanswertech.com>
À: nvda-addons@groups.io
Envoyé: Fri, 23 Aug 2019 05:03:50 +0200 (CEST)
Objet: [nvda-addons] Debug Helper 1.0: new stable add-on released #addonrelease
Hello all
I am herewith releasing the first stable version of Debug Helper. This is an
add-on which is intended to help people who do a lot of work with the NVDA log.
If you are trying to report problems with something you're doing, or writing an
add-on, or trying to fix something, you may find it useful to be able to jump
right to the spot in the log before or after the error occurred, or some
important output happened.
At the press of a key (default: nvda+shift+F1), this add-on will insert a "mark
line" in the NVDA log, which you can then search for in a text editor. Each mark
line includes a sequential number, and can have 1 or more blank lines
before/after it to aid in finding it quickly when fast-arrowing.
It is Python 2 and 3 compatible, and works in NVDA versions from 2017.3
through 2019.3.
The add-on will hopefully be on the community site soon, but for now it can be
downloaded here:
https://github.com/XLTechie/debugHelper/releases/download/1.0/debugHelper-1.0.nvda-addon
Full documentation, including larger usage examples:
https://github.com/XLTechie/debugHelper/blob/stable/readme.md
GitHub repo (for issues/to download development versions, etc.):
https://github.com/XLTechie/debugHelper
This is a small add-on with a very specific set of use cases right now, but if
you have ideas for ways it could be expanded, please contact me.
Luke


Error sometimes in focus highlight add on

Brian's Mail list account
 

When typing into a message or edit field at apparently random times we get the error sound in the latest beta of nvda.

IO - speech._speakSpellingGen (09:11:05.130):
Speaking character u'o'
DEBUG - queueHandler.registerGeneratorObject (09:11:05.130):
Adding generator 203
DEBUG - queueHandler.pumpAll (09:11:05.137):
generator 203 finished
ERROR - queueHandler.flushQueue (09:11:05.246):
Error in func update from eventQueue
Traceback (most recent call last):
File "queueHandler.pyc", line 53, in flushQueue
File "C:\nvda test folder\userConfig\addons\focusHighlight\globalPlugins\focusHighlight.py", line 600, in update
File "C:\nvda test folder\userConfig\addons\focusHighlight\globalPlugins\focusHighlight.py", line 482, in updateLocations
File "C:\nvda test folder\userConfig\addons\focusHighlight\globalPlugins\focusHighlight.py", line 341, in updateFocusLocation
File "C:\nvda test folder\userConfig\addons\focusHighlight\globalPlugins\focusHighlight.py", line 321, in locationAvailable
TypeError: object of type 'NoneType' has no len()
IO - inputCore.InputManager.executeGesture (09:11:05.428):
Input: kb(desktop):n
IO - speech._speakSpellingGen (09:11:05.440):
Speaking character u'n'
DEBUG - queueHandler.registerGeneratorObject (09:11:05.441):
Adding generator 204

I do not think its destructive but I cannot actually see what the screen is doing of course, myself.

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


Re : [nvda-addons] Debug Helper 1.0: new stable add-on released #addonrelease

Cyrille
 

Hello Luke
I have some scripts that I use for debug purpose. All these scripts are in the following repo :
The doc for these scripts is in the readme that appears on the main page of the repo.
Allows to activate and de-activate a stack trace log each time NVDA speaks something. Useful if you want to know which function has made NVDA speak. This script also contains instructions if you want to trigger stack trace log on an other output function ; an example with braille is commented.
This script activate the beep on error NVDA feature even on NVDA stable releases. Useful if you want to track bugs in environments where you do not want to install alpha or beta version of NVDA such as work's computer, shared computer (with NVDA shared with other users...)

A script to get quickly info on an object, such as name, role, value, window control ID, python class mro(), etc.
If you feel these scripts could be integrated in your addon, feel free to copy, rework and/or integrate them partially or entirely. I think that integrating debugTool (stack trace log on speech) could be the most interesting to integrate.
If you prefer, I may also provide PR  once you have agreed on a feature. However, I do not know when I will be able to make this/these PR(s).
Cheers,
Cyrille
----- Mail d'origine -----
De: Luke Davis <luke@...>
À: nvda-addons@groups.io
Envoyé: Fri, 23 Aug 2019 05:03:50 +0200 (CEST)
Objet: [nvda-addons] Debug Helper 1.0: new stable add-on released #addonrelease
Hello all
I am herewith releasing the first stable version of Debug Helper. This is an
add-on which is intended to help people who do a lot of work with the NVDA log.
If you are trying to report problems with something you're doing, or writing an
add-on, or trying to fix something, you may find it useful to be able to jump
right to the spot in the log before or after the error occurred, or some
important output happened.
At the press of a key (default: nvda+shift+F1), this add-on will insert a "mark
line" in the NVDA log, which you can then search for in a text editor. Each mark
line includes a sequential number, and can have 1 or more blank lines
before/after it to aid in finding it quickly when fast-arrowing.
It is Python 2 and 3 compatible, and works in NVDA versions from 2017.3
through 2019.3.
The add-on will hopefully be on the community site soon, but for now it can be
downloaded here:
https://github.com/XLTechie/debugHelper/releases/download/1.0/debugHelper-1.0.nvda-addon
Full documentation, including larger usage examples:
https://github.com/XLTechie/debugHelper/blob/stable/readme.md
GitHub repo (for issues/to download development versions, etc.):
https://github.com/XLTechie/debugHelper
This is a small add-on with a very specific set of use cases right now, but if
you have ideas for ways it could be expanded, please contact me.
Luke


Debug Helper 1.0: new stable add-on released #addonrelease

Luke Davis
 

Hello all

I am herewith releasing the first stable version of Debug Helper. This is an add-on which is intended to help people who do a lot of work with the NVDA log. If you are trying to report problems with something you're doing, or writing an add-on, or trying to fix something, you may find it useful to be able to jump right to the spot in the log before or after the error occurred, or some important output happened.

At the press of a key (default: nvda+shift+F1), this add-on will insert a "mark line" in the NVDA log, which you can then search for in a text editor. Each mark line includes a sequential number, and can have 1 or more blank lines before/after it to aid in finding it quickly when fast-arrowing.

It is Python 2 and 3 compatible, and works in NVDA versions from 2017.3 through 2019.3.
The add-on will hopefully be on the community site soon, but for now it can be downloaded here: https://github.com/XLTechie/debugHelper/releases/download/1.0/debugHelper-1.0.nvda-addon

Full documentation, including larger usage examples: https://github.com/XLTechie/debugHelper/blob/stable/readme.md

GitHub repo (for issues/to download development versions, etc.):
https://github.com/XLTechie/debugHelper

This is a small add-on with a very specific set of use cases right now, but if you have ideas for ways it could be expanded, please contact me.

Luke


Release Character Information 1.1

Cyrille
 

Hello
The stable release of Character Information 1.1 is now available.
Download link at :
@Website admins:
Could you please update stable and dev link to this release link ?
Same feature as previous dev version :
• Updates to support newer versions of NVDA (Python 2 and 3 compatible)
• Releases performed now with appveyo
Cheers,
Cyrille


Re: Translate 2019.03.3 is ready for review #addon-review

Locutor Antonio Cezar
 

Ok. Thanks.



Por favor, assine nossa petição no link abaixo, compartilhe com todos os seus amigos, e colabore com a gente! Em favor do suporte para teclados Braille com digitação multitoque diretamente na tela de dispositivos Android para qualquer leitor de telas, principalmente para o Talkback!

https://secure.avaaz.org/po/petition/Google_Inc_Talkback_Development_Team_Google_Disability_Support_Team_PRECISAMOS_DO_BRAILLE_NO_ANDROID_TAMBEM/

Yannick PLASSIARD escreveu:

Hi,

This is a known issue, as the Python3 migration for this module is not yet published.


Stay tuned for updates in the coming week.



Le 22/08/2019 à 13:46, Locutor Antonio Cezar a écrit :

No compatible NVDA Version threshold-18166,75c8d00e, here... Thanks.



Por favor, assine nossa petição no link abaixo, compartilhe com todos os seus amigos, e colabore com a gente! Em favor do suporte para teclados Braille com digitação multitoque diretamente na tela de dispositivos Android para qualquer leitor de telas, principalmente para o Talkback!

https://secure.avaaz.org/po/petition/Google_Inc_Talkback_Development_Team_Google_Disability_Support_Team_PRECISAMOS_DO_BRAILLE_NO_ANDROID_TAMBEM/

Yannick PLASSIARD escreveu:

Dear all,


A new add-on version will published soon to address Python3 compatibility, during this week I think.


@Paulina: It is currently not possible to change the translation destination language: the language is set either to the NVDA's language, or the Windows's user language.


Cheers,


Yannick


Le 19/08/2019 à 12:47, Paulina Gajoch a écrit :

Hello,

Sorry for question, but how to set languages in his addon?

Best regards,

Paulina

W dniu 18.08.2019 o 22:58, Rémy Ruiz pisze:

Hello Adriani,

translate-2019.03.3.nvda-addon
https://github.com/yplassiard/nvda-translate/releases/download/v2019.03.3/translate-2019.03.3.nvda-addon

Source:

Release v2019.03.3 · yplassiard/nvda-translate · GitHub

https://github.com/yplassiard/nvda-translate/releases/tag/v2019.03.3


Thanks to him.

Cheers.

Rémy

Le 18/08/2019 à 21:14, Adriani Botez a écrit :

Hello all,

 

what is the status for this addon?

 

@Yannick could you please post the link to the last version for review? It seems a review has been forgotten here. I must admit at that time there were lot of things happening and there are too less people who review addons.

 

Best

Adriani

 

Von: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> Im Auftrag von Yannick PLASSIARD
Gesendet: Montag, 18. März 2019 15:12
An: nvda-addons@nvda-addons.groups.io
Betreff: [nvda-addons] Translate 2019.03.3 is ready for review #addon-review

 

Dear all,

The NVDA Translate v2019.03.3 module is ready for review and to be used by everyone.

In this version:

- Fixed cache saving/loading issues

- Separated cache files per application so that it is easier to distribute them.

 

The release is here:

 

Enjoy,

 


 

--

--

Yannick PLASSIARD

plassiardyannick@...


Re: Translate 2019.03.3 is ready for review #addon-review

Yannick PLASSIARD <plassiardyannick@...>
 

Hi,

This is a known issue, as the Python3 migration for this module is not yet published.


Stay tuned for updates in the coming week.



Le 22/08/2019 à 13:46, Locutor Antonio Cezar a écrit :

No compatible NVDA Version threshold-18166,75c8d00e, here... Thanks.



Por favor, assine nossa petição no link abaixo, compartilhe com todos os seus amigos, e colabore com a gente! Em favor do suporte para teclados Braille com digitação multitoque diretamente na tela de dispositivos Android para qualquer leitor de telas, principalmente para o Talkback!

https://secure.avaaz.org/po/petition/Google_Inc_Talkback_Development_Team_Google_Disability_Support_Team_PRECISAMOS_DO_BRAILLE_NO_ANDROID_TAMBEM/

Yannick PLASSIARD escreveu:

Dear all,


A new add-on version will published soon to address Python3 compatibility, during this week I think.


@Paulina: It is currently not possible to change the translation destination language: the language is set either to the NVDA's language, or the Windows's user language.


Cheers,


Yannick


Le 19/08/2019 à 12:47, Paulina Gajoch a écrit :

Hello,

Sorry for question, but how to set languages in his addon?

Best regards,

Paulina

W dniu 18.08.2019 o 22:58, Rémy Ruiz pisze:

Hello Adriani,

translate-2019.03.3.nvda-addon
https://github.com/yplassiard/nvda-translate/releases/download/v2019.03.3/translate-2019.03.3.nvda-addon

Source:

Release v2019.03.3 · yplassiard/nvda-translate · GitHub

https://github.com/yplassiard/nvda-translate/releases/tag/v2019.03.3


Thanks to him.

Cheers.

Rémy

Le 18/08/2019 à 21:14, Adriani Botez a écrit :

Hello all,

 

what is the status for this addon?

 

@Yannick could you please post the link to the last version for review? It seems a review has been forgotten here. I must admit at that time there were lot of things happening and there are too less people who review addons.

 

Best

Adriani

 

Von: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> Im Auftrag von Yannick PLASSIARD
Gesendet: Montag, 18. März 2019 15:12
An: nvda-addons@nvda-addons.groups.io
Betreff: [nvda-addons] Translate 2019.03.3 is ready for review #addon-review

 

Dear all,

The NVDA Translate v2019.03.3 module is ready for review and to be used by everyone.

In this version:

- Fixed cache saving/loading issues

- Separated cache files per application so that it is easier to distribute them.

 

The release is here:

 

Enjoy,

 


 

--

--

Yannick PLASSIARD

plassiardyannick@...


Re: Translate 2019.03.3 is ready for review #addon-review

Locutor Antonio Cezar
 

No compatible NVDA Version threshold-18166,75c8d00e, here... Thanks.



Por favor, assine nossa petição no link abaixo, compartilhe com todos os seus amigos, e colabore com a gente! Em favor do suporte para teclados Braille com digitação multitoque diretamente na tela de dispositivos Android para qualquer leitor de telas, principalmente para o Talkback!

https://secure.avaaz.org/po/petition/Google_Inc_Talkback_Development_Team_Google_Disability_Support_Team_PRECISAMOS_DO_BRAILLE_NO_ANDROID_TAMBEM/

Yannick PLASSIARD escreveu:

Dear all,


A new add-on version will published soon to address Python3 compatibility, during this week I think.


@Paulina: It is currently not possible to change the translation destination language: the language is set either to the NVDA's language, or the Windows's user language.


Cheers,


Yannick


Le 19/08/2019 à 12:47, Paulina Gajoch a écrit :

Hello,

Sorry for question, but how to set languages in his addon?

Best regards,

Paulina

W dniu 18.08.2019 o 22:58, Rémy Ruiz pisze:

Hello Adriani,

translate-2019.03.3.nvda-addon
https://github.com/yplassiard/nvda-translate/releases/download/v2019.03.3/translate-2019.03.3.nvda-addon

Source:

Release v2019.03.3 · yplassiard/nvda-translate · GitHub

https://github.com/yplassiard/nvda-translate/releases/tag/v2019.03.3


Thanks to him.

Cheers.

Rémy

Le 18/08/2019 à 21:14, Adriani Botez a écrit :

Hello all,

 

what is the status for this addon?

 

@Yannick could you please post the link to the last version for review? It seems a review has been forgotten here. I must admit at that time there were lot of things happening and there are too less people who review addons.

 

Best

Adriani

 

Von: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> Im Auftrag von Yannick PLASSIARD
Gesendet: Montag, 18. März 2019 15:12
An: nvda-addons@nvda-addons.groups.io
Betreff: [nvda-addons] Translate 2019.03.3 is ready for review #addon-review

 

Dear all,

The NVDA Translate v2019.03.3 module is ready for review and to be used by everyone.

In this version:

- Fixed cache saving/loading issues

- Separated cache files per application so that it is easier to distribute them.

 

The release is here:

 

Enjoy,

 


 

--

--

Yannick PLASSIARD

plassiardyannick@...


Developer toolkit (DTK) 2020.1.0 now available!

Andy B.
 

Hi,

DTK 2020.1.0 is now available for download! To download the newest version, visit the following link: https://github.com/ajborka/nvda_developer_toolkit/releases/tag/2020.1.0. After the 2020.1.0 release, I am stepping back from new feature development for a while and focusing on cleaning up documentation/source code. I will take new feature requests and bug reports for the next development cycle during this time. However, I will only address critical/fatal bugs. I thank you for your support with the development of DTK and hope it serves you well. I will remain active on the DTK project and in the NVDA community, and hope to return to active development by the end of September. Feel free to contact me if the need arises.


Re: nvda-addons] Workaround fix - NVDA starts after logon even when this is disabled (Win 10 1903)

James Scholes
 

If this particular code works for your use case, great. In a shared environment such as a school or work network, NVDA shouldn't even be starting if not configured to, and therefore a network administrator should find a work-around for this (I'm sure there are some). For example, disallow nvda.exe to run on all profiles other than those which explicitly should be allowed.

Regards,

James Scholes

On 22/08/2019 at 12:44 am, Luke Davis wrote:
On Wed, 21 Aug 2019, Cyrille via Groups.Io wrote:

NVDA from source and thus will not propose a PR for NVDA core. I agree that exiting NVDA at first stage of startup (just after config reading) would be
cleaner. If you or anyone else want to make such a PR, just feel free.
I also don't have a source setup at the moment to do work on core, which is why I didn't try to do this, and won't be trying for some weeks at least.
It does need to be done by somebody, however--there are organizations, as described in the original issue, that really need this fixed immediately.
I think it is not good for the public relations of NVDA, regardless of whether this happens to all other screen readers or not, to have this problem outstanding when the fix is rather easy.

2. Change name and pack it as an addon. I do not understand why this would change since NVDA full initialization is performed anyway, regardless scripts'
and addons' loading order, as explaned earlier. Anyway I may have missed something. I can perform this packaging and renaming if needed.
No, you're right. Interestingly though, I tried packaging it myself (without renaming), and found that I could not get it to run as an add-on, even though the same code does run as a scratchpad script.
I have not figured out why yet.
Regards,
Luke


Re: [nvda-translations] Audio theme 3d - request of removal from the official website due to missing maintenance

Brian's Mail list account
 

I have said my piece as a user.
Do we have a full list of add ons that don't work with Python 3 or are in some way an issue with nvda in the latest versions of Windows?
I have seen ref to dropbox, and understand this is going to get an official update shortly, I myself modified extended Winamp to fix the unicode issue and put it on a dropbox link, but have not actually said its put on the web site as the original author is still around and my have plans to alter or enhance it.
I note that Indent Nav seems not to work in Python 3 at least on Windows 7, nor text nav either.

Others I've not tried, but Remote is one which is in need of a bit of sticking plaster.
The synths Pico and Speech player in Espeak load after some modification but no longer are seen in the list of synths. I'm not sure if they need work in nvda or in the drivers themselves.

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: "Noelia Ruiz" <nrm1977@gmail.com>
To: <nvda-translations@groups.io>
Cc: <nvda-addons@nvda-addons.groups.io>; <nvda@nvda.groups.io>
Sent: Thursday, August 22, 2019 12:03 AM
Subject: Re: [nvda-addons] [nvda-translations] Audio theme 3d - request of removal from the official website due to missing maintenance


I agree with Adrianis justification. If concerns are justified, in case nobody does this before, I will remove this add-on for now from the stable section of the website. As a minimum, I think that stable add-ons shouldnt cause issues for NVDA or Windows, and if maintainers cannot fix them in a period of time, add-ons must be removed at least from the stable section. And of course, if addons are harmful, at least potentially, like announced for BlindExtra, they must be deleted from development section too. Addons are shared in websites, repos, Dropbox, etc., and the website accessible from add-ons manager should be distinguished by the review process, including security and certain requirements regarding user experience. At least for me it is painful the deletion of add-ons, but it is a duty for reviewers and we have the possibility of ignoring these rules, but in this case I think that the whole addons website should be abandoned, leting people to search addons in lots of webpages or wherever they want, without spending our time on this. Just to confirm my agreement with Adriani. Cheers.

Enviado desde mi iPhone

El 22 ago 2019, a las 0:16, Adriani Botez <adriani.botez@gmail.com> escribió:

Hello all,

to clarify abit my request, with incompatible addons I meant the addons where no maintenance is given, where we lost contact to the author etc. Those addons should in my opinion go offline for a period until a maintainer is found.

For developers, the old versions of every addon can be found most often on github anyway. For the users, it is important that people do not run into issues and do not get the impression that NVDA is getting worse. We want to avoid huge workloads which could arise if people report unrelated issues on github, driving long discussions in which at the end it comes out the issue was caused by an old addon.

The justification for my request is as follows:
The community has implemented rules and processes for addons which can be posted on the website. That’s why we have a community review for every new addon at all. And by the way, the community review contains also compatibility checks. If this is not given, the new addon is not being posted. So is it not unfair to have an old and abandoned addon on the website while other engaged authors create new addons and apply for a review but they do not get posted? In my view, the addons website should guarantee security and compatibility for users. Otherwise we can drop all our review rules and processes and can post anything on the website.

But note that this official addons website is also the face of the NVDA community when it comes to corporate environments. We must make sure that people are able to bring arguments when security questions are raised. How should users bring reliable arguments when incompatible addons and most important, addons which cause significant bugs, can be downloaded from the official website?

So the question is, what should be the purpose of an official addon website? If you expect the addons website to be an archive for all kinds of old and incompatible addons along with new addons, then we do not need to spend time and ressources on reviewing addons at all. But I hope the community will not choose this way.


Best regards
Adriani




Von: adriani.botez@gmail.com <adriani.botez@gmail.com>
Gesendet: Mittwoch, 21. August 2019 19:04
An: nvda-addons@nvda-addons.groups.io
Cc: nvda-translations@groups.io; nvda@nvda.groups.io
Betreff: Audio theme 3d - request of removal from the official website due to missing maintenance

Dear all,

with this message I request the community to remove the audiotheme 3d from the website and from the translations system because it seems we cannot find someone who maintain it. This addon causes problems in NVDA 2019.2 (i.e. NVDA does not announce elements on desktop after closing applications). It will also cause problems if the compatibility is not being updated.

To avoid invalid issues in NVDA’s repository on github, I further suggest to remove all incompatible addons from the website once NVDA 2019.3 comes out. Otherwise people, especially beginners, will download incompatible addons and will run into issues.

The authors are very welcome to request a re-integration of their addons on the website as soon as the compatibility flags are updated.

Thanks for your understanding.

Best regards
Adriani


Re: Audio theme 3d - request of removal from the official website due to missing maintenance

Brian's Mail list account
 

Many web sites of a similar nature tend to have clearly marked links to programs which are no longer currently maintained or are for older versions of windows. I would suggest that this approach may well be the way to go here. Its very confusing for a user to simply say this add on was removed go to github or talk to the author.
As you say, links to an author can be lost quite easily.

Just saying.
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: "Adriani Botez" <adriani.botez@gmail.com>
To: <nvda-addons@nvda-addons.groups.io>
Cc: <nvda-translations@groups.io>; <nvda@nvda.groups.io>
Sent: Wednesday, August 21, 2019 11:16 PM
Subject: Re: [nvda-addons] Audio theme 3d - request of removal from the official website due to missing maintenance


Hello all,



to clarify abit my request, with incompatible addons I meant the addons
where no maintenance is given, where we lost contact to the author etc.
Those addons should in my opinion go offline for a period until a maintainer
is found.



For developers, the old versions of every addon can be found most often on
github anyway. For the users, it is important that people do not run into
issues and do not get the impression that NVDA is getting worse. We want to
avoid huge workloads which could arise if people report unrelated issues on
github, driving long discussions in which at the end it comes out the issue
was caused by an old addon.



The justification for my request is as follows:

The community has implemented rules and processes for addons which can be
posted on the website. That's why we have a community review for every new
addon at all. And by the way, the community review contains also
compatibility checks. If this is not given, the new addon is not being
posted. So is it not unfair to have an old and abandoned addon on the
website while other engaged authors create new addons and apply for a review
but they do not get posted? In my view, the addons website should guarantee
security and compatibility for users. Otherwise we can drop all our review
rules and processes and can post anything on the website.



But note that this official addons website is also the face of the NVDA
community when it comes to corporate environments. We must make sure that
people are able to bring arguments when security questions are raised. How
should users bring reliable arguments when incompatible addons and most
important, addons which cause significant bugs, can be downloaded from the
official website?



So the question is, what should be the purpose of an official addon website?
If you expect the addons website to be an archive for all kinds of old and
incompatible addons along with new addons, then we do not need to spend time
and ressources on reviewing addons at all. But I hope the community will not
choose this way.





Best regards

Adriani









Von: adriani.botez@gmail.com <adriani.botez@gmail.com>
Gesendet: Mittwoch, 21. August 2019 19:04
An: nvda-addons@nvda-addons.groups.io
Cc: nvda-translations@groups.io; nvda@nvda.groups.io
Betreff: Audio theme 3d - request of removal from the official website due
to missing maintenance



Dear all,



with this message I request the community to remove the audiotheme 3d from
the website and from the translations system because it seems we cannot find
someone who maintain it. This addon causes problems in NVDA 2019.2 (i.e.
NVDA does not announce elements on desktop after closing applications). It
will also cause problems if the compatibility is not being updated.



To avoid invalid issues in NVDA's repository on github, I further suggest to
remove all incompatible addons from the website once NVDA 2019.3 comes out.
Otherwise people, especially beginners, will download incompatible addons
and will run into issues.



The authors are very welcome to request a re-integration of their addons on
the website as soon as the compatibility flags are updated.



Thanks for your understanding.



Best regards

Adriani





5421 - 5440 of 14681