Feature Request: Update Source Labels

TheIronGolem · June 28th, 2016, 09:02 PM

In the menu for adding new update sources, it would be nice if we could have a user-editable text box to associate a label with each source. This would give us a way to easily identify what content each source provides (other than the URL, which isn't always obvious).

Bonus points if it could read a property in the remote XML file to auto-populate the field.

Mathias · June 29th, 2016, 07:06 AM

This is already available, but you need to formally define the source in a .1st file, instead of quick-defining it in the editor.

ShadowChemosh · June 29th, 2016, 08:15 AM

I am guessing that he means the Secondary Update URL that people enter on the Find Updates screen. Or at least that is my thoughts as TheIronGolem knows how to define .1st files.

TheIronGolem · June 29th, 2016, 09:01 PM

To be clear, I'm referring to this:

I know from the first URL that this is Shadow's Community package. And I know that the next two are my Spheres of Power projects, but I only know that because I'm the one who wrote them. And I can't tell by looking at the URL which is the core book and which is the expansion book I'm working on. This will only get more confusing in the future as there are at least 20 more books in the future (one handbook for each "sphere" of magic in that system). That's not a big deal for me personally since I have reason to track these URL's anyway. But I'm thinking that our customers might like have an easy way of seeing which source updates which expansion, for things like troubleshooting or removing individual books they don't want anymore.

Not a huge deal, of course, but it would be a nice convenience.

TheIronGolem Senior Member Join Date: Feb 2015 Posts: 676 June 28th, 2016, 09:02 PM	In the menu for adding new update sources, it would be nice if we could have a user-editable text box to associate a label with each source. This would give us a way to easily identify what content each source provides (other than the URL, which isn't always obvious). Bonus points if it could read a property in the remote XML file to auto-populate the field.
#1

Mathias Senior Member Lone Wolf Staff Join Date: May 2005 Posts: 13,213 June 29th, 2016, 07:06 AM	This is already available, but you need to formally define the source in a .1st file, instead of quick-defining it in the editor.
#2