|
NVDA add-on Developer toolkit getting started guide contributions
Andy B.
Hi,
To help write a portion of the NVDA add-on Developer toolkit getting started guide, I have two questions for its current users, or potential users of the add-on:
Send your responses to ajborka@.... Thanks for your help in the creation of a getting started guide.
Sent from Mail for Windows 10
|
|
|
|
Re: #project-idea Grouping similar issues by project
#project-idea
Noelia Ruiz
Yes, I didn"t know what cars are. This explanation is useful and I like the idea of using projects.
toggle quoted messageShow quoted text
Thanks Enviado desde mi iPhone
El 1 may 2020, a las 13:17, Reef Turner <reef@...> escribió:
|
|
|
|
Re: #project-idea Grouping similar issues by project
#project-idea
Reef Turner
Yes, the GitHub project boards need some work to be easy to use with a screen reader that's for sure. Cards are just issues, but can be organized within the project by using the columns. The columns on these projects are automated, cards / issues will automatically move from "to do", "in progress", "review in progress", "review approved", "done" as the work progresses. For most, these details are probably not that useful, but may be interesting.
For most people, it's probably adequate to use the filter on the issue list project: is:open is:issue project:nvaccess/nvda/7 If you don't know the project number, use the 'projects' button on the issues page to select the project to filter by, it is announced as "clickable button collapsed subMenu Projects". You can also find out which project and column an issue is in by looking at the issue itself. After labels is projects. It tells you which projects this issue is part of, the status of that project (done / in progress/ to do) and then the column the issue is in. I hope this is helpful.
|
|
|
|
Re: #project-idea Grouping similar issues by project
#project-idea
Noelia Ruiz
Hi, I like the idea of projects to make easier to pay attention to
toggle quoted messageShow quoted text
specific and related issues. Anyway, a short explanation about the differences between projects, cars and columns maybe useful for screen reader users, at least for me :) I have seen the shortcuts provided by GitHub pressing ?, but I don't know how to interact with projects, though columns seem to be under headings of level 3 and we can press g to go to issues, I think. Kind regards 2020-04-30 16:28 GMT+02:00, Reef Turner <reef@nvaccess.org>:
I'd like to take advantage of GitHub's projects feature to make it easier
|
|
|
|
Announcing Project Blackjack: hunting for NVDA add-on bugs and coding style improvements with Flake8
Hello NVDA add-ons and development community,
For those new to the community: I’m Joseph Lee, one of the volunteer code contributors to NVDA screen reader project. I hope everyone is staying safe and healthy during this uncertain time.
Like many of you, the ongoing COVID-19 pandemic had a profound impact in my life. After thinking about what to do while juggling online classes, I decided to take a look at the overall health of the NVDA add-ons ecosystem, specifically a way to hunt for bugs and improve code quality and style. The result is Project Blackjack, a set of recommendations for doing just that (linting) with help from Flake8.
As some of you might be aware by now, NVDA project is using Flake8, a popular coding style checker (linter) to deal with coding style. This tool allows us (NVDA contributors) to look at potential issues that can arise from inconsistent coding style, and in some cases, find things that appear to be harmless but are actual bugs (syntax warnings and errors and such). Some of you posting pull requests to GitHub may have noticed messages about Flake8 errors on your code, with the tool asking you to fix issues found.
In April 2020, I decided to run Flake8 against add-ons I have developed so far. Not only this tool found linting issues, it found potential bugs, and in at least two occasions, actual bugs that weren’t obvious at first. Notable finds include error handling logic error in encoder support in StationPlaylist, unused variable in Resource Monitor, and a need to update Weather app module in Windows 10 App Essentials to modern NVDA coding standards. Thanks to this tool, these three add-ons have gone through coding style changes, bug fixes, and passes Flake8 test.
Because linting NVDA source code itself is something that will take months, I propose that add-ons community use Flake8 to look into coding style, and in some cases, hunt for potential and actual bugs. To do this:
For more info on Flake8, take a look at: https://flake8.pycqa.org/en/latest/
Recommended usage while developing and maintaining add-ons:
Tips:
For NVDA code contributors: to reduce messages you get about Flake8 when you submit pull requests, I recommend doing a local linting and runtime tests first before committing changes. Not only it can reduce Flake8 messages, it can also reduce diffs and let you see that your changes are fine and readable (no regressions, for example).
As a practical demonstration of linting, I will be dedicating upcoming version 20.06 release of my add-ons to Flake8 work. Resource Monitor, StationPlaylist, and Windows 10 App Essentials have gone through linting check in April and they are working as advertised.
If you have any questions, feel free to ask. For coding style for NVDA project, refer to NVDA wiki article on coding style and contributing. Thanks. Cheers, Joseph
|
|
|
|
Re: NVDA 2020.1rc1 released
Cyrille
toggle quoted messageShow quoted text
Le 30/04/2020 à 10:34, Reef Turner a écrit :
No, I'm not sure which message and I can't find it. Can you tell me the title?
|
|
|
|
Re: #project-idea Grouping similar issues by project
#project-idea
Marlon Brandão de Sousa
This would be a huge thing.
toggle quoted messageShow quoted text
Obrigado, Marlon
Em 30 de abr de 2020, à(s) 13:06, Joseph Lee <joseph.lee22590@...> escreveu:
|
|
|
|
Re: #project-idea Grouping similar issues by project
#project-idea
Hi, At one point I was going to propose creating subgroups for people interested in doing specific work, but it looks like GitHub projects might be a bit more flexible. Cheers, Joseph
From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Reef Turner
Sent: Thursday, April 30, 2020 7:29 AM To: nvda-devel@groups.io Subject: [nvda-devel] #project-idea Grouping similar issues by project
I'd like to take advantage of GitHub's projects feature to make it easier for new and existing developers to find work relevant to their interest, group related work to help ensure it works towards a common goal and generally be more organized.
|
|
|
|
#project-idea Grouping similar issues by project
#project-idea
Reef Turner
I'd like to take advantage of GitHub's projects feature to make it easier for new and existing developers to find work relevant to their interest, group related work to help ensure it works towards a common goal and generally be more organized.
I have just created one such project: [Project] Bullet / list UX These NVDA dev community projects will be prefaced with "[Project]" to make filtering of the projects list easier with "is:open project" I'll add and announce these projects in 'nvda-devel' message board with the hashtag #project-idea. For now this can be considered a draft process. Any feedback on this is welcome, for now I won't be creating a large collection of projects, first I would like to see how NVDA devs react to this idea.
|
|
|
|
Re: NVDA 2020.1rc1 released
Reef Turner
No, I'm not sure which message and I can't find it. Can you tell me the title?
toggle quoted messageShow quoted text
-----Original Message-----
From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Brian's Mail list account via groups.io Sent: Thursday, 30 April 2020 9:35 AM To: nvda-devel@groups.io Subject: Re: [nvda-devel] NVDA 2020.1rc1 released did you spot the message about the beta from Cyrille just a few up from this one? Brian bglists@blueyonder.co.uk Sent via blueyonder. Please address personal E-mail to:- briang1@blueyonder.co.uk, putting 'Brian Gaff' in the display name field. Newsgroup monitored: alt.comp.blind-users ----- Original Message ----- From: "Reef Turner" <reef@nvaccess.org> To: <nvda-devel@groups.io> Sent: Wednesday, April 29, 2020 4:03 PM Subject: [nvda-devel] NVDA 2020.1rc1 released Hi all, NVDA 2020.1rc1 has been released. This is a release candidate, and unless any critical issues are found, this will be identical to the 2020.1 release. Highlights and download links can be found in the release blog post at: https://www.nvaccess.org/post/nvda-2020-1rc1-now-available-for-testing/
|
|
|
|
Re: NVDA 2020.1rc1 released
Brian's Mail list account
did you spot the message about the beta from Cyrille just a few up from this one?
toggle quoted messageShow quoted text
Brian bglists@blueyonder.co.uk Sent via blueyonder. Please address personal E-mail to:- briang1@blueyonder.co.uk, putting 'Brian Gaff' in the display name field. Newsgroup monitored: alt.comp.blind-users
----- Original Message -----
From: "Reef Turner" <reef@nvaccess.org> To: <nvda-devel@groups.io> Sent: Wednesday, April 29, 2020 4:03 PM Subject: [nvda-devel] NVDA 2020.1rc1 released Hi all, NVDA 2020.1rc1 has been released. This is a release candidate, and unless any critical issues are found, this will be identical to the 2020.1 release. Highlights and download links can be found in the release blog post at: https://www.nvaccess.org/post/nvda-2020-1rc1-now-available-for-testing/
|
|
|
|
Re: NVDA 2020 release schedule
Noelia Ruiz
Thanks.
toggle quoted messageShow quoted text
2020-04-29 16:55 GMT+02:00, Reef Turner <reef@nvaccess.org>:
I agree, that page could use updating, though it's a bit of a chicken and
|
|
|
|
NVDA 2020.1rc1 released
Reef Turner
Hi all,
NVDA 2020.1rc1 has been released. This is a release candidate, and unless any critical issues are found, this will be identical to the 2020.1 release.
Highlights and download links can be found in the release blog post at: https://www.nvaccess.org/post/nvda-2020-1rc1-now-available-for-testing/
|
|
|
|
Re: NVDA 2020 release schedule
Reef Turner
I agree, that page could use updating, though it's a bit of a chicken and egg situation. We are currently working out the details of this process, and trying to be transparent about the changes we are making as we make them. If there are aspects of that page that are particularly misleading, please let me know.
|
|
|
|
Re: NVDA 2020 release schedule
Noelia Ruiz
Imo this may be documented if you find it useful, since the article
toggle quoted messageShow quoted text
about the release process was updated more than a year ago. https://github.com/nvaccess/nvda/wiki/ReleaseProcess Kind regards 2020-04-29 14:59 GMT+02:00, Reef Turner <reef@nvaccess.org>:
In the past we have aimed for 4 releases a year. The new approach will
|
|
|
|
Re: NVDA 2020 release schedule
Reef Turner
In the past we have aimed for 4 releases a year. The new approach will likely result in a variable number of releases per year. The releases will be smaller but more often. The release process takes a minimum of 6 weeks from first beta until release. That said, releases may be delayed up by high priority issues. Realistically, I don't expect the number of releases to change drastically.
toggle quoted messageShow quoted text
-----Original Message-----
From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Akash Kakkar Sent: Tuesday, 21 April 2020 8:37 PM To: nvda-devel@groups.io Subject: Re: [nvda-devel] NVDA 2020 release schedule Hey Reef, You said: --We are aiming for a shorter release cycle, so we will likely start the 2020.2 beta as soon as the 2020.1 release is made.-- So, will it be for always or only for this time? and if it will be persistent, then how many releases we can expect in a year? Although, I'm interested in having more releases throughout the year. On 4/21/20, Reef Turner <reef@nvaccess.org> wrote: The 2020.1 RC is currently blocked waiting for:
|
|
|
|
locked
Re: NVDA add-on Developer toolkit tutorials and guides
Andy B.
Hi,
The directions stated to send an email to ajborka@... with your response. Can someone lock the thread to avoid this problem again?
Sent from Mail for Windows 10
From: Alexander Epaneshnikov
Sent: Wednesday, April 29, 2020 8:20 AM To: nvda-devel@groups.io Subject: Re: [nvda-devel] NVDA add-on Developer toolkit tutorials and guides
hello. i am a proponent of html docs.
-- Sincerely, Alexander.
|
|
|
|
locked
Re: NVDA add-on Developer toolkit tutorials and guides
hello. i am a proponent of html docs.
-- Sincerely, Alexander.
|
|
|
|
locked
NVDA add-on Developer toolkit tutorials and guides
Andy B.
Developer toolkit is an NVDA add-on that assists blind and visually impaired software/web developers create appealing user interfaces and web pages. It does this through analyzing the accessibility tree provided by browsers and other software conforming to the UIA specifications set out by Microsoft or the legacy IAccessible2 interfaces, also provided by Microsoft. Once Developer toolkit 20.03 is released, it will be stable enough for general production use. In which formats would you like to see the tutorials or guides produced? For example, Word, PDF, HTML, screen casts/YouTube videos, or audio files? What type of user interfaces would you like to create or get a tutorial/guide on how to create? Send your submissions to ajborka@... and I will start looking into the process once DTK 20.03 is released.
Sent from Mail for Windows 10
Sent from Mail for Windows 10
|
|
|
|
Re: Log full of error in NVDA 2020.1beta1
Brian's Mail list account
As I say, raise an issue on the tracker, since you understand the issues.
toggle quoted messageShow quoted text
Brian bglists@blueyonder.co.uk Sent via blueyonder. Please address personal E-mail to:- briang1@blueyonder.co.uk, putting 'Brian Gaff' in the display name field. Newsgroup monitored: alt.comp.blind-users
----- Original Message -----
From: "Cyrille via groups.io" <cyrille.bougot2=laposte.net@groups.io> To: <nvda-devel@groups.io> Sent: Monday, April 27, 2020 10:57 AM Subject: Re: [nvda-devel] Log full of error in NVDA 2020.1beta1 I do not think the issue comes from speech.speak. This speech.speak is called as soon as NVDA starts because the focused window information is spoken: Speaking ['Loupe'] "Loupe" = "Magnifier" and Speaking ['Zoom arrière', 'bouton', 'Zoom arrière'] "Zoom arrière" = "Zoom out" The issue comes from a continuously executed callback. This callback is calling JABHandler. Windows Magnifier does not rely on Java Access Bridge so that is why I do not think it is related to this issue. On the contrary Matlab downloader probably relies on Java Access Bridge. At least, I know that Matlab itself relies on Java UI. So I think there is something wrong with this downloader window even in background. Maybe du to progress bar? Cheers, Cyrille Le 27/04/2020 à 09:34, Brian's Mail list account via groups.io a écrit : Your problem appears to start here.
|
|
|
