Difference between revisions of "2013 Summer Project Week Breakout Session:SlicerExtensions"
From NAMIC Wiki
m |
m |
||
| Line 18: | Line 18: | ||
''Do not hesitate to edit this page and add more questions'' | ''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: | 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) | (extensions appear in a different section) | ||
| − | + | : Hosting of binary releases: shared between Slicer core and extensions | |
(extensions appear in a different category) | (extensions appear in a different category) | ||
| − | + | : Dashboard: shared between Slicer core and extensions (extensions appear in | |
a different category) | a different category) | ||
| − | + | * Process: Can you make a python scripted extension without a built version of slicer ? | |
Revision as of 19:12, 13 June 2013
Home < 2013 Summer Project Week Breakout Session:SlicerExtensionsBack to Summer project week Agenda
Before the breakout session
- Complete the New community member checklist
- Build Slicer revision >= 22100 with default options
During the breakout session
- What is an extension ?
- How to
We will follow the updated documentation and
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 ?
