how to get to the nvda add on store to find add ons you don't yet have installed


Mary Otten
 

I have add on updater, and I changed its source to be the nvda store. However, since I don't have any add ons but one other than the add on updater, and that one came from community add on site, how can I get to the nvda add on store, url perhaps? to get updates there and then subsequent updates will come through the add on updater.


Mary


 

Hi,

Add-on Updater does not let you browse add-on store - it will check for updates to add-ons you have already installed if they are available from add-on store or other source of your choosing. You still need to visit community add-ons website (addons.nvda-project.org), select the add-on you wish to install, download it, install it, restart NVDA, and check for add-on updates.

Cheers,

Joseph


Mary Otten
 

So if the add on on the community website has not been updated for the latest NVDA, it will not be able to be installed, as it is not compatible, yes? That's why I asked about how to get directly to that new add on store.


Mary


On 3/29/2023 12:41 PM, Joseph Lee wrote:

Hi,

Add-on Updater does not let you browse add-on store - it will check for updates to add-ons you have already installed if they are available from add-on store or other source of your choosing. You still need to visit community add-ons website (addons.nvda-project.org), select the add-on you wish to install, download it, install it, restart NVDA, and check for add-on updates.

Cheers,

Joseph


 

Hi,

There are two things going on:

  1. Incompatible add-ons: NVDA will prevent you from installing incompatible add-ons, and in this case, you still can't browse the add-on store directly from Add-on Updater.
  2. Compatible add-ons: right now the add-ons community are updating add-on download links to point to add-on store entries so you can download compatble add-on releases.

Cheers,

Joseph


Gerardo Corripio
 

Or you could always install the "Tienda" add-on, a sort of NVDA Store in the meantime. This will let you not only browse, but also update add-ons.

Gera
Enviado desde mi iPhone SE (2nd Generation) de Telcel

El 29 mar 2023, a la(s) 1:52 p.m., Mary Otten <maryotten@...> escribió:



So if the add on on the community website has not been updated for the latest NVDA, it will not be able to be installed, as it is not compatible, yes? That's why I asked about how to get directly to that new add on store.


Mary


On 3/29/2023 12:41 PM, Joseph Lee wrote:

Hi,

Add-on Updater does not let you browse add-on store - it will check for updates to add-ons you have already installed if they are available from add-on store or other source of your choosing. You still need to visit community add-ons website (addons.nvda-project.org), select the add-on you wish to install, download it, install it, restart NVDA, and check for add-on updates.

Cheers,

Joseph


Kenny Cheung
 

Wouldn’t it be easier to have all add-ons in the store to download and install also   to update?
Sent from Kenny’s MacBook Pro

On Mar 29, 2023, at 17:11, Gerardo Corripio <gera1027@...> wrote:

Or you could always install the "Tienda" add-on, a sort of NVDA Store in the meantime. This will let you not only browse, but also update add-ons.

Gera
Enviado desde mi iPhone SE (2nd Generation) de Telcel

El 29 mar 2023, a la(s) 1:52 p.m., Mary Otten <maryotten@...> escribió:



So if the add on on the community website has not been updated for the latest NVDA, it will not be able to be installed, as it is not compatible, yes? That's why I asked about how to get directly to that new add on store.


Mary


On 3/29/2023 12:41 PM, Joseph Lee wrote:

Hi,

Add-on Updater does not let you browse add-on store - it will check for updates to add-ons you have already installed if they are available from add-on store or other source of your choosing. You still need to visit community add-ons website (addons.nvda-project.org), select the add-on you wish to install, download it, install it, restart NVDA, and check for add-on updates.

Cheers,

Joseph



Mary Otten
 

Thank you, Joseph for that clarification. You may well have said that earlier, and I just missed it in the many messages around this entire topic.


Mary


On 3/29/2023 2:06 PM, Joseph Lee wrote:

Hi,

There are two things going on:

  1. Incompatible add-ons: NVDA will prevent you from installing incompatible add-ons, and in this case, you still can't browse the add-on store directly from Add-on Updater.
  2. Compatible add-ons: right now the add-ons community are updating add-on download links to point to add-on store entries so you can download compatble add-on releases.

Cheers,

Joseph


Ryan Mann
 

Is the plan to be able to search the addon store directly in the future?

Ryan Mann
Certified Assistive Technology Instructional Specialist
rmann0581@...
386-383-5175


On Mar 29, 2023, at 3:42 PM, Joseph Lee <joseph.lee22590@...> wrote:



Hi,

Add-on Updater does not let you browse add-on store - it will check for updates to add-ons you have already installed if they are available from add-on store or other source of your choosing. You still need to visit community add-ons website (addons.nvda-project.org), select the add-on you wish to install, download it, install it, restart NVDA, and check for add-on updates.

Cheers,

Joseph


Rui Fontes
 

Hi Joseph!


You wrote:

2. Compatible add-ons: right now the add-ons community are updating add-on download links to point to add-on store entries so you can download compatble add-on releases.


Yah, but that do not answer everything...

How to find, by instance, NVDARecorder already in NVDA add-on store?

It is available there, but no way to look for it...


I think it was that problem Mary would like to solve...

Maybe pointing to the list Noelia have?

https://nvdaes.github.io/nvdastore/


It is not the best, but have all add-ons included in the NVDA add-on store...


Best regards,

Rui Fontes
NVDA portuguese team


 

Hi,

Another option is getting NVDA Recorder and other add-ons registered on community add-ons website to improve discoverability. We might as well invite authors of add-ons hosted on Spanish community catalog to bring their add-on documentation to community add-ons website to help others discover theri wonderful work.

As for searching the ad-on store in the future, I hope so perhaps through NVDA (not via Add-on Updater at the moment as I am ready to declare a feature freeze on that add-on and I will be suspending add-ons work until late April; school takes priority).

Cheers,

Joseph


Rui Fontes
 

Why authors should submit add-ons to two repositories?


Best regards,

Rui Fontes
NVDA portuguese team


Às 00:15 de 30/03/2023, Joseph Lee escreveu:

Hi,

Another option is getting NVDA Recorder and other add-ons registered on community add-ons website to improve discoverability. We might as well invite authors of add-ons hosted on Spanish community catalog to bring their add-on documentation to community add-ons website to help others discover theri wonderful work.

As for searching the ad-on store in the future, I hope so perhaps through NVDA (not via Add-on Updater at the moment as I am ready to declare a feature freeze on that add-on and I will be suspending add-ons work until late April; school takes priority).

Cheers,

Joseph





Mary Otten
 

I am certainly not Joseph. But if the only App Store we can readily and easily get to is the community add-ons one, it seems to me that everybody would want to put their add-ons there so that everybody could find them. Eventually it will be in the NVDA store. But until then, what possible the sense does it make to have three different depositories when only one can really be effectively searched. What am I missing here?

On Mar 29, 2023, at 4:56 PM, Rui Fontes <rui.fontes@...> wrote:

Why authors should submit add-ons to two repositories?


Best regards,

Rui Fontes
NVDA portuguese team


Às 00:15 de 30/03/2023, Joseph Lee escreveu:
Hi,

Another option is getting NVDA Recorder and other add-ons registered on community add-ons website to improve discoverability. We might as well invite authors of add-ons hosted on Spanish community catalog to bring their add-on documentation to community add-ons website to help others discover theri wonderful work.

As for searching the ad-on store in the future, I hope so perhaps through NVDA (not via Add-on Updater at the moment as I am ready to declare a feature freeze on that add-on and I will be suspending add-ons work until late April; school takes priority).

Cheers,

Joseph








 

Hi,

The reason for putting add-ons in community add-ons website is discoverability as addons.nvda-project.org is a little bit better known and can be accessed from NVDA itself (under add-ons manager/get button).

At the moment some (if not all) add-ons hosted on community add-ons website will point their download links to the one provided by the add-on store. What's happening is that NV Access and several members of the add-ons community are working on back-end work, with the user visible work going to be the add-on store client that's in the works. Once the add-on store client comes to NVDA in a future release, people will be able to browse the add-on store and download add-ons (including updates). Once that is in place, there will be no longer a need for Add-on Updater (at least as far as that add-on is concerned).

What I',m about to describe is based on latest Add-on Updater release, internals of add-on store (work in progress), and what NV Access said in recent days:

  • Add-on store: it is in the works with add-on authors submitting add-on updates.
  • To help tools such as Add-on Updater, what is called a legacy endpoint is provided that lists download links for add-ons registered on the add-on store. The legacy endpoint is also used to point to download links posted on community add-ons website.
  • Add-on Updater sources and the add-on store: effectively, Add-on Updater is accessing add-on store in two ways: the actual store mechanism, and via a legacy endpoint called community add-ons website update source. At the moment the default update source is community add-ons website update source which accesses add-on store via the legacy endpoint. The new add-on store also accesses the store but using the actual store endpoints to be used by NVDA in the future. These sources will be swapped (add-on store becoming the default source) when the add-on store client comes to NVDA in the future.

In effect, although Add-on Updater shows five update sources (community add-ons website, Spanish community catalog, catalogs maintained by communities in China and Taiwan, and the new add-on store), the actual number of update sources is four because community add-ons website and add-on store sources are really one and the same apart from how it is accessed.

Hope this helps.

Cheers,

Joseph


Luke Davis
 

Mary Otten wrote:

I am certainly not Joseph. But if the only App Store we can readily and easily get to is the community add-ons one, it seems to me that everybody would want to put their add-ons there so that everybody could find them. Eventually it will be in the NVDA store. But until then, what possible the sense does it make to have three different depositories when only one can really be effectively searched. What am I missing here?
You, and apparently Rui, are missing this.

The NVDA add-ons store *will* be coming to NVDA. I don't know when, but maybe in 2023.2 or 2023.3.

For now, it's only being used as a back-end for add-on developers to submit their add-ons to.

However, the front-end for the store, is still the add-ons community website, just as it always has been.

People will not be submitting their add-ons to three separate repositories. It will still be only two--the store, and if they want, the language specific ones such as the Spanish directory.

The thing with the community website is, while it doesn't directly host any add-ons and just provides readmes and links, those links have to be updated to point to the files in the new data store.

As soon as authors do that, or ask someone on the add-ons list to do it for them, the add-ons in the store will be listed on the community website. This is a one-time action.

The whole complication we are seeing here, I think, is the varying versions available from different sources in add-on updater. I would personally like to have seen Updater check the community site and the store, and deliver whatever is the latest version from either, rather than making users choose.

The store is mainly a developer requirement at this stage, and IMO should have remained in that realm until NV Access brought the user facing part of it on line. It is a back-end only for now. The community website is still its front-end, but must be updated on an add-on by add-on basis, by volunteers.

Luke


Mary Otten
 

Thank you, Luke. That cleared it up for me, although for the Spanish repository, it sounds like those guys will still want to send to the community add on store to make their work more easily accessed by folks who are not using Spanish? I had the impression that there were add ons on that ssite that could be useful for folk who don't speak Spanish.


Mary

On 3/29/2023 5:37 PM, Luke Davis wrote:
Mary Otten wrote:

I am certainly not Joseph. But if the only App Store we can readily and easily get to is the community add-ons one, it seems to me that everybody would want to put their add-ons there so that everybody could find them. Eventually it will be in the NVDA store. But until then, what possible the sense does it make to have three different depositories when only one can really be effectively searched. What am I missing here?
You, and apparently Rui, are missing this.

The NVDA add-ons store *will* be coming to NVDA. I don't know when, but maybe in 2023.2 or 2023.3.

For now, it's only being used as a back-end for add-on developers to submit their add-ons to.

However, the front-end for the store, is still the add-ons community website, just as it always has been.

People will not be submitting their add-ons to three separate repositories. It will still be only two--the store, and if they want, the language specific ones such as the Spanish directory.

The thing with the community website is, while it doesn't directly host any add-ons and just provides readmes and links, those links have to be updated to point to the files in the new data store.

As soon as authors do that, or ask someone on the add-ons list to do it for them, the add-ons in the store will be listed on the community website. This is a one-time action.

The whole complication we are seeing here, I think, is the varying versions available from different sources in add-on updater. I would personally like to have seen Updater check the community site and the store, and deliver whatever is the latest version from either, rather than making users choose.

The store is mainly a developer requirement at this stage, and IMO should have remained in that realm until NV Access brought the user facing part of it on line. It is a back-end only for now. The community website is still its front-end, but must be updated on an add-on by add-on basis, by volunteers.

Luke





Sarah k Alawami
 

The Spanish community contains unofficial add ons as well as official ones. I personally like this one over the community one as I can make nvda do some things I need whereas on the official side, some add on devs will not release their stuff there. . I've asked,, and got a very blunt, no.

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Mary Otten
Sent: Wednesday, March 29, 2023 5:42 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] how to get to the nvda add on store to find add ons you don't yet have installed

Thank you, Luke. That cleared it up for me, although for the Spanish repository, it sounds like those guys will still want to send to the community add on store to make their work more easily accessed by folks who are not using Spanish? I had the impression that there were add ons on that ssite that could be useful for folk who don't speak Spanish.


Mary


On 3/29/2023 5:37 PM, Luke Davis wrote:
Mary Otten wrote:

I am certainly not Joseph. But if the only App Store we can readily
and easily get to is the community add-ons one, it seems to me that
everybody would want to put their add-ons there so that everybody
could find them. Eventually it will be in the NVDA store. But until
then, what possible the sense does it make to have three different
depositories when only one can really be effectively searched. What
am I missing here?
You, and apparently Rui, are missing this.

The NVDA add-ons store *will* be coming to NVDA. I don't know when,
but maybe in 2023.2 or 2023.3.

For now, it's only being used as a back-end for add-on developers to
submit their add-ons to.

However, the front-end for the store, is still the add-ons community
website, just as it always has been.

People will not be submitting their add-ons to three separate
repositories. It will still be only two--the store, and if they want,
the language specific ones such as the Spanish directory.

The thing with the community website is, while it doesn't directly
host any add-ons and just provides readmes and links, those links have
to be updated to point to the files in the new data store.

As soon as authors do that, or ask someone on the add-ons list to do
it for them, the add-ons in the store will be listed on the community
website. This is a one-time action.

The whole complication we are seeing here, I think, is the varying
versions available from different sources in add-on updater. I would
personally like to have seen Updater check the community site and the
store, and deliver whatever is the latest version from either, rather
than making users choose.

The store is mainly a developer requirement at this stage, and IMO
should have remained in that realm until NV Access brought the user
facing part of it on line. It is a back-end only for now. The
community website is still its front-end, but must be updated on an
add-on by add-on basis, by volunteers.

Luke












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

Sarah Alawami, owner of flying Blind. Visit my website ( http://flyingblind.us ) to read my story.

Windows 11 22H2 (AMD64) build 22621.1413
NonVisual Desktop Access (NVDA)
Version: 2023.1 (2023.1.0.27913)

Microsoft 365 MSO (Version 2302 Build 16.0.16130.20332) 64-bit


 

On Wed, Mar 29, 2023 at 08:41 PM, Mary Otten wrote:
That cleared it up for me, although for the Spanish repository, it sounds like those guys will still want to send to the community add on store to make their work more easily accessed by folks who are not using Spanish? I had the impression that there were add ons on that ssite that could be useful for folk who don't speak Spanish.
-
Well, yes and no.  Any add-on that appears on the Community Add-Ons Site as well as the Spanish Add-Ons Directory is an "officially vetted" one that qualifies for inclusion in the Community Add-Ons site (and, by extension, in the new Add-Ons Store as well at the moment).  All "officially vetted" add-ons I'm aware of (and I'm certain someone will correct me if I'm wrong) has to be set up so that it allows translation tables for all of its messages, settings, etc., based upon the system language settings in use where it's being used.  That doesn't mean that there will currently exist translations for every language in the world, only that if someone wanted to use it in that language and a translator were available to create the necessary translations, they could be added just like all the existing ones already are.

The Spanish Add-Ons Directory includes a lot of "unofficial" add-ons, and a number of these not in Spanish if memory serves about some I've stumbled over, and where those add-ons were not built such that translation tables are a built-in part of their structure.

So while the Add-Ons Directory definitely does include the add-ons that the Community Add-Ons Site does, it includes many others, in at least several other languages, that may or may not be of use to someone who doesn't speak the language in which their UI is presented, as it would not be a simple undertaking to make add-ons so coded in other translations.

Things like Windows, NVDA, many NVDA add-ons, and a lot of commercial software to not have "language specific" versions, but are built to be able to be localized/translated.  Many different languages exist in what's most easily thought of as a localization/translation table, and where the program checks to see what the system language is set to, and then uses that language out of the localization/translation table to present its own user interface in the same language, presuming those translations actually exist in the table.  If they don't, they can easily be added if someone does the translations.

The concept is pretty simple in that localizable software is built from the outset with none of its "linguistic elements" like messages, settings, etc., hard coded.  They're in a table that can be expanded and accessed when needed for other languages.  Non-localizable software is not written that way and is not at all easy to localize on demand.
 
--

Brian Virginia, USA Windows 11 Pro, 64-Bit, Version 22H2, Build 22621; Office 2016, Version 16.0.15726.20188, 32-bit

It is much easier to be critical than to be correct.

       ~ Benjamin Disraeli, 1804-1881


 

On Wed, Mar 29, 2023 at 09:02 PM, Sarah k Alawami wrote:
some add on devs will not release their stuff there [the Community Add-Ons Page] . . I've asked,, and got a very blunt, no.
-
That's because there are requirements that are similar to those Joseph Lee outlined with regard to the new Add-Ons Store. See message  in the NVDA Group Archive.

For someone who created an add-on as a "throw together tool" for their personal use, but who's allowed others who want to use it to do so, it's unlikely they want to get into the level of formality required by the Community Add-Ons page and, it seems, Add-On Store.

I have been saying, for years now, that until and unless a unified add-on repository that includes both classes of add-ons is created, there will be splintering of add-on sources that is wholly unnecessary.  The Spanish Add-Ons Directory is, so far, the closest thing I've seen to a unified add-on repository and I hope to heaven that the Add-On Store ends up following its lead.  If it doesn't, then it's just another spin on the Community Add-Ons Site that's managed by NVAccess directly.  And if the Add-On Updater functionality were ever to restrict strictly to one repository, that's a big, big step backwards, in my opinion.
--

Brian Virginia, USA Windows 11 Pro, 64-Bit, Version 22H2, Build 22621; Office 2016, Version 16.0.15726.20188, 32-bit

It is much easier to be critical than to be correct.

       ~ Benjamin Disraeli, 1804-1881


Luke Davis
 

Brian Vogel wrote:

Any add-on that appears on the Community Add-Ons Site as well as the Spanish Add-Ons Directory is an "officially vetted" one that
Brian, I'm curious about that phrase "officially vetted"--you've used it several times now.

What exactly do you mean by it?

If you're speaking of the old code review process that add-ons had to go through, that hasn't "officially" been the case for quite a while (a year or so?). It was still being done, at least to some extent, by Noelia and Joseph only, up until about three weeks ago, when the store came on line.

As of now, there is no "official vetting" process of which I am aware. Not to say that I am aware of everything--the situation is quite dynamic with documentation and such; but given the submission automation now available, pretty much anyone could submit anything.

Luke


 

On Wed, Mar 29, 2023 at 11:57 PM, Luke Davis wrote:
What exactly do you mean by it?
-
I don't know, hence the quotes.  But it is abundantly clear that some sort of review process, whether automated, done by humans, or a combination of the two takes place before the "seal of approval" is placed on an add-on and it is included on the Community Add-Ons page.

It doesn't matter if anyone can submit anything, what matters is that not everything submitted will pass muster, whatever "passing muster" might be at the moment the evaluation is being done.

Since not everything that exists already, some of which is in pretty wide use, is on the Community Add-Ons site some sort of gate-keeping is occurring, and that's what "official vetting" is.  I've never attempted to describe the process in detail, but it has to be acknowledged that it exists.  If it doesn't, I'd like to know how you, or anyone else, has come to that conclusion.  Even what Joseph recently wrote about the Add-Ons store that I alluded to in another message clearly indicates that there are certain requirements that a developer must meet in terms of their own project management practices before an add-on can even "enter the pipeline" for inclusion there.  That's vetting, and it's being done by NVAccess "officialdom" for lack of a better way of putting it.
--

Brian Virginia, USA Windows 11 Pro, 64-Bit, Version 22H2, Build 22621; Office 2016, Version 16.0.15726.20188, 32-bit

It is much easier to be critical than to be correct.

       ~ Benjamin Disraeli, 1804-1881