Difference between revisions of "Documentation/Labs/AutomaticUpdateAndInstallationFramework"
From Slicer Wiki
| Line 13: | Line 13: | ||
== Proposed Changed == | == Proposed Changed == | ||
| − | == Progress = | + | == Progress == |
* Extract list of extensions installed. Look at npm for the format. '''ToBeDone''' | * Extract list of extensions installed. Look at npm for the format. '''ToBeDone''' | ||
| Line 22: | Line 22: | ||
Meta issue: | Meta issue: | ||
* [http://www.na-mic.org/Bug/view.php?id=2779 2779]: Mechanism to keep track of the installed extensions across version '''ToBeDone''' | * [http://www.na-mic.org/Bug/view.php?id=2779 2779]: Mechanism to keep track of the installed extensions across version '''ToBeDone''' | ||
| + | |||
| + | == Completed == | ||
Revision as of 15:56, 3 May 2016
Home < Documentation < Labs < AutomaticUpdateAndInstallationFramework
Contents
Overview
Use cases:
- New Slicer version installed locally should be updated with the list of extension previously installed.
- Self update of Slicer
Keep track of the installed extensions across version
Current Process
Proposed Changed
Progress
- Extract list of extensions installed. Look at npm for the format. ToBeDone
- Extension manager:
- Update ExtensionManageModel API so that "list" can be processed ToBeDone
- Update entry "Install Extension from file" to "Install Extensions from file" and support "tar.gz", ".json" ToBeDone
Meta issue:
- 2779: Mechanism to keep track of the installed extensions across version ToBeDone
Completed
Notes
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/ ?
- Serialize what is installed in you current Slicer
- Update of installed extensions:
