Hi, I agree with Joseph. Also, I think that it's better to include this
info in the About button, not in a new column on the add-ons manager:
The columns show mandatory fields, and maybe that add-ons which don't
support updates ommit the channel.
Cheers.
El 27/03/2017 a las 16:55, Joseph Lee escribió:
Hi,----------------------------------------------------------------
This brings up an inconsistency: the Core itself does not support
changing update channel (or there isn’t a UI for it yet). One way to
bring this to life is at least accept Noelia’s suggestion whereby update
channel info will be shown in About dialog. Another way is to show
current channel information on add-ons list by adding a new column named
“update channel” or similar. Note that this runs into localization issue
where translators would want to give localized names for user-friendly
labels for channel names.
Cheers,
Joseph
*From:*nvda-addons-bounce@xxxxxxxxxxxxx
[mailto:nvda-addons-bounce@xxxxxxxxxxxxx] *On Behalf Of *Derek Riemer
*Sent:* Monday, March 27, 2017 7:06 AM
*To:* nvda-addons@xxxxxxxxxxxxx
*Subject:* [nvda-addons] Re: Add-on template: proposed changes to
support add-on updates and channel selection
Hi,
Probably not in About page, as it'll be an internal key.
I'd argue it should be user facing. The user should be able to change
from chanel x to y, so we'll need to provide all possible channels in
the addon. How about a list of chanels, with a default channel key as well.
Cheers,
Joseph
-----Original Message-----
From: nvda-addons-bounce@xxxxxxxxxxxxx
<mailto:nvda-addons-bounce@xxxxxxxxxxxxx>
[mailto:nvda-addons-bounce@xxxxxxxxxxxxx
<mailto:nvda-addons-bounce@xxxxxxxxxxxxx>] On Behalf Of Noelia
Sent: Sunday, March 26, 2017 9:36 PM
To: nvda-addons@xxxxxxxxxxxxx <mailto:nvda-addons@xxxxxxxxxxxxx>
Subject: [nvda-addons] Re: Add-on template: proposed changes to
support add-on updates and channel selection
For me is good.
Aside, the About button could show the current channel too.
Thanks for this great work.
Cheers.
El 27/03/2017 a las 5:39, Joseph Lee escribió:
> Fellow add-ons community members,
>
>
>
> 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
>
----------------------------------------------------------------
NVDA add-ons: A list to discuss add-on code enhancements and for
reporting bugs.
Community addons are available from: http://addons.nvda-project.org
To send a message to the list: nvda-addons@xxxxxxxxxxxxx
<mailto:nvda-addons@xxxxxxxxxxxxx> To change your list
settings/unsubscribe: //www.freelists.org/list/nvda-addons
To contact list moderators: nvda-addons-moderators@xxxxxxxxxxxxx
<mailto:nvda-addons-moderators@xxxxxxxxxxxxx>
----------------------------------------------------------------
NVDA add-ons: A list to discuss add-on code enhancements and for
reporting bugs.
Community addons are available from: http://addons.nvda-project.org
To send a message to the list: nvda-addons@xxxxxxxxxxxxx
<mailto:nvda-addons@xxxxxxxxxxxxx>
To change your list settings/unsubscribe:
//www.freelists.org/list/nvda-addons
To contact list moderators: nvda-addons-moderators@xxxxxxxxxxxxx
<mailto:nvda-addons-moderators@xxxxxxxxxxxxx>
--
Derek Riemer: Improving the world one byte at a time!
· University of Colorado Boulder Department of computer science,
4th year undergraduate student.
· Accessibility enthusiast.
· Proud user of the NVDA screen reader.
· Open source enthusiast.
· Skier.
Personal website <http://derekriemer.com>
