Documentation/4.8/Modules/DeveloperToolsForExtensions

From Slicer Wiki
Revision as of 07:03, 18 October 2017 by UpdateBot (talk | contribs) (Nightly -> 4.8)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
Home < Documentation < 4.8 < Modules < DeveloperToolsForExtensions


For the latest Slicer documentation, visit the read-the-docs.



Introduction and Acknowledgements

Extension: DeveloperToolsForExtensions
Acknowledgments: This work is part of the National Alliance for Medical Image Computing (NAMIC), funded by the National Institutes of Health through the NIH Roadmap for Medical Research, Grant U54 EB005149.
This tool extension exposes slicer features to help developers to test their own extensions
Author: Francois Budin (UNC)
Contact: Francois Budin, <email>fbudin@unc.edu</email>

Website: https://github.com/fbudin69500/SlicerDeveloperToolsForExtensions.
License: Apache License, Version 2.0

Module Description

This module currently presents two options to the user:

-Installing an extension from an archive (*.tar.gz or *.zip) that is on the user's computer. This is useful if one wants to test that their extension has packaged correctly without uploading their extension onto the Midas server. Additionally, this can also be used by labs to distribute their extensions on their own website (uploading the extension archive directly on their website) and users can install these extensions using this module. It is also possible to install an extension package directly from the extension manager (from the toolbar).

-Load a module that has not been loaded at the start-up of Slicer, while Slicer is running, without having to restart Slicer (limited to scripted python modules).


Use Cases

Loading an extension archive

Tutorials

Panels and their use

Module UI

Similar Modules

Information for Developers