Difference between revisions of "Developer Meetings/20131126"
From Slicer Wiki
m (→Conclusion) |
m (→To discuss) |
||
Line 1: | Line 1: | ||
== To discuss == | == To discuss == | ||
+ | * SimpleITK v0.7.1 | ||
+ | ** a couple bug fixes | ||
* Refactoring of RemoteIO. See below | * Refactoring of RemoteIO. See below | ||
* Extension and dependency on ITKDeprecated and ITKV3Compatibility library | * Extension and dependency on ITKDeprecated and ITKV3Compatibility library | ||
− | |||
− | |||
== News & Update == | == News & Update == |
Revision as of 21:24, 26 November 2013
Home < Developer Meetings < 20131126To discuss
- SimpleITK v0.7.1
- a couple bug fixes
- Refactoring of RemoteIO. See below
- Extension and dependency on ITKDeprecated and ITKV3Compatibility library
News & Update
- Support for Slicer_USE_SYSTEM_* options
In progress
- Integration of LandmarkRegistration in trunk
Usage of RemoteIO in Slicer
I notice that the only reason we depend on curl is for existence of RemoteIO library that has been "replaced" by SampleData and DataStore. I really like the concept of registering URI that could be downloaded that is why we should keep the infrastructure in place. That said, I was thinking to get remove the following classes: vtkHIDHandler.h vtkHIDTagTable.h vtkSRBHandler.h vtkXNATHandler.h vtkXNDHandler.h vtkXNDTagTable.h Then, we could implement a Qt based vtkHTTPHandler handler, that way we could simply remove the curl dependency. In the mean time, I would also remove the FetchMI logic which is not maintained or used at that point. Let me know what you think, Jc
Conclusion
- Bump:
- ITK tag to
4.5rc01
- SimpleITK to release branch
a2b29110771a
- ITK tag to
- Steve: Slicer AHM Tutorial related to wrapping of custom class using SimpleITK ?
- Brad: The underlying infrastructure is not yet ready to support this. We should provide some requirement / use case.