<div dir="ltr">Hi Luke,<div><br></div><div>Yes, I see your point.</div><div><br></div><div>What comes to mind is to write a specialized Writer class that could</div><div>take as input a GroupSpatialObject, and inspect it for the presence</div>
<div>of itkLineSpatialObjects, then proceed to write them out as .vtk files.</div><div><br></div><div>It wouldn't fit initially into the IO Spatial framework (since that addresses</div><div>a much more generic case), but would allow you to address the </div>
<div>immediate issue at hand.</div><div><br></div><div>It could also be later transformed into a writer of GCode files,</div><div>and in this way provide dual use for supporting basic 3D printing ;-)</div><div><br></div>
<div>Please let us know if you would like to take a cut at writing such class,</div><div>maybe a:</div><div><br></div><div> itkGroupSpatialObjectVTKPolyLineWriter</div><div><br></div><div>we will be happy to assist you in the process.</div>
<div><br></div><div><br></div><div> Thanks</div><div><br></div><div><br></div><div> Luis</div><div><br></div><div> </div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Jan 23, 2014 at 1:11 PM, Luke Bloy <span dir="ltr"><<a href="mailto:luke.bloy@gmail.com" target="_blank">luke.bloy@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi Luis,<div><br></div><div>Thanks for the response.</div><div><br></div><div>So what you proposed is done. At least a method for converting LineSpatialObjects to vtkPolyLines has been written. but I make use of vtk objects and writers, so while it solves my problem I don't see an easy way to fit it into ITK? At least at the IO level, which is where it would be useful. A possible work around would be to add a class to vtkGlue that would convert a SpatialObject to a vtkPolydata? That being said maybe there isn't a lot of need for spatialObject to vtk compatibility?</div>
<span class="HOEnZb"><font color="#888888">
<div><br></div><div>-Luke</div><div><br></div><div><br></div></font></span></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Jan 23, 2014 at 9:10 AM, Luis Ibanez <span dir="ltr"><<a href="mailto:luis.ibanez@kitware.com" target="_blank">luis.ibanez@kitware.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi Luke<br><div class="gmail_extra"><br><br><div class="gmail_quote"><div>On Mon, Jan 20, 2014 at 3:25 PM, Luke Bloy <span dir="ltr"><<a href="mailto:luke.bloy@gmail.com" target="_blank">luke.bloy@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><br></div><div>I'm not sure how miserable it would be to have the SpatialObjectWriter support vtk output? It seems like that would be an ideal situation if it were possible.</div>
<div>
<br></div><div><br></div></div></blockquote><div><br></div></div><div>I agree with you.</div><div>It will certainly be very useful.</div><div><br></div><div>I would guess that writing a couple of special cases will be relatively easy,</div>
<div>and that writing the generic case (that can manage any SpatialObject)</div><div>will be an interesting challenge.</div><div><br></div><div>So, following the agile philosophy, it sounds like a good idea to write the</div>
<div>special case for writing out the LineSpatialObject (which should be relatively</div><div>simple), and then later grow from there.</div><div><br></div><div>This will also take care of the current itch :-)</div><div>
<br></div><div>If you would like to give it a try at writing that initial class,</div><div>we will be happy to assist you.</div><div><br></div><div><br></div><div> HTH</div><span><font color="#888888"><div>
<br></div><div><br></div><div> Luis</div>
<div><br></div><div><br></div></font></span></div></div></div>
</blockquote></div><br></div>
</div></div></blockquote></div><br></div>