Difference between revisions of "2013 Summer Project Week Breakout Session:SlicerExtensions"
From NAMIC Wiki
m (→Q&A) |
m (Text replacement - "http://www.slicer.org/slicerWiki/index.php/" to "https://www.slicer.org/wiki/") |
||
| (7 intermediate revisions by 2 users not shown) | |||
| Line 4: | Line 4: | ||
== Before the breakout session == | == Before the breakout session == | ||
| − | * Complete the [ | + | * Complete the [https://www.slicer.org/wiki/Documentation/Nightly/Developers/StartHere New community member checklist] |
| − | * [ | + | * [https://www.slicer.org/wiki/Documentation/Nightly/Developers/Build_Instructions 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''' | '''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''' | ||
| Line 12: | Line 12: | ||
== Goal == | == 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). | + | * 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 [ | + | * We will go through the [https://www.slicer.org/wiki/Documentation/Nightly/Developers/Tutorials/BuildTestPackageDistributeExtensions 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. | + | * Finally we'll go through the list of questions reported below and look at how the current system could be improved. |
| − | == Q&A == | + | == 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 [ | + | ''Do not hesitate to edit this page and add more questions. Before doing so, make also sure to scan through the existing [https://www.slicer.org/wiki/Documentation/Nightly/FAQ/Extensions user] and [https://www.slicer.org/wiki/Documentation/Nightly/Developers/FAQ/Extensions developer] extension FAQs'' |
=== How much of slicer's core infrastructure should be used by extensions ? === | === How much of slicer's core infrastructure should be used by extensions ? === | ||
| − | + | <pre> | |
| − | < | ||
From Andra Lasso: Currently the picture is quite mixed: | From Andra Lasso: Currently the picture is quite mixed: | ||
: Source control: separate for all extensions | : Source control: separate for all extensions | ||
| Line 34: | Line 33: | ||
: 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) | ||
| − | + | </pre> | |
=== Can you make a python scripted extension without a built version of slicer ? === | === Can you make a python scripted extension without a built version of slicer ? === | ||
| + | |||
| + | === Is the API key only used for 'make Experimental' and 'make ExperimentalUpload'? === | ||
| + | |||
| + | === Slicer only allows to download extensions that are build against the same Slicer svn revision. If an extension is built against Slicer which was downloaded from github, will Slicer recognize in that that specific version of Slicer matches the version of Slicer that was used to compile the extension? (ie: if I build the extension against a version of Slicer (downloaded from github) on my computer, can I download that extension in that same Slicer?)=== | ||
| + | |||
| + | === Is there some documentation that explains how to upload and use test data from a server? === | ||
Latest revision as of 17:17, 10 July 2017
Home < 2013 Summer Project Week Breakout Session:SlicerExtensionsBack to Summer project week Agenda
Contents
- 1 Before the breakout session
- 2 Goal
- 3 Q&A / Group discussion
- 3.1 How much of slicer's core infrastructure should be used by extensions ?
- 3.2 Can you make a python scripted extension without a built version of slicer ?
- 3.3 Is the API key only used for 'make Experimental' and 'make ExperimentalUpload'?
- 3.4 Slicer only allows to download extensions that are build against the same Slicer svn revision. If an extension is built against Slicer which was downloaded from github, will Slicer recognize in that that specific version of Slicer matches the version of Slicer that was used to compile the extension? (ie: if I build the extension against a version of Slicer (downloaded from github) on my computer, can I download that extension in that same Slicer?)
- 3.5 Is there some documentation that explains how to upload and use test data from a server?
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)
