Date   

StationPlaylist add-on 20.10 released, version 20.11 will require NVDA 2020.1 or later 3AddonRelease

 

Hello everyone,

StationPlaylist add-on 20.10 is now available. This release is applicable for anyone using 20.09.0 (initial 20.09 release) who decided to not update to 20.09.1-LTS or those using Studio 5.30 or later. In case you did install 20.09.1-LTS but would like to switch back to stable update channel, the direct download link for 20.10 is:

https://github.com/josephsl/stationPlaylist/releases/download/20.10/stationPlaylist-20.10.nvda-addon

 

This release includes internal settings file format changes (as a result, you can’t downgrade) and fixes an issue where NVDA will say “unavailable” when trying to switch to Studio when it is minimized to system tray. Also, this release is the last stable version to be compatible with NVDA 2019.3 – upcoming version 20.11 (November) will require NVDA 2020.1 (and a heads up: early next year, a stable version of this add-on will be released that will absolutely require upcoming NVDA 2020.3).

 

Cheers,

Joseph


Re: numpadNavMode Add-on: all new beta release 0.5-dev for testing & review

Luke Davis
 

Hi Carlos-Esteban

First, thank you for your review.

Answering one comment:

The idea of enable this add-on to start NVDA or when the user change to the laptop layout is very good for a future version.
I have a test up for that first feature. It is a very small change, based on well known code. I was going to just hold it for the stable version so as not to upset the review process. But if you want to look at it, it is here:
https://github.com/opensourcesys/numpadNavMode/releases/download/0.6-dev/numpadNavMode-0.6-dev.nvda-addon

Doing it automatically for laptop layout will definitely not be happening until after the first stable release.

Regards,

Luke


Re: nvMathViewer add-on for viewing math content in LaTeX and AsciiMath notations as MathML

Nikita
 

Hi Rowen,

Please tell me if this error occurs every time or from time to time?

Best regards, Nikita.

 

From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of rowen brian
Sent: Wednesday, September 16, 2020 2:00 PM
To: nvda-addons@nvda-addons.groups.io
Subject: Re: [nvda-addons] nvMathViewer add-on for viewing math content in LaTeX and AsciiMath notations as MathML

 

Hi Nikita.
I did encounter an error. Here is my error log.

The formula for testing: x_{1, 2} = \frac{-b \pm \sqrt{b^2 -4ac}}{2a}

INFO - __main__ (18:53:30.182) - MainThread (13524):

Starting NVDA version 2020.3beta1

INFO - core.main (18:53:30.277) - MainThread (13524):

Config dir: C:\Users\manch\AppData\Roaming\nvda

INFO - config.ConfigManager._loadConfig (18:53:30.277) - MainThread (13524):

Loading config: C:\Users\manch\AppData\Roaming\nvda\nvda.ini

INFO - core.main (18:53:30.352) - MainThread (13524):

Using Windows version 10.0.19041 workstation

INFO - core.main (18:53:30.352) - MainThread (13524):

Using Python version 3.7.9 (tags/v3.7.9:13c94747c7, Aug 17 2020, 18:01:55) [MSC v.1900 32 bit (Intel)]

INFO - core.main (18:53:30.352) - MainThread (13524):

Using comtypes version 1.1.7

INFO - core.main (18:53:30.352) - MainThread (13524):

Using configobj version 5.1.0 with validate version 1.0.1

INFO - synthDriverHandler.setSynth (18:53:30.756) - MainThread (13524):

Loaded synthDriver vocalizer_expressive2

INFO - core.main (18:53:30.756) - MainThread (13524):

Using wx version 4.0.3 msw (phoenix) wxWidgets 3.0.5 with six version 1.12.0

INFO - brailleInput.initialize (18:53:30.757) - MainThread (13524):

Braille input initialized

INFO - braille.initialize (18:53:30.758) - MainThread (13524):

Using liblouis version 3.14.0

INFO - braille.initialize (18:53:30.761) - MainThread (13524):

Using pySerial version 3.4

INFO - braille.BrailleHandler.setDisplayByName (18:53:30.771) - MainThread (13524):

Loaded braille display driver brltty, current display has 40 cells.

INFO - core.main (18:53:30.975) - MainThread (13524):

Java Access Bridge support initialized

INFO - _UIAHandler.UIAHandler.MTAThreadFunc (18:53:30.985) - _UIAHandler.UIAHandler.MTAThread (10028):

UIAutomation: IUIAutomation6

DEBUGWARNING - inputCore.InputManager.loadLocaleGestureMap (18:53:31.087) - MainThread (13524):

No locale gesture map for language zh_CN

DEBUGWARNING - touchHandler.touchSupported (18:53:31.103) - MainThread (13524):

No touch devices found

INFO - external:globalPlugins.starClip.patch_speak_functions (18:53:31.901) - MainThread (13524):

Patched speak function

IO - external:globalPlugins.fixime.GuessComposition.get_code_by_name (18:53:31.941) - MainThread (13524):

controlconverted to 17

IO - external:globalPlugins.fixime.GuessComposition.get_code_by_name (18:53:31.942) - MainThread (13524):

numpadenterconverted to 13

IO - external:globalPlugins.fixime.GuessComposition.get_code_by_name (18:53:31.942) - MainThread (13524):

enterconverted to 13

INFO - external:globalPlugins.fixime.GlobalPlugin.refreshLayoutString (18:53:31.946) - MainThread (13524):

2052

INFO - external:globalPlugins.fixime.GlobalPlugin.refreshLayoutString (18:53:31.946) - MainThread (13524):

00000804

IO - inputCore.InputManager.executeGesture (18:53:31.949) - winInputHook (1372):

Input: kb(laptop):windows+shift+space

INFO - external:globalPlugins.fixime.GlobalPlugin.refreshLayoutString (18:53:31.951) - MainThread (13524):

2052

INFO - external:globalPlugins.fixime.GlobalPlugin.refreshLayoutString (18:53:31.951) - MainThread (13524):

00000804

IO - inputCore.InputManager.executeGesture (18:53:31.952) - winInputHook (1372):

Input: kb(laptop):windows+space

INFO - external:globalPlugins.fixime.GlobalPlugin.refreshLayoutString (18:53:31.953) - MainThread (13524):

2052

INFO - external:globalPlugins.fixime.GlobalPlugin.refreshLayoutString (18:53:31.953) - MainThread (13524):

00000804

IO - braille.BrailleBuffer.update (18:53:32.029) - MainThread (13524):

Braille regions text: ['NVDA 已启']

IO - braille.BrailleHandler.update (18:53:32.029) - MainThread (13524):

Braille window dots: 6 6 1345 1236 145 1 - 24 3 13 24 3 145 256 23

INFO - core.main (18:53:32.032) - MainThread (13524):

NVDA initialized

IO - braille.BrailleBuffer.update (18:53:32.046) - MainThread (13524):

Braille regions text: ['桌面 窗口']

INFO - external:globalPlugins.fixime.GlobalPlugin.event_typedCharacter (18:53:32.058) - MainThread (13524):

<NVDAObjects.window.Desktop object at 0x06656F30>

WARNING - characterProcessing.SpeechSymbolProcessor.__init__ (18:53:32.119) - MainThread (13524):

Replacement not defined in locale zh_CN for symbol:

IO - speech.speak (18:53:32.159) - MainThread (13524):

Speaking [LangChangeCommand ('zh_CN'), '空格', EndUtteranceCommand()]

INFO - external:globalPlugins.fixime.GlobalPlugin.event_typedCharacter (18:53:32.160) - MainThread (13524):

<NVDAObjects.window.Desktop object at 0x06656F30>

IO - speech.speak (18:53:32.160) - MainThread (13524):

Speaking [LangChangeCommand ('zh_CN'), '空格', EndUtteranceCommand()]

DEBUGWARNING - Python warning (18:53:32.192) - MainThread (13524):

C:\Program Files (x86)\NVDA\library.zip\api.py:287: DeprecationWarning: Yield() is deprecated

IO - speech.speak (18:53:32.193) - MainThread (13524):

Speaking [LangChangeCommand ('zh_CN'), '务栏', CancellableSpeech (still valid devInfo( isCanceledCache: False, isValidCallback: True, isValidCallbackDevInfo:  )]

IO - braille.BrailleBuffer.update (18:53:32.193) - MainThread (13524):

Braille regions text: ['务栏']

IO - inputCore.InputManager.executeGesture (18:53:32.938) - winInputHook (1372):

Input: kb(laptop):alt+tab

INFO - external:globalPlugins.fixime.GlobalPlugin.event_typedCharacter (18:53:32.948) - MainThread (13524):

<NVDAObjects.IAccessible.Taskbar object at 0x0AA05530>

IO - speech.speak (18:53:33.041) - MainThread (13524):

Speaking [LangChangeCommand ('zh_CN'), '*标题 - 记事本', CancellableSpeech (still valid devInfo( isCanceledCache: False, isValidCallback: True, isValidCallbackDevInfo:  )]

IO - braille.BrailleBuffer.update (18:53:33.042) - MainThread (13524):

Braille regions text: ['*标题 - 记事本']

IO - braille.BrailleHandler.update (18:53:33.042) - MainThread (13524):

Braille window dots: 35 35 136 2 12 345 1 2345 24 2 - 36 - 1245 24 23 156 23 12 356 3

IO - speech.speak (18:53:33.179) - MainThread (13524):

Speaking [LangChangeCommand ('zh_CN'), '*标题 - 记事本', CancellableSpeech (still valid devInfo( isCanceledCache: False, isValidCallback: True, isValidCallbackDevInfo:  )]

IO - braille.BrailleBuffer.update (18:53:33.180) - MainThread (13524):

Braille regions text: ['*标题 - 记事本']

IO - braille.BrailleHandler.update (18:53:33.180) - MainThread (13524):

Braille window dots: 35 35 136 2 12 345 1 2345 24 2 - 36 - 1245 24 23 156 23 12 356 3

INFO - external:globalPlugins.fixime.GlobalPlugin.add_capture_function (18:53:33.225) - MainThread (13524):

Added capture function

IO - speech.speak (18:53:33.228) - MainThread (13524):

Speaking [LangChangeCommand ('zh_CN'), '文本编辑器', '编辑框', '多行', CancellableSpeech (still valid devInfo( isCanceledCache: False, isValidCallback: True, isValidCallbackDevInfo:  ), 'x_{1, 2} = \\frac{-b \\pm \\sqrt{b^2 -4ac}}{2a}']

IO - braille.BrailleBuffer.update (18:53:33.232) - MainThread (13524):

Braille regions text: ['*标题 - 记事本 ', '文本编辑器 单栏 编辑 ', 'x_{1, 2} = \\frac{-b \\pm \\sqrt{b^2 -4ac}}{2a} ']

IO - braille.BrailleHandler.update (18:53:33.233) - MainThread (13524):

Braille window dots: 456 16 56 234 12345 1235 2345 56 36 12 - 4 26 3456 12 - 36 3456 145 56 1 14 36 23 36 23 56 36 3456 12 56 1 36 23 -

IO - braille.BrailleHandler.update (18:53:33.235) - MainThread (13524):

Braille window dots: 456 16 56 234 12345 1235 2345 56 36 12 - 4 26 3456 12 - 36 3456 145 56 1 14 36 23 36 23 56 36 3456 12 56 1 36 23 -

IO - braille.BrailleBuffer.update (18:53:33.243) - MainThread (13524):

Braille regions text: ['*标题 - 记事本 ', '文本编辑器 单栏 编辑 ', 'x_{1, 2} = \\frac{-b \\pm \\sqrt{b^2 -4ac}}{2a} ']

IO - braille.BrailleHandler.update (18:53:33.243) - MainThread (13524):

Braille window dots: 456 16 56 234 12345 1235 2345 56 36 12 - 4 26 3456 12 - 36 3456 145 56 1 14 36 23 36 23 56 36 3456 12 56 1 36 23 -

IO - braille.BrailleHandler.update (18:53:33.245) - MainThread (13524):

Braille window dots: 456 16 56 234 12345 1235 2345 56 36 12 - 4 26 3456 12 - 36 3456 145 56 1 14 36 23 36 23 56 36 3456 12 56 1 36 23 -

IO - inputCore.InputManager.executeGesture (18:53:33.774) - winInputHook (1372):

Input: kb(laptop):control+a

INFO - external:globalPlugins.fixime.GuessComposition.GuessedCompositionStatus.add_gesture (18:53:33.774) - winInputHook (1372):

Name:

control+a

ID:

control+a

vkCode:

65

IO - speech.speak (18:53:33.793) - MainThread (13524):

Speaking [LangChangeCommand ('zh_CN'), 'x_{1, 2} = \\frac{-b \\pm \\sqrt{b^2 -4ac}}{2a},已选择']

IO - braille.BrailleBuffer.update (18:53:33.796) - MainThread (13524):

Braille regions text: ['*标题 - 记事本 ', '文本编辑器 单栏 编辑 ', 'x_{1, 2} = \\frac{-b \\pm \\sqrt{b^2 -4ac}}{2a} ']

IO - braille.BrailleHandler.update (18:53:33.797) - MainThread (13524):

Braille window dots: 134678 78 4678 3678 5678 3678 345678 178 278 78 345678 1278 3678 2378 78 578 235678 78 45678 1678 5678 12478 123578 178 1478 5678 3678 3678 1278 78 45678 1678 5678 123478 13478 78 45678 1678 5678 23478

IO - braille.BrailleHandler.update (18:53:33.799) - MainThread (13524):

Braille window dots: 134678 78 4678 3678 5678 3678 345678 178 278 78 345678 1278 3678 2378 78 578 235678 78 45678 1678 5678 12478 123578 178 1478 5678 3678 3678 1278 78 45678 1678 5678 123478 13478 78 45678 1678 5678 23478

IO - inputCore.InputManager.executeGesture (18:53:34.836) - winInputHook (1372):

Input: kb(laptop):shift+NVDA+i

INFO - external:globalPlugins.fixime.GuessComposition.GuessedCompositionStatus.add_gesture (18:53:34.836) - winInputHook (1372):

Name:

shift+NVDA+i

ID:

shift+NVDA+i

vkCode:

73

IO - speech.speak (18:53:34.854) - Thread-4 (1512):

Speaking [LangChangeCommand ('zh_CN'), 'Convert LaTeX']

IO - braille.BrailleBuffer.update (18:53:34.855) - Thread-4 (1512):

Braille regions text: ['Convert LaTeX']

IO - braille.BrailleHandler.update (18:53:34.855) - Thread-4 (1512):

Braille window dots: 6 14 135 1345 1236 15 1235 2345 - 6 123 1 6 2345 15 6 1346

ERROR - stderr (18:53:34.858) - Thread-4 (1512):

Exception in thread Thread-4:

Traceback (most recent call last):

  File "threading.pyc", line 926, in _bootstrap_inner

  File "threading.pyc", line 870, in run

  File "C:\Users\manch\AppData\Roaming\nvda\addons\nvMathViewer\globalPlugins\nvMathViewer\__init__.py", line 120, in showMathML

    ui.message(_("Convert {format}").format(format=format))

  File "ui.pyc", line 78, in message

  File "braille.pyc", line 1873, in message

  File "braille.pyc", line 1887, in _resetMessageTimer

  File "wx\core.pyc", line 3284, in __init__

  File "wx\core.pyc", line 3305, in Start

wx._core.wxAssertionError: C++ assertion "wxThread::IsMain()" failed at ..\..\src\common\timerimpl.cpp(60) in wxTimerImpl::Start(): timer can only be started from the main thread

IO - inputCore.InputManager.executeGesture (18:53:37.728) - winInputHook (1372):

Input: kb(laptop):NVDA+f1

INFO - external:globalPlugins.fixime.GuessComposition.GuessedCompositionStatus.add_gesture (18:53:37.728) - winInputHook (1372):

Name:

NVDA+f1

ID:

NVDA+f1

vkCode:

112

INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo (18:53:37.857) - MainThread (13524):

Developer info for navigator object:

name: '文本编辑器'

role: ROLE_EDITABLETEXT

roleText: None

states: STATE_MULTILINE, STATE_FOCUSABLE, STATE_FOCUSED

isFocusable: True

hasFocus: True

Python object: <NVDAObjects.Dynamic_IAccessibleEditWindowNVDAObject object at 0x0AA05A30>

Python class mro: (<class 'NVDAObjects.Dynamic_IAccessibleEditWindowNVDAObject'>, <class 'NVDAObjects.IAccessible.IAccessible'>, <class 'NVDAObjects.window.edit.Edit'>, <class 'NVDAObjects.behaviors.EditableTextWithAutoSelectDetection'>, <class 'NVDAObjects.behaviors.EditableText'>, <class 'editableText.EditableText'>, <class 'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class 'documentBase.TextContainerObject'>, <class 'baseObject.ScriptableObject'>, <class 'baseObject.AutoPropertyObject'>, <class 'garbageHandler.TrackedObject'>, <class 'object'>)

description: None

location: RectLTWH(left=109, top=152, width=927, height=393)

value: 'x_{1, 2} = \\frac{-b \\pm \\sqrt{b^2 -4ac}}{2a}'

appModule: <'appModuleHandler' (appName 'notepad', process ID 15168) at address 446e630>

appModule.productName: 'Microsoft® Windows® Operating System'

appModule.productVersion: '10.0.19041.507'

TextInfo: <class 'NVDAObjects.window.edit.EditTextInfo'>

windowHandle: 1312054

windowClassName: 'Edit'

windowControlID: 15

windowStyle: 1345323268

extendedWindowStyle: 0

windowThreadID: 6664

windowText: 'x_{1, 2} = \\frac{-b \\pm \\sqrt{b^2 -4ac}}{2a}'

displayText: 'x_{ ,  } = \\frac{-b \\pm \\sqrt{b^  - ac}}{ a}'

IAccessibleObject: <POINTER(IAccessible) ptr=0x68aa358 at aa76350>

IAccessibleChildID: 0

IAccessible event parameters: windowHandle=1312054, objectID=-4, childID=0

IAccessible accName: '文本编辑器'

IAccessible accRole: ROLE_SYSTEM_TEXT

IAccessible accState: STATE_SYSTEM_FOCUSED, STATE_SYSTEM_FOCUSABLE, STATE_SYSTEM_VALID (1048580)

IAccessible accDescription: None

IAccessible accValue: 'x_{1, 2} = \\frac{-b \\pm \\sqrt{b^2 -4ac}}{2a}'

 


Re: nvMathViewer add-on for viewing math content in LaTeX and AsciiMath notations as MathML

James Scholes
 

Hi Nikita, thanks for that explanation and for your work on this. Sounds superb.

Regards,

James Scholes

On 14/09/2020 at 11:07 am, Nikita wrote:
Hi James,
nvMathViewer solves other problems. It does not replace MathPlayer or
Access8Math, but complements them.
For example, there is a user who doesn't know LaTeX, but wants to read a
formula like this.
nvMathViewer will display LaTeX as MathML and then the user can view it
using MathPlayer.
The user needs to select a line
x_{1, 2} = \frac{-b \pm \sqrt{b^2 -4ac}}{2a}
and perform a special gesture.
After that, he can hear this line as
"x sub 1 comma 2 end sub equals the fraction with numerator negative b plus
or minus the square root of b squared minus 4 a c and denominator 2 a"
nvMathViewer is a solution for those who don't know LaTeX or AsciiMath, but
need to read formulas like this sometimes.
Best regards, Nikita.
-----Original Message-----
From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io>
On Behalf Of James Scholes
Sent: Monday, September 14, 2020 5:29 PM
To: nvda-addons@nvda-addons.groups.io
Subject: Re: [nvda-addons] nvMathViewer add-on for viewing math content in
LaTeX and AsciiMath notations as MathML
How does this differ from MathPlayer and the support already present in
NVDA?
Regards,
James Scholes
On 12/09/2020 at 1:33 pm, Nikita wrote:
Hello everybody!
nvMathViewer has been released. It is an a add-on that can be used to view mathematical content in LaTeX and AsciiMath notations as MathML.
These notations are widely used to write mathematical symbols and formulas in computer systems. However, understanding LaTeX and AsciiMath requires special knowledge and skills that the average user may not have, such as a simple schoolboy or a humanitarian student. In addition, reading these notations directly may not be convenient enough, because it does not provide additional opportunities for analyzing the structure of formulas.
nvMathViewer solves these problems and enables blind users to quickly view any LaTeX or AsciiMath notations using special functions of NVDA for non-visual reading mathematical content and structural navigation through it.
Links:
Add-on for NVDA 2019.3 and newer - https://tseykovets.ru/download/nvda/nvMathViewer.nvda-addon
Source code - https://github.com/tseykovets/nvmathviewer
Best regards, Nikita.


Re: nvMathViewer add-on for viewing math content in LaTeX and AsciiMath notations as MathML

rowen brian
 

Hi Nikita.
I did encounter an error. Here is my error log.

The formula for testing: x_{1, 2} = \frac{-b \pm \sqrt{b^2 -4ac}}{2a}

INFO - __main__ (18:53:30.182) - MainThread (13524):
Starting NVDA version 2020.3beta1
INFO - core.main (18:53:30.277) - MainThread (13524):
Config dir: C:\Users\manch\AppData\Roaming\nvda
INFO - config.ConfigManager._loadConfig (18:53:30.277) - MainThread (13524):
Loading config: C:\Users\manch\AppData\Roaming\nvda\nvda.ini
INFO - core.main (18:53:30.352) - MainThread (13524):
Using Windows version 10.0.19041 workstation
INFO - core.main (18:53:30.352) - MainThread (13524):
Using Python version 3.7.9 (tags/v3.7.9:13c94747c7, Aug 17 2020, 18:01:55) [MSC v.1900 32 bit (Intel)]
INFO - core.main (18:53:30.352) - MainThread (13524):
Using comtypes version 1.1.7
INFO - core.main (18:53:30.352) - MainThread (13524):
Using configobj version 5.1.0 with validate version 1.0.1
INFO - synthDriverHandler.setSynth (18:53:30.756) - MainThread (13524):
Loaded synthDriver vocalizer_expressive2
INFO - core.main (18:53:30.756) - MainThread (13524):
Using wx version 4.0.3 msw (phoenix) wxWidgets 3.0.5 with six version 1.12.0
INFO - brailleInput.initialize (18:53:30.757) - MainThread (13524):
Braille input initialized
INFO - braille.initialize (18:53:30.758) - MainThread (13524):
Using liblouis version 3.14.0
INFO - braille.initialize (18:53:30.761) - MainThread (13524):
Using pySerial version 3.4
INFO - braille.BrailleHandler.setDisplayByName (18:53:30.771) - MainThread (13524):
Loaded braille display driver brltty, current display has 40 cells.
INFO - core.main (18:53:30.975) - MainThread (13524):
Java Access Bridge support initialized
INFO - _UIAHandler.UIAHandler.MTAThreadFunc (18:53:30.985) - _UIAHandler.UIAHandler.MTAThread (10028):
UIAutomation: IUIAutomation6
DEBUGWARNING - inputCore.InputManager.loadLocaleGestureMap (18:53:31.087) - MainThread (13524):
No locale gesture map for language zh_CN
DEBUGWARNING - touchHandler.touchSupported (18:53:31.103) - MainThread (13524):
No touch devices found
INFO - external:globalPlugins.starClip.patch_speak_functions (18:53:31.901) - MainThread (13524):
Patched speak function
IO - external:globalPlugins.fixime.GuessComposition.get_code_by_name (18:53:31.941) - MainThread (13524):
controlconverted to 17
IO - external:globalPlugins.fixime.GuessComposition.get_code_by_name (18:53:31.942) - MainThread (13524):
numpadenterconverted to 13
IO - external:globalPlugins.fixime.GuessComposition.get_code_by_name (18:53:31.942) - MainThread (13524):
enterconverted to 13
INFO - external:globalPlugins.fixime.GlobalPlugin.refreshLayoutString (18:53:31.946) - MainThread (13524):
2052
INFO - external:globalPlugins.fixime.GlobalPlugin.refreshLayoutString (18:53:31.946) - MainThread (13524):
00000804
IO - inputCore.InputManager.executeGesture (18:53:31.949) - winInputHook (1372):
Input: kb(laptop):windows+shift+space
INFO - external:globalPlugins.fixime.GlobalPlugin.refreshLayoutString (18:53:31.951) - MainThread (13524):
2052
INFO - external:globalPlugins.fixime.GlobalPlugin.refreshLayoutString (18:53:31.951) - MainThread (13524):
00000804
IO - inputCore.InputManager.executeGesture (18:53:31.952) - winInputHook (1372):
Input: kb(laptop):windows+space
INFO - external:globalPlugins.fixime.GlobalPlugin.refreshLayoutString (18:53:31.953) - MainThread (13524):
2052
INFO - external:globalPlugins.fixime.GlobalPlugin.refreshLayoutString (18:53:31.953) - MainThread (13524):
00000804
IO - braille.BrailleBuffer.update (18:53:32.029) - MainThread (13524):
Braille regions text: ['NVDA 已启动']
IO - braille.BrailleHandler.update (18:53:32.029) - MainThread (13524):
Braille window dots: 6 6 1345 1236 145 1 - 24 3 13 24 3 145 256 23
INFO - core.main (18:53:32.032) - MainThread (13524):
NVDA initialized
IO - braille.BrailleBuffer.update (18:53:32.046) - MainThread (13524):
Braille regions text: ['桌面 窗口']
INFO - external:globalPlugins.fixime.GlobalPlugin.event_typedCharacter (18:53:32.058) - MainThread (13524):
<NVDAObjects.window.Desktop object at 0x06656F30>
WARNING - characterProcessing.SpeechSymbolProcessor.__init__ (18:53:32.119) - MainThread (13524):
Replacement not defined in locale zh_CN for symbol: ﹔
IO - speech.speak (18:53:32.159) - MainThread (13524):
Speaking [LangChangeCommand ('zh_CN'), '空格', EndUtteranceCommand()]
INFO - external:globalPlugins.fixime.GlobalPlugin.event_typedCharacter (18:53:32.160) - MainThread (13524):
<NVDAObjects.window.Desktop object at 0x06656F30>
IO - speech.speak (18:53:32.160) - MainThread (13524):
Speaking [LangChangeCommand ('zh_CN'), '空格', EndUtteranceCommand()]
DEBUGWARNING - Python warning (18:53:32.192) - MainThread (13524):
C:\Program Files (x86)\NVDA\library.zip\api.py:287: DeprecationWarning: Yield() is deprecated
IO - speech.speak (18:53:32.193) - MainThread (13524):
Speaking [LangChangeCommand ('zh_CN'), '任务栏', CancellableSpeech (still valid devInfo( isCanceledCache: False, isValidCallback: True, isValidCallbackDevInfo:  )]
IO - braille.BrailleBuffer.update (18:53:32.193) - MainThread (13524):
Braille regions text: ['任务栏']
IO - inputCore.InputManager.executeGesture (18:53:32.938) - winInputHook (1372):
Input: kb(laptop):alt+tab
INFO - external:globalPlugins.fixime.GlobalPlugin.event_typedCharacter (18:53:32.948) - MainThread (13524):
<NVDAObjects.IAccessible.Taskbar object at 0x0AA05530>
IO - speech.speak (18:53:33.041) - MainThread (13524):
Speaking [LangChangeCommand ('zh_CN'), '*无标题 - 记事本', CancellableSpeech (still valid devInfo( isCanceledCache: False, isValidCallback: True, isValidCallbackDevInfo:  )]
IO - braille.BrailleBuffer.update (18:53:33.042) - MainThread (13524):
Braille regions text: ['*无标题 - 记事本']
IO - braille.BrailleHandler.update (18:53:33.042) - MainThread (13524):
Braille window dots: 35 35 136 2 12 345 1 2345 24 2 - 36 - 1245 24 23 156 23 12 356 3
IO - speech.speak (18:53:33.179) - MainThread (13524):
Speaking [LangChangeCommand ('zh_CN'), '*无标题 - 记事本', CancellableSpeech (still valid devInfo( isCanceledCache: False, isValidCallback: True, isValidCallbackDevInfo:  )]
IO - braille.BrailleBuffer.update (18:53:33.180) - MainThread (13524):
Braille regions text: ['*无标题 - 记事本']
IO - braille.BrailleHandler.update (18:53:33.180) - MainThread (13524):
Braille window dots: 35 35 136 2 12 345 1 2345 24 2 - 36 - 1245 24 23 156 23 12 356 3
INFO - external:globalPlugins.fixime.GlobalPlugin.add_capture_function (18:53:33.225) - MainThread (13524):
Added capture function
IO - speech.speak (18:53:33.228) - MainThread (13524):
Speaking [LangChangeCommand ('zh_CN'), '文本编辑器', '编辑框', '多行', CancellableSpeech (still valid devInfo( isCanceledCache: False, isValidCallback: True, isValidCallbackDevInfo:  ), 'x_{1, 2} = \\frac{-b \\pm \\sqrt{b^2 -4ac}}{2a}']
IO - braille.BrailleBuffer.update (18:53:33.232) - MainThread (13524):
Braille regions text: ['*无标题 - 记事本 ', '文本编辑器 菜单栏 可编辑 ', 'x_{1, 2} = \\frac{-b \\pm \\sqrt{b^2 -4ac}}{2a} ']
IO - braille.BrailleHandler.update (18:53:33.233) - MainThread (13524):
Braille window dots: 456 16 56 234 12345 1235 2345 56 36 12 - 4 26 3456 12 - 36 3456 145 56 1 14 36 23 36 23 56 36 3456 12 56 1 36 23 -
IO - braille.BrailleHandler.update (18:53:33.235) - MainThread (13524):
Braille window dots: 456 16 56 234 12345 1235 2345 56 36 12 - 4 26 3456 12 - 36 3456 145 56 1 14 36 23 36 23 56 36 3456 12 56 1 36 23 -
IO - braille.BrailleBuffer.update (18:53:33.243) - MainThread (13524):
Braille regions text: ['*无标题 - 记事本 ', '文本编辑器 菜单栏 可编辑 ', 'x_{1, 2} = \\frac{-b \\pm \\sqrt{b^2 -4ac}}{2a} ']
IO - braille.BrailleHandler.update (18:53:33.243) - MainThread (13524):
Braille window dots: 456 16 56 234 12345 1235 2345 56 36 12 - 4 26 3456 12 - 36 3456 145 56 1 14 36 23 36 23 56 36 3456 12 56 1 36 23 -
IO - braille.BrailleHandler.update (18:53:33.245) - MainThread (13524):
Braille window dots: 456 16 56 234 12345 1235 2345 56 36 12 - 4 26 3456 12 - 36 3456 145 56 1 14 36 23 36 23 56 36 3456 12 56 1 36 23 -
IO - inputCore.InputManager.executeGesture (18:53:33.774) - winInputHook (1372):
Input: kb(laptop):control+a
INFO - external:globalPlugins.fixime.GuessComposition.GuessedCompositionStatus.add_gesture (18:53:33.774) - winInputHook (1372):
Name:
control+a
ID:
control+a
vkCode:
65
IO - speech.speak (18:53:33.793) - MainThread (13524):
Speaking [LangChangeCommand ('zh_CN'), 'x_{1, 2} = \\frac{-b \\pm \\sqrt{b^2 -4ac}}{2a},已选择']
IO - braille.BrailleBuffer.update (18:53:33.796) - MainThread (13524):
Braille regions text: ['*无标题 - 记事本 ', '文本编辑器 菜单栏 可编辑 ', 'x_{1, 2} = \\frac{-b \\pm \\sqrt{b^2 -4ac}}{2a} ']
IO - braille.BrailleHandler.update (18:53:33.797) - MainThread (13524):
Braille window dots: 134678 78 4678 3678 5678 3678 345678 178 278 78 345678 1278 3678 2378 78 578 235678 78 45678 1678 5678 12478 123578 178 1478 5678 3678 3678 1278 78 45678 1678 5678 123478 13478 78 45678 1678 5678 23478
IO - braille.BrailleHandler.update (18:53:33.799) - MainThread (13524):
Braille window dots: 134678 78 4678 3678 5678 3678 345678 178 278 78 345678 1278 3678 2378 78 578 235678 78 45678 1678 5678 12478 123578 178 1478 5678 3678 3678 1278 78 45678 1678 5678 123478 13478 78 45678 1678 5678 23478
IO - inputCore.InputManager.executeGesture (18:53:34.836) - winInputHook (1372):
Input: kb(laptop):shift+NVDA+i
INFO - external:globalPlugins.fixime.GuessComposition.GuessedCompositionStatus.add_gesture (18:53:34.836) - winInputHook (1372):
Name:
shift+NVDA+i
ID:
shift+NVDA+i
vkCode:
73
IO - speech.speak (18:53:34.854) - Thread-4 (1512):
Speaking [LangChangeCommand ('zh_CN'), 'Convert LaTeX']
IO - braille.BrailleBuffer.update (18:53:34.855) - Thread-4 (1512):
Braille regions text: ['Convert LaTeX']
IO - braille.BrailleHandler.update (18:53:34.855) - Thread-4 (1512):
Braille window dots: 6 14 135 1345 1236 15 1235 2345 - 6 123 1 6 2345 15 6 1346
ERROR - stderr (18:53:34.858) - Thread-4 (1512):
Exception in thread Thread-4:
Traceback (most recent call last):
  File "threading.pyc", line 926, in _bootstrap_inner
  File "threading.pyc", line 870, in run
  File "C:\Users\manch\AppData\Roaming\nvda\addons\nvMathViewer\globalPlugins\nvMathViewer\__init__.py", line 120, in showMathML
    ui.message(_("Convert {format}").format(format=format))
  File "ui.pyc", line 78, in message
  File "braille.pyc", line 1873, in message
  File "braille.pyc", line 1887, in _resetMessageTimer
  File "wx\core.pyc", line 3284, in __init__
  File "wx\core.pyc", line 3305, in Start
wx._core.wxAssertionError: C++ assertion "wxThread::IsMain()" failed at ..\..\src\common\timerimpl.cpp(60) in wxTimerImpl::Start(): timer can only be started from the main thread
IO - inputCore.InputManager.executeGesture (18:53:37.728) - winInputHook (1372):
Input: kb(laptop):NVDA+f1
INFO - external:globalPlugins.fixime.GuessComposition.GuessedCompositionStatus.add_gesture (18:53:37.728) - winInputHook (1372):
Name:
NVDA+f1
ID:
NVDA+f1
vkCode:
112
INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo (18:53:37.857) - MainThread (13524):
Developer info for navigator object:
name: '文本编辑器'
role: ROLE_EDITABLETEXT
roleText: None
states: STATE_MULTILINE, STATE_FOCUSABLE, STATE_FOCUSED
isFocusable: True
hasFocus: True
Python object: <NVDAObjects.Dynamic_IAccessibleEditWindowNVDAObject object at 0x0AA05A30>
Python class mro: (<class 'NVDAObjects.Dynamic_IAccessibleEditWindowNVDAObject'>, <class 'NVDAObjects.IAccessible.IAccessible'>, <class 'NVDAObjects.window.edit.Edit'>, <class 'NVDAObjects.behaviors.EditableTextWithAutoSelectDetection'>, <class 'NVDAObjects.behaviors.EditableText'>, <class 'editableText.EditableText'>, <class 'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class 'documentBase.TextContainerObject'>, <class 'baseObject.ScriptableObject'>, <class 'baseObject.AutoPropertyObject'>, <class 'garbageHandler.TrackedObject'>, <class 'object'>)
description: None
location: RectLTWH(left=109, top=152, width=927, height=393)
value: 'x_{1, 2} = \\frac{-b \\pm \\sqrt{b^2 -4ac}}{2a}'
appModule: <'appModuleHandler' (appName 'notepad', process ID 15168) at address 446e630>
appModule.productName: 'Microsoft® Windows® Operating System'
appModule.productVersion: '10.0.19041.507'
TextInfo: <class 'NVDAObjects.window.edit.EditTextInfo'>
windowHandle: 1312054
windowClassName: 'Edit'
windowControlID: 15
windowStyle: 1345323268
extendedWindowStyle: 0
windowThreadID: 6664
windowText: 'x_{1, 2} = \\frac{-b \\pm \\sqrt{b^2 -4ac}}{2a}'
displayText: 'x_{ ,  } = \\frac{-b \\pm \\sqrt{b^  - ac}}{ a}'
IAccessibleObject: <POINTER(IAccessible) ptr=0x68aa358 at aa76350>
IAccessibleChildID: 0
IAccessible event parameters: windowHandle=1312054, objectID=-4, childID=0
IAccessible accName: '文本编辑器'
IAccessible accRole: ROLE_SYSTEM_TEXT
IAccessible accState: STATE_SYSTEM_FOCUSED, STATE_SYSTEM_FOCUSABLE, STATE_SYSTEM_VALID (1048580)
IAccessible accDescription: None
IAccessible accValue: 'x_{1, 2} = \\frac{-b \\pm \\sqrt{b^2 -4ac}}{2a}'
 


Re: numpadNavMode Add-on: all new beta release 0.5-dev for testing & review

Locutor Antonio Cezar
 

I forgot to say that when I get an error due to .2.0 and .3.0, for instance, in Alpha versions, dialogue to restart NVDA is not shown and the Add-On is not installs as it should be. So the solution I find is to open the Add-Ons manager NVDA and click the Close button. So, after clicking the close button, it shows the dialog to restart NVDA after installing an add-on, and the installation is finally finished... Thank you.



Locutor Antonio Cezar

Em 15/09/2020 18:24, Antonio Cezar - Locutor escreveu:

In my experience of use when writing .2.0, .3.0, for example, or something similar to it, is a strong possibility of error during installation, especially for users of Alpha versions, so much so that whenever I I will install an Add-on with installation error, the error ceases to exist when I delete the final zero... Thanks.



Locutor Antonio Cezar

Em 15/09/2020 17:18, CARLOS-ESTEBAN escreveu:

So, a question about the compatibility in the manifest, because I am not sure: Is necessary or recommendable write 2020.1.0, for example or 2020.3.0 (with “.0 to end”? In this manifest, Luke write 2020.1 and 2020.3 (no have “.0”).

Regards.

 

 

Carlos Esteban Martínez Macías.

Músico (pianista) y también ayuda a usuarios ciegos y con discapacidad visual con el uso de lectores de pantalla y tecnología.

Experto certificado en el lector de pantalla NVDA.

 

Musician (pianist) and help to the blind people, with use of screen readers and technology. Certified expert in the screen reader NVDA.

 

NVDA certified expert certificate

 

De: CARLOS-ESTEBAN via groups.io
Enviado: martes, 15 de septiembre de 2020 15:10
Para: nvda-addons@nvda-addons.groups.io
Asunto: Re: [nvda-addons] numpadNavMode Add-on: all new beta release 0.5-dev for testing & review

 

Hi all.

For me, user experience and manifest, pass. I not check the source code because I am not yet a developer.

Tested with NVDA 2020.3beta1 and a Numpad keyboard by USB).

The feature of disable the insert from Numpad of modifier key of NVDA no is very necessary, is possible disable it in the category keyboard from the NVDA options and press the insert key two times.

The idea of enable this add-on to start NVDA or when the user change to the laptop layout is very good for a future version.

 

Regards.

 

Carlos Esteban Martínez Macías.

Músico (pianista) y también ayuda a usuarios ciegos y con discapacidad visual con el uso de lectores de pantalla y tecnología.

Experto certificado en el lector de pantalla NVDA.

 

Musician (pianist) and help to the blind people, with use of screen readers and technology. Certified expert in the screen reader NVDA.

 

NVDA certified expert certificate

 

De: Joseph Lee
Enviado: martes, 15 de septiembre de 2020 11:03
Para: nvda-addons@nvda-addons.groups.io
Asunto: Re: [nvda-addons] numpadNavMode Add-on: all new beta release 0.5-dev for testing & review

 

Hi,

I would like to request someone who has never reviewed an add-on and wanted

to learn how to do so to review this add-on. Thanks.

Cheers,

Joseph

 

-----Original Message-----

From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io>

On Behalf Of Luke Davis

Sent: Tuesday, September 15, 2020 4:35 AM

To: nvda-addons@groups.io

Subject: [nvda-addons] numpadNavMode Add-on: all new beta release 0.5-dev

for testing & review

 

Hello all!

 

I'm happy to announce an all-new beta of the numpadNavMode add-on, of which

I released an alpha a couple weeks ago.

 

It has been almost completely rewritten, both to address some of the

comments received, and because I just didn't like how it worked before.  I

think it is much better in this form, and I request anyone who tried it

before, to try it again.

 

For those who didn't test it yet, please consider testing it now: it really

is new and improved, if I do say so.

 

New in this version:

 

* Warning dialog on installation has been removed, no longer applies.

* The add-on should now avoid allowing any Windows nav, or any of its other

numpad gestures, to be saved to a user's gestures.ini file.

* If a user maps one of the numpad gestures while in NVDA mode, it will

remember that mapping when it switches back to NVDA mode from Windows mode.

 

A reminder of what it does:

Allows you to switch your numpad into Windows navigation mode, so you can

use its arrow keys, home/end, and page up and down.

 

  Download:

https://github.com/opensourcesys/numpadNavMode/releases/download/0.5-dev/num

padNavMode-0.5-dev.nvda-addon

 

Readme:

https://github.com/opensourcesys/numpadNavMode/blob/master/readme.md

 

Known issues:

 

At the moment, I am not sure about its translatability.  The add-on itself

could be translated, but I have not yet looked into what I would have to do

for locale gesture configurations.  It may work well, it may not, for non-US

keyboard users.

I intend to dig into that more in an upcoming version. If anyone wants to

provide suggestions about that, please get in touch.

 

Luke

 

 

 

 

 

 

 

 


Re: numpadNavMode Add-on: all new beta release 0.5-dev for testing & review

Locutor Antonio Cezar
 

In my experience of use when writing .2.0, .3.0, for example, or something similar to it, is a strong possibility of error during installation, especially for users of Alpha versions, so much so that whenever I I will install an Add-on with installation error, the error ceases to exist when I delete the final zero... Thanks.



Locutor Antonio Cezar

Em 15/09/2020 17:18, CARLOS-ESTEBAN escreveu:

So, a question about the compatibility in the manifest, because I am not sure: Is necessary or recommendable write 2020.1.0, for example or 2020.3.0 (with “.0 to end”? In this manifest, Luke write 2020.1 and 2020.3 (no have “.0”).

Regards.

 

 

Carlos Esteban Martínez Macías.

Músico (pianista) y también ayuda a usuarios ciegos y con discapacidad visual con el uso de lectores de pantalla y tecnología.

Experto certificado en el lector de pantalla NVDA.

 

Musician (pianist) and help to the blind people, with use of screen readers and technology. Certified expert in the screen reader NVDA.

 

NVDA certified expert certificate

 

De: CARLOS-ESTEBAN via groups.io
Enviado: martes, 15 de septiembre de 2020 15:10
Para: nvda-addons@nvda-addons.groups.io
Asunto: Re: [nvda-addons] numpadNavMode Add-on: all new beta release 0.5-dev for testing & review

 

Hi all.

For me, user experience and manifest, pass. I not check the source code because I am not yet a developer.

Tested with NVDA 2020.3beta1 and a Numpad keyboard by USB).

The feature of disable the insert from Numpad of modifier key of NVDA no is very necessary, is possible disable it in the category keyboard from the NVDA options and press the insert key two times.

The idea of enable this add-on to start NVDA or when the user change to the laptop layout is very good for a future version.

 

Regards.

 

Carlos Esteban Martínez Macías.

Músico (pianista) y también ayuda a usuarios ciegos y con discapacidad visual con el uso de lectores de pantalla y tecnología.

Experto certificado en el lector de pantalla NVDA.

 

Musician (pianist) and help to the blind people, with use of screen readers and technology. Certified expert in the screen reader NVDA.

 

NVDA certified expert certificate

 

De: Joseph Lee
Enviado: martes, 15 de septiembre de 2020 11:03
Para: nvda-addons@nvda-addons.groups.io
Asunto: Re: [nvda-addons] numpadNavMode Add-on: all new beta release 0.5-dev for testing & review

 

Hi,

I would like to request someone who has never reviewed an add-on and wanted

to learn how to do so to review this add-on. Thanks.

Cheers,

Joseph

 

-----Original Message-----

From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io>

On Behalf Of Luke Davis

Sent: Tuesday, September 15, 2020 4:35 AM

To: nvda-addons@groups.io

Subject: [nvda-addons] numpadNavMode Add-on: all new beta release 0.5-dev

for testing & review

 

Hello all!

 

I'm happy to announce an all-new beta of the numpadNavMode add-on, of which

I released an alpha a couple weeks ago.

 

It has been almost completely rewritten, both to address some of the

comments received, and because I just didn't like how it worked before.  I

think it is much better in this form, and I request anyone who tried it

before, to try it again.

 

For those who didn't test it yet, please consider testing it now: it really

is new and improved, if I do say so.

 

New in this version:

 

* Warning dialog on installation has been removed, no longer applies.

* The add-on should now avoid allowing any Windows nav, or any of its other

numpad gestures, to be saved to a user's gestures.ini file.

* If a user maps one of the numpad gestures while in NVDA mode, it will

remember that mapping when it switches back to NVDA mode from Windows mode.

 

A reminder of what it does:

Allows you to switch your numpad into Windows navigation mode, so you can

use its arrow keys, home/end, and page up and down.

 

  Download:

https://github.com/opensourcesys/numpadNavMode/releases/download/0.5-dev/num

padNavMode-0.5-dev.nvda-addon

 

Readme:

https://github.com/opensourcesys/numpadNavMode/blob/master/readme.md

 

Known issues:

 

At the moment, I am not sure about its translatability.  The add-on itself

could be translated, but I have not yet looked into what I would have to do

for locale gesture configurations.  It may work well, it may not, for non-US

keyboard users.

I intend to dig into that more in an upcoming version. If anyone wants to

provide suggestions about that, please get in touch.

 

Luke

 

 

 

 

 

 

 

 


Re: numpadNavMode Add-on: all new beta release 0.5-dev for testing & review

CARLOS-ESTEBAN
 

OK, Thanks.

 

 

Carlos Esteban Martínez Macías.

Músico (pianista) y también ayuda a usuarios ciegos y con discapacidad visual con el uso de lectores de pantalla y tecnología.

Experto certificado en el lector de pantalla NVDA.

 

Musician (pianist) and help to the blind people, with use of screen readers and technology. Certified expert in the screen reader NVDA.

 

NVDA certified expert certificate

 

De: Joseph Lee
Enviado: martes, 15 de septiembre de 2020 15:21
Para: nvda-addons@nvda-addons.groups.io
Asunto: Re: [nvda-addons] numpadNavMode Add-on: all new beta release 0.5-dev for testing & review

 

Hi,

It doesn’t matter.

Cheers,

Joseph

 

From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of CARLOS-ESTEBAN
Sent: Tuesday, September 15, 2020 1:18 PM
To: nvda-addons@nvda-addons.groups.io
Subject: Re: [nvda-addons] numpadNavMode Add-on: all new beta release 0.5-dev for testing & review

 

So, a question about the compatibility in the manifest, because I am not sure: Is necessary or recommendable write 2020.1.0, for example or 2020.3.0 (with “.0 to end”? In this manifest, Luke write 2020.1 and 2020.3 (no have “.0”).

Regards.

 

 

Carlos Esteban Martínez Macías.

Músico (pianista) y también ayuda a usuarios ciegos y con discapacidad visual con el uso de lectores de pantalla y tecnología.

Experto certificado en el lector de pantalla NVDA.

 

Musician (pianist) and help to the blind people, with use of screen readers and technology. Certified expert in the screen reader NVDA.

 

NVDA certified expert certificate

 

De: CARLOS-ESTEBAN via groups.io
Enviado: martes, 15 de septiembre de 2020 15:10
Para: nvda-addons@nvda-addons.groups.io
Asunto: Re: [nvda-addons] numpadNavMode Add-on: all new beta release 0.5-dev for testing & review

 

Hi all.

For me, user experience and manifest, pass. I not check the source code because I am not yet a developer.

Tested with NVDA 2020.3beta1 and a Numpad keyboard by USB).

The feature of disable the insert from Numpad of modifier key of NVDA no is very necessary, is possible disable it in the category keyboard from the NVDA options and press the insert key two times.

The idea of enable this add-on to start NVDA or when the user change to the laptop layout is very good for a future version.

 

Regards.

 

Carlos Esteban Martínez Macías.

Músico (pianista) y también ayuda a usuarios ciegos y con discapacidad visual con el uso de lectores de pantalla y tecnología.

Experto certificado en el lector de pantalla NVDA.

 

Musician (pianist) and help to the blind people, with use of screen readers and technology. Certified expert in the screen reader NVDA.

 

NVDA certified expert certificate

 

De: Joseph Lee
Enviado: martes, 15 de septiembre de 2020 11:03
Para: nvda-addons@nvda-addons.groups.io
Asunto: Re: [nvda-addons] numpadNavMode Add-on: all new beta release 0.5-dev for testing & review

 

Hi,

I would like to request someone who has never reviewed an add-on and wanted

to learn how to do so to review this add-on. Thanks.

Cheers,

Joseph

 

-----Original Message-----

From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io>

On Behalf Of Luke Davis

Sent: Tuesday, September 15, 2020 4:35 AM

To: nvda-addons@groups.io

Subject: [nvda-addons] numpadNavMode Add-on: all new beta release 0.5-dev

for testing & review

 

Hello all!

 

I'm happy to announce an all-new beta of the numpadNavMode add-on, of which

I released an alpha a couple weeks ago.

 

It has been almost completely rewritten, both to address some of the

comments received, and because I just didn't like how it worked before.  I

think it is much better in this form, and I request anyone who tried it

before, to try it again.

 

For those who didn't test it yet, please consider testing it now: it really

is new and improved, if I do say so.

 

New in this version:

 

* Warning dialog on installation has been removed, no longer applies.

* The add-on should now avoid allowing any Windows nav, or any of its other

numpad gestures, to be saved to a user's gestures.ini file.

* If a user maps one of the numpad gestures while in NVDA mode, it will

remember that mapping when it switches back to NVDA mode from Windows mode.

 

A reminder of what it does:

Allows you to switch your numpad into Windows navigation mode, so you can

use its arrow keys, home/end, and page up and down.

 

  Download:

https://github.com/opensourcesys/numpadNavMode/releases/download/0.5-dev/num

padNavMode-0.5-dev.nvda-addon

 

Readme:

https://github.com/opensourcesys/numpadNavMode/blob/master/readme.md

 

Known issues:

 

At the moment, I am not sure about its translatability.  The add-on itself

could be translated, but I have not yet looked into what I would have to do

for locale gesture configurations.  It may work well, it may not, for non-US

keyboard users.

I intend to dig into that more in an upcoming version. If anyone wants to

provide suggestions about that, please get in touch.

 

Luke

 

 

 

 

 

 

 

 

 


Re: numpadNavMode Add-on: all new beta release 0.5-dev for testing & review

 

Hi,

It doesn’t matter.

Cheers,

Joseph

 

From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of CARLOS-ESTEBAN
Sent: Tuesday, September 15, 2020 1:18 PM
To: nvda-addons@nvda-addons.groups.io
Subject: Re: [nvda-addons] numpadNavMode Add-on: all new beta release 0.5-dev for testing & review

 

So, a question about the compatibility in the manifest, because I am not sure: Is necessary or recommendable write 2020.1.0, for example or 2020.3.0 (with “.0 to end”? In this manifest, Luke write 2020.1 and 2020.3 (no have “.0”).

Regards.

 

 

Carlos Esteban Martínez Macías.

Músico (pianista) y también ayuda a usuarios ciegos y con discapacidad visual con el uso de lectores de pantalla y tecnología.

Experto certificado en el lector de pantalla NVDA.

 

Musician (pianist) and help to the blind people, with use of screen readers and technology. Certified expert in the screen reader NVDA.

 

NVDA certified expert certificate

 

De: CARLOS-ESTEBAN via groups.io
Enviado: martes, 15 de septiembre de 2020 15:10
Para: nvda-addons@nvda-addons.groups.io
Asunto: Re: [nvda-addons] numpadNavMode Add-on: all new beta release 0.5-dev for testing & review

 

Hi all.

For me, user experience and manifest, pass. I not check the source code because I am not yet a developer.

Tested with NVDA 2020.3beta1 and a Numpad keyboard by USB).

The feature of disable the insert from Numpad of modifier key of NVDA no is very necessary, is possible disable it in the category keyboard from the NVDA options and press the insert key two times.

The idea of enable this add-on to start NVDA or when the user change to the laptop layout is very good for a future version.

 

Regards.

 

Carlos Esteban Martínez Macías.

Músico (pianista) y también ayuda a usuarios ciegos y con discapacidad visual con el uso de lectores de pantalla y tecnología.

Experto certificado en el lector de pantalla NVDA.

 

Musician (pianist) and help to the blind people, with use of screen readers and technology. Certified expert in the screen reader NVDA.

 

NVDA certified expert certificate

 

De: Joseph Lee
Enviado: martes, 15 de septiembre de 2020 11:03
Para: nvda-addons@nvda-addons.groups.io
Asunto: Re: [nvda-addons] numpadNavMode Add-on: all new beta release 0.5-dev for testing & review

 

Hi,

I would like to request someone who has never reviewed an add-on and wanted

to learn how to do so to review this add-on. Thanks.

Cheers,

Joseph

 

-----Original Message-----

From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io>

On Behalf Of Luke Davis

Sent: Tuesday, September 15, 2020 4:35 AM

To: nvda-addons@groups.io

Subject: [nvda-addons] numpadNavMode Add-on: all new beta release 0.5-dev

for testing & review

 

Hello all!

 

I'm happy to announce an all-new beta of the numpadNavMode add-on, of which

I released an alpha a couple weeks ago.

 

It has been almost completely rewritten, both to address some of the

comments received, and because I just didn't like how it worked before.  I

think it is much better in this form, and I request anyone who tried it

before, to try it again.

 

For those who didn't test it yet, please consider testing it now: it really

is new and improved, if I do say so.

 

New in this version:

 

* Warning dialog on installation has been removed, no longer applies.

* The add-on should now avoid allowing any Windows nav, or any of its other

numpad gestures, to be saved to a user's gestures.ini file.

* If a user maps one of the numpad gestures while in NVDA mode, it will

remember that mapping when it switches back to NVDA mode from Windows mode.

 

A reminder of what it does:

Allows you to switch your numpad into Windows navigation mode, so you can

use its arrow keys, home/end, and page up and down.

 

  Download:

https://github.com/opensourcesys/numpadNavMode/releases/download/0.5-dev/num

padNavMode-0.5-dev.nvda-addon

 

Readme:

https://github.com/opensourcesys/numpadNavMode/blob/master/readme.md

 

Known issues:

 

At the moment, I am not sure about its translatability.  The add-on itself

could be translated, but I have not yet looked into what I would have to do

for locale gesture configurations.  It may work well, it may not, for non-US

keyboard users.

I intend to dig into that more in an upcoming version. If anyone wants to

provide suggestions about that, please get in touch.

 

Luke

 

 

 

 

 

 

 

 


Re: numpadNavMode Add-on: all new beta release 0.5-dev for testing & review

CARLOS-ESTEBAN
 

So, a question about the compatibility in the manifest, because I am not sure: Is necessary or recommendable write 2020.1.0, for example or 2020.3.0 (with “.0 to end”? In this manifest, Luke write 2020.1 and 2020.3 (no have “.0”).

Regards.

 

 

Carlos Esteban Martínez Macías.

Músico (pianista) y también ayuda a usuarios ciegos y con discapacidad visual con el uso de lectores de pantalla y tecnología.

Experto certificado en el lector de pantalla NVDA.

 

Musician (pianist) and help to the blind people, with use of screen readers and technology. Certified expert in the screen reader NVDA.

 

NVDA certified expert certificate

 

De: CARLOS-ESTEBAN via groups.io
Enviado: martes, 15 de septiembre de 2020 15:10
Para: nvda-addons@nvda-addons.groups.io
Asunto: Re: [nvda-addons] numpadNavMode Add-on: all new beta release 0.5-dev for testing & review

 

Hi all.

For me, user experience and manifest, pass. I not check the source code because I am not yet a developer.

Tested with NVDA 2020.3beta1 and a Numpad keyboard by USB).

The feature of disable the insert from Numpad of modifier key of NVDA no is very necessary, is possible disable it in the category keyboard from the NVDA options and press the insert key two times.

The idea of enable this add-on to start NVDA or when the user change to the laptop layout is very good for a future version.

 

Regards.

 

Carlos Esteban Martínez Macías.

Músico (pianista) y también ayuda a usuarios ciegos y con discapacidad visual con el uso de lectores de pantalla y tecnología.

Experto certificado en el lector de pantalla NVDA.

 

Musician (pianist) and help to the blind people, with use of screen readers and technology. Certified expert in the screen reader NVDA.

 

NVDA certified expert certificate

 

De: Joseph Lee
Enviado: martes, 15 de septiembre de 2020 11:03
Para: nvda-addons@nvda-addons.groups.io
Asunto: Re: [nvda-addons] numpadNavMode Add-on: all new beta release 0.5-dev for testing & review

 

Hi,

I would like to request someone who has never reviewed an add-on and wanted

to learn how to do so to review this add-on. Thanks.

Cheers,

Joseph

 

-----Original Message-----

From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io>

On Behalf Of Luke Davis

Sent: Tuesday, September 15, 2020 4:35 AM

To: nvda-addons@groups.io

Subject: [nvda-addons] numpadNavMode Add-on: all new beta release 0.5-dev

for testing & review

 

Hello all!

 

I'm happy to announce an all-new beta of the numpadNavMode add-on, of which

I released an alpha a couple weeks ago.

 

It has been almost completely rewritten, both to address some of the

comments received, and because I just didn't like how it worked before.  I

think it is much better in this form, and I request anyone who tried it

before, to try it again.

 

For those who didn't test it yet, please consider testing it now: it really

is new and improved, if I do say so.

 

New in this version:

 

* Warning dialog on installation has been removed, no longer applies.

* The add-on should now avoid allowing any Windows nav, or any of its other

numpad gestures, to be saved to a user's gestures.ini file.

* If a user maps one of the numpad gestures while in NVDA mode, it will

remember that mapping when it switches back to NVDA mode from Windows mode.

 

A reminder of what it does:

Allows you to switch your numpad into Windows navigation mode, so you can

use its arrow keys, home/end, and page up and down.

 

  Download:

https://github.com/opensourcesys/numpadNavMode/releases/download/0.5-dev/num

padNavMode-0.5-dev.nvda-addon

 

Readme:

https://github.com/opensourcesys/numpadNavMode/blob/master/readme.md

 

Known issues:

 

At the moment, I am not sure about its translatability.  The add-on itself

could be translated, but I have not yet looked into what I would have to do

for locale gesture configurations.  It may work well, it may not, for non-US

keyboard users.

I intend to dig into that more in an upcoming version. If anyone wants to

provide suggestions about that, please get in touch.

 

Luke

 

 

 

 

 

 

 

 


Re: numpadNavMode Add-on: all new beta release 0.5-dev for testing & review

CARLOS-ESTEBAN
 

Hi all.

For me, user experience and manifest, pass. I not check the source code because I am not yet a developer.

Tested with NVDA 2020.3beta1 and a Numpad keyboard by USB).

The feature of disable the insert from Numpad of modifier key of NVDA no is very necessary, is possible disable it in the category keyboard from the NVDA options and press the insert key two times.

The idea of enable this add-on to start NVDA or when the user change to the laptop layout is very good for a future version.

 

Regards.

 

Carlos Esteban Martínez Macías.

Músico (pianista) y también ayuda a usuarios ciegos y con discapacidad visual con el uso de lectores de pantalla y tecnología.

Experto certificado en el lector de pantalla NVDA.

 

Musician (pianist) and help to the blind people, with use of screen readers and technology. Certified expert in the screen reader NVDA.

 

NVDA certified expert certificate

 

De: Joseph Lee
Enviado: martes, 15 de septiembre de 2020 11:03
Para: nvda-addons@nvda-addons.groups.io
Asunto: Re: [nvda-addons] numpadNavMode Add-on: all new beta release 0.5-dev for testing & review

 

Hi,

I would like to request someone who has never reviewed an add-on and wanted

to learn how to do so to review this add-on. Thanks.

Cheers,

Joseph

 

-----Original Message-----

From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io>

On Behalf Of Luke Davis

Sent: Tuesday, September 15, 2020 4:35 AM

To: nvda-addons@groups.io

Subject: [nvda-addons] numpadNavMode Add-on: all new beta release 0.5-dev

for testing & review

 

Hello all!

 

I'm happy to announce an all-new beta of the numpadNavMode add-on, of which

I released an alpha a couple weeks ago.

 

It has been almost completely rewritten, both to address some of the

comments received, and because I just didn't like how it worked before.  I

think it is much better in this form, and I request anyone who tried it

before, to try it again.

 

For those who didn't test it yet, please consider testing it now: it really

is new and improved, if I do say so.

 

New in this version:

 

* Warning dialog on installation has been removed, no longer applies.

* The add-on should now avoid allowing any Windows nav, or any of its other

numpad gestures, to be saved to a user's gestures.ini file.

* If a user maps one of the numpad gestures while in NVDA mode, it will

remember that mapping when it switches back to NVDA mode from Windows mode.

 

A reminder of what it does:

Allows you to switch your numpad into Windows navigation mode, so you can

use its arrow keys, home/end, and page up and down.

 

  Download:

https://github.com/opensourcesys/numpadNavMode/releases/download/0.5-dev/num

padNavMode-0.5-dev.nvda-addon

 

Readme:

https://github.com/opensourcesys/numpadNavMode/blob/master/readme.md

 

Known issues:

 

At the moment, I am not sure about its translatability.  The add-on itself

could be translated, but I have not yet looked into what I would have to do

for locale gesture configurations.  It may work well, it may not, for non-US

keyboard users.

I intend to dig into that more in an upcoming version. If anyone wants to

provide suggestions about that, please get in touch.

 

Luke

 

 

 

 

 

 

 


Re: numpadNavMode Add-on: all new beta release 0.5-dev for testing & review

 

Hi,
I would like to request someone who has never reviewed an add-on and wanted
to learn how to do so to review this add-on. Thanks.
Cheers,
Joseph

-----Original Message-----
From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io>
On Behalf Of Luke Davis
Sent: Tuesday, September 15, 2020 4:35 AM
To: nvda-addons@groups.io
Subject: [nvda-addons] numpadNavMode Add-on: all new beta release 0.5-dev
for testing & review

Hello all!

I'm happy to announce an all-new beta of the numpadNavMode add-on, of which
I released an alpha a couple weeks ago.

It has been almost completely rewritten, both to address some of the
comments received, and because I just didn't like how it worked before. I
think it is much better in this form, and I request anyone who tried it
before, to try it again.

For those who didn't test it yet, please consider testing it now: it really
is new and improved, if I do say so.

New in this version:

* Warning dialog on installation has been removed, no longer applies.
* The add-on should now avoid allowing any Windows nav, or any of its other
numpad gestures, to be saved to a user's gestures.ini file.
* If a user maps one of the numpad gestures while in NVDA mode, it will
remember that mapping when it switches back to NVDA mode from Windows mode.

A reminder of what it does:
Allows you to switch your numpad into Windows navigation mode, so you can
use its arrow keys, home/end, and page up and down.

Download:
https://github.com/opensourcesys/numpadNavMode/releases/download/0.5-dev/num
padNavMode-0.5-dev.nvda-addon

Readme:
https://github.com/opensourcesys/numpadNavMode/blob/master/readme.md

Known issues:

At the moment, I am not sure about its translatability. The add-on itself
could be translated, but I have not yet looked into what I would have to do
for locale gesture configurations. It may work well, it may not, for non-US
keyboard users.
I intend to dig into that more in an upcoming version. If anyone wants to
provide suggestions about that, please get in touch.

Luke


numpadNavMode Add-on: all new beta release 0.5-dev for testing & review

Luke Davis
 

Hello all!

I'm happy to announce an all-new beta of the numpadNavMode add-on, of which I released an alpha a couple weeks ago.

It has been almost completely rewritten, both to address some of the comments received, and because I just didn't like how it worked before. I think it is much better in this form, and I request anyone who tried it before, to try it again.

For those who didn't test it yet, please consider testing it now: it really is new and improved, if I do say so.

New in this version:

* Warning dialog on installation has been removed, no longer applies.
* The add-on should now avoid allowing any Windows nav, or any of its other numpad gestures, to be saved to a user's gestures.ini file.
* If a user maps one of the numpad gestures while in NVDA mode, it will remember that mapping when it switches back to NVDA mode from Windows mode.

A reminder of what it does:
Allows you to switch your numpad into Windows navigation mode, so you can use its arrow keys, home/end, and page up and down.

Download: https://github.com/opensourcesys/numpadNavMode/releases/download/0.5-dev/numpadNavMode-0.5-dev.nvda-addon

Readme:
https://github.com/opensourcesys/numpadNavMode/blob/master/readme.md

Known issues:

At the moment, I am not sure about its translatability. The add-on itself could be translated, but I have not yet looked into what I would have to do for locale gesture configurations. It may work well, it may not, for non-US keyboard users.
I intend to dig into that more in an upcoming version. If anyone wants to provide suggestions about that, please get in touch.

Luke


Re: Licensing and pip questions

James Scholes
 

This has nothing to do with hardware virtualisation, and for add-on users it's most likely irrelevant. This is only of any use to add-on developers who wish to use external Python packages which aren't included in NVDA (or stdlib modules which are removed during the build process).

Regards,

James Scholes

On 14/09/2020 at 1:52 pm, Shaun Everiss wrote:
What would be needed for me to use pip and run an environment.
If you mean hardware virtualisation, my workstation has it.
Actually, to anyone that has an hp computer, it may need to be enabled in bios but you do have the support most likely.
I have seen this in a 6th generation system in bios as I was configuring it with friends helping for someone.
So its possible it will be about in every hp computer.
On 15/09/2020 4:48 am, Joseph Lee wrote:
Hi,
As for Pip and virtual environments, unlikely as NVDA must be run as a dedicated binary for those who do not have resources to run Python, let alone virtual environments. It might be possible to create such a scenario on newer Windows 10 releases, but since many users are still on older Windows releases (even older Windows 10 feature updates), this coming to fruition is quite unlikely.
Cheers,
Joseph

-----Original Message-----
From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of Omer Zak
Sent: Monday, September 14, 2020 12:49 AM
To: nvda-addons@nvda-addons.groups.io
Subject: Re: [nvda-addons] Licensing and pip questions

On Sun, 2020-09-13 at 23:42 -0700, Joseph Lee wrote:
Regarding licensing question, as some may say that add-ons are
derivatives of NVDA, they must be licensed under GPL 2 as NVDA itself
is licensed under GPL 2. One possible workaround could be stating in
your add-on file headers that the add-on is licensed under GPL, or
perhaps GPL 2 or later. Note that not all dependencies NVDA uses are
licensed under GPL, so one must be careful of that. More info can be
found in NVDA license file (NVDA menu/Help/License).
Thanks for the reference to the license file.

I remember seeing mentions of proprietary plugins/add-ons.
It is my understanding from reading the above that those plugins work via the exception to GPLv2 which permits use of such plugins under certain conditions.

So I understand that my own plugin has to be licensed under GPLv2, but I'll be allowed to license few data files under GPLv3+ (they contain materials from GPLv3+ licensed projects).


As for including external modules, you must include them manually as
part of your add-on (Resource Monitor comes with Psutil for this very
reason).
Looks to me to be prohibitively heavy-weight.

Did anyone request a NVDA feature which would work like the following:

1. NVDA runs inside a virtualenv.

2. When installed, plugins may request that certain modules be installed from PyPI via pip.

3. A module in NVDA manages dependencies of modules installed via pip in behalf of add-ons, and blocks uninstallation of pip-installed modules unless all add-ons needing them have been uninstalled.


Cheers,
Joseph

-----Original Message-----
From: nvda-addons@nvda-addons.groups.io <
nvda-addons@nvda-addons.groups.io> On Behalf Of Omer Zak
Sent: Sunday, September 13, 2020 9:50 PM
To: NVDA Addons Mailing List <nvda-addons@nvda-addons.groups.io>
Subject: [nvda-addons] Licensing and pip questions

I apologize if the following questions are FAQs but I did not find
answers in any NVDA documentation that I know of.

I'll appreciate being pointed at answers in NVDA's documentation if
any, rather than getting direct answers to my questions.

1. What is the policy concerning licensing of NVDA add-ons?
Does NVDA require that all its add-ons be released under GPLv2+, or am
I allowed to release my add-on under GPLv3+ ("GPLv3 or later")?

2. I want my add-on to use a module from PyPI.
When developing, I can build a virtualenv and use 'pip install' to
install the add-on module in the virtualenv.
However, in end-user's NVDA installation I have no access to his
virtualenv.
How to build my add-on to ensure that the end-user will have that
module in his system?
--
The key to making programs fast is to make them do practically nothing.
Mike Haertel (original author of GNU grep) My own blog is at https://tddpirate.zak.co.il/

My opinions, as expressed in this E-mail message, are mine alone.
They do not represent the official policy of any organization with which I may be affiliated in any way.
WARNING TO SPAMMERS:  at https://www.zak.co.il/spamwarning.html








Re: Licensing and pip questions

 

Hi,
It has nothing to do with hardware virtualization, but rather a specific Python setup routine.
Cheers,
Joseph

-----Original Message-----
From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of Shaun Everiss
Sent: Monday, September 14, 2020 11:53 AM
To: nvda-addons@nvda-addons.groups.io
Subject: Re: [nvda-addons] Licensing and pip questions

What would be needed for me to use pip and run an environment.

If you mean hardware virtualisation, my workstation has it.

Actually, to anyone that has an hp computer, it may need to be enabled in bios but you do have the support most likely.

I have seen this in a 6th generation system in bios as I was configuring it with friends helping for someone.

So its possible it will be about in every hp computer.



On 15/09/2020 4:48 am, Joseph Lee wrote:
Hi,
As for Pip and virtual environments, unlikely as NVDA must be run as a dedicated binary for those who do not have resources to run Python, let alone virtual environments. It might be possible to create such a scenario on newer Windows 10 releases, but since many users are still on older Windows releases (even older Windows 10 feature updates), this coming to fruition is quite unlikely.
Cheers,
Joseph

-----Original Message-----
From: nvda-addons@nvda-addons.groups.io
<nvda-addons@nvda-addons.groups.io> On Behalf Of Omer Zak
Sent: Monday, September 14, 2020 12:49 AM
To: nvda-addons@nvda-addons.groups.io
Subject: Re: [nvda-addons] Licensing and pip questions

On Sun, 2020-09-13 at 23:42 -0700, Joseph Lee wrote:
Regarding licensing question, as some may say that add-ons are
derivatives of NVDA, they must be licensed under GPL 2 as NVDA itself
is licensed under GPL 2. One possible workaround could be stating in
your add-on file headers that the add-on is licensed under GPL, or
perhaps GPL 2 or later. Note that not all dependencies NVDA uses are
licensed under GPL, so one must be careful of that. More info can be
found in NVDA license file (NVDA menu/Help/License).
Thanks for the reference to the license file.

I remember seeing mentions of proprietary plugins/add-ons.
It is my understanding from reading the above that those plugins work via the exception to GPLv2 which permits use of such plugins under certain conditions.

So I understand that my own plugin has to be licensed under GPLv2, but I'll be allowed to license few data files under GPLv3+ (they contain materials from GPLv3+ licensed projects).


As for including external modules, you must include them manually as
part of your add-on (Resource Monitor comes with Psutil for this very
reason).
Looks to me to be prohibitively heavy-weight.

Did anyone request a NVDA feature which would work like the following:

1. NVDA runs inside a virtualenv.

2. When installed, plugins may request that certain modules be installed from PyPI via pip.

3. A module in NVDA manages dependencies of modules installed via pip in behalf of add-ons, and blocks uninstallation of pip-installed modules unless all add-ons needing them have been uninstalled.


Cheers,
Joseph

-----Original Message-----
From: nvda-addons@nvda-addons.groups.io <
nvda-addons@nvda-addons.groups.io> On Behalf Of Omer Zak
Sent: Sunday, September 13, 2020 9:50 PM
To: NVDA Addons Mailing List <nvda-addons@nvda-addons.groups.io>
Subject: [nvda-addons] Licensing and pip questions

I apologize if the following questions are FAQs but I did not find
answers in any NVDA documentation that I know of.

I'll appreciate being pointed at answers in NVDA's documentation if
any, rather than getting direct answers to my questions.

1. What is the policy concerning licensing of NVDA add-ons?
Does NVDA require that all its add-ons be released under GPLv2+, or
am I allowed to release my add-on under GPLv3+ ("GPLv3 or later")?

2. I want my add-on to use a module from PyPI.
When developing, I can build a virtualenv and use 'pip install' to
install the add-on module in the virtualenv.
However, in end-user's NVDA installation I have no access to his
virtualenv.
How to build my add-on to ensure that the end-user will have that
module in his system?
--
The key to making programs fast is to make them do practically nothing.
Mike Haertel (original author of GNU grep) My own blog is at
https://tddpirate.zak.co.il/

My opinions, as expressed in this E-mail message, are mine alone.
They do not represent the official policy of any organization with which I may be affiliated in any way.
WARNING TO SPAMMERS: at https://www.zak.co.il/spamwarning.html








Re: Licensing and pip questions

 

What would be needed for me to use pip and run an environment.

If you mean hardware virtualisation, my workstation has it.

Actually, to anyone that has an hp computer, it may need to be enabled in bios but you do have the support most likely.

I have seen this in a 6th generation system in bios as I was configuring it with friends helping for someone.

So its possible it will be about in every hp computer.

On 15/09/2020 4:48 am, Joseph Lee wrote:
Hi,
As for Pip and virtual environments, unlikely as NVDA must be run as a dedicated binary for those who do not have resources to run Python, let alone virtual environments. It might be possible to create such a scenario on newer Windows 10 releases, but since many users are still on older Windows releases (even older Windows 10 feature updates), this coming to fruition is quite unlikely.
Cheers,
Joseph

-----Original Message-----
From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of Omer Zak
Sent: Monday, September 14, 2020 12:49 AM
To: nvda-addons@nvda-addons.groups.io
Subject: Re: [nvda-addons] Licensing and pip questions

On Sun, 2020-09-13 at 23:42 -0700, Joseph Lee wrote:
Regarding licensing question, as some may say that add-ons are
derivatives of NVDA, they must be licensed under GPL 2 as NVDA itself
is licensed under GPL 2. One possible workaround could be stating in
your add-on file headers that the add-on is licensed under GPL, or
perhaps GPL 2 or later. Note that not all dependencies NVDA uses are
licensed under GPL, so one must be careful of that. More info can be
found in NVDA license file (NVDA menu/Help/License).
Thanks for the reference to the license file.

I remember seeing mentions of proprietary plugins/add-ons.
It is my understanding from reading the above that those plugins work via the exception to GPLv2 which permits use of such plugins under certain conditions.

So I understand that my own plugin has to be licensed under GPLv2, but I'll be allowed to license few data files under GPLv3+ (they contain materials from GPLv3+ licensed projects).


As for including external modules, you must include them manually as
part of your add-on (Resource Monitor comes with Psutil for this very
reason).
Looks to me to be prohibitively heavy-weight.

Did anyone request a NVDA feature which would work like the following:

1. NVDA runs inside a virtualenv.

2. When installed, plugins may request that certain modules be installed from PyPI via pip.

3. A module in NVDA manages dependencies of modules installed via pip in behalf of add-ons, and blocks uninstallation of pip-installed modules unless all add-ons needing them have been uninstalled.


Cheers,
Joseph

-----Original Message-----
From: nvda-addons@nvda-addons.groups.io <
nvda-addons@nvda-addons.groups.io> On Behalf Of Omer Zak
Sent: Sunday, September 13, 2020 9:50 PM
To: NVDA Addons Mailing List <nvda-addons@nvda-addons.groups.io>
Subject: [nvda-addons] Licensing and pip questions

I apologize if the following questions are FAQs but I did not find
answers in any NVDA documentation that I know of.

I'll appreciate being pointed at answers in NVDA's documentation if
any, rather than getting direct answers to my questions.

1. What is the policy concerning licensing of NVDA add-ons?
Does NVDA require that all its add-ons be released under GPLv2+, or am
I allowed to release my add-on under GPLv3+ ("GPLv3 or later")?

2. I want my add-on to use a module from PyPI.
When developing, I can build a virtualenv and use 'pip install' to
install the add-on module in the virtualenv.
However, in end-user's NVDA installation I have no access to his
virtualenv.
How to build my add-on to ensure that the end-user will have that
module in his system?
--
The key to making programs fast is to make them do practically nothing.
Mike Haertel (original author of GNU grep) My own blog is at https://tddpirate.zak.co.il/

My opinions, as expressed in this E-mail message, are mine alone.
They do not represent the official policy of any organization with which I may be affiliated in any way.
WARNING TO SPAMMERS: at https://www.zak.co.il/spamwarning.html







Re: Licensing and pip questions

James Scholes
 

Looks to me to be prohibitively heavy-weight.
Heavy-weight, perhaps, depending on the size of the dependency tree, how many add-ons a user has with external dependencies, etc. But I'm not sure "prohibitively" is true. What dependencies do you need to include?

The problem with the approach you've suggested is that different add-ons will need to depend on different versions of external packages. So ultimately, a user will end up needing to download and store them regardless. I do think there is room for a dependency management system, and it has been discussed previously. But it is a non-trivial problem.

Regards,

James Scholes

On 14/09/2020 at 2:48 am, Omer Zak wrote:
On Sun, 2020-09-13 at 23:42 -0700, Joseph Lee wrote:
Regarding licensing question, as some may say that add-ons are
derivatives of NVDA, they must be licensed under GPL 2 as NVDA itself
is licensed under GPL 2. One possible workaround could be stating in
your add-on file headers that the add-on is licensed under GPL, or
perhaps GPL 2 or later. Note that not all dependencies NVDA uses are
licensed under GPL, so one must be careful of that. More info can be
found in NVDA license file (NVDA menu/Help/License).
Thanks for the reference to the license file.
I remember seeing mentions of proprietary plugins/add-ons.
It is my understanding from reading the above that those plugins work
via the exception to GPLv2 which permits use of such plugins under
certain conditions.
So I understand that my own plugin has to be licensed under GPLv2, but
I'll be allowed to license few data files under GPLv3+ (they contain
materials from GPLv3+ licensed projects).

As for including external modules, you must include them manually as
part of your add-on (Resource Monitor comes with Psutil for this very
reason).
Looks to me to be prohibitively heavy-weight.
Did anyone request a NVDA feature which would work like the following:
1. NVDA runs inside a virtualenv.
2. When installed, plugins may request that certain modules be
installed from PyPI via pip.
3. A module in NVDA manages dependencies of modules installed via pip
in behalf of add-ons, and blocks uninstallation of pip-installed
modules unless all add-ons needing them have been uninstalled.

Cheers,
Joseph
-----Original Message-----
From: nvda-addons@nvda-addons.groups.io <
nvda-addons@nvda-addons.groups.io> On Behalf Of Omer Zak
Sent: Sunday, September 13, 2020 9:50 PM
To: NVDA Addons Mailing List <nvda-addons@nvda-addons.groups.io>
Subject: [nvda-addons] Licensing and pip questions
I apologize if the following questions are FAQs but I did not find
answers in any NVDA documentation that I know of.
I'll appreciate being pointed at answers in NVDA's documentation if
any, rather than getting direct answers to my questions.
1. What is the policy concerning licensing of NVDA add-ons?
Does NVDA require that all its add-ons be released under GPLv2+, or
am I allowed to release my add-on under GPLv3+ ("GPLv3 or later")?
2. I want my add-on to use a module from PyPI.
When developing, I can build a virtualenv and use 'pip install' to
install the add-on module in the virtualenv.
However, in end-user's NVDA installation I have no access to his
virtualenv.
How to build my add-on to ensure that the end-user will have that
module in his system?


Joseph Lee's add-ons: compatible with 2020.3

 

Hi all,

I’m delighted to announce that all of my add-ons are NVDA 2020.3 ready. There are features in 2020.3 that add-ons can use to update their user experience, particularly for add-ons that include graphical user interfaces.

 

Note: there will come a day when some of my add-ons will require NVDA 2020.3 or later due to changes that cannot be backported to earlier NVDA releases. These will include Enhanced Touch Gestures, StationPlaylist, and Windows 10 App Essentials. Minimum NVDA version requirement will not be updated until end of 2020 at the earliest.

Cheers,

Joseph


Re: Licensing and pip questions

 

Hi,
As for Pip and virtual environments, unlikely as NVDA must be run as a dedicated binary for those who do not have resources to run Python, let alone virtual environments. It might be possible to create such a scenario on newer Windows 10 releases, but since many users are still on older Windows releases (even older Windows 10 feature updates), this coming to fruition is quite unlikely.
Cheers,
Joseph

-----Original Message-----
From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of Omer Zak
Sent: Monday, September 14, 2020 12:49 AM
To: nvda-addons@nvda-addons.groups.io
Subject: Re: [nvda-addons] Licensing and pip questions

On Sun, 2020-09-13 at 23:42 -0700, Joseph Lee wrote:
Regarding licensing question, as some may say that add-ons are
derivatives of NVDA, they must be licensed under GPL 2 as NVDA itself
is licensed under GPL 2. One possible workaround could be stating in
your add-on file headers that the add-on is licensed under GPL, or
perhaps GPL 2 or later. Note that not all dependencies NVDA uses are
licensed under GPL, so one must be careful of that. More info can be
found in NVDA license file (NVDA menu/Help/License).
Thanks for the reference to the license file.

I remember seeing mentions of proprietary plugins/add-ons.
It is my understanding from reading the above that those plugins work via the exception to GPLv2 which permits use of such plugins under certain conditions.

So I understand that my own plugin has to be licensed under GPLv2, but I'll be allowed to license few data files under GPLv3+ (they contain materials from GPLv3+ licensed projects).


As for including external modules, you must include them manually as
part of your add-on (Resource Monitor comes with Psutil for this very
reason).
Looks to me to be prohibitively heavy-weight.

Did anyone request a NVDA feature which would work like the following:

1. NVDA runs inside a virtualenv.

2. When installed, plugins may request that certain modules be installed from PyPI via pip.

3. A module in NVDA manages dependencies of modules installed via pip in behalf of add-ons, and blocks uninstallation of pip-installed modules unless all add-ons needing them have been uninstalled.


Cheers,
Joseph

-----Original Message-----
From: nvda-addons@nvda-addons.groups.io <
nvda-addons@nvda-addons.groups.io> On Behalf Of Omer Zak
Sent: Sunday, September 13, 2020 9:50 PM
To: NVDA Addons Mailing List <nvda-addons@nvda-addons.groups.io>
Subject: [nvda-addons] Licensing and pip questions

I apologize if the following questions are FAQs but I did not find
answers in any NVDA documentation that I know of.

I'll appreciate being pointed at answers in NVDA's documentation if
any, rather than getting direct answers to my questions.

1. What is the policy concerning licensing of NVDA add-ons?
Does NVDA require that all its add-ons be released under GPLv2+, or am
I allowed to release my add-on under GPLv3+ ("GPLv3 or later")?

2. I want my add-on to use a module from PyPI.
When developing, I can build a virtualenv and use 'pip install' to
install the add-on module in the virtualenv.
However, in end-user's NVDA installation I have no access to his
virtualenv.
How to build my add-on to ensure that the end-user will have that
module in his system?
--
The key to making programs fast is to make them do practically nothing.
Mike Haertel (original author of GNU grep) My own blog is at https://tddpirate.zak.co.il/

My opinions, as expressed in this E-mail message, are mine alone.
They do not represent the official policy of any organization with which I may be affiliated in any way.
WARNING TO SPAMMERS: at https://www.zak.co.il/spamwarning.html


FW: [nvda-devel] NVDA 2020.3beta1 is now available for testing

 

Hi all,

Consider 2020.3 an important release due to some GUI changes and other internal improvements. Good luck.

 

From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Reef Turner
Sent: Monday, September 14, 2020 5:42 AM
To: nvda-devel@groups.io
Subject: [nvda-devel] NVDA 2020.3beta1 is now available for testing

 

Hi all,

NVDA 2020.3beta1 is now available for testing. This is the first beta for the 2020.3 release, please install and test the release and report any issues.

Highlights and download links can be found in the release blog post at: https://www.nvaccess.org/post/nvda-2020-3beta1/

Thanks!