Difference between revisions of "Developer Meetings/20140527"
From Slicer Wiki
m (→Conclusion) |
|||
| (One intermediate revision by the same user not shown) | |||
| Line 4: | Line 4: | ||
== Conclusion == | == Conclusion == | ||
| − | * Extensions: | + | * Extensions: We will add a convenience launcher to allow easy use of the ExtensionWizard (Jc & Matt W.) |
* SubjectHierarchy: Csaba will rebase the commits and then integrate into Slicer core | * SubjectHierarchy: Csaba will rebase the commits and then integrate into Slicer core | ||
| − | * Matt will look at jsonld and finalize integration of the parameter serializer | + | * Matt M. will look at jsonld and finalize integration of the parameter serializer |
* Update of Teem version | * Update of Teem version | ||
** Currently using teem-1.1.10 (Dec 10, 2008) built from source. See [https://github.com/Slicer/Slicer/blob/3c4dc4490488e545c354472521f634a786f121c6/SuperBuild/External_teem.cmake#L47 here] | ** Currently using teem-1.1.10 (Dec 10, 2008) built from source. See [https://github.com/Slicer/Slicer/blob/3c4dc4490488e545c354472521f634a786f121c6/SuperBuild/External_teem.cmake#L47 here] | ||
| Line 13: | Line 13: | ||
** Question to address: | ** Question to address: | ||
*** In case we depend on teem master/trunk/release-branch ... is there a github repo that could be forked and would make contribution of fixes easier ? | *** In case we depend on teem master/trunk/release-branch ... is there a github repo that could be forked and would make contribution of fixes easier ? | ||
| − | *** vtkTeem: In Slicer we are maintaining a layer allowing to easily | + | *** vtkTeem: In Slicer we are maintaining a layer allowing to easily expose teem by integrating VTK and teem. See [https://github.com/Slicer/Slicer/tree/master/Libs/vtkTeem here], should we change anything ? |
*** vtkTeem: Should this later be maintained in a dedicated repository ? With it own dashboard and testing infrastructure ? | *** vtkTeem: Should this later be maintained in a dedicated repository ? With it own dashboard and testing infrastructure ? | ||
Latest revision as of 19:01, 27 May 2014
Home < Developer Meetings < 20140527To discuss
- Review Roadmap and issue tracker
- Open discussion, Q&A
Conclusion
- Extensions: We will add a convenience launcher to allow easy use of the ExtensionWizard (Jc & Matt W.)
- SubjectHierarchy: Csaba will rebase the commits and then integrate into Slicer core
- Matt M. will look at jsonld and finalize integration of the parameter serializer
- Update of Teem version
- Currently using teem-1.1.10 (Dec 10, 2008) built from source. See here
- The idea would be to use teem-1.1.11 when available ? or teem trunk ?
- Raul will check with Gordon what is the status.
- Question to address:
- In case we depend on teem master/trunk/release-branch ... is there a github repo that could be forked and would make contribution of fixes easier ?
- vtkTeem: In Slicer we are maintaining a layer allowing to easily expose teem by integrating VTK and teem. See here, should we change anything ?
- vtkTeem: Should this later be maintained in a dedicated repository ? With it own dashboard and testing infrastructure ?
