Quantcast

NVDA Core issue 3208: add an update channel key to add-on manifests to support add-on updates

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

NVDA Core issue 3208: add an update channel key to add-on manifests to support add-on updates

Joseph Lee

Hi all,

 

As some of you may know, I’m working on ability for NVDA to check for and download add-on updates. This project consists of a client UI and update experience, add-on update info retriever and protocols, and a server-side implementation to gather add-on versions and other metadata under one roof. More info about this project can be found at:

https://github.com/nvaccess/nvda/issues/3208

 

At the moment the client UI is done. Once NV Access comes up with a protocol and server-side facility, I’ll update my client UI bits to point to new capabilities. But this is just the start, as bulk of this project relies on cooperation with add-on writers when it comes to making our add-ons support updates. In order to do so, I propose the following changes to the add-on template and manifests:

 

  • Update channel: I propose adding a new manifest key named “updateChannel” that’ll let NVDA know which update channel should be consulted when checking for an add-on update. By default, this key will hold a null string (None), or for add-ons that does not support updates, this key will not be defined. For most add-ons, possible channels could be “stable” and “dev”. The add-on author must notify server-side admins or reviewers whenever channels need to be added, changed or removed.

 

Comments are appreciated.

Cheers,

Joseph


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Nvda-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/nvda-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: NVDA Core issue 3208: add an update channel key to add-on manifests to support add-on updates

Sarah Alawami
Nice nice. Waht if though the update is *not* on nvda's official page, like what if we got the updates from a third party resource. Will the updater still work? Or are these only for nvda's officially supported updates.

Thanks.
On Mar 26, 2017, at 8:40 PM, Joseph Lee <[hidden email]> wrote:

Hi all,
 
As some of you may know, I’m working on ability for NVDA to check for and download add-on updates. This project consists of a client UI and update experience, add-on update info retriever and protocols, and a server-side implementation to gather add-on versions and other metadata under one roof. More info about this project can be found at:
 
At the moment the client UI is done. Once NV Access comes up with a protocol and server-side facility, I’ll update my client UI bits to point to new capabilities. But this is just the start, as bulk of this project relies on cooperation with add-on writers when it comes to making our add-ons support updates. In order to do so, I propose the following changes to the add-on template and manifests:
 
  • Update channel: I propose adding a new manifest key named “updateChannel” that’ll let NVDA know which update channel should be consulted when checking for an add-on update. By default, this key will hold a null string (None), or for add-ons that does not support updates, this key will not be defined. For most add-ons, possible channels could be “stable” and “dev”. The add-on author must notify server-side admins or reviewers whenever channels need to be added, changed or removed.
 
Comments are appreciated.
Cheers,
Joseph
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________
Nvda-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/nvda-devel


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Nvda-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/nvda-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: NVDA Core issue 3208: add an update channel key to add-on manifests to support add-on updates

Joseph Lee

Hi,

It’ll be limited to add-ons registered with the community (those listed on the add-ons website).

Cheers,

Joseph

 

From: Sarah Alawami [mailto:[hidden email]]
Sent: Monday, March 27, 2017 1:52 PM
To: NVDA screen reader development <[hidden email]>
Subject: Re: [Nvda-devel] NVDA Core issue 3208: add an update channel key to add-on manifests to support add-on updates

 

Nice nice. Waht if though the update is *not* on nvda's official page, like what if we got the updates from a third party resource. Will the updater still work? Or are these only for nvda's officially supported updates.

 

Thanks.

On Mar 26, 2017, at 8:40 PM, Joseph Lee <[hidden email]> wrote:

 

Hi all,

 

As some of you may know, I’m working on ability for NVDA to check for and download add-on updates. This project consists of a client UI and update experience, add-on update info retriever and protocols, and a server-side implementation to gather add-on versions and other metadata under one roof. More info about this project can be found at:

 

At the moment the client UI is done. Once NV Access comes up with a protocol and server-side facility, I’ll update my client UI bits to point to new capabilities. But this is just the start, as bulk of this project relies on cooperation with add-on writers when it comes to making our add-ons support updates. In order to do so, I propose the following changes to the add-on template and manifests:

 

  • Update channel: I propose adding a new manifest key named “updateChannel” that’ll let NVDA know which update channel should be consulted when checking for an add-on update. By default, this key will hold a null string (None), or for add-ons that does not support updates, this key will not be defined. For most add-ons, possible channels could be “stable” and “dev”. The add-on author must notify server-side admins or reviewers whenever channels need to be added, changed or removed.

 

Comments are appreciated.

Cheers,

Joseph

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

 


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