Update: when cloning UpdateSites, clone the 'active' flag, too

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Updater (Update Site Dialog): always allow changing the name

Even if the site is not yet active.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Updater (Update Site Dialog): use the user-specified URL

Without setting the site's URL explicitly, it would use the previous
value, not the one the user has just typed in.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Updater: prepare the db.xml.gz format to store disabled sites

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Updater (FilesCollection): add methods to retrieve even disabled sites

Over the next few commits, we will add support to store and persist
even disabled update sites.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Updater: avoid using the now-deprected methods

We just added methods to retrieve even disabled update sites from the
FilesCollection. Therefore, we must visit every caller and specify
whether to include or to exclude the disabled sites stored in the
FilesCollection instance.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Updater: read back even disabled update sites from db.xml.gz

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Updater: persist even disabled update sites to db.xml.gz

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Updater: store also sites' descriptions and maintainers in db.xml.gz

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Updater (FilesCollection): do not activate UpdateSite instance
when adding

When adding without an explicit UpdateSite instance, we assume that
it should be activated, as before.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Manage Update Sites: always add new sites to the FilesCollection

Thus they will be persisted, as disabled update sites.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Manage Update Sites: let (de)activateSite() take the UpdateSite itself

We do not have to go through the row anymore because the UpdateSite
instances are all stored in the FilesCollection.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Manage Update Sites: update the GUI when auto-activating a site

When a valid URL was entered, the currently-edited site is
auto-activated. With this change, the check mark is even shown...

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Manage Update Sites: sites are really stored in FilesCollection

So do not remove and re-add them anymore just mark them as
enabled/disabled.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Manage Update Sites: disable a site when it could not be activated

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Manage Update Sites: fix compile warning

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Updater (Swing): do not hide 'Manage Update Sites' in easy mode

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Merge branch 'updater-sites'

The main purpose of this branch is to address the issues raised in

	http://trac.imagej.net/ticket/1957

In particular,

- the "Manage Update Sites" button should be visible even in easy mode,

- when adding a site, the name should be editable before a valid URL is
  provided

- non-standard update sites should be retained even if they are disabled

- whenever a URL is typed in manually, it should not complain 'Not a
  valid URL!'