Difference between revisions of "2013 Summer Project Week Breakout Session:SlicerExtensions"
From NAMIC Wiki
(Created page with ' == Topics requested by the community == How much of slicer's core infrastructure should be used by extensions? From Andra Lasso: Currently the picture is quite mixed: * Source …') |
|||
| Line 2: | Line 2: | ||
== Topics requested by the community == | == Topics requested by the community == | ||
| + | ===Infrastructure=== | ||
How much of slicer's core infrastructure should be used by extensions? | 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: | ||
| Line 12: | Line 13: | ||
* Dashboard: shared between Slicer core and extensions (extensions appear in | * Dashboard: shared between Slicer core and extensions (extensions appear in | ||
a different category) | a different category) | ||
| + | ===Simplifying the process=== | ||
| + | * Can you make a python scripted extension without a built version of slicer? | ||
Revision as of 17:04, 8 May 2013
Home < 2013 Summer Project Week Breakout Session:SlicerExtensions
Topics requested by the community
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)
Simplifying the process
- Can you make a python scripted extension without a built version of slicer?
