Skip to content, Skip to search



440 bytes added, 13 May
Class perspective
* the user can manually add additional update sites which will then also be checked for updates on startup
Updates will be downloaded to <code></code>. The launcher is moving the updates to their final destination on the next reboot (?).
== Update site maintainer perspective ==
* <code>UpToDate</code> checks if the user wants to ignore updates, checks the internet connection, checks write access, etc..
* <code>UpToDate</code> also checks if any of the enabled update sites have different URLs on the available list of update sites (since Updater V1) and whether any update sites have a newer update timestamp than the one locally stored for that update site
* in case there are updates, <code>CheckForUpdates</code> calls <code>PromptUserToUpdate</code> which invokes <code>net.imagej.ui.swing.updater.ImageJUpdater</code> is called
* <code>ImageJUpdater</code> is the command creating the graphical user interfaces for dealing with updated files and update site URLs
=== Changes on V2 ===
* In case there are updates, <code>UpToDate</code> will tell the <code>UpdateService</code> which can be used to open the ImageJUpdater directly or just trigger a notification indicator in the UI
== The official list of update sites ==
Bureaucrat, emailconfirmed, incoming, administrator, uploaders, widget editor