Date   

Re: A plea to NVDA developers

 

Hi,
To better understand what's going on, please answer the following questions:
* When the pop-up comes up, did you say 'no"?
* If you said "no" yet the dialog opens again, chances are that NVDA can't save settings. Have you tried saving settings manually by pressing Control+NVDA+C?
* Under Settings/General panel, is the last checkbox named "Allow the NVDA project to gather NVDA usage statistics" not checked?

Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Mallard
Sent: Friday, July 6, 2018 5:53 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] A plea to NVDA developers

I'm using the ex next... Not here yet.

Thanks for the heads-up!

Ciao,

Ollie





Il 06/07/2018 14:34, Christo de Klerk ha scritto:
I should have mentioned that I am using Master snapshots. If the
developers don't stop this behaviour, it is lying in wait for all of
you in version 18.3.

Kind regards

Christo


On 2018/07/06 01:24 PM, Darren Harris via Groups.Io wrote:
Hi,

I must admit I haven't ever gotten this either.

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joshua
Hendrickson
Sent: 06 July 2018 12:17
To: nvda@nvda.groups.io
Subject: Re: [nvda] A plea to NVDA developers

I never get that message either. I just start up NVDA and away it goes.

On 7/6/18, Mallard <mallard@...> wrote:
Hello Christo,


Strange thing indeed! I never get the dialogue. I got the request
once, and never again.

I'm sure there's an option to avoid that.


I've checked my settings. Under Settings, General, the relevant
checkbox is checked here. It's the last one before the OK.

hth, ciao,

Ollie





Il 06/07/2018 12:15, Christo de Klerk ha scritto:
Hello to NVDA developers on the list


I understand the need to get a user's permission to collect usage
data, but popping up that dialog at every start-up of NVDA is
totally over the top. Please please please don't do that. Please
include a "Don't ask me again" checkbox in the dialog and retain
the option in General settings. This is not something on which one
would regularly change one's mind. It is really annoying and
irritating to have this dialog pop up with every start-up. If you
feel it is necessary, pop it up during installation and during an
update or provide the option not to be asked again.


Kind regards


Christo







--
Joshua Hendrickson

Joshua Hendrickson










Re: A plea to NVDA developers

Mallard
 

I'm using the ex next... Not here yet.

Thanks for the heads-up!

Ciao,

Ollie

Il 06/07/2018 14:34, Christo de Klerk ha scritto:
I should have mentioned that I am using Master snapshots. If the developers don't stop this behaviour, it is lying in wait for all of you in version 18.3.

Kind regards

Christo


On 2018/07/06 01:24 PM, Darren Harris via Groups.Io wrote:
Hi,

I must admit I haven't ever gotten this either.

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joshua Hendrickson
Sent: 06 July 2018 12:17
To: nvda@nvda.groups.io
Subject: Re: [nvda] A plea to NVDA developers

I never get that message either.  I just start up NVDA and away it goes.

On 7/6/18, Mallard <mallard@...> wrote:
Hello Christo,


Strange thing indeed! I never get the dialogue. I got the request
once, and never again.

I'm sure there's an option to avoid that.


I've checked my settings. Under Settings, General, the relevant
checkbox is checked here. It's the last one before the OK.

hth, ciao,

Ollie





Il 06/07/2018 12:15, Christo de Klerk ha scritto:
Hello to NVDA developers on the list


I understand the need to get a user's permission to collect usage
data, but popping up that dialog at every start-up of NVDA is totally
over the top. Please please please don't do that. Please include a
"Don't ask me again" checkbox in the dialog and retain the option in
General settings. This is not something on which one would regularly
change one's mind. It is really annoying and irritating to have this
dialog pop up with every start-up. If you feel it is necessary, pop
it up during installation and during an update or provide the option
not to be asked again.


Kind regards


Christo







--
Joshua Hendrickson

Joshua Hendrickson









Re: A plea to NVDA developers

 

Hi,
Correct: it is part of 2018.3 to comply with privacy regulations among other things. At the moment the best person who can give you a definitive answer is out of town for a few days, so don't take my answer as official.
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Christo de Klerk
Sent: Friday, July 6, 2018 5:35 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] A plea to NVDA developers

I should have mentioned that I am using Master snapshots. If the developers don't stop this behaviour, it is lying in wait for all of you in version 18.3.

Kind regards

Christo


On 2018/07/06 01:24 PM, Darren Harris via Groups.Io wrote:
Hi,

I must admit I haven't ever gotten this either.

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joshua
Hendrickson
Sent: 06 July 2018 12:17
To: nvda@nvda.groups.io
Subject: Re: [nvda] A plea to NVDA developers

I never get that message either. I just start up NVDA and away it goes.

On 7/6/18, Mallard <mallard@...> wrote:
Hello Christo,


Strange thing indeed! I never get the dialogue. I got the request
once, and never again.

I'm sure there's an option to avoid that.


I've checked my settings. Under Settings, General, the relevant
checkbox is checked here. It's the last one before the OK.

hth, ciao,

Ollie





Il 06/07/2018 12:15, Christo de Klerk ha scritto:
Hello to NVDA developers on the list


I understand the need to get a user's permission to collect usage
data, but popping up that dialog at every start-up of NVDA is
totally over the top. Please please please don't do that. Please
include a "Don't ask me again" checkbox in the dialog and retain the
option in General settings. This is not something on which one would
regularly change one's mind. It is really annoying and irritating to
have this dialog pop up with every start-up. If you feel it is
necessary, pop it up during installation and during an update or
provide the option not to be asked again.


Kind regards


Christo







--
Joshua Hendrickson

Joshua Hendrickson







Re: A plea to NVDA developers

Christo de Klerk
 

I should have mentioned that I am using Master snapshots. If the developers don't stop this behaviour, it is lying in wait for all of you in version 18.3.

Kind regards

Christo

On 2018/07/06 01:24 PM, Darren Harris via Groups.Io wrote:
Hi,

I must admit I haven't ever gotten this either.

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joshua Hendrickson
Sent: 06 July 2018 12:17
To: nvda@nvda.groups.io
Subject: Re: [nvda] A plea to NVDA developers

I never get that message either. I just start up NVDA and away it goes.

On 7/6/18, Mallard <mallard@...> wrote:
Hello Christo,


Strange thing indeed! I never get the dialogue. I got the request
once, and never again.

I'm sure there's an option to avoid that.


I've checked my settings. Under Settings, General, the relevant
checkbox is checked here. It's the last one before the OK.

hth, ciao,

Ollie





Il 06/07/2018 12:15, Christo de Klerk ha scritto:
Hello to NVDA developers on the list


I understand the need to get a user's permission to collect usage
data, but popping up that dialog at every start-up of NVDA is totally
over the top. Please please please don't do that. Please include a
"Don't ask me again" checkbox in the dialog and retain the option in
General settings. This is not something on which one would regularly
change one's mind. It is really annoying and irritating to have this
dialog pop up with every start-up. If you feel it is necessary, pop
it up during installation and during an update or provide the option
not to be asked again.


Kind regards


Christo







--
Joshua Hendrickson

Joshua Hendrickson






Re: A plea to NVDA developers

 

Hey,

I got that message after I installed NVDA 2018.3beta. Have you turned off automatic saving of the configuration? If so, I think you should manually save the configuration after you have given permission.

Sincerely,
Artin Dekker


Op 6-7-2018 om 12:15 schreef Christo de Klerk:

Hello to NVDA developers on the list


I understand the need to get a user's permission to collect usage data, but popping up that dialog at every start-up of NVDA is totally over the top. Please please please don't do that. Please include a "Don't ask me again" checkbox in the dialog and retain the option in General settings. This is not something on which one would regularly change one's mind. It is really annoying and irritating to have this dialog pop up with every start-up. If you feel it is necessary, pop it up during installation and during an update or provide the option not to be asked again.


Kind regards


Christo




Re: A plea to NVDA developers

Chris
 

I didn’t even know data was even being collected :D

 

Maybe other screen reader do that

 

Anyway no dialog here either

 

 

 

From: Christo de Klerk
Sent: 06 July 2018 11:15
To: nvda@nvda.groups.io
Subject: [nvda] A plea to NVDA developers

 

Hello to NVDA developers on the list

 

 

I understand the need to get a user's permission to collect usage data,

but popping up that dialog at every start-up of NVDA is totally over the

top. Please please please don't do that. Please include a "Don't ask me

again" checkbox in the dialog and retain the option in General settings.

This is not something on which one would regularly change one's mind. It

is really annoying and irritating to have this dialog pop up with every

start-up. If you feel it is necessary, pop it up during installation and

during an update or provide the option not to be asked again.

 

 

Kind regards

 

 

Christo

 

 

 

 

 


Re: A plea to NVDA developers

Darren Harris
 

Hi,

I must admit I haven't ever gotten this either.

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joshua Hendrickson
Sent: 06 July 2018 12:17
To: nvda@nvda.groups.io
Subject: Re: [nvda] A plea to NVDA developers

I never get that message either. I just start up NVDA and away it goes.

On 7/6/18, Mallard <mallard@...> wrote:
Hello Christo,


Strange thing indeed! I never get the dialogue. I got the request
once, and never again.

I'm sure there's an option to avoid that.


I've checked my settings. Under Settings, General, the relevant
checkbox is checked here. It's the last one before the OK.

hth, ciao,

Ollie





Il 06/07/2018 12:15, Christo de Klerk ha scritto:
Hello to NVDA developers on the list


I understand the need to get a user's permission to collect usage
data, but popping up that dialog at every start-up of NVDA is totally
over the top. Please please please don't do that. Please include a
"Don't ask me again" checkbox in the dialog and retain the option in
General settings. This is not something on which one would regularly
change one's mind. It is really annoying and irritating to have this
dialog pop up with every start-up. If you feel it is necessary, pop
it up during installation and during an update or provide the option
not to be asked again.


Kind regards


Christo









--
Joshua Hendrickson

Joshua Hendrickson


Re: A plea to NVDA developers

Joshua Hendrickson
 

I never get that message either. I just start up NVDA and away it goes.

On 7/6/18, Mallard <mallard@...> wrote:
Hello Christo,


Strange thing indeed! I never get the dialogue. I got the request once,
and never again.

I'm sure there's an option to avoid that.


I've checked my settings. Under Settings, General, the relevant checkbox
is checked here. It's the last one before the OK.

hth, ciao,

Ollie





Il 06/07/2018 12:15, Christo de Klerk ha scritto:
Hello to NVDA developers on the list


I understand the need to get a user's permission to collect usage
data, but popping up that dialog at every start-up of NVDA is totally
over the top. Please please please don't do that. Please include a
"Don't ask me again" checkbox in the dialog and retain the option in
General settings. This is not something on which one would regularly
change one's mind. It is really annoying and irritating to have this
dialog pop up with every start-up. If you feel it is necessary, pop it
up during installation and during an update or provide the option not
to be asked again.


Kind regards


Christo








--
Joshua Hendrickson

Joshua Hendrickson


Re: A plea to NVDA developers

Mallard
 

Hello Christo,


Strange thing indeed! I never get the dialogue. I got the request once, and never again.

I'm sure there's an option to avoid that.


I've checked my settings. Under Settings, General, the relevant checkbox is checked here. It's the last one before the OK.

hth, ciao,

Ollie

Il 06/07/2018 12:15, Christo de Klerk ha scritto:
Hello to NVDA developers on the list


I understand the need to get a user's permission to collect usage data, but popping up that dialog at every start-up of NVDA is totally over the top. Please please please don't do that. Please include a "Don't ask me again" checkbox in the dialog and retain the option in General settings. This is not something on which one would regularly change one's mind. It is really annoying and irritating to have this dialog pop up with every start-up. If you feel it is necessary, pop it up during installation and during an update or provide the option not to be asked again.


Kind regards


Christo





Re: A plea to NVDA developers

Chris Mullins
 

Hi Christo
I am not a developer but a regular user and don't get such behaviour when using NVDA. The only thing I can think you are alluding to is the Welcome dialog box, which contains a check box entitled "Show Welcome Dialog At Start up", or something similar, which you should uncheck. I think the setting for this is stored in the NVDA.Ini file.

Cheers
Chris

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Christo de Klerk
Sent: 6 July 2018 11:15
To: nvda@nvda.groups.io
Subject: [nvda] A plea to NVDA developers

Hello to NVDA developers on the list


I understand the need to get a user's permission to collect usage data,
but popping up that dialog at every start-up of NVDA is totally over the
top. Please please please don't do that. Please include a "Don't ask me
again" checkbox in the dialog and retain the option in General settings.
This is not something on which one would regularly change one's mind. It
is really annoying and irritating to have this dialog pop up with every
start-up. If you feel it is necessary, pop it up during installation and
during an update or provide the option not to be asked again.


Kind regards


Christo


A plea to NVDA developers

Christo de Klerk
 

Hello to NVDA developers on the list


I understand the need to get a user's permission to collect usage data, but popping up that dialog at every start-up of NVDA is totally over the top. Please please please don't do that. Please include a "Don't ask me again" checkbox in the dialog and retain the option in General settings. This is not something on which one would regularly change one's mind. It is really annoying and irritating to have this dialog pop up with every start-up. If you feel it is necessary, pop it up during installation and during an update or provide the option not to be asked again.


Kind regards


Christo


Re: FW: [Nvda-devel] Changes to release process

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

Yes indeed.

IO - tones.beep (09:18:38.006):
Beep at pitch 1711.87270745, for 40 ms, left volume 50, right volume 50
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (09:18:38.010):
oleacc.AccessibleObjectFromEvent with window 1377398, objectID 284 and childID 0: [Error -2147467259] Unspecified error
DEBUGWARNING - updateCheck.UpdateDownloader._bg (09:18:38.032):
Error downloading https://www.nvaccess.org/download/nvda/releases/2018.3beta1/nvda_2018.3beta1.exe?update=1
Traceback (most recent call last):
File "updateCheck.pyc", line 469, in _bg
File "updateCheck.pyc", line 521, in _download
RuntimeError: Content has incorrect file hash
IO - speech.speak (09:18:38.115):
Speaking [LangChangeCommand ('en_GB'), u'Error dialog Error downloading update.']
IO - speech.speak (09:18:38.125):
Speaking [LangChangeCommand ('en_GB'), u'OK button']
IO - inputCore.InputManager.executeGesture (09:18:46.831):
Input: kb(desktop):control+alt+r
IO - speech.speak (09:18:46.937):
Speaking [LangChangeCommand ('en_GB'), u'Taskbar']
IO - speech.speak (09:18:47.005):
Speaking [LangChangeCommand ('en_GB'), u'reboot nvda with log terminal']
IO - speech.speak (09:18:47.006):
Speaking [LangChangeCommand ('en_GB'), u'80 space', u'blank']
INFO - core.main (09:18:47.030):
Exiting
DEBUG - core._terminate (09:18:47.030):
Terminating updateCheck
DEBUG - core._terminate (09:18:47.030):
Terminating watchdog
DEBUG - core._terminate (09:18:47.032):
Terminating global plugin handler
DEBUG - core._terminate (09:18:47.533):
Terminating gui
DEBUG - fileUtils.FaultTolerantFile (09:18:47.732):
C:\Users\Brian\AppData\Roaming\nvda\nvda.iniepxdqq.tmp
INFO - config.ConfigManager.save (09:18:47.749):
Base configuration saved
DEBUG - core.main (09:18:47.750):
calling lose focus on object with focus
DEBUG - core._terminate (09:18:47.750):
Terminating treeInterceptorHandler
DEBUG - core._terminate (09:18:47.752):
Terminating IAccessible support
DEBUG - core._terminate (09:18:47.752):
Terminating UIA support
DEBUGWARNING - _UIAHandler.UIAHandler.terminate (09:18:47.951):
Timeout or error while waiting for UIAHandler MTA thread
DEBUG - core._terminate (09:18:47.951):
Terminating winConsole support


snip.
Looks like its giving a wrong result to the checks made by the master snap.
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" <@joslee>
To: <nvda@nvda.groups.io>
Sent: Friday, July 06, 2018 7:47 AM
Subject: Re: [nvda] FW: [Nvda-devel] Changes to release process


Hi,
Someone also told me about this, and the log fragment indicates failed hash check.
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: Thursday, July 5, 2018 11:44 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] FW: [Nvda-devel] Changes to release process

The only issues I have had is that it seems that auto updates, although apparently downloading, do not work or install, ie, If I download them from the page and run them, I can update the target version manually in the old way, but the auto updater fails to run the snaps downloaded and says download failed At least this has happened with master to beta , and I have left it and used the downloaded manually build as a portable version. I suspect something in the existing master build might well be seeing the new name as an error. If this is the case the only work around might be to ask people to manually download the first time.
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "David Moore" <jesusloves1966@...>
To: <nvda@nvda.groups.io>
Sent: Friday, July 06, 2018 1:14 AM
Subject: Re: [nvda] FW: [Nvda-devel] Changes to release process


Hi Joseph!
Thanks a lot.
I like using the latest code possible, so I will use the alpha snapshots. I
will make comments on how everything is working in that snapshot.
David Moore
Sent from Mail for Windows 10

From: Joseph Lee
Sent: Thursday, July 5, 2018 7:27 PM
To: nvda@nvda.groups.io
Subject: [nvda] FW: [Nvda-devel] Changes to release process

Hi,
Please read Mick's follow-up post below. Thanks.
Cheers,
Joseph

-----Original Message-----
From: Mick Curran <mick@...>
Sent: Thursday, July 5, 2018 3:32 PM
To: NVDA screen reader development <nvda-devel@...>
Subject: Re: [Nvda-devel] Changes to release process

Hi all,


The Release process article has been updated again based on user feedback.


The most important parts are in the Changes for Testers:

* The next branch and next snapshots will no longer exist. Anyone currently
on a next snapshot will be automatically updated to new "alpha" snapshots.
Alpha snapshots are created directly from Master each time it changes (I.e.
when a pull request is merged). As the name suggests, these snapshots are
alpha quality. And although automated tests pass, these builds have had no
user testing.
* Anyone currently on master snapshots will be upgraded to the first
available tagged beta for the current release. Beta builds, as the name
implies, are beta quality and have had some testing by users. Note that as
new betas are made available you will keep automatically upgrading, and then
also upgrade to the final stable release. To get back to beta testing for
the next release you will need to manually download a new beta for that
release.
* The snapshots page at https://www.nvaccess.org/files/nvda/snapshots/
now lists both alpha snapshots and all beta releases.

Everything is now in place and snapshots should now start asking to upgrade
to their respective new version types.


Please note: as the new Alpha snapshots are based on current master, not
all previously incubating PRs are yet included. E.g. wxPython4 is not
yet in the alpha snapshots. These previously incubating PRs will be
merged within the near future when we are sure the infrastructure is
working.


Mick





On 4/07/2018 6:28 PM, Mick Curran wrote:
Hi Brian,


I appreciate your constructive feedback. We will certainly think about
your proposal and see what we can manage.

Although we have published the new process, we have not yet removed
any branches or switched anyone over, so we can still make some
changes before committing to this fully.


The reasons for sticking with the name master for the default
development branch are:

1. We don't want to break existing pull requests which are currently
open against master. There are more than 40 or so.

2. We don't want new contributors submitting pull requests against an
old (defunct) version of master (if we do move).

3. master is the generally accepted name for the default branch of git
repositories for most projects on github.


There may be another way to solve this specifically for snapshots.
I'll have to research this further.


We will wait for more feedback and think on this more.


Mick





But,




On 4/07/2018 4:59 PM, Brians old account via Nvda-devel wrote:
While I can see the reasoning for this change. I do think that a
number of us are going to have to do the following. When the Next
becomes master, we are going to have a period when the new beta
branch does not exist, Now taking my own case as a for instance. I
currently use master as my working version though I of course do have
a portable of the latest stable version, That will mean if I do
nothing result in effectively my master becoming next, which means my
normal copy is now bleeding edge code. I may have to wait till the
new beta is created for the ability to change this around, and make
next master and master beta. Would it not be more sensible to just
remove master, and use next as you propose master is to be, then
create a new beta when applicable?
That way folk used to using master as pretty stable will not be
affected. They will stay on master, then when a new beta comes out
they will be migrated to this for their working versions.
if you want users to participate, as I think is a good thing, in my
view the proposal I outline above will carry more people with you.
also please remember to formerly tell people on the user list about
what you are doing so you do not suddenly find a lot of folk with
problems.
I do realise that there are now a lot more checks done
automatically, but in the end its the user that will be running the
code more than anyone else, and feedback from that cohort of people
is worth its weight in gold. we all know that many programmers are
the worst testers as they are predictable. its the newbie and the
less confident user who finds the bugs.
So what do you think?

Brian

bgaff@...
Brian Gaff's other account.

----- Original Message ----- From: "Mick Curran" <mick@...>
To: "NVDA screen reader development"
<nvda-devel@...>; <nvda-translations@groups.io>
Sent: Wednesday, July 04, 2018 2:43 AM
Subject: [Nvda-devel] Changes to release process


Hi contributors,


We have made some small changes to the NVDA release process. Please
read the updated Release Process article carefully to understand the
changes and how they will affect you.

https://github.com/nvaccess/nvda/wiki/ReleaseProcess


In short, Next/incubation is going away, and prs are going to be
merged straight to master. Periodic betas will be offered startin
from 5 weeks before a release.

Please read the entire article to understand the changes fully.


Translators should not be directly affected by this change. Though
technically, translations are now based on a new "beta" branch
rather than master.


Mick









--
--
Mick Curran
Executive Director, NV Access Limited
PH: +61 7 3149 3306 ext. 101
www: http://www.nvaccess.org/
Twitter: @NVAccess
Facebook: http://www.facebook.com/NVAccess


------------------------------------------------------------------------------

Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Nvda-devel mailing list
Nvda-devel@...
https://lists.sourceforge.net/lists/listinfo/nvda-devel

------------------------------------------------------------------------------

Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Nvda-devel mailing list
Nvda-devel@...
https://lists.sourceforge.net/lists/listinfo/nvda-devel
--
--
Mick Curran
Executive Director, NV Access Limited
PH: +61 7 3149 3306 ext. 101
www: http://www.nvaccess.org/
Twitter: @NVAccess
Facebook: http://www.facebook.com/NVAccess


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Nvda-devel mailing list
Nvda-devel@...
https://lists.sourceforge.net/lists/listinfo/nvda-devel


Re: FW: [Nvda-devel] Changes to release process

 

Hi,
Someone also told me about this, and the log fragment indicates failed hash check.
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: Thursday, July 5, 2018 11:44 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] FW: [Nvda-devel] Changes to release process

The only issues I have had is that it seems that auto updates, although apparently downloading, do not work or install, ie, If I download them from the page and run them, I can update the target version manually in the old way, but the auto updater fails to run the snaps downloaded and says download failed At least this has happened with master to beta , and I have left it and used the downloaded manually build as a portable version. I suspect something in the existing master build might well be seeing the new name as an error. If this is the case the only work around might be to ask people to manually download the first time.
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "David Moore" <jesusloves1966@...>
To: <nvda@nvda.groups.io>
Sent: Friday, July 06, 2018 1:14 AM
Subject: Re: [nvda] FW: [Nvda-devel] Changes to release process


Hi Joseph!
Thanks a lot.
I like using the latest code possible, so I will use the alpha snapshots. I
will make comments on how everything is working in that snapshot.
David Moore
Sent from Mail for Windows 10

From: Joseph Lee
Sent: Thursday, July 5, 2018 7:27 PM
To: nvda@nvda.groups.io
Subject: [nvda] FW: [Nvda-devel] Changes to release process

Hi,
Please read Mick's follow-up post below. Thanks.
Cheers,
Joseph

-----Original Message-----
From: Mick Curran <mick@...>
Sent: Thursday, July 5, 2018 3:32 PM
To: NVDA screen reader development <nvda-devel@...>
Subject: Re: [Nvda-devel] Changes to release process

Hi all,


The Release process article has been updated again based on user feedback.


The most important parts are in the Changes for Testers:

* The next branch and next snapshots will no longer exist. Anyone currently
on a next snapshot will be automatically updated to new "alpha" snapshots.
Alpha snapshots are created directly from Master each time it changes (I.e.
when a pull request is merged). As the name suggests, these snapshots are
alpha quality. And although automated tests pass, these builds have had no
user testing.
* Anyone currently on master snapshots will be upgraded to the first
available tagged beta for the current release. Beta builds, as the name
implies, are beta quality and have had some testing by users. Note that as
new betas are made available you will keep automatically upgrading, and then
also upgrade to the final stable release. To get back to beta testing for
the next release you will need to manually download a new beta for that
release.
* The snapshots page at https://www.nvaccess.org/files/nvda/snapshots/
now lists both alpha snapshots and all beta releases.

Everything is now in place and snapshots should now start asking to upgrade
to their respective new version types.


Please note: as the new Alpha snapshots are based on current master, not
all previously incubating PRs are yet included. E.g. wxPython4 is not
yet in the alpha snapshots. These previously incubating PRs will be
merged within the near future when we are sure the infrastructure is
working.


Mick





On 4/07/2018 6:28 PM, Mick Curran wrote:
Hi Brian,


I appreciate your constructive feedback. We will certainly think about
your proposal and see what we can manage.

Although we have published the new process, we have not yet removed
any branches or switched anyone over, so we can still make some
changes before committing to this fully.


The reasons for sticking with the name master for the default
development branch are:

1. We don't want to break existing pull requests which are currently
open against master. There are more than 40 or so.

2. We don't want new contributors submitting pull requests against an
old (defunct) version of master (if we do move).

3. master is the generally accepted name for the default branch of git
repositories for most projects on github.


There may be another way to solve this specifically for snapshots.
I'll have to research this further.


We will wait for more feedback and think on this more.


Mick





But,




On 4/07/2018 4:59 PM, Brians old account via Nvda-devel wrote:
While I can see the reasoning for this change. I do think that a
number of us are going to have to do the following. When the Next
becomes master, we are going to have a period when the new beta
branch does not exist, Now taking my own case as a for instance. I
currently use master as my working version though I of course do have
a portable of the latest stable version, That will mean if I do
nothing result in effectively my master becoming next, which means my
normal copy is now bleeding edge code. I may have to wait till the
new beta is created for the ability to change this around, and make
next master and master beta. Would it not be more sensible to just
remove master, and use next as you propose master is to be, then
create a new beta when applicable?
That way folk used to using master as pretty stable will not be
affected. They will stay on master, then when a new beta comes out
they will be migrated to this for their working versions.
if you want users to participate, as I think is a good thing, in my
view the proposal I outline above will carry more people with you.
also please remember to formerly tell people on the user list about
what you are doing so you do not suddenly find a lot of folk with
problems.
I do realise that there are now a lot more checks done
automatically, but in the end its the user that will be running the
code more than anyone else, and feedback from that cohort of people
is worth its weight in gold. we all know that many programmers are
the worst testers as they are predictable. its the newbie and the
less confident user who finds the bugs.
So what do you think?

Brian

bgaff@...
Brian Gaff's other account.

----- Original Message ----- From: "Mick Curran" <mick@...>
To: "NVDA screen reader development"
<nvda-devel@...>; <nvda-translations@groups.io>
Sent: Wednesday, July 04, 2018 2:43 AM
Subject: [Nvda-devel] Changes to release process


Hi contributors,


We have made some small changes to the NVDA release process. Please
read the updated Release Process article carefully to understand the
changes and how they will affect you.

https://github.com/nvaccess/nvda/wiki/ReleaseProcess


In short, Next/incubation is going away, and prs are going to be
merged straight to master. Periodic betas will be offered startin
from 5 weeks before a release.

Please read the entire article to understand the changes fully.


Translators should not be directly affected by this change. Though
technically, translations are now based on a new "beta" branch
rather than master.


Mick









--
--
Mick Curran
Executive Director, NV Access Limited
PH: +61 7 3149 3306 ext. 101
www: http://www.nvaccess.org/
Twitter: @NVAccess
Facebook: http://www.facebook.com/NVAccess


------------------------------------------------------------------------------

Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Nvda-devel mailing list
Nvda-devel@...
https://lists.sourceforge.net/lists/listinfo/nvda-devel

------------------------------------------------------------------------------

Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Nvda-devel mailing list
Nvda-devel@...
https://lists.sourceforge.net/lists/listinfo/nvda-devel
--
--
Mick Curran
Executive Director, NV Access Limited
PH: +61 7 3149 3306 ext. 101
www: http://www.nvaccess.org/
Twitter: @NVAccess
Facebook: http://www.facebook.com/NVAccess


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Nvda-devel mailing list
Nvda-devel@...
https://lists.sourceforge.net/lists/listinfo/nvda-devel


Re: FW: [Nvda-devel] Changes to release process

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

The only issues I have had is that it seems that auto updates, although apparently downloading, do not work or install, ie, If I download them from the page and run them, I can update the target version manually in the old way, but the auto updater fails to run the snaps downloaded and says download failed At least this has happened with master to beta , and I have left it and used the downloaded manually build as a portable version. I suspect something in the existing master build might well be seeing the new name as an error. If this is the case the only work around might be to ask people to manually download the first time.
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "David Moore" <jesusloves1966@...>
To: <nvda@nvda.groups.io>
Sent: Friday, July 06, 2018 1:14 AM
Subject: Re: [nvda] FW: [Nvda-devel] Changes to release process


Hi Joseph!
Thanks a lot.
I like using the latest code possible, so I will use the alpha snapshots. I will make comments on how everything is working in that snapshot.
David Moore
Sent from Mail for Windows 10

From: Joseph Lee
Sent: Thursday, July 5, 2018 7:27 PM
To: nvda@nvda.groups.io
Subject: [nvda] FW: [Nvda-devel] Changes to release process

Hi,
Please read Mick's follow-up post below. Thanks.
Cheers,
Joseph

-----Original Message-----
From: Mick Curran <mick@...>
Sent: Thursday, July 5, 2018 3:32 PM
To: NVDA screen reader development <nvda-devel@...>
Subject: Re: [Nvda-devel] Changes to release process

Hi all,


The Release process article has been updated again based on user feedback.


The most important parts are in the Changes for Testers:

* The next branch and next snapshots will no longer exist. Anyone currently on a next snapshot will be automatically updated to new "alpha" snapshots. Alpha snapshots are created directly from Master each time it changes (I.e. when a pull request is merged). As the name suggests, these snapshots are alpha quality. And although automated tests pass, these builds have had no user testing.
* Anyone currently on master snapshots will be upgraded to the first available tagged beta for the current release. Beta builds, as the name implies, are beta quality and have had some testing by users. Note that as new betas are made available you will keep automatically upgrading, and then also upgrade to the final stable release. To get back to beta testing for the next release you will need to manually download a new beta for that release.
* The snapshots page at https://www.nvaccess.org/files/nvda/snapshots/
now lists both alpha snapshots and all beta releases.

Everything is now in place and snapshots should now start asking to upgrade to their respective new version types.


Please note: as the new Alpha snapshots are based on current master, not
all previously incubating PRs are yet included. E.g. wxPython4 is not
yet in the alpha snapshots. These previously incubating PRs will be
merged within the near future when we are sure the infrastructure is
working.


Mick





On 4/07/2018 6:28 PM, Mick Curran wrote:
Hi Brian,


I appreciate your constructive feedback. We will certainly think about
your proposal and see what we can manage.

Although we have published the new process, we have not yet removed
any branches or switched anyone over, so we can still make some
changes before committing to this fully.


The reasons for sticking with the name master for the default
development branch are:

1. We don't want to break existing pull requests which are currently
open against master. There are more than 40 or so.

2. We don't want new contributors submitting pull requests against an
old (defunct) version of master (if we do move).

3. master is the generally accepted name for the default branch of git
repositories for most projects on github.


There may be another way to solve this specifically for snapshots.
I'll have to research this further.


We will wait for more feedback and think on this more.


Mick





But,




On 4/07/2018 4:59 PM, Brians old account via Nvda-devel wrote:
While I can see the reasoning for this change. I do think that a
number of us are going to have to do the following. When the Next
becomes master, we are going to have a period when the new beta
branch does not exist, Now taking my own case as a for instance. I
currently use master as my working version though I of course do have
a portable of the latest stable version, That will mean if I do
nothing result in effectively my master becoming next, which means my
normal copy is now bleeding edge code. I may have to wait till the
new beta is created for the ability to change this around, and make
next master and master beta. Would it not be more sensible to just
remove master, and use next as you propose master is to be, then
create a new beta when applicable?
That way folk used to using master as pretty stable will not be
affected. They will stay on master, then when a new beta comes out
they will be migrated to this for their working versions.
if you want users to participate, as I think is a good thing, in my
view the proposal I outline above will carry more people with you.
also please remember to formerly tell people on the user list about
what you are doing so you do not suddenly find a lot of folk with
problems.
I do realise that there are now a lot more checks done
automatically, but in the end its the user that will be running the
code more than anyone else, and feedback from that cohort of people
is worth its weight in gold. we all know that many programmers are
the worst testers as they are predictable. its the newbie and the
less confident user who finds the bugs.
So what do you think?

Brian

bgaff@...
Brian Gaff's other account.

----- Original Message ----- From: "Mick Curran" <mick@...>
To: "NVDA screen reader development"
<nvda-devel@...>; <nvda-translations@groups.io>
Sent: Wednesday, July 04, 2018 2:43 AM
Subject: [Nvda-devel] Changes to release process


Hi contributors,


We have made some small changes to the NVDA release process. Please
read the updated Release Process article carefully to understand the
changes and how they will affect you.

https://github.com/nvaccess/nvda/wiki/ReleaseProcess


In short, Next/incubation is going away, and prs are going to be
merged straight to master. Periodic betas will be offered startin
from 5 weeks before a release.

Please read the entire article to understand the changes fully.


Translators should not be directly affected by this change. Though
technically, translations are now based on a new "beta" branch
rather than master.


Mick









--
--
Mick Curran
Executive Director, NV Access Limited
PH: +61 7 3149 3306 ext. 101
www: http://www.nvaccess.org/
Twitter: @NVAccess
Facebook: http://www.facebook.com/NVAccess


------------------------------------------------------------------------------

Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Nvda-devel mailing list
Nvda-devel@...
https://lists.sourceforge.net/lists/listinfo/nvda-devel

------------------------------------------------------------------------------

Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Nvda-devel mailing list
Nvda-devel@...
https://lists.sourceforge.net/lists/listinfo/nvda-devel
--
--
Mick Curran
Executive Director, NV Access Limited
PH: +61 7 3149 3306 ext. 101
www: http://www.nvaccess.org/
Twitter: @NVAccess
Facebook: http://www.facebook.com/NVAccess


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Nvda-devel mailing list
Nvda-devel@...
https://lists.sourceforge.net/lists/listinfo/nvda-devel


Re: nvda on xbox one s?

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

I am told Narrator is on x box, well the newer ones obviously. I do not do gaming, but exactly how do you do some of the keys, Is not this purely a game box, You presumably add a keyboard. There is in development a windows store version of nvda, but at present I don't think you can use add ons on it.
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "Sky Mundell" <skyt@...>
To: <nvda@nvda.groups.io>
Sent: Thursday, July 05, 2018 8:57 PM
Subject: Re: [nvda] nvda on xbox one s?


Wow it would be awesome if NVDA could be on Xbox!



From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Josh Kennedy
Sent: Thursday, July 05, 2018 12:53 PM
To: nvda@groups.io
Subject: [nvda] nvda on xbox one s?



Hi,



In the future, is there any way that NVDA could be an app in the xbox one s app store? Then I could maybe use NVDA’s windows10 OCR feature to read game menus to more easily play games like madden nfl 2018 and others. Xbox one s runs on windows10.



Josh





Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10


Re: FW: [Nvda-devel] Changes to release process

 

Hi Joseph!
Thank you for your message, I will use the latest alpha version to do the translation test version.


Re: FW: [Nvda-devel] Changes to release process

David Moore
 

Hi Joseph!

Thanks a lot.

I like using the latest code possible, so I will use the alpha snapshots. I will make comments on how everything is working in that snapshot.

David Moore

               Sent from Mail for Windows 10

 

From: Joseph Lee
Sent: Thursday, July 5, 2018 7:27 PM
To: nvda@nvda.groups.io
Subject: [nvda] FW: [Nvda-devel] Changes to release process

 

Hi,

Please read Mick's follow-up post below. Thanks.

Cheers,

Joseph

 

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

From: Mick Curran <mick@...>

Sent: Thursday, July 5, 2018 3:32 PM

To: NVDA screen reader development <nvda-devel@...>

Subject: Re: [Nvda-devel] Changes to release process

 

Hi all,

 

 

The Release process article has been updated again based on user feedback.

 

 

The most important parts are in the Changes for Testers:

 

* The next branch and next snapshots will no longer exist. Anyone currently on a next snapshot will be automatically updated to new "alpha" snapshots. Alpha snapshots are created directly from Master each time it changes (I.e. when a pull request is merged). As the name suggests, these snapshots are alpha quality. And although automated tests pass, these builds have had no user testing.

  * Anyone currently on master snapshots will be upgraded to the first available tagged beta for the current release. Beta builds, as the name implies, are beta quality and have had some testing by users. Note that as new betas are made available you will keep automatically upgrading, and then also upgrade to the final stable release. To get back to beta testing for the next release you will need to manually download a new beta for that release.

  * The snapshots page at https://www.nvaccess.org/files/nvda/snapshots/

now lists both alpha snapshots and all beta releases.

 

Everything is now in place and snapshots should now start  asking to upgrade to their respective new version types.

 

 

Please note: as the new Alpha snapshots are based on current master, not

all previously incubating PRs are yet included. E.g. wxPython4 is not 

yet in the alpha snapshots. These previously incubating PRs will be

merged within the near future when we are sure the infrastructure is

working.

 

 

Mick

 

 

 

 

 

On 4/07/2018 6:28 PM, Mick Curran wrote:

> Hi Brian,

> I appreciate your constructive feedback. We will certainly think about

> your proposal and see what we can manage.

> Although we have published the new process, we have not yet removed

> any branches or switched anyone over, so we can still make some

> changes before committing to this fully.

> The reasons for sticking with the name master for the default

> development branch are:

> 1. We don't want to break existing pull requests which are currently

> open against master. There are more than 40 or so.

> 2. We don't want new contributors submitting pull requests against an

> old (defunct) version of master (if we do move).

> 3. master is the generally accepted name for the default branch of git

> repositories for most projects on github.

> There may be another way to solve this specifically for snapshots.

> I'll have to research this further.

> We will wait for more feedback and think on this more.

> Mick

> But,

> On 4/07/2018 4:59 PM, Brians old account via Nvda-devel wrote:

>> While I can see the reasoning for this change. I do think that a

>> number of us are going to have to do the following. When the Next

>> becomes master, we are going to have a period when the new beta

>> branch does not exist, Now taking my own case as a for instance. I

>> currently use master as my working version though I of course do have

>> a portable of the latest stable version, That will mean if I do

>> nothing result in effectively my master becoming next, which means my

>> normal copy is now bleeding edge code. I may have to wait till the

>> new beta is created for the ability to change this around, and make

>> next master and master beta. Would it not be more sensible to  just

>> remove master, and use next as you propose master is to be, then

>> create a new beta when applicable?

>> That way  folk used to using master as pretty stable will not be

>> affected. They will stay on master, then when a new beta comes out

>> they will be migrated to this for their  working versions.

>> if you want users to participate, as I think is a good thing, in my

>> view the proposal I outline above will carry more people with you.

>> also please remember to formerly tell people on the user list about

>> what you are doing so you do not suddenly find a lot of folk with

>> problems.

>> I do realise that there are now a lot more checks  done

>> automatically, but in the end its the user that will be  running the

>> code more than anyone else, and feedback from that cohort of people

>> is worth its weight in gold. we all know that  many programmers are

>> the worst testers as they are predictable. its the newbie and the

>> less confident user who finds the bugs.

>> So what do you think?

>> 

>> Brian

>> 

>> bgaff@...

>> Brian Gaff's other account.

>> 

>> ----- Original Message ----- From: "Mick Curran" <mick@...>

>> To: "NVDA screen reader development"

>> <nvda-devel@...>; <nvda-translations@groups.io>

>> Sent: Wednesday, July 04, 2018 2:43 AM

>> Subject: [Nvda-devel] Changes to release process

>> 

>> 

>>> Hi contributors,

>>> 

>>> 

>>> We have made some small changes to the NVDA release process. Please

>>> read the updated Release Process article carefully to understand the

>>> changes and how they will affect you.

>>> 

>>> https://github.com/nvaccess/nvda/wiki/ReleaseProcess

>>> 

>>> 

>>> In short, Next/incubation is going away, and prs are going to be

>>> merged straight to master. Periodic betas will be offered startin

>>> from 5 weeks before a release.

>>> 

>>> Please read the entire article to understand the changes fully.

>>> 

>>> 

>>> Translators should not be directly affected by this change. Though

>>> technically, translations are now based on a new "beta" branch

>>> rather than master.

>>> 

>>> 

>>> Mick

>>> 

>>> 

>>> 

>>> 

>>> 

>>> 

>>> 

>>> 

>>> 

>>> --

>>> --

>>> Mick Curran

>>> Executive Director, NV Access Limited

>>> PH: +61 7 3149 3306 ext. 101

>>> www: http://www.nvaccess.org/

>>> Twitter: @NVAccess

>>> Facebook: http://www.facebook.com/NVAccess

>>> 

>>> 

>>> ------------------------------------------------------------------------------

>>> 

>>> Check out the vibrant tech community on one of the world's most

>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot

>>> _______________________________________________

>>> Nvda-devel mailing list

>>> Nvda-devel@...

>>> https://lists.sourceforge.net/lists/listinfo/nvda-devel

>>> 

>> 

>> 

>> ------------------------------------------------------------------------------

>> 

>> Check out the vibrant tech community on one of the world's most

>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot

>> _______________________________________________

>> Nvda-devel mailing list

>> Nvda-devel@...

>> https://lists.sourceforge.net/lists/listinfo/nvda-devel

 

--

--

Mick Curran

Executive Director, NV Access Limited

PH: +61 7 3149 3306 ext. 101

www: http://www.nvaccess.org/

Twitter: @NVAccess

Facebook: http://www.facebook.com/NVAccess

 

 

------------------------------------------------------------------------------

Check out the vibrant tech community on one of the world's most

engaging tech sites, Slashdot.org! http://sdm.link/slashdot

_______________________________________________

Nvda-devel mailing list

Nvda-devel@...

https://lists.sourceforge.net/lists/listinfo/nvda-devel

 

 

 

 


FW: [Nvda-devel] Changes to release process

 

Hi,
Please read Mick's follow-up post below. Thanks.
Cheers,
Joseph

-----Original Message-----
From: Mick Curran <mick@...>
Sent: Thursday, July 5, 2018 3:32 PM
To: NVDA screen reader development <nvda-devel@...>
Subject: Re: [Nvda-devel] Changes to release process

Hi all,


The Release process article has been updated again based on user feedback.


The most important parts are in the Changes for Testers:

* The next branch and next snapshots will no longer exist. Anyone currently on a next snapshot will be automatically updated to new "alpha" snapshots. Alpha snapshots are created directly from Master each time it changes (I.e. when a pull request is merged). As the name suggests, these snapshots are alpha quality. And although automated tests pass, these builds have had no user testing.
* Anyone currently on master snapshots will be upgraded to the first available tagged beta for the current release. Beta builds, as the name implies, are beta quality and have had some testing by users. Note that as new betas are made available you will keep automatically upgrading, and then also upgrade to the final stable release. To get back to beta testing for the next release you will need to manually download a new beta for that release.
* The snapshots page at https://www.nvaccess.org/files/nvda/snapshots/
now lists both alpha snapshots and all beta releases.

Everything is now in place and snapshots should now start asking to upgrade to their respective new version types.


Please note: as the new Alpha snapshots are based on current master, not
all previously incubating PRs are yet included. E.g. wxPython4 is not
yet in the alpha snapshots. These previously incubating PRs will be
merged within the near future when we are sure the infrastructure is
working.


Mick





On 4/07/2018 6:28 PM, Mick Curran wrote:
Hi Brian,


I appreciate your constructive feedback. We will certainly think about
your proposal and see what we can manage.

Although we have published the new process, we have not yet removed
any branches or switched anyone over, so we can still make some
changes before committing to this fully.


The reasons for sticking with the name master for the default
development branch are:

1. We don't want to break existing pull requests which are currently
open against master. There are more than 40 or so.

2. We don't want new contributors submitting pull requests against an
old (defunct) version of master (if we do move).

3. master is the generally accepted name for the default branch of git
repositories for most projects on github.


There may be another way to solve this specifically for snapshots.
I'll have to research this further.


We will wait for more feedback and think on this more.


Mick





But,




On 4/07/2018 4:59 PM, Brians old account via Nvda-devel wrote:
While I can see the reasoning for this change. I do think that a
number of us are going to have to do the following. When the Next
becomes master, we are going to have a period when the new beta
branch does not exist, Now taking my own case as a for instance. I
currently use master as my working version though I of course do have
a portable of the latest stable version, That will mean if I do
nothing result in effectively my master becoming next, which means my
normal copy is now bleeding edge code. I may have to wait till the
new beta is created for the ability to change this around, and make
next master and master beta. Would it not be more sensible to just
remove master, and use next as you propose master is to be, then
create a new beta when applicable?
That way folk used to using master as pretty stable will not be
affected. They will stay on master, then when a new beta comes out
they will be migrated to this for their working versions.
if you want users to participate, as I think is a good thing, in my
view the proposal I outline above will carry more people with you.
also please remember to formerly tell people on the user list about
what you are doing so you do not suddenly find a lot of folk with
problems.
I do realise that there are now a lot more checks done
automatically, but in the end its the user that will be running the
code more than anyone else, and feedback from that cohort of people
is worth its weight in gold. we all know that many programmers are
the worst testers as they are predictable. its the newbie and the
less confident user who finds the bugs.
So what do you think?

Brian

bgaff@...
Brian Gaff's other account.

----- Original Message ----- From: "Mick Curran" <mick@...>
To: "NVDA screen reader development"
<nvda-devel@...>; <nvda-translations@groups.io>
Sent: Wednesday, July 04, 2018 2:43 AM
Subject: [Nvda-devel] Changes to release process


Hi contributors,


We have made some small changes to the NVDA release process. Please
read the updated Release Process article carefully to understand the
changes and how they will affect you.

https://github.com/nvaccess/nvda/wiki/ReleaseProcess


In short, Next/incubation is going away, and prs are going to be
merged straight to master. Periodic betas will be offered startin
from 5 weeks before a release.

Please read the entire article to understand the changes fully.


Translators should not be directly affected by this change. Though
technically, translations are now based on a new "beta" branch
rather than master.


Mick









--
--
Mick Curran
Executive Director, NV Access Limited
PH: +61 7 3149 3306 ext. 101
www: http://www.nvaccess.org/
Twitter: @NVAccess
Facebook: http://www.facebook.com/NVAccess


------------------------------------------------------------------------------

Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Nvda-devel mailing list
Nvda-devel@...
https://lists.sourceforge.net/lists/listinfo/nvda-devel

------------------------------------------------------------------------------

Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Nvda-devel mailing list
Nvda-devel@...
https://lists.sourceforge.net/lists/listinfo/nvda-devel
--
--
Mick Curran
Executive Director, NV Access Limited
PH: +61 7 3149 3306 ext. 101
www: http://www.nvaccess.org/
Twitter: @NVAccess
Facebook: http://www.facebook.com/NVAccess


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Nvda-devel mailing list
Nvda-devel@...
https://lists.sourceforge.net/lists/listinfo/nvda-devel


Re: nvda on xbox one s?

simon wheatcroft
 

B along these lines. Last I read ea were working on making madden play well without sight. Using narrator for starting the game and navigation of the dashboard 


On 5 Jul 2018, at 20:57, Sky Mundell <skyt@...> wrote:

Wow it would be awesome if NVDA could be on Xbox!

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Josh Kennedy
Sent: Thursday, July 05, 2018 12:53 PM
To: nvda@groups.io
Subject: [nvda] nvda on xbox one s?

 

Hi,

 

In the future, is there any way that NVDA could be an app in the xbox one s app store? Then I could maybe use NVDA’s windows10 OCR feature to read game menus to more easily play games like madden nfl 2018 and others. Xbox one s runs on windows10.

 

Josh

 

 

Sent from Mail for Windows 10

 


Re: ocr with latest nvda on win7-64

Gene New Zealand <hurrikennyandopo@...>
 

Hi


This is off my how to install additional  components page.


Written stuff is below. I think there is a audio one but not on that page.


How to install and use the OCR plugin for NVDA
To give the new experimental OCR plugin (that Jamie created) a whirl,
you will need to download the plugin
from http://addons.nvda-project.org/addons/ocr.en.html and unzip the
file.  It will make a directory called OCR.  This will need to be copied
and pasted into the global plugin directory.

The easiest way to find out where to put the OCR plugin for the
installer version, (and once you have copied the OCR directory), is to
press the Windows key. Your start menu will come up. Go to programmes,
then another set of menus will come up with all of the programmes on
your PC. Once this comes up, find a menu called NVDA. Once there, a
submenu will come up and you will need to find one called explore user
configuration directory. Next, press enter. There will be some folders
in there and you will need to find one called global plugins. Paste the
OCR plugin into that directory. This is where other plugins will go for
the installer version.

For the portable version, the OCR plugin will have to be put into the
following directory: nvda...user configuration...global plugins. Make
sure that you paste the plugin for the portable version into that directory.

You will need to reload the plugins, by going to reload plugins under
the tools section in NVDA. (Insert N...tools...reload plugins). You will
also need to reload NVDA to update your settings. The object you are
going to scan must be in focus otherwise it will not work.  If you are
unsure, go to running locations and locate the item and press enter to
put you into focus.  To OCR the item (for example a pdf that has not
been done), use the Insert key and the letter r to start it.  It will
say performing OCR,  then say done.  To read what has been written
there, you will need to change over to the review cursor to read the
contents of that document.  Please read the section called reviewing
text in the user manual if you are unsure.  The information given back
to you will vary from scanned image to image, depending on the quality
of the things you have scanned. Please refer to step 4 above if needed.
Currently, the OCR only works with the snapshots.
Reviewing the text within your OCR'd document
NVDA allows you to read the contents of the current navigator object
(including flat review) by character, word or line using the numeric
keypad. This is mostly useful in places (including Windows command
consoles) where there is no system caret. For example, you might use it
to review the text of a long information message in a dialogue.
Reviewing text by character, word or line
To help you remember these commands, note that the basic text review
commands are organized in a grid of three by three, with top to bottom
being line, word and character and left to right being previous, current
and next. Using the numpad keys requires the NumLock key to be turned
off to work properly. Using your numeric keypad, the following are
reported by pressing the appropriate numbers:
Previous line 7
Current line 8
Next line 9
Previous word 4
Current word 5
Next word 6
Previous character 1
Current character 2
Next character 3
For a full list of other text review related commands (for example
report text formatting or copy from review cursor etcetera), please
refer to the Reviewing Text section in the user manual.


Gene nz

On 7/6/2018 2:36 AM, Rusty Perez wrote:
Hi folks,
I have the ocr addon installed but when I press nvda/R NVDA reports
that it is performing ocr, but I don't know what to do next.
When it is finished, I seem to be back in the exact same place where I started.
I'm trying to read a screen shot provided on a page of instructions.

Any help using OCR with NVDA would be appreciated since I'm also
trying to use software which may only be accessible using OCR..



thanks!
Rusty