Difference between revisions of "Developer Meetings/20121002"
From Slicer Wiki
| Line 11: | Line 11: | ||
* Support of new data types implemented in extensions | * Support of new data types implemented in extensions | ||
** Andrey: I would like to know how feasible/difficult it is to have a new type of MRML node that will be possible to add as a new item to "Add data"/"Save data" dialog. Is this extensible from an extension? We need to have this capability to provide consistent user experience (this is also Ron's request/strong suggestion for Reporting module) | ** Andrey: I would like to know how feasible/difficult it is to have a new type of MRML node that will be possible to add as a new item to "Add data"/"Save data" dialog. Is this extensible from an extension? We need to have this capability to provide consistent user experience (this is also Ron's request/strong suggestion for Reporting module) | ||
| + | * Greg: Why is Slicer extension documentation hosted on github, instead of slicer.org? | ||
== Conclusion == | == Conclusion == | ||
Revision as of 22:00, 3 August 2012
Home < Developer Meetings < 20121002Attendees:
To discuss
- Create a 'developer sandbox' extension index
- Support continuous builds so developers can test
- cross-platform builds
- extension installation issues
- Support nightly builds so new experimental extensions can be delivered to users
- https://gist.github.com/3171634
- Support continuous builds so developers can test
- Support of new data types implemented in extensions
- Andrey: I would like to know how feasible/difficult it is to have a new type of MRML node that will be possible to add as a new item to "Add data"/"Save data" dialog. Is this extensible from an extension? We need to have this capability to provide consistent user experience (this is also Ron's request/strong suggestion for Reporting module)
- Greg: Why is Slicer extension documentation hosted on github, instead of slicer.org?
