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

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 / Group discussion

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 ?

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)