Difference between revisions of "2013 Summer Project Week Breakout Session:SlicerExtensions"
m (→Goal) |
|||
Line 14: | Line 14: | ||
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). | 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 [http://www.slicer.org/slicerWiki/index.php/Documentation/Nightly/Developers/Tutorials/BuildTestPackageDistributeExtensions updated Slicer wiki documentation], then attendees will install extension developed and published by the other attendees. | |
− | |||
− | |||
+ | Then we'll go through the list of questions reported below and look at how the current system could be improved. | ||
== Q&A == | == Q&A == |
Revision as of 19:47, 13 June 2013
Home < 2013 Summer Project Week Breakout Session:SlicerExtensionsBack to Summer project week Agenda
Contents
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.
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. Before doing so, make also sure to scan through the existing Template:Documentation/version/FAQ/Extensions user and Template:Documentation/version/Developers/FAQ/Extensions developer extension FAQs