Announcement: NVDA Add-on Store is under development, NV Access folks are seeking feedback


 

Hello NVDA community,

The following notice is really meant for resident developers and early adopters (power users included) as it discusses prerelease software:

For some time various communities hosted add-ons metadata and produced add-ons to browse and download add-ons. These include NVDA Store from French community, Tienda the Spanish community NVDA Store, and of course, Add-on Updater (not a store but an update client). Recently NV Access has shown interest in creating a central repository of add-ons and a store feature so users can browse, install, and update add-ons directly from NVDA without relying on store add-ons.

After months of design and gathering early feedback, NV Access staff has published a pull request to let folks try it and give feedback:

Addon store by feerrenrut · Pull Request #13985 · nvaccess/nvda (github.com)

 

IMPORTANT: this is a pull request, a place to comment on design and direction of a new feature, change, or a bug fix. As Add-on Store is in early development, things can change without notice. Therefore, only developers and early adopters (especially add-on authors) are asked to provide feedback for now, either by commenting on the pull request itself or sending an email to info@... after trying out the linked pull request.

 

A note for Add-on Updater users: as I promised years ago, once NVDA gains ability to update add-ons by itself, Add-on Updater will be discontinued. I’ll talk more about the “end game” once the linked pull request is integrated into NVDA in the future.

Cheers,

Joseph


Devin Prater
 

This is really great. I'd been seeing Github notifications about this. Are there designs to allow users to import repositories from other stores, like Spanish-only addons from a repo, stuff like that? Or will they all just be in one big list?
Devin Prater




On Fri, Aug 5, 2022 at 7:46 AM Joseph Lee <joseph.lee22590@...> wrote:

Hello NVDA community,

The following notice is really meant for resident developers and early adopters (power users included) as it discusses prerelease software:

For some time various communities hosted add-ons metadata and produced add-ons to browse and download add-ons. These include NVDA Store from French community, Tienda the Spanish community NVDA Store, and of course, Add-on Updater (not a store but an update client). Recently NV Access has shown interest in creating a central repository of add-ons and a store feature so users can browse, install, and update add-ons directly from NVDA without relying on store add-ons.

After months of design and gathering early feedback, NV Access staff has published a pull request to let folks try it and give feedback:

Addon store by feerrenrut · Pull Request #13985 · nvaccess/nvda (github.com)

 

IMPORTANT: this is a pull request, a place to comment on design and direction of a new feature, change, or a bug fix. As Add-on Store is in early development, things can change without notice. Therefore, only developers and early adopters (especially add-on authors) are asked to provide feedback for now, either by commenting on the pull request itself or sending an email to info@... after trying out the linked pull request.

 

A note for Add-on Updater users: as I promised years ago, once NVDA gains ability to update add-ons by itself, Add-on Updater will be discontinued. I’ll talk more about the “end game” once the linked pull request is integrated into NVDA in the future.

Cheers,

Joseph


 

Hi,

I think the latter as these repositories (including the NV Access add-ons datastore) use different formats to store add-on metadata. For example, the default repo Add-on Updater uses (community add-ons website with compatibility info from a second repository) store add-on information in a dictionary format, whereas Spanish community and NV Access datastore use a list to store data. Also, the backend (server side) is different - the new datastore from NV Access wants to know which NVDA release the user is using so it can display compatible add-ons, whereas other repositories simply return a JSON dump of the entire database. As a result, Add-on Updater (and other store clients) must parse add-ons metadata to see if there are compatible add-ons based on compatibility information recorded in the database, whereas with the new NV Access datastore, only add-ons compatible with the current release are returned so clients do not have to do any work.

Cheers,

Joseph


Devin Prater
 

Awesome, thanks!
Devin Prater




On Fri, Aug 5, 2022 at 8:21 AM Joseph Lee <joseph.lee22590@...> wrote:

Hi,

I think the latter as these repositories (including the NV Access add-ons datastore) use different formats to store add-on metadata. For example, the default repo Add-on Updater uses (community add-ons website with compatibility info from a second repository) store add-on information in a dictionary format, whereas Spanish community and NV Access datastore use a list to store data. Also, the backend (server side) is different - the new datastore from NV Access wants to know which NVDA release the user is using so it can display compatible add-ons, whereas other repositories simply return a JSON dump of the entire database. As a result, Add-on Updater (and other store clients) must parse add-ons metadata to see if there are compatible add-ons based on compatibility information recorded in the database, whereas with the new NV Access datastore, only add-ons compatible with the current release are returned so clients do not have to do any work.

Cheers,

Joseph


Afik Souffir
 

Hi Joseph,

Can you please tell how to download the client?

Thanks,

 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee
Sent: Friday, August 5, 2022 3:47 PM
To: nvda@nvda.groups.io
Subject: [nvda] Announcement: NVDA Add-on Store is under development, NV Access folks are seeking feedback

 

Hello NVDA community,

The following notice is really meant for resident developers and early adopters (power users included) as it discusses prerelease software:

For some time various communities hosted add-ons metadata and produced add-ons to browse and download add-ons. These include NVDA Store from French community, Tienda the Spanish community NVDA Store, and of course, Add-on Updater (not a store but an update client). Recently NV Access has shown interest in creating a central repository of add-ons and a store feature so users can browse, install, and update add-ons directly from NVDA without relying on store add-ons.

After months of design and gathering early feedback, NV Access staff has published a pull request to let folks try it and give feedback:

Addon store by feerrenrut · Pull Request #13985 · nvaccess/nvda (github.com)

 

IMPORTANT: this is a pull request, a place to comment on design and direction of a new feature, change, or a bug fix. As Add-on Store is in early development, things can change without notice. Therefore, only developers and early adopters (especially add-on authors) are asked to provide feedback for now, either by commenting on the pull request itself or sending an email to info@... after trying out the linked pull request.

 

A note for Add-on Updater users: as I promised years ago, once NVDA gains ability to update add-ons by itself, Add-on Updater will be discontinued. I’ll talk more about the “end game” once the linked pull request is integrated into NVDA in the future.

Cheers,

Joseph


Sarah k Alawami
 

This is just the update add on which you can get from the nvda add ons site.

 

Good luck.

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Afik Souffir
Sent: Friday, August 5, 2022 9:02 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Announcement: NVDA Add-on Store is under development, NV Access folks are seeking feedback

 

Hi Joseph,

Can you please tell how to download the client?

Thanks,

 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee
Sent: Friday, August 5, 2022 3:47 PM
To: nvda@nvda.groups.io
Subject: [nvda] Announcement: NVDA Add-on Store is under development, NV Access folks are seeking feedback

 

Hello NVDA community,

The following notice is really meant for resident developers and early adopters (power users included) as it discusses prerelease software:

For some time various communities hosted add-ons metadata and produced add-ons to browse and download add-ons. These include NVDA Store from French community, Tienda the Spanish community NVDA Store, and of course, Add-on Updater (not a store but an update client). Recently NV Access has shown interest in creating a central repository of add-ons and a store feature so users can browse, install, and update add-ons directly from NVDA without relying on store add-ons.

After months of design and gathering early feedback, NV Access staff has published a pull request to let folks try it and give feedback:

Addon store by feerrenrut · Pull Request #13985 · nvaccess/nvda (github.com)

 

IMPORTANT: this is a pull request, a place to comment on design and direction of a new feature, change, or a bug fix. As Add-on Store is in early development, things can change without notice. Therefore, only developers and early adopters (especially add-on authors) are asked to provide feedback for now, either by commenting on the pull request itself or sending an email to info@... after trying out the linked pull request.

 

A note for Add-on Updater users: as I promised years ago, once NVDA gains ability to update add-ons by itself, Add-on Updater will be discontinued. I’ll talk more about the “end game” once the linked pull request is integrated into NVDA in the future.

Cheers,

Joseph


Brian's Mail list account
 

I wrote this on the add ons list but will put it here also. One idea assuming current add ons have a contact for the creator would be to have it notify the author, say once a month if it is about to be broken by an nvda version.
Also will modifying your add ons yourself still be a valid way to carry on, whether it be merely trying it with changed manifest, or doing some simple tweaks of syntax?
Brian

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

----- Original Message -----
From: "Joseph Lee" <joseph.lee22590@...>
To: <nvda@nvda.groups.io>
Sent: Friday, August 05, 2022 1:46 PM
Subject: [nvda] Announcement: NVDA Add-on Store is under development, NV Access folks are seeking feedback


Hello NVDA community,

The following notice is really meant for resident developers and early
adopters (power users included) as it discusses prerelease software:

For some time various communities hosted add-ons metadata and produced
add-ons to browse and download add-ons. These include NVDA Store from French
community, Tienda the Spanish community NVDA Store, and of course, Add-on
Updater (not a store but an update client). Recently NV Access has shown
interest in creating a central repository of add-ons and a store feature so
users can browse, install, and update add-ons directly from NVDA without
relying on store add-ons.

After months of design and gathering early feedback, NV Access staff has
published a pull request to let folks try it and give feedback:

Addon store by feerrenrut <https://github.com/nvaccess/nvda/pull/13985> .
Pull Request #13985 . nvaccess/nvda (github.com)



IMPORTANT: this is a pull request, a place to comment on design and
direction of a new feature, change, or a bug fix. As Add-on Store is in
early development, things can change without notice. Therefore, only
developers and early adopters (especially add-on authors) are asked to
provide feedback for now, either by commenting on the pull request itself or
sending an email to info@... <mailto:info@...> after
trying out the linked pull request.



A note for Add-on Updater users: as I promised years ago, once NVDA gains
ability to update add-ons by itself, Add-on Updater will be discontinued.
I'll talk more about the "end game" once the linked pull request is
integrated into NVDA in the future.

Cheers,

Joseph


 

Hi,

Regarding contacting authors about compatibility breaking releases: this is quite uncertain as to when that can happen, and to whom the message should be sent. Specifically, we (add-on authors) don't know when the first beta of a compatibility breaking release will be published (we can guess but plans can change), and not all authors have an active email address or other forms of contact. What you are suggesting is a valid concern.

Cheers,

Joseph