Difference between revisions of "Documentation/4.2/Extensions/Description"

From Slicer Wiki
Jump to: navigation, search
(Nightly -> 4.2)
 
(Add extension manager screenshot to illustrate what an extension is)
Line 1: Line 1:
 +
[[Image:Extension_Manager.png|thumb|Extensions in the [[Documentation/{{documentation/version}}/SlicerApplication/ExtensionsManager|Extension manager]].]]
 +
 
An [[Documentation/{{documentation/version}}/Extensions|extension]] could be seen as a delivery package bundling together one or more Slicer [[Documentation/{{documentation/version}}/Developers/Modules|modules]]. After installing an extension, the associated [[Documentation/{{documentation/version}}/Developers/Modules|modules]] will be presented to the user as built-in ones
 
An [[Documentation/{{documentation/version}}/Extensions|extension]] could be seen as a delivery package bundling together one or more Slicer [[Documentation/{{documentation/version}}/Developers/Modules|modules]]. After installing an extension, the associated [[Documentation/{{documentation/version}}/Developers/Modules|modules]] will be presented to the user as built-in ones
  

Revision as of 21:07, 8 April 2013

Home < Documentation < 4.2 < Extensions < Description
Extensions in the Extension manager.

An extension could be seen as a delivery package bundling together one or more Slicer modules. After installing an extension, the associated modules will be presented to the user as built-in ones

The Slicer community maintains a website referred to as the Slicer Extensions Catalog to support finding, downloading and installing of extensions. Access to this website is integral to Slicer and facilitated by the Extensions Manager functionality built into the distributed program.

The Catalog classifies extensions into three levels of compliance:

  1. Category 1: Fully compliant Slicer Extensions: Slicer license, open source, maintained.
  2. Category 2: Open source, contact exists.
  3. Category 3: All other extensions (work in progress, beta, closed source etc).

To publish extensions, developers should consider reading the following pages: