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

From NAMIC Wiki
Jump to: navigation, search
Line 20: Line 20:
 
== Q&A ==
 
== Q&A ==
  
''Do not hesitate to edit this page and add more questions. Before doing so, make also sure to scan through the existing [http://www.slicer.org/slicerWiki/index.php/Documentation/{{documentation/version}}/FAQ/Extensions user] and [http://www.slicer.org/slicerWiki/index.php/Documentation/{{documentation/version}}/Developers/FAQ/Extensions developer] extension FAQs''
+
''Do not hesitate to edit this page and add more questions. Before doing so, make also sure to scan through the existing [http://www.slicer.org/slicerWiki/index.php/Documentation/Nightly/FAQ/Extensions user] and [http://www.slicer.org/slicerWiki/index.php/Documentation/Nightly/Developers/FAQ/Extensions developer] extension FAQs''
  
 
=== How much of slicer's core infrastructure should be used by extensions ? ===
 
=== How much of slicer's core infrastructure should be used by extensions ? ===

Revision as of 19:54, 13 June 2013

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


Before the breakout session

Important: Since building Slicer can be network intensive and can take between 1hr and 3hrs, make sure to build it before coming to the Project week

Goal

During the breakout session we will walk through the resources available for creating, building and distributing extension in Slicer 4. It is based on a build of Slicer r22100 and the wiki documentation as of project week (June 17, 2013).

We will go through the updated Slicer wiki documentation, then attendees will install extension developed and published by the other attendees.

Finally we'll go through the list of questions reported below and look at how the current system could be improved.

Q&A

Do not hesitate to edit this page and add more questions. Before doing so, make also sure to scan through the existing user and developer extension FAQs

How much of slicer's core infrastructure should be used by extensions ?

Can you make a python scripted extension without a built version of slicer ?