Implement release download mechanism

[aschaeffer]

Tasks

• [ ] Tree structure
  • [ ] /releases/config
  • /automaticCheckForNewReleases (bool)
  • /automaticDownload (bool)
  • /automaticInstallation (bool)
  • [x] /releases/{channel}/{version} (is in v0.9.0)
  • /channel (string)
  • /version (string)
  • /name (string)
  • /date (string)
  • /downloaded (bool)
  • /installed (bool)
  • /fileSize (int64)
  • /downloadedFileSize (int64)
• [x] Tree events (is in v0.9.0)
  • onNewReleaseAvailable
  • onReleaseDownloaded
  • onReleaseInstalled
• [x] Service ReleaseManager (is in v0.9.0)
  • [x] checkForNewReleases()
  • Checks the GitHub API for new releases
  • Updates the tree information about releases
  • fires tree event onNewReleaseAvailable
  • [x] downloadRelease(channel, version)
  • Download the ZIP file inexor-core-{platform}-{arch}.zip
  • fires tree event onReleaseDownloaded
  • subscribes onNewReleaseAvailable
  • [x] installRelease(channel, version)
  • Extracts the ZIP file to the installation folder
  • The installation folder location is either a standard path or relative to the root folder of the Inexor Flex installation
  • fires tree event onReleaseInstalled
  • subscribes onReleaseDownloaded
  • [x] uninstallRelease(version)
  • Deletes the ZIP file and the installation folder for the given release
  • fires tree event onReleaseUninstalled
• [ ] User Interface (ui-flex)
  • [ ] List view for the list of releases
  • [x] Show columns: codeName, channel, versionNumber, date, fileSize
  • [x] Show download progress
  • [ ] Buttons for download, installation and uninstallation
  • [ ] Button for check for new releases
  • [ ] Configuration page
  • automatically check for new releases
  • automatically download new releases
  • automatically install new releases

[Fohlen]

@aschaeffer will do this

[Croydon]

Should the auto update to new core releases already work?

Even Flex discovers the new Core releases I do stuck with the Core version Flex initally downloaded.

[Croydon]

This is just one of endless examples where I never got an answer.

This issue can be furthermore likely be thrown away as the decision was made to move away from Node.js and by this throwing away the current implementation of Flex.