Developer Meetings/20131126 - Revision history

JChris.FillionR: /* Usage of RemoteIO in Slicer */

2013-11-26T23:15:52Z

Usage of RemoteIO in Slicer

JChris.FillionR: /* Usage of RemoteIO in Slicer */

2013-11-26T23:14:48Z

Usage of RemoteIO in Slicer

JChris.FillionR: /* Usage of RemoteIO in Slicer */

2013-11-26T23:14:01Z

Usage of RemoteIO in Slicer

JChris.FillionR: /* To discuss */

2013-11-26T21:24:05Z

To discuss

JChris.FillionR: /* Conclusion */

2013-11-26T21:20:34Z

Conclusion

JChris.FillionR: /* Conclusion */

2013-11-26T21:18:14Z

Conclusion

JChris.FillionR at 21:16, 26 November 2013

2013-11-26T21:16:45Z

Blowekamp: /* To discuss */

2013-11-26T18:15:58Z

To discuss

JChris.FillionR: Created page with '== To discuss == * Refactoring of RemoteIO. See below * Extension and dependency on ITKDeprecated and ITKV3Compatibility library == News & Update == * Support for Slicer_USE_SYS…'

2013-11-26T17:32:05Z

Created page with '== To discuss == * Refactoring of RemoteIO. See below * Extension and dependency on ITKDeprecated and ITKV3Compatibility library == News & Update == * Support for Slicer_USE_SYS…'

New page

== To discuss ==
* 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 [https://github.com/pieper/LandmarkRegistration LandmarkRegistration] in trunk

== Usage of RemoteIO in Slicer ==

<pre>
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
</pre>

@@ Line 17: / Line 17: @@
 <pre>
 (1) Jc - Nov 26, 2013
-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 notice that the only reason we depend on curl is for existence
-I really like the concept of registering URI that could be downloaded that is why we should keep the infrastructure in place.
+I really like the concept of registering URI that could be
 That said, I was thinking to get remove the following classes:
@@ Line 33: / Line 35: @@
 vtkXNDTagTable.h
-Then, we could implement a Qt based  vtkHTTPHandler handler, that way we could simply remove the curl dependency.
+Then, we could implement a Qt based  vtkHTTPHandler handler, that
-In the mean time, I would also remove the FetchMI logic which is not maintained or used at that point.
+In the mean time, I would also remove the FetchMI logic which is
 Let me know what you think,
@@ Line 42: / Line 46: @@
 (2) Andras - Nov 26, 2013
-It’s always a good idea to make the core smaller and simpler, so I support the idea of getting rid of unused classes and unnecessary dependencies.
+It’s always a good idea to make the core smaller and simpler, so
-We planned to use curl for uploading training results in a .zip file to Moodle, but I guess we can add curl to our module then.
+We planned to use curl for uploading training results in a .zip
 // --------------------
@@ Line 51: / Line 58: @@
 Thanks for commenting.
-If your module is a loadable or a scripted module, all "curl" functionality can be provided by Qt. Would that work for you ?
+If your module is a loadable or a scripted module, all "curl"
 // --------------------
 (4) Andras - Nov 26, 2013
-We would need quite complex curl functionalities for uploading data, see the scripts below:
+We would need quite complex curl functionalities for uploading data,
 https://gist.github.com/Joshkunz/4516316
@@ Line 71: / Line 80: @@
    (1) remove dependency of Slicer core against curl
-   (2) Only, build both the Curl library and the curl executable, keeping them in the package.
+   (2) Only, build both the Curl library and the curl executable, keeping
 That way, it would provide great flexibility with minimum overhead.
@@ Line 80: / Line 90: @@
 Sounds like an excellent plan.
-Yes, I like the design of the remote IO support in MRML, but it's not being used and is great to simplify wherever possible.  FetchMI can go away for now, with the hope that we'll reproduce and improve on it in the future (someday).
+Yes, I like the design of the remote IO support in MRML, but it's not
+ being used and is great to simplify wherever possible.  FetchMI can
 </pre>

@@ Line 18: / Line 18: @@
 // --------------------
-Jc - Nov 26, 2013
+(1) Jc - Nov 26, 2013
 I notice that the only reason we depend on curl is for existence of RemoteIO library that has been "replaced" by SampleData and DataStore.
@@ Line 38: / Line 38: @@
 Let me know what you think,
 // --------------------
-Andras - Nov 26, 2013
+(2) Andras - Nov 26, 2013
 It’s always a good idea to make the core smaller and simpler, so I support the idea of getting rid of unused classes and unnecessary dependencies.
@@ Line 48: / Line 47: @@
 // --------------------
-Jc - Nov 26, 2013
+(3) Jc - Nov 26, 2013
 Thanks for commenting.
@@ Line 55: / Line 54: @@
 // --------------------
-Andras - Nov 26, 2013
+(4) Andras - Nov 26, 2013
 We would need quite complex curl functionalities for uploading data, see the scripts below:
@@ Line 66: / Line 65: @@
 // --------------------
-Jc - Nov 26, 2013
+(5) Jc - Nov 26, 2013
 Good point. The plan would then be to:
@@ Line 77: / Line 76: @@
 // --------------------
-Steve - Nov 26, 2013
+(6) Steve - Nov 26, 2013
 Sounds like an excellent plan.

← Older revision		Revision as of 21:20, 26 November 2013
Line 42:		Line 42:
	** ITK tag to <code>4.5rc01</code>		** ITK tag to <code>4.5rc01</code>
	** SimpleITK to release branch <code>a2b29110771a</code>		** SimpleITK to release branch <code>a2b29110771a</code>
		+
		+	* 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.

← Older revision		Revision as of 21:18, 26 November 2013
Line 39:		Line 39:
	== Conclusion ==		== Conclusion ==

−	* Bump ITK tag to 4.5rc01 ~~and~~ SimpleITK release branch	+	* Bump:
		+	** ITK tag to <code>4.5rc01</code>
		+	** SimpleITK to release branch <code>a2b29110771a</code>

← Older revision		Revision as of 21:16, 26 November 2013
Line 36:		Line 36:
	Jc		Jc
	</pre>		</pre>
		+
		+	== Conclusion ==
		+
		+	* Bump ITK tag to 4.5rc01 and SimpleITK release branch

@@ Line 1: / Line 1: @@
 == To discuss ==
 * Refactoring of RemoteIO. See below
 * Extension and dependency on ITKDeprecated and ITKV3Compatibility library
 == News & Update ==