Difference between revisions of "Documentation/Labs/AutomaticUpdateAndInstallationFramework"

From Slicer Wiki
Jump to: navigation, search
Line 2: Line 2:
  
 
= Overview =
 
= Overview =
 +
 +
This page serves as roadmap for the Slicer Automatic Update and Installation framework.
  
 
Use cases:
 
Use cases:
Line 23: Line 25:
 
** [https://github.com/Slicer/Slicer/tree/master/Utilities/Scripts/SlicerWizard Utilities/Scripts/SlicerWizard]: This is a python package used in the ExtensionWizard
 
** [https://github.com/Slicer/Slicer/tree/master/Utilities/Scripts/SlicerWizard Utilities/Scripts/SlicerWizard]: This is a python package used in the ExtensionWizard
  
= Keep track of the installed extensions across version =
+
= Convention =
 +
 
 +
Tasks list in this page can be associated with any of these state:
 +
* '''ToBeDone'''
 +
*  {{done}} '''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 ==
 
== Current Process ==

Revision as of 16:44, 3 May 2016

Home < Documentation < Labs < AutomaticUpdateAndInstallationFramework


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.



Convention

Tasks list in this page can be associated with any of these state:

  • ToBeDone
  • Check.svg 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

  • Serialize what is installed in you current Slicer