Revision as of 15:48, 3 May 2016

Home < Documentation < Labs < AutomaticUpdateAndInstallationFramework

Use cases:

new version installed locally should be updated with the list of extension previously installed
self update of Slicer

Notes from 2016.05.03

Ability to ask the installer (or Slicer) to install other extensions
- Would it make sense to transition to http://doc.qt.io/qtinstallerframework/ ?

Extract list of extensions installed. Look at npm for the format.
Extension manager:
- Update ExtensionManageModel API so that "list" can be processed
- Update entry "Install Extension from file" to "Install Extensions from file" and support "tar.gz", ".json"

@@ Line 8: / Line 8: @@
 * See also [[Documentation/Labs/ExtensionsFrameworkRoadmap]]
-* Automatic update of Slicer
 * Ability to ask the installer (or Slicer) to install other extensions
 ** Would it make sense to transition to http://doc.qt.io/qtinstallerframework/ ?
-* Mechanism to keep track of the installed extensions across version. See http://www.na-mic.org/Bug/view.php?id=2779
 * Serialize what is installed in you current Slicer
@@ Line 18: / Line 15: @@
 * Update of installed extensions:
 ** See https://www.slicer.org/slicerWiki/index.php/Documentation/4.5/SlicerApplication/ExtensionsManager#Updating_installed_extensions
+= Related issues =
+* [http://www.na-mic.org/Bug/view.php?id=2779 2779]: Mechanism to keep track of the installed extensions across version
+= Todo =
+* Extract list of extensions installed. Look at npm for the format.
+* Extension manager:
+** Update ExtensionManageModel API so that "list" can be processed
+** Update entry "Install Extension from file" to "Install Extensions from file" and support "tar.gz", ".json"