Date   
Re: Weather_Plus7.6 update available

وفيق طاهر
 

Cities are no longer approved in Arabic

Weather_Plus7.6 update available

Adriano Barbieri
 

Hi to every one,


• Fixed a bug while searching for the most recent weather report due to data transmission error from the service (rare case)
Weather_Plus can update itself, but you can download it from this direct link:
https://www.nvda.it/files/plugin/weather_plus7.6.nvda-addon

Note: The international Weather_Plus download page link will not work for the time being until it is updated.


Regards
Adriano


Re: Image Describer: add-on is no longer working, potential replacement is Larry Wang's Online Image Describer

Shubham Jain
 

Hello Joseph,

I contacted Oliver over a month ago, seeking some information about his add-on. He replied and said that he was "in a very hectic period due to the coronavirus". This might be the reason he hasn't replied to emails. As for the add-on itself, he did not provide any details about it's status and his intentions to continue supporting it.
Hope this information is helpful.

regards,
Shubham Jain

Re: Image Describer: add-on is no longer working, potential replacement is Larry Wang's Online Image Describer

Noelia Ruiz
 

Hello, this is an extremely important feature. I would like to remember that very long time ago I had to uninstall OnlineImageDescriber by Larry Wang, since he didn"t work, probably because the free apis offered stopped working for free, and I wasn"t be able to include Azure apis. I think that Shuban project, with an internal library not needing an online service, is very important and hope this can be achieved successfully.
Cheers

Enviado desde mi iPhone

El 14 jun 2020, a las 22:21, Joseph Lee <joseph.lee22590@...> escribió:



Hi all,

Follow-up: a reviewer reminds me that Larry's Online Image Describer (found under development section on community ad-dons website) would be a suitable alternative. Once that add-on becomes stable, we need to either replace original Image Describer with Larry's version, or remove Image Describer add-on and keep Larry's version (I think the former is much better for everyone).

For Larry: I know the community took a look at your add-on last December. Any updates since then? Are you ready to declare the add-on as stable or need someone to review changes? If you declare the add-on as stable, let us know how you want us to proceed with replacing original Image Describer add-on.

Cheers,

Joseph

Re: Image Describer: add-on is no longer working, potential replacement is Larry Wang's Online Image Describer

 

Hi all,

Follow-up: a reviewer reminds me that Larry's Online Image Describer (found under development section on community ad-dons website) would be a suitable alternative. Once that add-on becomes stable, we need to either replace original Image Describer with Larry's version, or remove Image Describer add-on and keep Larry's version (I think the former is much better for everyone).

For Larry: I know the community took a look at your add-on last December. Any updates since then? Are you ready to declare the add-on as stable or need someone to review changes? If you declare the add-on as stable, let us know how you want us to proceed with replacing original Image Describer add-on.

Cheers,

Joseph

Image Describer: add-on is no longer working, potential replacement is Larry Wang's Online Image Describer

 

Hello all,

No, I’m still out of office, but the following matter is very important for us:

Several members of NVDA users list report that Image Describer add-on from Oliver Edholm is no longer working. One member reported to me privately that Oliver stated on his add-on page (not the community website) that the add-on is not working due to lack of payment. Also, the person who wrote to me privately adds that he tried to contact Oliver a few days ago regarding his add-on with no responses yet.

Please help find answers about this add-on for users. If Oliver says the add-on cannot be resurrected due to circumstances beyond his control, and if others cannot maintain this add-on on behalf of the community due to requiring payment for its upkeep and other matters beyond the community’s control, the add-on will be subject to removal as early as once NVDA 2020.2 is released.

Cheers,

Joseph

Re: Developer toolkit reaches a new level

Andy B.
 

Hi,

 

Thanks for the support. I will have to try some simple tests in Chrome. On the desktop environment side of things, I might have figured out how to avoid the NVDA add-on idea completely, and go with a pure python implementation of DTK. As a result, there would be browser extension implementations and a python implementation of DTK. Would this be worth paying for?

 

 

Sent from Mail for Windows 10

 

From: James Scholes
Sent: Thursday, June 11, 2020 6:37 PM
To: nvda-addons@nvda-addons.groups.io
Subject: Re: [nvda-addons] Developer toolkit reaches a new level

 

As far as I know, the only way to access a true representation of the

DOM and accessibility tree (if web extensions have direct access to

that) is to run your code inside the browser.  I believe you've already

realised this yourself through a lot of trial and error, trying to

obtain the mark-up of an element from within NVDA.  It just doesn't work.

 

So, my vote is that any accessibility-focused tools which need DOM

access must run in the browser.  If you want to expose an interface via

an NVDA add-on, your browser extension can share information with a

native process and vice-versa.  But equally, if the UI was good, I would

use an entirely in-browser version of DTK.

 

Regards,

 

James Scholes

 

On 11/06/2020 at 1:56 pm, Andy B. wrote:

> Is this even worth putting into an NVDA add-on then? Why not have the

> add-on for desktop environments and a browser extension for web content?

> The only question then, is the layout of the browser extension’s output.

>

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

> Windows 10

>

> *From: *James Scholes <mailto:james@...>

> *Sent: *Thursday, June 11, 2020 12:23 PM

> *To: *nvda-addons@nvda-addons.groups.io

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

> *Subject: *Re: [nvda-addons] Developer toolkit reaches a new level

>

> That explains how it parses the content, but not where it gets it from.

>

> If your add-on downloads a copy of the web page and only uses

>

> stylesheets or inline styles, that's not a true representation of the

>

> DOM for a huge percentage of websites which rely on JavaScript.  It

>

> won't work at all with SPAs, or websites which require a login.  And as

>

> the web moves more towards web components and other dynamic techniques,

>

> it will become increasingly less useful.

>

> Now, if you were to write a web extension for the browser which could

>

> communicate a true representation of DOM elements to your add-on via

>

> IPC, that would be worth paying for.

>

> Regards,

>

> James Scholes

>

> On 11/06/2020 at 11:19 am, Andy B. wrote:

>

>  > It uses the bs4 and tinycss libraries found in the pip repository.

>

>  >

>

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

>

>  > Windows 10

>

>  >

>

>  > *From: *James Scholes <mailto:james@...>

>

>  > *Sent: *Thursday, June 11, 2020 10:57 AM

>

>  > *To: *nvda-addons@nvda-addons.groups.io

>

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

>

>  > *Subject: *Re: [nvda-addons] Developer toolkit reaches a new level

>

>  >

>

>  > Before offering any sort of paid material, be that the add-on itself or

>

>  >

>

>  > supporting content, it would be good to know how the add-on is obtaining

>

>  >

>

>  > the mark-up and styling information.  Is it taken directly from the

>

>  >

>

>  > browser's DOM?

>

>  >

>

>  > Regards,

>

>  >

>

>  > James Scholes

>

>  >

>

>  > On 10/06/2020 at 9:10 pm, Andy B. wrote:

>

>  >

>

>  >  > Hi,

>

>  >

>

>  >  >

>

>  >

>

>  >  > I am writing today to let you know that Developer toolkit, an NVDA

>

>  >

>

>  >  > add-on which assists with the user interface design experience for

>

>  >

>

>  >  > blind/visually impaired developers, has reached a major milestone

> in its

>

>  >

>

>  >  > development. For the first time in its history, users can gain

> access to

>

>  >

>

>  >  > the css and html of the focused object while developer toolkit mode is

>

>  >

>

>  >  > turned on.

>

>  >

>

>  >  >

>

>  >

>

>  >  > Once implemented, you can do the following:

>

>  >

>

>  >  >

>

>  >

>

>  >  >   * See positioning of the focused object. For example, absolute,

>

>  >

>

>  >  >     relative, and float.

>

>  >

>

>  >  >   * Determine the margins for each object.

>

>  >

>

>  >  >   * Find out how much padding each object contains.

>

>  >

>

>  >  >   * Find out the borders of an object if one is present.

>

>  >

>

>  >  >   * Find font/formatting information provided directly from the css.

>

>  >

>

>  >  >   * Determine if text or objects in a parent object are

>

>  >

>

>  >  >     vertical/horizontally aligned.

>

>  >

>

>  >  >   * Find the z-index of the focused object.

>

>  >

>

>  >  >   * Find out anything the style rule has defined for the focused

> object.

>

>  >

>

>  >  >   * Obtain the html source for the focused object.

>

>  >

>

>  >  >   * Explore and get suggestions on common color schemes such as

>

>  >

>

>  >  >     complementary, monochrome, analogous, triad, square, etc.

>

>  >

>

>  >  >   * Anything that having the css/html source will allow.

>

>  >

>

>  >  >

>

>  >

>

>  >  > Since this opens many more opportunities, it also demands more

> time and

>

>  >

>

>  >  > work. I would like to know how interested people are in obtaining

> a paid

>

>  >

>

>  >  > version once it is complete. The options are as follows:

>

>  >

>

>  >  >

>

>  >

>

>  >  >   * Offer a free NVDA add-on that does everything, and sell how-to

>

>  >

>

>  >  >     guides, training, and books.

>

>  >

>

>  >  >   * Offer a free edition and paid edition of the add-on, and sell

> how-to

>

>  >

>

>  >  >     guides, training, and books.

>

>  >

>

>  >  >

>

>  >

>

>  >  > Send your preferences and any concerns to ajborka@...

>

>  >

>

>  >  > <mailto:ajborka@...> as to not lock up the lists with unrelated

>

>  >

>

>  >  > content. Thanks for your time and consideration.

>

>  >

>

>  >  >

>

>  >

>

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

>

>  >

>

>  >  > Windows 10

>

>  >

>

>  >  >

>

>  >

>

>  >  >

>

>  >

>

>  >

>

>

 

 

 

Re: Developer toolkit reaches a new level

James Scholes
 

As far as I know, the only way to access a true representation of the DOM and accessibility tree (if web extensions have direct access to that) is to run your code inside the browser. I believe you've already realised this yourself through a lot of trial and error, trying to obtain the mark-up of an element from within NVDA. It just doesn't work.

So, my vote is that any accessibility-focused tools which need DOM access must run in the browser. If you want to expose an interface via an NVDA add-on, your browser extension can share information with a native process and vice-versa. But equally, if the UI was good, I would use an entirely in-browser version of DTK.

Regards,

James Scholes

On 11/06/2020 at 1:56 pm, Andy B. wrote:
Is this even worth putting into an NVDA add-on then? Why not have the add-on for desktop environments and a browser extension for web content? The only question then, is the layout of the browser extension’s output.
Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10
*From: *James Scholes <mailto:james@...>
*Sent: *Thursday, June 11, 2020 12:23 PM
*To: *nvda-addons@nvda-addons.groups.io <mailto:nvda-addons@nvda-addons.groups.io>
*Subject: *Re: [nvda-addons] Developer toolkit reaches a new level
That explains how it parses the content, but not where it gets it from.
If your add-on downloads a copy of the web page and only uses
stylesheets or inline styles, that's not a true representation of the
DOM for a huge percentage of websites which rely on JavaScript.  It
won't work at all with SPAs, or websites which require a login.  And as
the web moves more towards web components and other dynamic techniques,
it will become increasingly less useful.
Now, if you were to write a web extension for the browser which could
communicate a true representation of DOM elements to your add-on via
IPC, that would be worth paying for.
Regards,
James Scholes
On 11/06/2020 at 11:19 am, Andy B. wrote:

> It uses the bs4 and tinycss libraries found in the pip repository.

>

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

> Windows 10

>

> *From: *James Scholes <mailto:james@...>

> *Sent: *Thursday, June 11, 2020 10:57 AM

> *To: *nvda-addons@nvda-addons.groups.io

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

> *Subject: *Re: [nvda-addons] Developer toolkit reaches a new level

>

> Before offering any sort of paid material, be that the add-on itself or

>

> supporting content, it would be good to know how the add-on is obtaining

>

> the mark-up and styling information.  Is it taken directly from the

>

> browser's DOM?

>

> Regards,

>

> James Scholes

>

> On 10/06/2020 at 9:10 pm, Andy B. wrote:

>

>  > Hi,

>

>  >

>

>  > I am writing today to let you know that Developer toolkit, an NVDA

>

>  > add-on which assists with the user interface design experience for

>

>  > blind/visually impaired developers, has reached a major milestone
in its

>

>  > development. For the first time in its history, users can gain
access to

>

>  > the css and html of the focused object while developer toolkit mode is

>

>  > turned on.

>

>  >

>

>  > Once implemented, you can do the following:

>

>  >

>

>  >   * See positioning of the focused object. For example, absolute,

>

>  >     relative, and float.

>

>  >   * Determine the margins for each object.

>

>  >   * Find out how much padding each object contains.

>

>  >   * Find out the borders of an object if one is present.

>

>  >   * Find font/formatting information provided directly from the css.

>

>  >   * Determine if text or objects in a parent object are

>

>  >     vertical/horizontally aligned.

>

>  >   * Find the z-index of the focused object.

>

>  >   * Find out anything the style rule has defined for the focused
object.

>

>  >   * Obtain the html source for the focused object.

>

>  >   * Explore and get suggestions on common color schemes such as

>

>  >     complementary, monochrome, analogous, triad, square, etc.

>

>  >   * Anything that having the css/html source will allow.

>

>  >

>

>  > Since this opens many more opportunities, it also demands more
time and

>

>  > work. I would like to know how interested people are in obtaining
a paid

>

>  > version once it is complete. The options are as follows:

>

>  >

>

>  >   * Offer a free NVDA add-on that does everything, and sell how-to

>

>  >     guides, training, and books.

>

>  >   * Offer a free edition and paid edition of the add-on, and sell
how-to

>

>  >     guides, training, and books.

>

>  >

>

>  > Send your preferences and any concerns to ajborka@...

>

>  > <mailto:ajborka@...> as to not lock up the lists with unrelated

>

>  > content. Thanks for your time and consideration.

>

>  >

>

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

>

>  > Windows 10

>

>  >

>

>  >

>

>

Re: Developer toolkit reaches a new level

Noelia Ruiz
 

Hello, since the conversation deals not just with the add-on but also
with related alternatives to analize how it maybe used or not, maybe
useful to share the Wave extension (focused on accessibility
evaluation, and in consequence in structure, contrast, etc):
https://wave.webaim.org/

Powered by WebAIM, it has an API which can be used purchasing credits.
Kind regards

2020-06-11 20:56 GMT+02:00, Andy B. <sonfire11@...>:

Is this even worth putting into an NVDA add-on then? Why not have the add-on
for desktop environments and a browser extension for web content? The only
question then, is the layout of the browser extension’s output.





Sent from Mail for Windows 10



From: James Scholes
Sent: Thursday, June 11, 2020 12:23 PM
To: nvda-addons@nvda-addons.groups.io
Subject: Re: [nvda-addons] Developer toolkit reaches a new level



That explains how it parses the content, but not where it gets it from.

If your add-on downloads a copy of the web page and only uses

stylesheets or inline styles, that's not a true representation of the

DOM for a huge percentage of websites which rely on JavaScript.  It

won't work at all with SPAs, or websites which require a login.  And as

the web moves more towards web components and other dynamic techniques,

it will become increasingly less useful.



Now, if you were to write a web extension for the browser which could

communicate a true representation of DOM elements to your add-on via

IPC, that would be worth paying for.



Regards,



James Scholes



On 11/06/2020 at 11:19 am, Andy B. wrote:

It uses the bs4 and tinycss libraries found in the pip repository.
Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for
Windows 10
*From: *James Scholes <mailto:james@...>
*Sent: *Thursday, June 11, 2020 10:57 AM
*To: *nvda-addons@nvda-addons.groups.io
<mailto:nvda-addons@nvda-addons.groups.io>
*Subject: *Re: [nvda-addons] Developer toolkit reaches a new level
Before offering any sort of paid material, be that the add-on itself or
supporting content, it would be good to know how the add-on is obtaining
the mark-up and styling information.  Is it taken directly from the
browser's DOM?
Regards,
James Scholes
On 10/06/2020 at 9:10 pm, Andy B. wrote:
  > Hi,
  >
  > I am writing today to let you know that Developer toolkit, an NVDA
  > add-on which assists with the user interface design experience for
  > blind/visually impaired developers, has reached a major milestone in
its
  > development. For the first time in its history, users can gain access
to
  > the css and html of the focused object while developer toolkit mode is
  > turned on.
  >
  > Once implemented, you can do the following:
  >
  >   * See positioning of the focused object. For example, absolute,
  >     relative, and float.
  >   * Determine the margins for each object.
  >   * Find out how much padding each object contains.
  >   * Find out the borders of an object if one is present.
  >   * Find font/formatting information provided directly from the css.
  >   * Determine if text or objects in a parent object are
  >     vertical/horizontally aligned.
  >   * Find the z-index of the focused object.
  >   * Find out anything the style rule has defined for the focused
object.
  >   * Obtain the html source for the focused object.
  >   * Explore and get suggestions on common color schemes such as
  >     complementary, monochrome, analogous, triad, square, etc.
  >   * Anything that having the css/html source will allow.
  >
  > Since this opens many more opportunities, it also demands more time and
  > work. I would like to know how interested people are in obtaining a
paid
  > version once it is complete. The options are as follows:
  >
  >   * Offer a free NVDA add-on that does everything, and sell how-to
  >     guides, training, and books.
  >   * Offer a free edition and paid edition of the add-on, and sell
how-to
  >     guides, training, and books.
  >
  > Send your preferences and any concerns to ajborka@...
  > <mailto:ajborka@...> as to not lock up the lists with unrelated
  > content. Thanks for your time and consideration.
  >
  > Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for
  > Windows 10
  >
  >






Re: Developer toolkit reaches a new level

Andy B.
 

Is this even worth putting into an NVDA add-on then? Why not have the add-on for desktop environments and a browser extension for web content? The only question then, is the layout of the browser extension’s output.

 

 

Sent from Mail for Windows 10

 

From: James Scholes
Sent: Thursday, June 11, 2020 12:23 PM
To: nvda-addons@nvda-addons.groups.io
Subject: Re: [nvda-addons] Developer toolkit reaches a new level

 

That explains how it parses the content, but not where it gets it from.

If your add-on downloads a copy of the web page and only uses

stylesheets or inline styles, that's not a true representation of the

DOM for a huge percentage of websites which rely on JavaScript.  It

won't work at all with SPAs, or websites which require a login.  And as

the web moves more towards web components and other dynamic techniques,

it will become increasingly less useful.

 

Now, if you were to write a web extension for the browser which could

communicate a true representation of DOM elements to your add-on via

IPC, that would be worth paying for.

 

Regards,

 

James Scholes

 

On 11/06/2020 at 11:19 am, Andy B. wrote:

> It uses the bs4 and tinycss libraries found in the pip repository.

>

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

> Windows 10

>

> *From: *James Scholes <mailto:james@...>

> *Sent: *Thursday, June 11, 2020 10:57 AM

> *To: *nvda-addons@nvda-addons.groups.io

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

> *Subject: *Re: [nvda-addons] Developer toolkit reaches a new level

>

> Before offering any sort of paid material, be that the add-on itself or

>

> supporting content, it would be good to know how the add-on is obtaining

>

> the mark-up and styling information.  Is it taken directly from the

>

> browser's DOM?

>

> Regards,

>

> James Scholes

>

> On 10/06/2020 at 9:10 pm, Andy B. wrote:

>

>  > Hi,

>

>  >

>

>  > I am writing today to let you know that Developer toolkit, an NVDA

>

>  > add-on which assists with the user interface design experience for

>

>  > blind/visually impaired developers, has reached a major milestone in its

>

>  > development. For the first time in its history, users can gain access to

>

>  > the css and html of the focused object while developer toolkit mode is

>

>  > turned on.

>

>  >

>

>  > Once implemented, you can do the following:

>

>  >

>

>  >   * See positioning of the focused object. For example, absolute,

>

>  >     relative, and float.

>

>  >   * Determine the margins for each object.

>

>  >   * Find out how much padding each object contains.

>

>  >   * Find out the borders of an object if one is present.

>

>  >   * Find font/formatting information provided directly from the css.

>

>  >   * Determine if text or objects in a parent object are

>

>  >     vertical/horizontally aligned.

>

>  >   * Find the z-index of the focused object.

>

>  >   * Find out anything the style rule has defined for the focused object.

>

>  >   * Obtain the html source for the focused object.

>

>  >   * Explore and get suggestions on common color schemes such as

>

>  >     complementary, monochrome, analogous, triad, square, etc.

>

>  >   * Anything that having the css/html source will allow.

>

>  >

>

>  > Since this opens many more opportunities, it also demands more time and

>

>  > work. I would like to know how interested people are in obtaining a paid

>

>  > version once it is complete. The options are as follows:

>

>  >

>

>  >   * Offer a free NVDA add-on that does everything, and sell how-to

>

>  >     guides, training, and books.

>

>  >   * Offer a free edition and paid edition of the add-on, and sell how-to

>

>  >     guides, training, and books.

>

>  >

>

>  > Send your preferences and any concerns to ajborka@...

>

>  > <mailto:ajborka@...> as to not lock up the lists with unrelated

>

>  > content. Thanks for your time and consideration.

>

>  >

>

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

>

>  > Windows 10

>

>  >

>

>  >

>

>

 

 

 

Re: Developer toolkit reaches a new level

Pawel Urbanski
 

I second James' point. Developers use Chrome or Firefox developer
tools for such inspection.
Accessibility of either is quite good, but making it much better or
optimized for a screen reader with some alternative way to review the
information would be something I would pay for...
If one wants to be into web development he or she, as James already
mentioned, must be aware that it is about React.js Angular or Vue for
that matter... Last but definitely not least about a good flow when it
comes to communication with other developers on the team...
Knowling a color of a button is useful in the grand scheme of things,
but the design of web sites and apps is much more nuance...
If I were considering some kind of career in the web area I would
focus on web performance optimization, backend and processes related
to devops, or accessibility in a pragmatic sense that is recently
gaining alot of attention.

On 11/06/2020, James Scholes <james@...> wrote:
That explains how it parses the content, but not where it gets it from.
If your add-on downloads a copy of the web page and only uses
stylesheets or inline styles, that's not a true representation of the
DOM for a huge percentage of websites which rely on JavaScript. It
won't work at all with SPAs, or websites which require a login. And as
the web moves more towards web components and other dynamic techniques,
it will become increasingly less useful.

Now, if you were to write a web extension for the browser which could
communicate a true representation of DOM elements to your add-on via
IPC, that would be worth paying for.

Regards,

James Scholes

On 11/06/2020 at 11:19 am, Andy B. wrote:
It uses the bs4 and tinycss libraries found in the pip repository.

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

*From: *James Scholes <mailto:james@...>
*Sent: *Thursday, June 11, 2020 10:57 AM
*To: *nvda-addons@nvda-addons.groups.io
<mailto:nvda-addons@nvda-addons.groups.io>
*Subject: *Re: [nvda-addons] Developer toolkit reaches a new level

Before offering any sort of paid material, be that the add-on itself or

supporting content, it would be good to know how the add-on is obtaining

the mark-up and styling information.  Is it taken directly from the

browser's DOM?

Regards,

James Scholes

On 10/06/2020 at 9:10 pm, Andy B. wrote:

> Hi,

>

> I am writing today to let you know that Developer toolkit, an NVDA

> add-on which assists with the user interface design experience for

> blind/visually impaired developers, has reached a major milestone in
its

> development. For the first time in its history, users can gain access
to

> the css and html of the focused object while developer toolkit mode is

> turned on.

>

> Once implemented, you can do the following:

>

>   * See positioning of the focused object. For example, absolute,

>     relative, and float.

>   * Determine the margins for each object.

>   * Find out how much padding each object contains.

>   * Find out the borders of an object if one is present.

>   * Find font/formatting information provided directly from the css.

>   * Determine if text or objects in a parent object are

>     vertical/horizontally aligned.

>   * Find the z-index of the focused object.

>   * Find out anything the style rule has defined for the focused
object.

>   * Obtain the html source for the focused object.

>   * Explore and get suggestions on common color schemes such as

>     complementary, monochrome, analogous, triad, square, etc.

>   * Anything that having the css/html source will allow.

>

> Since this opens many more opportunities, it also demands more time
and

> work. I would like to know how interested people are in obtaining a
paid

> version once it is complete. The options are as follows:

>

>   * Offer a free NVDA add-on that does everything, and sell how-to

>     guides, training, and books.

>   * Offer a free edition and paid edition of the add-on, and sell
how-to

>     guides, training, and books.

>

> Send your preferences and any concerns to ajborka@...

> <mailto:ajborka@...> as to not lock up the lists with unrelated

> content. Thanks for your time and consideration.

>

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

> Windows 10

>

>



Re: Developer toolkit reaches a new level

James Scholes
 

That explains how it parses the content, but not where it gets it from. If your add-on downloads a copy of the web page and only uses stylesheets or inline styles, that's not a true representation of the DOM for a huge percentage of websites which rely on JavaScript. It won't work at all with SPAs, or websites which require a login. And as the web moves more towards web components and other dynamic techniques, it will become increasingly less useful.

Now, if you were to write a web extension for the browser which could communicate a true representation of DOM elements to your add-on via IPC, that would be worth paying for.

Regards,

James Scholes

On 11/06/2020 at 11:19 am, Andy B. wrote:
It uses the bs4 and tinycss libraries found in the pip repository.
Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10
*From: *James Scholes <mailto:james@...>
*Sent: *Thursday, June 11, 2020 10:57 AM
*To: *nvda-addons@nvda-addons.groups.io <mailto:nvda-addons@nvda-addons.groups.io>
*Subject: *Re: [nvda-addons] Developer toolkit reaches a new level
Before offering any sort of paid material, be that the add-on itself or
supporting content, it would be good to know how the add-on is obtaining
the mark-up and styling information.  Is it taken directly from the
browser's DOM?
Regards,
James Scholes
On 10/06/2020 at 9:10 pm, Andy B. wrote:

> Hi,

>

> I am writing today to let you know that Developer toolkit, an NVDA

> add-on which assists with the user interface design experience for

> blind/visually impaired developers, has reached a major milestone in its

> development. For the first time in its history, users can gain access to

> the css and html of the focused object while developer toolkit mode is

> turned on.

>

> Once implemented, you can do the following:

>

>   * See positioning of the focused object. For example, absolute,

>     relative, and float.

>   * Determine the margins for each object.

>   * Find out how much padding each object contains.

>   * Find out the borders of an object if one is present.

>   * Find font/formatting information provided directly from the css.

>   * Determine if text or objects in a parent object are

>     vertical/horizontally aligned.

>   * Find the z-index of the focused object.

>   * Find out anything the style rule has defined for the focused object.

>   * Obtain the html source for the focused object.

>   * Explore and get suggestions on common color schemes such as

>     complementary, monochrome, analogous, triad, square, etc.

>   * Anything that having the css/html source will allow.

>

> Since this opens many more opportunities, it also demands more time and

> work. I would like to know how interested people are in obtaining a paid

> version once it is complete. The options are as follows:

>

>   * Offer a free NVDA add-on that does everything, and sell how-to

>     guides, training, and books.

>   * Offer a free edition and paid edition of the add-on, and sell how-to

>     guides, training, and books.

>

> Send your preferences and any concerns to ajborka@...

> <mailto:ajborka@...> as to not lock up the lists with unrelated

> content. Thanks for your time and consideration.

>

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

> Windows 10

>

>

Re: Developer toolkit reaches a new level

Andy B.
 

It uses the bs4 and tinycss libraries found in the pip repository.

 

Sent from Mail for Windows 10

 

From: James Scholes
Sent: Thursday, June 11, 2020 10:57 AM
To: nvda-addons@nvda-addons.groups.io
Subject: Re: [nvda-addons] Developer toolkit reaches a new level

 

Before offering any sort of paid material, be that the add-on itself or

supporting content, it would be good to know how the add-on is obtaining

the mark-up and styling information.  Is it taken directly from the

browser's DOM?

 

Regards,

 

James Scholes

 

On 10/06/2020 at 9:10 pm, Andy B. wrote:

> Hi,

>

> I am writing today to let you know that Developer toolkit, an NVDA

> add-on which assists with the user interface design experience for

> blind/visually impaired developers, has reached a major milestone in its

> development. For the first time in its history, users can gain access to

> the css and html of the focused object while developer toolkit mode is

> turned on.

>

> Once implemented, you can do the following:

>

>   * See positioning of the focused object. For example, absolute,

>     relative, and float.

>   * Determine the margins for each object.

>   * Find out how much padding each object contains.

>   * Find out the borders of an object if one is present.

>   * Find font/formatting information provided directly from the css.

>   * Determine if text or objects in a parent object are

>     vertical/horizontally aligned.

>   * Find the z-index of the focused object.

>   * Find out anything the style rule has defined for the focused object.

>   * Obtain the html source for the focused object.

>   * Explore and get suggestions on common color schemes such as

>     complementary, monochrome, analogous, triad, square, etc.

>   * Anything that having the css/html source will allow.

>

> Since this opens many more opportunities, it also demands more time and

> work. I would like to know how interested people are in obtaining a paid

> version once it is complete. The options are as follows:

>

>   * Offer a free NVDA add-on that does everything, and sell how-to

>     guides, training, and books.

>   * Offer a free edition and paid edition of the add-on, and sell how-to

>     guides, training, and books.

>

> Send your preferences and any concerns to ajborka@...

> <mailto:ajborka@...> as to not lock up the lists with unrelated

> content. Thanks for your time and consideration.

>

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

> Windows 10

>

>

 

 

 

Re: Developer toolkit reaches a new level

James Scholes
 

Before offering any sort of paid material, be that the add-on itself or supporting content, it would be good to know how the add-on is obtaining the mark-up and styling information. Is it taken directly from the browser's DOM?

Regards,

James Scholes

On 10/06/2020 at 9:10 pm, Andy B. wrote:
Hi,
I am writing today to let you know that Developer toolkit, an NVDA add-on which assists with the user interface design experience for blind/visually impaired developers, has reached a major milestone in its development. For the first time in its history, users can gain access to the css and html of the focused object while developer toolkit mode is turned on.
Once implemented, you can do the following:
* See positioning of the focused object. For example, absolute,
relative, and float.
* Determine the margins for each object.
* Find out how much padding each object contains.
* Find out the borders of an object if one is present.
* Find font/formatting information provided directly from the css.
* Determine if text or objects in a parent object are
vertical/horizontally aligned.
* Find the z-index of the focused object.
* Find out anything the style rule has defined for the focused object.
* Obtain the html source for the focused object.
* Explore and get suggestions on common color schemes such as
complementary, monochrome, analogous, triad, square, etc.
* Anything that having the css/html source will allow.
Since this opens many more opportunities, it also demands more time and work. I would like to know how interested people are in obtaining a paid version once it is complete. The options are as follows:
* Offer a free NVDA add-on that does everything, and sell how-to
guides, training, and books.
* Offer a free edition and paid edition of the add-on, and sell how-to
guides, training, and books.
Send your preferences and any concerns to ajborka@... <mailto:ajborka@...> as to not lock up the lists with unrelated content. Thanks for your time and consideration.
Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10

Developer toolkit reaches a new level

Andy B.
 

Hi,

 

I am writing today to let you know that Developer toolkit, an NVDA add-on which assists with the user interface design experience for blind/visually impaired developers, has reached a major milestone in its development. For the first time in its history, users can gain access to the css and html of the focused object while developer toolkit mode is turned on.

Once implemented, you can do the following:

 

  • See positioning of the focused object. For example, absolute, relative, and float.
  • Determine the margins for each object.
  • Find out how much padding each object contains.
  • Find out the borders of an object if one is present.
  • Find font/formatting information provided directly from the css.
  • Determine if text or objects in a parent object are vertical/horizontally aligned.
  • Find the z-index of the focused object.
  • Find out anything the style rule has defined for the focused object.
  • Obtain the html source for the focused object.
  • Explore and get suggestions on common color schemes such as complementary, monochrome, analogous, triad, square, etc.
  • Anything that having the css/html source will allow.

 

Since this opens many more opportunities, it also demands more time and work. I would like to know how interested people are in obtaining a paid version once it is complete. The options are as follows:

 

  • Offer a free NVDA add-on that does everything, and sell how-to guides, training, and books.
  • Offer a free edition and paid edition of the add-on, and sell how-to guides, training, and books.

Send your preferences and any concerns to ajborka@... as to not lock up the lists with unrelated content. Thanks for your time and consideration.

 

Sent from Mail for Windows 10

 

Re: Python dependencies in add-ons

Andy B.
 

Hi,

 

After sorting out the problem, I came up with the following that works to this point.

 

  • Grab the addon’s path from addon.path property.
  • Append ‘\lib’ to the addon.path property.
  • insert the path above into the first position sys.path property
  • Make any needed imports such as html.parser, bs4, cssutils, etc.
  • Remove the sys.path[0] entry.
  • Continue coding as normal.

 

The added benefit is the ability to start an NVDA Python terminal and still have access to the custom 3rd party libraries. I could still access bs4 and html.parser with import statements, even when the path is removed. Will do more testing later tonight/tomorrow though.

 

Sent from Mail for Windows 10

 

From: James Scholes
Sent: Tuesday, June 9, 2020 1:45 PM
To: nvda-addons@nvda-addons.groups.io
Subject: Re: [nvda-addons] Python dependencies in add-ons

 

First, as others have suggested, you should be inserting any new paths

at the beginning of sys.path, not appending them.  Otherwise, whatever

is built into NVDA will get priority.

 

You can copy _markupbase.py from any Python 3.x installation; it's

located inside the lib folder.

 

Regards,

 

James Scholes

 

On 09/06/2020 at 10:37 am, Andy B. wrote:

> At this point, ideal isn’t an option, and I am ready to accept that

> fact. There isn’t a problem with importing html/xml into my addon.

> However, attempting to import html.parser violates the relative imports

> rule set in Python 3, or least I believe it is a relative imports

> problem. When I copy the html library found in python3 install path/lib

> into my addon, then include the following code at the top of the

> __init__.py file, I get an error in the log saying ‘import error: no

> module by the name html.parser found’.

>

> Sample code:

>

> import os

>

> import sys

>

> addonNamePath = os.path.abspath(os.path.dirname(__file__)) #addon folder

> path

>

> sys.path.append(addonNamePath)

>

> import html.parser

>

> del sys.path[-1]

>

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

> Windows 10

>

> *From: *James Scholes <mailto:james@...>

> *Sent: *Tuesday, June 9, 2020 11:19 AM

> *To: *nvda-addons@nvda-addons.groups.io

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

> *Subject: *Re: [nvda-addons] Python dependencies in add-ons

>

>  > Using NVDA’s version of html and xml breaks the imported libraries

>

> that require html.parser or xml.parser. On the other hand, using the

>

> original Python provided versions breaks NVDA.

>

> Breaks NVDA in what way?  If you include a full version of html and xml

>

> in your add-on, modify sys.path appropriately, import bs4 or whatever

>

> and then remove your path modifications, I don't understand why there

>

> would be a conflict?  I understand that the setup is not ideal, but not

>

> why it would break NVDA.

>

> Regards,

>

> James Scholes

>

> On 08/06/2020 at 1:41 pm, Andy B. wrote:

>

>  > Hi,

>

>  >

>

>  > This generally works. However, it has one major problem that NVDA won’t

>

>  > allow add-on authors to overcome. If a dependency requires

>

>  > modules/libraries that NVDA removed from the standard Python library,

>

>  > all of the included Python libraries that attempt to import such removed

>

>  > libraries will fail. For example, trying to import bs4, lxml, or

>

>  > cssutils will terminally fail because NVDA removed html.parser and

>

>  > xml.parser from the standard library while maintaining the rest of the

>

>  > html and xml modules. Attempting to reimport the original html or xml

>

>  > standard Python libraries into an add-on also fails because it will

>

>  > cause a namespace conflict with the NVDA provided html and xml

>

>  > libraries. As a result, either one can exist, but not both. I attempted

>

>  > this and was forced to choose from a few different options:

>

>  >

>

>  >   * Use NVDA’s version of html and xml with parsers removed.

>

>  >   * Use my version of html or xml and ignore NVDA’s version.

>

>  >   * Rename the original html or xml standard Python libraries and manage

>

>  >     3^rd party dependencies myself.

>

>  >   * Give up and consider it a lost cause.

>

>  >

>

>  > I took the last option: give up because it is a lost cause. Using NVDA’s

>

>  > version of html and xml breaks the imported libraries that require

>

>  > html.parser or xml.parser. On the other hand, using the original Python

>

>  > provided versions breaks NVDA. Renaming the originals to something

>

>  > different seems like a ton of unwanted work because I would have to

>

>  > trudge through all the bs4/cssutils/lxml code and rename html.parser to

>

>  > something else, and after all of that, we can’t be sure it will work. If

>

>  > someone has a fix or workaround for this problem, I am all ears. It

>

>  > would bring a whole new level to my add-on.

>

>  >

>

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

>

>  > Windows 10

>

>  >

>

>  > *From: *Sean <mailto:s.tolstoyevski@...>

>

>  > *Sent: *Monday, June 8, 2020 1:40 PM

>

>  > *To: *nvda-addons@nvda-addons.groups.io

>

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

>

>  > *Subject: *Re: [nvda-addons] Python dependencies in add-ons

>

>  >

>

>  > example code:

>

>  >

>

>  > addonNamePathxX = os.path.abspath(os.path.dirname(__file__)) ^ #addon

>

>  > folder path

>

>  > sys.path.append(addonNamePathX)

>

>  >

>

>  > import numpy

>

>  >

>

>  > import opencv #example modules, Not available in NVDA.

>

>  >

>

>  > del sys.path[-1]

>

>  >

>

>  > ......

>

>  >

>

>  > #content code

>

>  >

>

>  > On 08/06/2020 20:33, Sean via groups.io wrote:

>

>  >

>

>  >     Hi  Subham,

>

>  >

>

>  >     I think your work will be a revolutionary thing.

>

>  >     Because screen readers have been working with the same logic for 20

>

>  >     years.

>

>  >     Good luck.

>

>  >

>

>  >     There is no separate tool to manage the dependencies of NVDA addons.

>

>  >

>

>  >     In addon's __init__.py file, the path of the modules is added with

>

>  >     sys.path.append.

>

>  >     Addon  writers often use this.

>

>  >

>

>  >     One thing I want to add is;

>

>  >     All required modules should be in the same folder.

>

>  >

>

>  >     You can write C ++ codes to Python with a tool like Cython.

>

>  >     Or the code section written in C ++ can be compiled as a DLL.

>

>  >     In this way, we can use the functions of the DLL with Ctypes.

>

>  >     Ctypes is more commonly used in NVDA source.

>

>  >

>

>  >     On 08/06/2020 14:19, Shubham Jain wrote:

>

>  >

>

>  >         Hello!

>

>  >

>

>  >         As part of my GSoC project

>

>  >        

> <https://summerofcode.withgoogle.com/projects/#6039693356957696>, I

>

>  >         am writing an add-on that allows users to get descriptions of

>

>  >         images. To work, the ML models depend on some python libraries

>

>  >         like Numpy, Pillow, onnxruntime and OpenCv. My questions are:

>

>  >

>

>  >           * Is it possible to package these libraries in an add-on?

>

>  >           * Since I only require a few specific functions from these

>

>  >             libraries, is it possible to only package those parts into

>

>  >             the add-on?

>

>  >

>

>  >

>

>  >         Alternatively, the models could be converted to run using native

>

>  >         C++ by depending on the LibTorch library. Is it possible to

>

>  >         write add-ons in native C++?

>

>  >

>

>  >         *regards,*

>

>  >         *Shubham Jain*

>

>  >

>

>  >     --

>

>  >

>

>  >

>

>  >         Sean

>

>  >

>

>  >       * Email: seantolstoyevski@...

>

>  >         <mailto:seantolstoyevski@...>

>

>  >       * GitHub: SeanTolstoyevski <https://github.com/SeanTolstoyevski/>

>

>  >

>

>  >     👨‍🦯 I’m student and programmer. I write often Python, sometimes Go

>

>  >     and rarely C++.

>

>  >

>

>  > --

>

>  >

>

>  >

>

>  >     Sean

>

>  >

>

>  >   * Email: seantolstoyevski@...

>

>  >     <mailto:seantolstoyevski@...>

>

>  >   * GitHub: SeanTolstoyevski <https://github.com/SeanTolstoyevski/>

>

>  >

>

>  > 👨‍🦯I’m student and programmer. I write often Python, sometimes Go and

>

>  > rarely C++.

>

>  >

>

>  >

>

>

 

 

 

Re: Python dependencies in add-ons

James Scholes
 

First, as others have suggested, you should be inserting any new paths at the beginning of sys.path, not appending them. Otherwise, whatever is built into NVDA will get priority.

You can copy _markupbase.py from any Python 3.x installation; it's located inside the lib folder.

Regards,

James Scholes

On 09/06/2020 at 10:37 am, Andy B. wrote:
At this point, ideal isn’t an option, and I am ready to accept that fact. There isn’t a problem with importing html/xml into my addon. However, attempting to import html.parser violates the relative imports rule set in Python 3, or least I believe it is a relative imports problem. When I copy the html library found in python3 install path/lib into my addon, then include the following code at the top of the __init__.py file, I get an error in the log saying ‘import error: no module by the name html.parser found’.
Sample code:
import os
import sys
addonNamePath = os.path.abspath(os.path.dirname(__file__)) #addon folder path
sys.path.append(addonNamePath)
import html.parser
del sys.path[-1]
Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10
*From: *James Scholes <mailto:james@...>
*Sent: *Tuesday, June 9, 2020 11:19 AM
*To: *nvda-addons@nvda-addons.groups.io <mailto:nvda-addons@nvda-addons.groups.io>
*Subject: *Re: [nvda-addons] Python dependencies in add-ons

> Using NVDA’s version of html and xml breaks the imported libraries
that require html.parser or xml.parser. On the other hand, using the
original Python provided versions breaks NVDA.
Breaks NVDA in what way?  If you include a full version of html and xml
in your add-on, modify sys.path appropriately, import bs4 or whatever
and then remove your path modifications, I don't understand why there
would be a conflict?  I understand that the setup is not ideal, but not
why it would break NVDA.
Regards,
James Scholes
On 08/06/2020 at 1:41 pm, Andy B. wrote:

> Hi,

>

> This generally works. However, it has one major problem that NVDA won’t

> allow add-on authors to overcome. If a dependency requires

> modules/libraries that NVDA removed from the standard Python library,

> all of the included Python libraries that attempt to import such removed

> libraries will fail. For example, trying to import bs4, lxml, or

> cssutils will terminally fail because NVDA removed html.parser and

> xml.parser from the standard library while maintaining the rest of the

> html and xml modules. Attempting to reimport the original html or xml

> standard Python libraries into an add-on also fails because it will

> cause a namespace conflict with the NVDA provided html and xml

> libraries. As a result, either one can exist, but not both. I attempted

> this and was forced to choose from a few different options:

>

>   * Use NVDA’s version of html and xml with parsers removed.

>   * Use my version of html or xml and ignore NVDA’s version.

>   * Rename the original html or xml standard Python libraries and manage

>     3^rd party dependencies myself.

>   * Give up and consider it a lost cause.

>

> I took the last option: give up because it is a lost cause. Using NVDA’s

> version of html and xml breaks the imported libraries that require

> html.parser or xml.parser. On the other hand, using the original Python

> provided versions breaks NVDA. Renaming the originals to something

> different seems like a ton of unwanted work because I would have to

> trudge through all the bs4/cssutils/lxml code and rename html.parser to

> something else, and after all of that, we can’t be sure it will work. If

> someone has a fix or workaround for this problem, I am all ears. It

> would bring a whole new level to my add-on.

>

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

> Windows 10

>

> *From: *Sean <mailto:s.tolstoyevski@...>

> *Sent: *Monday, June 8, 2020 1:40 PM

> *To: *nvda-addons@nvda-addons.groups.io

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

> *Subject: *Re: [nvda-addons] Python dependencies in add-ons

>

> example code:

>

> addonNamePathxX = os.path.abspath(os.path.dirname(__file__)) ^ #addon

> folder path

> sys.path.append(addonNamePathX)

>

> import numpy

>

> import opencv #example modules, Not available in NVDA.

>

> del sys.path[-1]

>

> ......

>

> #content code

>

> On 08/06/2020 20:33, Sean via groups.io wrote:

>

>     Hi  Subham,

>

>     I think your work will be a revolutionary thing.

>     Because screen readers have been working with the same logic for 20

>     years.

>     Good luck.

>

>     There is no separate tool to manage the dependencies of NVDA addons.

>

>     In addon's __init__.py file, the path of the modules is added with

>     sys.path.append.

>     Addon  writers often use this.

>

>     One thing I want to add is;

>     All required modules should be in the same folder.

>

>     You can write C ++ codes to Python with a tool like Cython.

>     Or the code section written in C ++ can be compiled as a DLL.

>     In this way, we can use the functions of the DLL with Ctypes.

>     Ctypes is more commonly used in NVDA source.

>

>     On 08/06/2020 14:19, Shubham Jain wrote:

>

>         Hello!

>

>         As part of my GSoC project

>
<https://summerofcode.withgoogle.com/projects/#6039693356957696>, I

>         am writing an add-on that allows users to get descriptions of

>         images. To work, the ML models depend on some python libraries

>         like Numpy, Pillow, onnxruntime and OpenCv. My questions are:

>

>           * Is it possible to package these libraries in an add-on?

>           * Since I only require a few specific functions from these

>             libraries, is it possible to only package those parts into

>             the add-on?

>

>

>         Alternatively, the models could be converted to run using native

>         C++ by depending on the LibTorch library. Is it possible to

>         write add-ons in native C++?

>

>         *regards,*

>         *Shubham Jain*

>

>     --

>

>

>         Sean

>

>       * Email: seantolstoyevski@...

>         <mailto:seantolstoyevski@...>

>       * GitHub: SeanTolstoyevski <https://github.com/SeanTolstoyevski/>

>

>     👨‍🦯 I’m student and programmer. I write often Python, sometimes Go

>     and rarely C++.

>

> --

>

>

>     Sean

>

>   * Email: seantolstoyevski@...

>     <mailto:seantolstoyevski@...>

>   * GitHub: SeanTolstoyevski <https://github.com/SeanTolstoyevski/>

>

> 👨‍🦯I’m student and programmer. I write often Python, sometimes Go and

> rarely C++.

>

>

Re: Python dependencies in add-ons

Andy B.
 

Hi,

 

I was able to import html.parser. Unfortunately, I receive an error: import error: no such module _markupbase. Further exploration of the topic concludes that _markupbase is a CPython module in the standard library. Unfortunately, NVDA also removed it as part of the size requirement issue. Thus, it appears that anything using markup of any sort will fail. Lxml, html.parser, bs4, cssutils, tinycss, etc. Any ideas how to get _markupbase in my addon?

 

 

Sent from Mail for Windows 10

 

From: Alberto Buffolino
Sent: Tuesday, June 9, 2020 11:44 AM
To: nvda-addons@nvda-addons.groups.io
Subject: Re: [nvda-addons] Python dependencies in add-ons

 

Andy B., il 09/06/2020 17.29, ha scritto:

> When I attempt to import a second

> copy of html library that contains parser, NVDA will either load my copy

> or its own copy, but not both.

Alberto:

Hi Andy,

I'm not sure, but have you tried to follow recomendation to put module

folder under a "lib" directory in add-on root (where manifest.ini is

located), instead of under globalPlugins?

It could avoid this problem, maybe...

Alberto

 

 

 

Re: how to build a settings panel with advanced options?

Noelia Ruiz
 

I think that the strategy of this class can be sumarized as follows:

1. Create a class (optional) to manage easily multiple controls
instead of managing each one. This is AdvancedPanelControls.

2. Create the main class AdvancedPanel and add the first class, after
other controls, in makesettings method.
3 Use this line to decide if the first class, that is, its controls,
will be enabled:
self.advancedControls.Enable(self.enableControlsCheckBox.IsChecked())



If self.enableControlsCheckBox.IsChecked(), then the controls will be
enabled, otherwise there will be disabled
Enable accepts as a parameter a boolean, which is True or False
deppending on the state of the checkbox.
Hope this helps.

2020-06-09 16:13 GMT+02:00, Christopher Pross <chpross42@...>:

Hi,

how I could easiely build a settingspanel, where some settings are
hidden until the user hits a button or a checkbox?

Like the advanced settings in nvda?

I read already the source code of the class, but don't understand the
main strategy.






Re: Creating an add-on for Transmission QT Client to make it accessible

Dickson Tan
 

Hey,


Anyone has any ideas on how any of these issues could be worked around?

On 5/6/2020 12:21 am, Dickson Tan wrote:
Hi,

I've been trying to find a BitTorrent client that would work well with NVDA. I really like Transmission especially because it works well on Docker, and you can use the desktop version for Windows to remotely control another instance of Transmission.

It almost works completely with NVDA but there a few issues I'd like to fix. It is using QT 5 and is exposed as UIA. Any advice about how to fix these would be great.

1. Certain dialogs that appear automatically such as the one for selecting options when opening a torrent [don't gain keyboard focus,](https://github.com/transmission/transmission/issues/1286). I couldn't find any other way of getting the keyboard focus inside them besides using the mouse. Is there any way of "watching out" for these things appearing on screen and forcing keyboard focus inside?
2. When tabbing to the list of downloads, NVDA doesn't seem to recognize that the sole item in the list has gained focus. This does work when there is more than one item if you press down or up to make a new item in the list gain focus. Is it possible to hook into the alt+tab behaviour?
3. This is probably going to be the toughest one. The list of downloads actually has additional info displayed below the name such as size, amount uploaded etc, [none of which appears in object navigation or can be found by NVDA](https://github.com/transmission/transmission/issues/1285). Object nav does find the list as a list of items, but each list item only contains the name. Screen review shows nothing at all. OCR does work pretty well though so I'm wondering if that's something that could be exploited. I rmeembered there's a way of getting the display text from coordinates, is that what screen review uses internally?
4. Some fields don't have any labels associated with them. If this were a web application, I'd write a greasemonkey script to apply the right label using reliable selectors. In NVDA which attributes are typically used as indentifiers to latch onto?
5. In the file selection list of the open torrent dialog:
    * It is a tree as well as a table. NVDA isn't able to detect if the item is checked or unchecked, collapsed or expanded, or level in the tree.
    * NVDA reads the file name of each individual file. You can get to the other columns of the table with object nav. I'm wondering if there's a way of having NVDA read the whole row out automatically, kind of what you see in Windows explorer or the list in Utorrent. Or alternatively to have right / left arrows let you move by column.