2013 Summer Project Week Breakout Session:SlicerExtensions

Back to Summer project week Agenda

Before the breakout session

• Complete the New community member checklist

• Build Slicer revision >= 22100 with default options

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).

Tutorial: http://www.slicer.org/slicerWiki/index.php/Documentation/Nightly/Developers/Tutorials/BuildTestPackageDistributeExtensions

Then 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

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

From Andra Lasso: Currently the picture is quite mixed:

Source control: separate for all extensions

Issue tracking: separate for most extensions

Module documentation: shared between Slicer core and extensions

(extensions appear in a different section)

Hosting of binary releases: shared between Slicer core and extensions

(extensions appear in a different category)

Dashboard: shared between Slicer core and extensions (extensions appear in

a different category)

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