Difference between revisions of "Documentation/Labs/AutomaticUpdateAndInstallationFramework"
From Slicer Wiki
| Line 27: | Line 27: | ||
= Convention = | = Convention = | ||
| − | Tasks | + | Tasks listed in this page can be associated with any of these state: |
* '''ToBeDone''' | * '''ToBeDone''' | ||
* {{done}} '''Completed''' | * {{done}} '''Completed''' | ||
* '''In progress''' | * '''In progress''' | ||
| − | |||
= Use case: Keep track of the installed extensions across version = | = Use case: Keep track of the installed extensions across version = | ||
Revision as of 16:45, 3 May 2016
Home < Documentation < Labs < AutomaticUpdateAndInstallationFramework
Contents
Overview
This page serves as roadmap for the Slicer Automatic Update and Installation framework.
Use cases:
- New Slicer version installed locally should be updated with the list of extensions previously installed.
- Self update of Slicer
Terminology
- User Interface
- Extensions Manager is a Slicer dialog allowing the user to Search, Install, Remove and disable extensions.
- ExtensionWizard module: This is a Slicer module providing a graphical interface within Slicer to aid in the creation of Slicer extensions.
- Command line
- ExtensionWizard is a command line tool to simplify the process of creating and contributing extensions.
- API
- ExtensionsManagerModel: This is the backend of the Extensions Manager displayed to the user
- Utilities/Scripts/SlicerWizard: This is a python package used in the ExtensionWizard
Convention
Tasks listed in this page can be associated with any of these state:
- ToBeDone
Completed- In progress
Use case: Keep track of the installed extensions across version
The goal here is to simplify the number of steps allowing people to reinstall extensions that were used in a previous installation.
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
NA
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:
