Documentation/Labs/ExtensionsFrameworkRoadmap

This page serves as roadmap for the Slicer Extensions framework.

Extension contribution process

The goal here is to simplify the number of steps allowing people to contribute extension.

More specifically, we would like to make it very easy for people to create a python extension by:

• removing the need for a Slicer build tree
• reducing the number of steps required to create and load an extension from a template
• simplifying how an extension is contributed to the index
• simplifying how an extension can be uploaded to the extension server

Current process

The current process to create an empty extension is documented here, then the steps to contribute the extension are documented here.

For all type of extension (C++ or python), the steps can then be summarized as:

To create an extension

1. Workstation: Build Slicer application in Release
2. Workstation: Use the Wizard to create an extension 5 commands to enter in a terminal
3. Workstation: Initialize git repository 1 command
4. Workstation: Implement extension / local commits

To save extension code

1. Github: Create an account
2. Github: Create a repository
3. Workstation -> Github: Push local work on Github

To contribute an extension to Index

1. SlicerWiki: Create documentation page
2. Extension Server: Create an account
3. Extension Server: Join community
4. Extension Server: Ask permission for experimental folder.
5. Workstation: Configure upload credential
6. Workstation -> ExtensionServer: Test upload [1 command to enter in a terminal / 1 click in visual studio]
7. Github: Fork ExtensionsIndex
8. Workstation: Clone fork locally
9. Workstation: Create branch add-YourExtensionName
10. Workstation: Commit description file obtained from build tree
11. Workstation -> Github: Push the topic to fork
12. Github: Click on Pull request button

To update an extension in Index

1. SlicerWiki: Update documentation page
2. Workstation: In extension index clone: 5 commands to type
3. Workstation: Create branch update-YourExtensionName
4. Workstation: Commit description file obtained from build tree
5. Workstation -> Github: Create pull request manually creating the URL
6. Github: Add a comment in the pull request with a Compare link also manually generated

Proposed changes

To create an extension

For all type of extensions, the simplified workflow is:

1. Workstation: Build Slicer application in Release
2. Workstation: Use the Wizard to create an extension 1 commands to enter in a terminal
3. Workstation: Initialize git repository 1 command
4. Workstation: Implement extension / local commits

For scripted extensions, creation directly from within Slicer:

1. Slicer: Modules -> Developer -> ExtensionWizard
2. ExtensionWizard module: Set name, description, contributors etc ... then click on Create
   1. Set the working directory ? Where to create.
   2. External link to the github account creation page (will open web browswer or tab in the extension manager ?)
   3. Optionally create github repo and pre-populate repo ...
3. Path to the module(s) in extension should be added to the additional module path.
4. Slicer: Restart - 'Foo' module should show up. Note: This last step could probably be removed

To save extension code

For all type of extensions, the simplified workflow is:

1. Github: Create an account
2. Workstation -> Github: Create repository done with 1 command. ExtensionWizard.py --publish ~/code/MyExtension

For scripted extensions:

1. initial publish on github done from the ExtensionWizard module. See above

To publish extension code update

For all type of extensions, the workflow is:

1. git commit, ..., git push

To contribute an extension to the Index

1. SlicerWiki: Create documentation page.
   1. Need to check with BHW if wiki version can be updated so that any IP could use the mediawiki API
2. Extension Server: Create an account [Join community + experimental folder permission consolidated in one location]
   1. Create a "Slicer Extensions" community where user have to request access
   2. Folks belonging to the "Slicer Extensions" would be automatically be granted access
   3. Jc: Check with Midas team with user can request access to community
3. Workstation: Configure upload credential
   1. Update documentation to explain that MIDAS_API_* variable can be set in the env.
4. Workstation -> ExtensionServer: Test upload [1 command to enter in a terminal / 1 click in visual studio]
5. Add extension to the index using 1 command: ExtensionWizard.py --contribute --target master ~/code/MyExtension

Progress

• Improve Wizard to create empty extension: reduce number of terminal commands to 1
  • 3566: Wizard: Simplify creation of extensions/modules: Completed
  • 3572: Add ExtensionWizard wiki page: Completed - See Documentation/Nightly/Developers/ExtensionWizard
  • 3572: Add developer documentation for ExtensionWizard: Completed - Review in progress - See [1]
• Publish extension on Github by creating github repo - Completed - Review in progress

• In case of Python extension, remove the need for a Slicer build tree: 50%
  • Wizard: Remove dependency on build tree or CMake generated file. - Review in progress
  • Add install rules for the template source code - To make them available from an installed Slicer
  • 3269: Simplify contribution of scripted extension: 50%
  • 3603 Slicer: Creation of python extension directly from Slicer. Awaiting Review
    • Slicer: Optional Restart. ToBeDone (do we actually need this?)

• 3604 ExtensionServer: Consolidate ExtensionsIndex account creation. ToBeDone

• 3605 SlicerWiki: Automatic creation of extension wiki page. ToBeDone

• 3606 Slicer: Given an extension python script. Should be possible to upload the extension directly from Slicer. ToBeDone

Extensions Catalog / Manager

The goal here is to improve the overall user experience associated with the extension catalog.

When accessed from within Slicer the catalog is also referred as extensions manager.

Progress

• 3564: Add search option in extension manager. Completed
• 3602: ExensionsManager - Add a "Show url" link'. Completed
• 2089: Either on-demand or when slicer starts, check if there are available extensions update.. ToBeDone
• 3607: ExtensionManager: Exclude category "Example" from "All" listing . Completed
• 2779: Mechanism to keep track of the installed extensions across version. ToBeDone
• 2912: Install dependent extensions . Completed

• Low priority:
  • 2334: Differentiate different type of extenions in extension manager: Concept of channel. ToBeDone
  • 2778: Add "Download stats" on each extension page . ToBeDone
  • 3608: ExtensionsManager: Display description for installed extensions.. Completed
  • Consolidate rating across extension version. See midasplatform/slicerappstore/issues/9

Extension developer documentation

The goal is to consolidate the existing documentation so that it is easy to understand what is the python API available to the Slicer python extension developer.

Progress

• Generate Slicer python API documentation. In progress. See experiment http://mwoehlke-kitware.github.io/Slicer/Base/

Extensions Wizard UI

The wizard UI will provide a Slicer module allowing to:

• easily create / publish / contribute extensions directly from Slicer.
• directly load scripted modules after they are created.

Progress

See issues #3603, #3606 listed above.