Date   

Add-on Updater: August 25th build revision A fixes compatibility with NVDA 2018.2

 

Hi all,

 

Several users reported a regression where Add-on Updater August 25th build didn’t work with NVDA 2018.2. This was traced to an attribute that does not exist in wxPython Classic. This regression was fixed with revision A (20180825A), and depending on which NVDA version you have, you can apply this via Add-on Updater (alpha and beta builds) or install it manually from add-ons website (NVDA 2018.2).

Cheers,

Joseph


Add on updater does not work on the release version of nvda

Brian's Mail list account <bglists@...>
 

The previous version does, so do not update it to the one which has the checkboxes. For some reason that extra feature has broken it. I have posted the error on the add on list, but suffice to say, the update button is not there whether you check or uncheck the checkbox. it will work fine on the beta and alpha snaps however, so I suspect its using some part of the newer code that does not exist in the current release version.
Just a bit of advice.
Its probably going to be fixed by Joseph soon so I'll leave it at that for now.
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.


Re: Advisory... once again (and one last time): NVDA Remote 2.1 (without patch) is incompatible with NVDA 2018.3 and future releases

Sarah k Alawami
 

I was actually wondering that. The authors seem to have gone awol so can we in theory integrate this or do we need their permission to do this?

On 25 Aug 2018, at 11:47, Jonathan Milam wrote:

If no further progress is made, is it possible for this to be adopted as part of NVDA itself going forward?


Thanks,
Jonathan


On Aug 25, 2018, at 2:39 PM, Joseph Lee <joseph.lee22590@...> wrote:

Dear NVDA community,

 

The following is a repeat of an advisory I sent out a few weeks ago regarding Remote Support add-on. Given there has been no progress whatsoever from original add-on authors (Tyler Spivey and Chris Toth), coupled with renewed reports of this add-on not working with NVDA 2018.3 beta 3, I’m sending the below advisory again:

 

NVDA Remote Support add-on 2.1 isn’t compatible with NVDA 2018.3 due to the add-on not being updated to support wxPython 4 attributes. The biggest problem is that the add-on will not load when installed on NVDA 2018.3 beta 3 and later. An emergency patch is available, but ideally, fixes should come from add-on authors themselves, and latest commits to this add-on does include compatibility fixes but not released as stable build.

 

IMPORTANT: this is the final advisory regarding this add-on. If no progress has been made by September 7, 2018, the add-ons community will declare this add-on (without the emergency patch) incompatible with future NVDA releases and will make an announcement to that effect on add-ons website.

 

A personal plea to Remote Support add-on authors: I really hate to say the following but it should be said now: please consider what I said above as an ultimatum from add-ons community (sorry for using that term, but it captures precisely the community’s feelings towards this add-on and understands how important this add-on is to so many people). If add-ons that did not ask for crowd funding is compatible with wxPython 4 features, and in extension, NVDA 2018.3, how come a project that received several thousand dollars of crowd funding in 2015 not future-proof? I have warned you for the last few months regarding compatibility issues with Remote add-on, and have asked repeatedly for a solution from add-on authors themselves, even going so far as producing a third-party patch myself. And no, I won’t keep holding onto my patch – there will come a day when I’ll say, “I had enough” and will take down my patch to demonstrate my own frustrations.

 

Now this is just a tip of the iceberg: if add-ons are not compatible with wxPython 4, how could they be compatible with Python 3 once NVDA project moves on? Consider what I just said and implications: there will be a huger uproar when users find out that their favorite add-on (and for some, a very critical add-on) stops functioning because add-on authors abandoned it or did not update their add-on to use Python 3 features. As I’ve been saying for the last twelve months or so, wxPython 4 transition is just a taste of what’s to come once NVDA is repowered by Python 3.

 

Thanks.

Cheers,

Joseph


Re: Advisory... once again (and one last time): NVDA Remote 2.1 (without patch) is incompatible with NVDA 2018.3 and future releases

Gene
 

It appears that NVDA policy makers should have some sort of legal language where it should be that by creating an add on and having it approved by the reviewers, this constitutes that the developers agree that the software is open-source and must release the code.  Of course, developers create add-ons and don't have them approved and this legal language wouldn't apply to them.  Nor, of course, would it apply to those who don't submit software in the first place.  To restate for clarity and brevity, the approval of add-ons for official recognition as approved by NVDA reviewers shall mean that the add-on is open source and all code and anything else relevant to meeting that definition shall be released to the public by either the reviewers or by the add-on developers or both..
 
Gene

----- Original Message -----
Sent: Saturday, August 25, 2018 2:08 PM
Subject: Re: [nvda] Advisory... once again (and one last time): NVDA Remote 2.1 (without patch) is incompatible with NVDA 2018.3 and future releases

Realistically though, if the authors have not replied then I guess you are
in a bit of a legal fix, but if at least one has and has no further
interest, then perhaps they can clarify this issue.
 It would, I think be a shame to let all that work die because of a fuzzy
bit of code that nobody really knows who owns.
 If the source is out there then maybe the best bet is to go ahead and fix
it, submit it to the originarators with a nicely worded ultimatum. I  am not
one to break the law, but sometimes the law is  not the problem the people
are, as has been said, if all the  authors  died what then?
Does the patch fix things for ever? If so then I see no problem, but of
course most if not all add ons are going to the wall when you all upgrade to
the newer version of Python.
 Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Joseph Lee" <joseph.lee22590@...>
To: <nvda@nvda.groups.io>
Sent: Saturday, August 25, 2018 7:53 PM
Subject: Re: [nvda] Advisory... once again (and one last time): NVDA Remote
2.1 (without patch) is incompatible with NVDA 2018.3 and future releases


Hi,

Based on discussions on Twitter, if I’m understanding it correctly, not all
source code for this add-on has been released to the public, which may
actually violate GPL’s terms. The client bits are available, but the server
bits may or may not be available in source code form.

Cheers,

Joseph



From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Brian Vogel
Sent: Saturday, August 25, 2018 11:51 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Advisory... once again (and one last time): NVDA Remote
2.1 (without patch) is incompatible with NVDA 2018.3 and future releases



Joseph,

             I understand and share your frustrations.  That being said, the
creators of an add-on (or any software, for that matter) are not responsible
for its perpetual maintenance unless they so choose.   It is quite clear,
given recent history and the attempt to get the original authors "back up on
that horse again," that they have not so chosen.  The fact that they were
crowdfunded is utterly irrelevant.  That funding gave birth to the software
and some period of maintenance.  It does not create a perpetual unbreakable
bond.

             If reasonable attempts have been made to re-engage the original
authors and they have declined to do so, are these add-ons not open-source?
Certainly someone else who is capable of maintaining them (and I hasten to
add I am not making a veiled reference to you and you alone, or even at all)
should feel perfectly free to step into the void left by the original
authors, pick up that torch, and run with it.

             This is the only way you can even hope to maintain perpetual
ongoing compatibility, as you could easily lose authoring resources due to
death, accident, or other factors besides lack of ongoing interest on the
part of the originating authors.

             If I am mistaken about this code being open source, then there
definitely needs to be some mechanism in place that grants formal ownership
and copyright for NVDA add-ons to NVAccess itself and allows them to be
passed along to other developers as circumstances dictate.

--

Brian - Windows 10 Home, 64-Bit, Version 1803, Build 17134

    A little kindness from person to person is better than a vast love for
all humankind.

           ~ Richard Dehmel














Re: Advisory... once again (and one last time): NVDA Remote 2.1 (without patch) is incompatible with NVDA 2018.3 and future releases

Brian's Mail list account <bglists@...>
 

Realistically though, if the authors have not replied then I guess you are in a bit of a legal fix, but if at least one has and has no further interest, then perhaps they can clarify this issue.
It would, I think be a shame to let all that work die because of a fuzzy bit of code that nobody really knows who owns.
If the source is out there then maybe the best bet is to go ahead and fix it, submit it to the originarators with a nicely worded ultimatum. I am not one to break the law, but sometimes the law is not the problem the people are, as has been said, if all the authors died what then?
Does the patch fix things for ever? If so then I see no problem, but of course most if not all add ons are going to the wall when you all upgrade to the newer version of Python.
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.

----- Original Message -----
From: "Joseph Lee" <joseph.lee22590@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Saturday, August 25, 2018 7:53 PM
Subject: Re: [nvda] Advisory... once again (and one last time): NVDA Remote 2.1 (without patch) is incompatible with NVDA 2018.3 and future releases


Hi,

Based on discussions on Twitter, if I’m understanding it correctly, not all source code for this add-on has been released to the public, which may actually violate GPL’s terms. The client bits are available, but the server bits may or may not be available in source code form.

Cheers,

Joseph



From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Brian Vogel
Sent: Saturday, August 25, 2018 11:51 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Advisory... once again (and one last time): NVDA Remote 2.1 (without patch) is incompatible with NVDA 2018.3 and future releases



Joseph,

I understand and share your frustrations. That being said, the creators of an add-on (or any software, for that matter) are not responsible for its perpetual maintenance unless they so choose. It is quite clear, given recent history and the attempt to get the original authors "back up on that horse again," that they have not so chosen. The fact that they were crowdfunded is utterly irrelevant. That funding gave birth to the software and some period of maintenance. It does not create a perpetual unbreakable bond.

If reasonable attempts have been made to re-engage the original authors and they have declined to do so, are these add-ons not open-source? Certainly someone else who is capable of maintaining them (and I hasten to add I am not making a veiled reference to you and you alone, or even at all) should feel perfectly free to step into the void left by the original authors, pick up that torch, and run with it.

This is the only way you can even hope to maintain perpetual ongoing compatibility, as you could easily lose authoring resources due to death, accident, or other factors besides lack of ongoing interest on the part of the originating authors.

If I am mistaken about this code being open source, then there definitely needs to be some mechanism in place that grants formal ownership and copyright for NVDA add-ons to NVAccess itself and allows them to be passed along to other developers as circumstances dictate.

--

Brian - Windows 10 Home, 64-Bit, Version 1803, Build 17134

A little kindness from person to person is better than a vast love for all humankind.

~ Richard Dehmel


Re: Advisory... once again (and one last time): NVDA Remote 2.1 (without patch) is incompatible with NVDA 2018.3 and future releases

 

Hi,

Based on discussions on Twitter, if I’m understanding it correctly, not all source code for this add-on has been released to the public, which may actually violate GPL’s terms. The client bits are available, but the server bits may or may not be available in source code form.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Brian Vogel
Sent: Saturday, August 25, 2018 11:51 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Advisory... once again (and one last time): NVDA Remote 2.1 (without patch) is incompatible with NVDA 2018.3 and future releases

 

Joseph,

             I understand and share your frustrations.  That being said, the creators of an add-on (or any software, for that matter) are not responsible for its perpetual maintenance unless they so choose.   It is quite clear, given recent history and the attempt to get the original authors "back up on that horse again," that they have not so chosen.  The fact that they were crowdfunded is utterly irrelevant.  That funding gave birth to the software and some period of maintenance.  It does not create a perpetual unbreakable bond.

             If reasonable attempts have been made to re-engage the original authors and they have declined to do so, are these add-ons not open-source?  Certainly someone else who is capable of maintaining them (and I hasten to add I am not making a veiled reference to you and you alone, or even at all) should feel perfectly free to step into the void left by the original authors, pick up that torch, and run with it.

             This is the only way you can even hope to maintain perpetual ongoing compatibility, as you could easily lose authoring resources due to death, accident, or other factors besides lack of ongoing interest on the part of the originating authors.

             If I am mistaken about this code being open source, then there definitely needs to be some mechanism in place that grants formal ownership and copyright for NVDA add-ons to NVAccess itself and allows them to be passed along to other developers as circumstances dictate.

--

Brian - Windows 10 Home, 64-Bit, Version 1803, Build 17134  

    A little kindness from person to person is better than a vast love for all humankind.

           ~ Richard Dehmel

 

 


Re: Advisory... once again (and one last time): NVDA Remote 2.1 (without patch) is incompatible with NVDA 2018.3 and future releases

 

On Sat, Aug 25, 2018 at 02:49 PM, Joseph Lee wrote:
Depends on what the original authors say.
And what if they decline to say?   Is there absolutely no existing mechanism to allow an orphaned piece of add-on software to be taken over by someone else?

If there isn't, this had better serve as a wake up call.
 
--

Brian - Windows 10 Home, 64-Bit, Version 1803, Build 17134  

    A little kindness from person to person is better than a vast love for all humankind.

           ~ Richard Dehmel

 

 


Re: Advisory... once again (and one last time): NVDA Remote 2.1 (without patch) is incompatible with NVDA 2018.3 and future releases

Lenron
 

I wish it had been adopted in to NVDA from the start, then this
wouldn't even be an issue.

On 8/25/18, Jonathan Milam <milamj@wfu.edu> wrote:
If no further progress is made, is it possible for this to be adopted as
part of NVDA itself going forward?


Thanks,
Jonathan
On Aug 25, 2018, at 2:39 PM, Joseph Lee <joseph.lee22590@gmail.com> wrote:

Dear NVDA community,



The following is a repeat of an advisory I sent out a few weeks ago
regarding Remote Support add-on. Given there has been no progress
whatsoever from original add-on authors (Tyler Spivey and Chris Toth),
coupled with renewed reports of this add-on not working with NVDA 2018.3
beta 3, I’m sending the below advisory again:



NVDA Remote Support add-on 2.1 isn’t compatible with NVDA 2018.3 due to the
add-on not being updated to support wxPython 4 attributes. The biggest
problem is that the add-on will not load when installed on NVDA 2018.3 beta
3 and later. An emergency patch is available, but ideally, fixes should
come from add-on authors themselves, and latest commits to this add-on does
include compatibility fixes but not released as stable build.



IMPORTANT: this is the final advisory regarding this add-on. If no progress
has been made by September 7, 2018, the add-ons community will declare this
add-on (without the emergency patch) incompatible with future NVDA releases
and will make an announcement to that effect on add-ons website.



A personal plea to Remote Support add-on authors: I really hate to say the
following but it should be said now: please consider what I said above as
an ultimatum from add-ons community (sorry for using that term, but it
captures precisely the community’s feelings towards this add-on and
understands how important this add-on is to so many people). If add-ons
that did not ask for crowd funding is compatible with wxPython 4 features,
and in extension, NVDA 2018.3, how come a project that received several
thousand dollars of crowd funding in 2015 not future-proof? I have warned
you for the last few months regarding compatibility issues with Remote
add-on, and have asked repeatedly for a solution from add-on authors
themselves, even going so far as producing a third-party patch myself. And
no, I won’t keep holding onto my patch – there will come a day when I’ll
say, “I had enough” and will take down my patch to demonstrate my own
frustrations.



Now this is just a tip of the iceberg: if add-ons are not compatible with
wxPython 4, how could they be compatible with Python 3 once NVDA project
moves on? Consider what I just said and implications: there will be a huger
uproar when users find out that their favorite add-on (and for some, a very
critical add-on) stops functioning because add-on authors abandoned it or
did not update their add-on to use Python 3 features. As I’ve been saying
for the last twelve months or so, wxPython 4 transition is just a taste of
what’s to come once NVDA is repowered by Python 3.



Thanks.

Cheers,

Joseph




--
Lenron Brown
Cell: 985-271-2832
Skype: ron.brown762


Re: Advisory... once again (and one last time): NVDA Remote 2.1 (without patch) is incompatible with NVDA 2018.3 and future releases

 

Joseph,

             I understand and share your frustrations.  That being said, the creators of an add-on (or any software, for that matter) are not responsible for its perpetual maintenance unless they so choose.   It is quite clear, given recent history and the attempt to get the original authors "back up on that horse again," that they have not so chosen.  The fact that they were crowdfunded is utterly irrelevant.  That funding gave birth to the software and some period of maintenance.  It does not create a perpetual unbreakable bond.

             If reasonable attempts have been made to re-engage the original authors and they have declined to do so, are these add-ons not open-source?  Certainly someone else who is capable of maintaining them (and I hasten to add I am not making a veiled reference to you and you alone, or even at all) should feel perfectly free to step into the void left by the original authors, pick up that torch, and run with it.

             This is the only way you can even hope to maintain perpetual ongoing compatibility, as you could easily lose authoring resources due to death, accident, or other factors besides lack of ongoing interest on the part of the originating authors.

             If I am mistaken about this code being open source, then there definitely needs to be some mechanism in place that grants formal ownership and copyright for NVDA add-ons to NVAccess itself and allows them to be passed along to other developers as circumstances dictate.

--

Brian - Windows 10 Home, 64-Bit, Version 1803, Build 17134  

    A little kindness from person to person is better than a vast love for all humankind.

           ~ Richard Dehmel

 

 


Re: Advisory... once again (and one last time): NVDA Remote 2.1 (without patch) is incompatible with NVDA 2018.3 and future releases

 

Hi,

Depends on what the original authors say. If Chris and Tyler says it is okay to let NV Access and others incorporate this into NVDA, then yes.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Jonathan Milam
Sent: Saturday, August 25, 2018 11:47 AM
To: nvda@nvda.groups.io
Cc: NVDA screen reader development <nvda-devel@...>
Subject: Re: [nvda] Advisory... once again (and one last time): NVDA Remote 2.1 (without patch) is incompatible with NVDA 2018.3 and future releases

 

If no further progress is made, is it possible for this to be adopted as part of NVDA itself going forward?

 

 

Thanks,

Jonathan


On Aug 25, 2018, at 2:39 PM, Joseph Lee <joseph.lee22590@...> wrote:

Dear NVDA community,

 

The following is a repeat of an advisory I sent out a few weeks ago regarding Remote Support add-on. Given there has been no progress whatsoever from original add-on authors (Tyler Spivey and Chris Toth), coupled with renewed reports of this add-on not working with NVDA 2018.3 beta 3, I’m sending the below advisory again:

 

NVDA Remote Support add-on 2.1 isn’t compatible with NVDA 2018.3 due to the add-on not being updated to support wxPython 4 attributes. The biggest problem is that the add-on will not load when installed on NVDA 2018.3 beta 3 and later. An emergency patch is available, but ideally, fixes should come from add-on authors themselves, and latest commits to this add-on does include compatibility fixes but not released as stable build.

 

IMPORTANT: this is the final advisory regarding this add-on. If no progress has been made by September 7, 2018, the add-ons community will declare this add-on (without the emergency patch) incompatible with future NVDA releases and will make an announcement to that effect on add-ons website.

 

A personal plea to Remote Support add-on authors: I really hate to say the following but it should be said now: please consider what I said above as an ultimatum from add-ons community (sorry for using that term, but it captures precisely the community’s feelings towards this add-on and understands how important this add-on is to so many people). If add-ons that did not ask for crowd funding is compatible with wxPython 4 features, and in extension, NVDA 2018.3, how come a project that received several thousand dollars of crowd funding in 2015 not future-proof? I have warned you for the last few months regarding compatibility issues with Remote add-on, and have asked repeatedly for a solution from add-on authors themselves, even going so far as producing a third-party patch myself. And no, I won’t keep holding onto my patch – there will come a day when I’ll say, “I had enough” and will take down my patch to demonstrate my own frustrations.

 

Now this is just a tip of the iceberg: if add-ons are not compatible with wxPython 4, how could they be compatible with Python 3 once NVDA project moves on? Consider what I just said and implications: there will be a huger uproar when users find out that their favorite add-on (and for some, a very critical add-on) stops functioning because add-on authors abandoned it or did not update their add-on to use Python 3 features. As I’ve been saying for the last twelve months or so, wxPython 4 transition is just a taste of what’s to come once NVDA is repowered by Python 3.

 

Thanks.

Cheers,

Joseph


Re: Advisory... once again (and one last time): NVDA Remote 2.1 (without patch) is incompatible with NVDA 2018.3 and future releases

Jonathan Milam
 

If no further progress is made, is it possible for this to be adopted as part of NVDA itself going forward?


Thanks,
Jonathan


On Aug 25, 2018, at 2:39 PM, Joseph Lee <joseph.lee22590@...> wrote:

Dear NVDA community,

 

The following is a repeat of an advisory I sent out a few weeks ago regarding Remote Support add-on. Given there has been no progress whatsoever from original add-on authors (Tyler Spivey and Chris Toth), coupled with renewed reports of this add-on not working with NVDA 2018.3 beta 3, I’m sending the below advisory again:

 

NVDA Remote Support add-on 2.1 isn’t compatible with NVDA 2018.3 due to the add-on not being updated to support wxPython 4 attributes. The biggest problem is that the add-on will not load when installed on NVDA 2018.3 beta 3 and later. An emergency patch is available, but ideally, fixes should come from add-on authors themselves, and latest commits to this add-on does include compatibility fixes but not released as stable build.

 

IMPORTANT: this is the final advisory regarding this add-on. If no progress has been made by September 7, 2018, the add-ons community will declare this add-on (without the emergency patch) incompatible with future NVDA releases and will make an announcement to that effect on add-ons website.

 

A personal plea to Remote Support add-on authors: I really hate to say the following but it should be said now: please consider what I said above as an ultimatum from add-ons community (sorry for using that term, but it captures precisely the community’s feelings towards this add-on and understands how important this add-on is to so many people). If add-ons that did not ask for crowd funding is compatible with wxPython 4 features, and in extension, NVDA 2018.3, how come a project that received several thousand dollars of crowd funding in 2015 not future-proof? I have warned you for the last few months regarding compatibility issues with Remote add-on, and have asked repeatedly for a solution from add-on authors themselves, even going so far as producing a third-party patch myself. And no, I won’t keep holding onto my patch – there will come a day when I’ll say, “I had enough” and will take down my patch to demonstrate my own frustrations.

 

Now this is just a tip of the iceberg: if add-ons are not compatible with wxPython 4, how could they be compatible with Python 3 once NVDA project moves on? Consider what I just said and implications: there will be a huger uproar when users find out that their favorite add-on (and for some, a very critical add-on) stops functioning because add-on authors abandoned it or did not update their add-on to use Python 3 features. As I’ve been saying for the last twelve months or so, wxPython 4 transition is just a taste of what’s to come once NVDA is repowered by Python 3.

 

Thanks.

Cheers,

Joseph


Re: Advisory... once again (and one last time): NVDA Remote 2.1 (without patch) is incompatible with NVDA 2018.3 and future releases

 

a shame really because I use this nvda add on  alot

time to go looking for another remote option

grrrrrrrrrrrrrrrrrrrrrrr

On 8/25/2018 11:39 AM, Joseph Lee wrote:

Dear NVDA community,

 

The following is a repeat of an advisory I sent out a few weeks ago regarding Remote Support add-on. Given there has been no progress whatsoever from original add-on authors (Tyler Spivey and Chris Toth), coupled with renewed reports of this add-on not working with NVDA 2018.3 beta 3, I’m sending the below advisory again:

 

NVDA Remote Support add-on 2.1 isn’t compatible with NVDA 2018.3 due to the add-on not being updated to support wxPython 4 attributes. The biggest problem is that the add-on will not load when installed on NVDA 2018.3 beta 3 and later. An emergency patch is available, but ideally, fixes should come from add-on authors themselves, and latest commits to this add-on does include compatibility fixes but not released as stable build.

 

IMPORTANT: this is the final advisory regarding this add-on. If no progress has been made by September 7, 2018, the add-ons community will declare this add-on (without the emergency patch) incompatible with future NVDA releases and will make an announcement to that effect on add-ons website.

 

A personal plea to Remote Support add-on authors: I really hate to say the following but it should be said now: please consider what I said above as an ultimatum from add-ons community (sorry for using that term, but it captures precisely the community’s feelings towards this add-on and understands how important this add-on is to so many people). If add-ons that did not ask for crowd funding is compatible with wxPython 4 features, and in extension, NVDA 2018.3, how come a project that received several thousand dollars of crowd funding in 2015 not future-proof? I have warned you for the last few months regarding compatibility issues with Remote add-on, and have asked repeatedly for a solution from add-on authors themselves, even going so far as producing a third-party patch myself. And no, I won’t keep holding onto my patch – there will come a day when I’ll say, “I had enough” and will take down my patch to demonstrate my own frustrations.

 

Now this is just a tip of the iceberg: if add-ons are not compatible with wxPython 4, how could they be compatible with Python 3 once NVDA project moves on? Consider what I just said and implications: there will be a huger uproar when users find out that their favorite add-on (and for some, a very critical add-on) stops functioning because add-on authors abandoned it or did not update their add-on to use Python 3 features. As I’ve been saying for the last twelve months or so, wxPython 4 transition is just a taste of what’s to come once NVDA is repowered by Python 3.

 

Thanks.

Cheers,

Joseph

-- 
check out my song on youtube
https://youtu.be/YeWgx2LRu7Y


Advisory... once again (and one last time): NVDA Remote 2.1 (without patch) is incompatible with NVDA 2018.3 and future releases

 

Dear NVDA community,

 

The following is a repeat of an advisory I sent out a few weeks ago regarding Remote Support add-on. Given there has been no progress whatsoever from original add-on authors (Tyler Spivey and Chris Toth), coupled with renewed reports of this add-on not working with NVDA 2018.3 beta 3, I’m sending the below advisory again:

 

NVDA Remote Support add-on 2.1 isn’t compatible with NVDA 2018.3 due to the add-on not being updated to support wxPython 4 attributes. The biggest problem is that the add-on will not load when installed on NVDA 2018.3 beta 3 and later. An emergency patch is available, but ideally, fixes should come from add-on authors themselves, and latest commits to this add-on does include compatibility fixes but not released as stable build.

 

IMPORTANT: this is the final advisory regarding this add-on. If no progress has been made by September 7, 2018, the add-ons community will declare this add-on (without the emergency patch) incompatible with future NVDA releases and will make an announcement to that effect on add-ons website.

 

A personal plea to Remote Support add-on authors: I really hate to say the following but it should be said now: please consider what I said above as an ultimatum from add-ons community (sorry for using that term, but it captures precisely the community’s feelings towards this add-on and understands how important this add-on is to so many people). If add-ons that did not ask for crowd funding is compatible with wxPython 4 features, and in extension, NVDA 2018.3, how come a project that received several thousand dollars of crowd funding in 2015 not future-proof? I have warned you for the last few months regarding compatibility issues with Remote add-on, and have asked repeatedly for a solution from add-on authors themselves, even going so far as producing a third-party patch myself. And no, I won’t keep holding onto my patch – there will come a day when I’ll say, “I had enough” and will take down my patch to demonstrate my own frustrations.

 

Now this is just a tip of the iceberg: if add-ons are not compatible with wxPython 4, how could they be compatible with Python 3 once NVDA project moves on? Consider what I just said and implications: there will be a huger uproar when users find out that their favorite add-on (and for some, a very critical add-on) stops functioning because add-on authors abandoned it or did not update their add-on to use Python 3 features. As I’ve been saying for the last twelve months or so, wxPython 4 transition is just a taste of what’s to come once NVDA is repowered by Python 3.

 

Thanks.

Cheers,

Joseph


Re: webpage shortcuts using firefox

 

The default method is drag and drop, which is not particularly convenient for screen reader users.

See this article on intowindows.com entitled, How To Create Website Shortcut On Desktop In Windows 10, which gives you alternative methods for creating desktop shortcuts to websites that are applicable no matter what web browser you're using.

If your default web browser is something other than Internet Explorer (and it should be) you can still use the trick of using IE just to create the desktop shortcut from the webpage currently visible.  The shortcut on the desktop will open in whatever your chosen default web browser happens to be, as what's created is nothing more than a shortcut to a web page and those are always opened by the default web browser you've chosen.

--

Brian - Windows 10 Home, 64-Bit, Version 1803, Build 17134  

    A little kindness from person to person is better than a vast love for all humankind.

           ~ Richard Dehmel

 

 


Re: webpage shortcuts using firefox

Brian Tew
 

Tell me a bit more. Do you want a clickable item on your desktop
that will open firefox to a specific web page?


Re: Open Office vs Libre

Brian's Mail list account <bglists@...>
 

Well, both have their limitations, in that there is no browse or focus mode on these document editors, however I have had considerably more luck with the Libra variant than the other, plus there is a portable version which seems to work well. Do not try to use the other bits of their office suite though as there seems to be issues.Even with Java and the access bridges installed bits seem not to work very well, but for word processing, I guess its OK, but I do still keep an old version of Office around.
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.

----- Original Message -----
From: "David Mellor" <david2@parasys.co.uk>
To: <nvda@nvda.groups.io>
Sent: Saturday, August 25, 2018 1:46 PM
Subject: [nvda] Open Office vs Libre


Could I ask which open office suite is best for use with NVDA please?
I only tend to use Word 2003, and Outlook but that's another matter.
The option to run the same software on Linux (Vinux) would be a big plus so
I'm skipping Jarte.
Very many thanks,
David



Re: downloding MP3 (Extracting and, splitting and trimming)

Larry Silvermintz <silvermintz@...>
 

Pazera free audio extractor is an excellent utility that transforms a group of videos to audio, can even truncate the start/end.

mp3splt.exe is another great freebie that splits and/or truncates.

 

 

 

 


From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Hope Williamson via Groups.Io
Sent: Saturday, August 25, 2018 12:42 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] downloding MP3 FILES

 

 Hi, it's probably not possible to get a virus downloading from Youtube itself. It may be possible though, depending on the converter you're using to download/convert the video to mp3 format.

 

On 8/24/2018 7:25 PM, Gene wrote:

You said it is possible to get a virus or malware downloading from Youtube.  Do you mean possible or impossible?  For that matter, if you would be infected by downloading, which I really doubt, why couldn't you be infected by playing the file from the site?  For reasons I stated in my previous message, I really doubt you can be infected by downloading from Youtube.

 

Gene

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

From: Kevin

Sent: Friday, August 24, 2018 8:34 PM

Subject: Re: [nvda] downloding MP3 FILES

 

It’s called WASAPI,, record the sound your speakers outputs

 

It is possible to get a virus or malware downloading fron youtube

 

E-mail is golden!!!
Kevin Lee

 

From: JM Casey
Sent: Friday, August 24, 2018 6:17 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] downloding MP3 FILES

 

Using “what you hear” or whatever it’s called in Goldwave is definitely a neat trick and can certainly be really helpful.

 

You can’t really get a virus from an mp3 though.

 

The OP asked for a programme so I assumed he wasn’t talking about a web browser. Surprised noone’s mentioned Soulseek yet, so I’ll mention it now. Unfortunately the QT version, the only one being updated, doesn’t seem very accessible from my standpoint, although apparently some people have gotten it to work with NVDA…

 

 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Kevin
Sent: August 24, 2018 9:08 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] downloding MP3 FILES

 

I use GoldWave to record songs, that way I can listen to the song as I rrecord it.  Also you don’t get any virus or trash that is in the music information such as author, extra url of ads etc…

 

E-mail is golden!!!
Kevin Lee

 

From: Kerryn Gunness via Groups.Io
Sent: Friday, August 24, 2018 10:44 AM
To: nvda@nvda.groups.io
Subject: [nvda] downloding MP3 FILES

 

hi group

which is the best and most accessible program for windows pc to downlode mp3 files using NVDA?

thank u

 

kerryn

 

 

 

 

Virus-free. www.avast.com


Add-on Updater and StationPlaylist Studio updated #addonrelease

 

Hi all,

 

A few hours ago I said that SPL add-on 18.08.2 will hand over update check feature to Add-on Updater. That moment has come with one crucial clarification: SPL add-on can check for updates on its own if Add-on Updater is disabled.

 

Besides this, Add-on Updater August 25th build will hit the air in less than an hour from now. The biggest change is ability to receive development snapshots for add-ons if you choose to via a new checkable list found in Add-on Updater settings panel. In addition, if the add-on is enabled, it’ll check updates for StationPlaylist Studio add-on.

 

Regarding update results checkboxes: after doing some thinking and research, I’ll make a change so that all checkboxes will be checked, meaning by default I’ll assume you wish to update all add-ons. This change will be part of not the August 25th build, but the one coming after that, as I need time to test this and apply corresponding changes to the pull request for NVDA issue 3208.

 

Cheers,

Joseph


LibreOffice

Don H
 

Is there any special settings for LibreOffice when using it on a Win 10 system and the latest version of NVDA?


Re: advisory: Windows 10 App Essentials 18.09 will no longer let you select update channel from the add-on itself

 

Hi,
You read it correctly, and this does not contradict my earlier "big picture"
statement that I'll be handing over update check feature to Add-on Updater.
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Brian's Mail
list account via Groups.Io
Sent: Saturday, August 25, 2018 12:28 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] advisory: Windows 10 App Essentials 18.09 will no longer
let you select update channel from the add-on itself

Joseph this seems to contradict the post you made in the add ons group. Can
you clarify. I think you mean that if you do not want to use add onupdater
updates will still work for this and station playlists, but if add on
updater is loaded it will be used instead. At least that is how I read the
post in the add ons list.
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.
----- Original Message -----
From: "Joseph Lee" <joseph.lee22590@gmail.com>
To: "'NVDA screen reader development'" <nvda-devel@lists.sourceforge.net>
Sent: Saturday, August 25, 2018 6:28 AM
Subject: [nvda] advisory: Windows 10 App Essentials 18.09 will no longer let
you select update channel from the add-on itself


Hi all,



The following is considered a critical advisory in that it affects
everyone using Windows 10 App Essentials add-on:



Starting from Windows 10 App Essentials 18.09, the add-on will no longer
offer update channel selection functionality. This is a necessary change
in
order to hand over add-on update checking functionality to Add-on Updater,
and in extension, NVDA Core in the future. In reality, you can change
update
channels, but this will involve modifying add-on manifest.



To switch channels from September 2018 onwards (or, for those on
development/pilot channels, August 27th snapshot and later), you need to
visit Community Add-ons website (addons.nvda-project.org), select Windows
10
App Essentials, and download the release you'd like to use/test. The full
switchover to Add-on Updater will occur with Windows 10 App Essentials
18.10.



Cheers,

Joseph