Re: And finally, Add-on Updater 20.06 #addonrelease
Hi, Using the current infrastructure, the best way is letting NVDA query a table of add-on identifiers and versions, which must be updated whenever new add-ons are registered and updates are released (still a manual intervention). Note that this fails for add-ons that receive updates from websites other than GitHub and ones that come with their own update mechanism. All this will change once add-ons store idea becomes reality, which will also make Add-on Updater and update mechanisms in other add-ons obsolete. Cheers, Joseph
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Robert Kingett
Sent: Wednesday, May 20, 2020 5:49 AM To: nvda@nvda.groups.io Subject: Re: [nvda] And finally, Add-on Updater 20.06 #AddonRelease
Is there a way this can be somewhat automated so you don't have to add every new add on that gets posted to the community website?
|
|