Difference between revisions of "Documentation/Labs/AutomaticUpdateAndInstallationFramework"

From Slicer Wiki
Jump to: navigation, search
Line 6: Line 6:
 
* New Slicer version installed locally should be updated with the list of extension previously installed.
 
* New Slicer version installed locally should be updated with the list of extension previously installed.
 
* Self update of Slicer
 
* Self update of Slicer
 +
 +
= Terminology =
 +
 +
* ExtensionManagerModel: This is the backend of the [Documentation/4.5/SlicerApplication/ExtensionsManager Extensions Manager] displayed to the user
 +
 +
* [https://github.com/Slicer/Slicer/tree/master/Utilities/Scripts/SlicerWizard Utilities/Scripts/SlicerWizard]: This is a python package allowing to create new extension using templates
 +
 +
  
 
= Keep track of the installed extensions across version =
 
= Keep track of the installed extensions across version =

Revision as of 16:07, 3 May 2016

Home < Documentation < Labs < AutomaticUpdateAndInstallationFramework


Overview

Use cases:

  • New Slicer version installed locally should be updated with the list of extension previously installed.
  • Self update of Slicer

Terminology

  • ExtensionManagerModel: This is the backend of the [Documentation/4.5/SlicerApplication/ExtensionsManager Extensions Manager] displayed to the user


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

NA


Notes

2016.05.03

  • Serialize what is installed in you current Slicer