Hi Folks, <br><br>Thanks for your feedback.<br><br>As I am writing this email, the MidasClient library is added
(thanks to Zach) to the regular MIDAS git repo and there will be will an
option to just build or test just the midas client library.<br><br>It means there will be no DataManagement library related to Midas within CTK.<br><br>Jc<br><br><div class="gmail_quote">On Fri, Oct 14, 2011 at 1:11 PM, Steve Pieper <span dir="ltr"><<a href="mailto:pieper@ibility.net" target="_blank">pieper@ibility.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">Hi Jc and all - <br><br>I'll be curious to hear what others have to say about this too - but I'd say my first reaction is to wonder if MIDAS 'common' enough (yet) to be part of CTK? I know we want to use MIDAS in slicer and ITK, but I wonder if we could enumerate other potential users who would benefit from having MIDAS support in CTK to help guide the discussion?<br>
<br>Regarding the idea of an abstracted layer that would support xnat/midas/ftp/dicom I would say that is harder in practice than I wish it were. Love it or Hate it, I have found that DICOM has a lot of unique aspects that we need to deal with explicitly if we are to present a usable interface and correctly interpret the image data and other content. It was one of the original goals of CTK to improve the ability of our applications to be more 'correct' in order to better interoperate with the medical imaging world at large. Finding the sweet spot between flexibility and ease of use is hard enough for DICOM alone without adding additional complexity IMHO :) If you have an architecture or plan for an abstraction layer it would be great to discuss.<br>
<br>-Steve<br><br><br><br><br><br><div class="gmail_quote"><div><div></div><div>On Fri, Oct 14, 2011 at 12:19 PM, Jean-Christophe Fillion-Robin <span dir="ltr"><<a href="mailto:jchris.fillionr@kitware.com" target="_blank">jchris.fillionr@kitware.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div><div></div><div>Hi Folks, <br><br>Three month ago, I already talked about possibly adding a DataManagement library into CTK. <br>
<br>The aim of that library would be to provide an abstraction for application willing to download / upload / browse data available on remote location.<br>
<br>As expressed earlier, we don't want CTK to become a <i>"Zoo of libraries with inconsistent</i><i> 'Look and Feel</i>'" [1]. This is something we are considering carefully. You will find below some background facts and questions.<br>
<br>* Zach from Kitware has been working a topic branch where he pushed its work: <a href="https://github.com/zachmullen/CTK/commits/add-midascpp-library" target="_blank">https://github.com/zachmullen/CTK/commits/add-midascpp-library</a><br>
<br>* The MIDAS team is actively developing an application named "MIDASDesktop" [2] that depends on CTK, and by extension, also depends on CTKDataManagementMidasClient{Core, Widget} libraries.<br><br>* CTKDataManagementMidasClient{Core, Widget} libraries do not depend on CTKCore or CTKWidgets<br>
<br>* On medium/long term, I envisioned:<br> - to have an abstracted layer that would provide us with a way to download/upload/browse data available on either a DICOM Pacs, a Midas server, a XNAT server, a FTP server, etc ... The user would basically input a URI and associated with the appropriate ServerType. <br>
- that ServerType would corresponds to a plugin providing a specific implementation<br> - that an appropriate level of abstraction could be reached especially considering the fact that data are "just blob" with associated meta data.<br>
- to possibly move DICOM code into, for example, Libs/DataManagement ? <br><br>* This <b>coming Monday</b>, within Kitware we will do a <b>one-day hackfest</b> to
consolidate this library. To move in the appropriate direction, I am
seeking your input to help addressing the following questions:<br><br> 1) What are your thought regarding the "medium/long term goal" I mentioned above ? <br><br> 2) As of today, does it make sens to add a library named DataManagement/MidasClient into CTK ? <br>
<br><br>This coming Monday, ...<br><br>... if we agree on including such library into CTK: I will work on reviewing the library to make sure it meets our standards and coding style<br><br>... If we do NOT reach consensus:I will create a separate project that would be hosted on Midas organization.<br>
<br><br>Thanks for your input, <br>Jc<br><br>Ps: If you reply to that email, make sure to use "reply to all" so that Patrick and Zach stay included in this email thread.<br><br><br>[1] <a href="http://public.kitware.com/pipermail/ctk-developers/2011-June/000615.html" target="_blank">http://public.kitware.com/pipermail/ctk-developers/2011-June/000615.html</a><br>
[2] <a href="http://www.kitware.com/midaswiki/index.php/MIDASDesktop" target="_blank">http://www.kitware.com/midaswiki/index.php/MIDASDesktop</a><br clear="all"><font color="#888888"><br>-- <br><a href="tel:%2B1%20919%20869%208849" value="+19198698849" target="_blank">+1 919 869 8849</a><br>
<br>
</font><br></div></div>_______________________________________________<br>
Ctk-developers mailing list<br>
<a href="mailto:Ctk-developers@commontk.org" target="_blank">Ctk-developers@commontk.org</a><br>
<a href="http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers" target="_blank">http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers</a><br>
<br></blockquote></div><br>
</blockquote></div><br><br clear="all"><br>-- <br><a href="tel:%2B1%20919%20869%208849" value="+19198698849" target="_blank">+1 919 869 8849</a><br><br>