Difference between revisions of "2014 Summer Project Week Breakout Session:SlicerExtensions"

From NAMIC Wiki
Jump to: navigation, search
m
m
 
(8 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
  [[2014_Summer_Project_Week#Agenda|Back to Summer project week Agenda]]
 
  [[2014_Summer_Project_Week#Agenda|Back to Summer project week Agenda]]
  
Presenters: Jean-Christophe Fillion-Robin
+
Presenters: Jean-Christophe Fillion-Robin, Steve Pieper
 +
 
 +
'''Slides source available here: https://github.com/jcfr/namic_projectweek_2014-06-23_slicerextensions_talk'''
 +
 
 +
'''Slides pdf available here: [https://github.com/jcfr/namic_projectweek_2014-06-23_slicerextensions_talk/blob/master/namic_projectweek_2014-06-23_slicerextensions_slides.pdf namic_projectweek_2014-06-23_slicerextensions_slides.pdf]'''
 +
 
  
 
== Background ==
 
== Background ==
  
A Slicer extension is a "package" bundling together one or more Slicer modules. Extensions can easily be installed using an "AppStore-like" interface known as the Extensions manager.
+
A Slicer extension is a "package" bundling together one or more Slicer modules. Extensions can easily be installed using an "AppStore-like" interface known as the [http://wiki.slicer.org/slicerWiki/index.php/Documentation/Nightly/SlicerApplication/ExtensionsManager Extensions manager].
  
 
Slicer supports three types of modules. While the developer has to choose between one of the three types to implement its module, the end user won't notice the difference as they all share the same look & feel. The choice for a given type of module is usually based on the type of inputs/parameters for a given module.
 
Slicer supports three types of modules. While the developer has to choose between one of the three types to implement its module, the end user won't notice the difference as they all share the same look & feel. The choice for a given type of module is usually based on the type of inputs/parameters for a given module.
Line 11: Line 16:
 
== Summary ==
 
== Summary ==
  
This presentation consists of an interactive demonstration of the creation of a python extension followed by a presentation of the overall extension infrastucture.
+
This presentation consists of an interactive demonstration of the creation of a python extension followed by a presentation of the overall extension infrastucture. (Jc, 50 minutes)
 +
 
 +
== Next Steps ==
 +
 
 +
Pointers to resources for developing the functionality of scripted, loadable, and CLI modules. (Steve, 10 minutes)
  
 
== Attendee Preparation ==
 
== Attendee Preparation ==
  
TBD
+
* Sign-up on [https://github.com/join Github].
 +
* Download [http://download.slicer.org recent nightly package] or [http://wiki.slicer.org/slicerWiki/index.php/Documentation/Nightly/Developers/Build_Instructions build Slicer] with [https://github.com/Slicer/Slicer/blob/33050e87401734191f95966cf5e856972c231723/CMakeLists.txt#L236 with OpenSSL support].

Latest revision as of 21:59, 24 June 2014

Home < 2014 Summer Project Week Breakout Session:SlicerExtensions
Back to Summer project week Agenda

Presenters: Jean-Christophe Fillion-Robin, Steve Pieper

Slides source available here: https://github.com/jcfr/namic_projectweek_2014-06-23_slicerextensions_talk

Slides pdf available here: namic_projectweek_2014-06-23_slicerextensions_slides.pdf


Background

A Slicer extension is a "package" bundling together one or more Slicer modules. Extensions can easily be installed using an "AppStore-like" interface known as the Extensions manager.

Slicer supports three types of modules. While the developer has to choose between one of the three types to implement its module, the end user won't notice the difference as they all share the same look & feel. The choice for a given type of module is usually based on the type of inputs/parameters for a given module.

Summary

This presentation consists of an interactive demonstration of the creation of a python extension followed by a presentation of the overall extension infrastucture. (Jc, 50 minutes)

Next Steps

Pointers to resources for developing the functionality of scripted, loadable, and CLI modules. (Steve, 10 minutes)

Attendee Preparation