<div class="gmail_quote"><span style="font-size: large; font-weight: bold;">Forwarded conversation</span><br>Subject: <b class="gmail_sendername">vtkOFFReader</b><br>------------------------<br><br><span class="undefined"><font color="#000000">From: <b class="undefined">David Doria</b> <span dir="ltr"><<a href="mailto:daviddoria%2Bvtk@gmail.com">daviddoria+vtk@gmail.com</a>></span><br>
Date: Thu, Oct 15, 2009 at 10:34 AM<br>To: VTK Developers <<a href="mailto:vtk-developers@vtk.org">vtk-developers@vtk.org</a>><br></font><br></span><br>I wrote a VTK reader for simple .off files (<a href="http://people.sc.fsu.edu/%7Eburkardt/data/off/off.html" target="_blank">http://people.sc.fsu.edu/~burkardt/data/off/off.html</a>).<br>
It only handles triangle meshes for now.<br><a href="http://www.rpi.edu/%7Edoriad/VTK_List/vtkOFFReader/" target="_blank">http://www.rpi.edu/~doriad/VTK_List/vtkOFFReader/</a><br>
<br>Does VTK have any interest in supporting this format? It seems like it would be good to allow users to read as many formats as possible, even if they are only weakly/partially supported.<br><br clear="all">Thanks,<br>
<font color="#888888">
<br>David<br>
</font><br>----------<br><span class="undefined"><font color="#000000">From: <b class="undefined">David Gobbi</b> <span dir="ltr"><<a href="mailto:david.gobbi@gmail.com">david.gobbi@gmail.com</a>></span><br>Date: Thu, Oct 15, 2009 at 3:28 PM<br>
To: David Doria <<a href="mailto:daviddoria%2Bvtk@gmail.com">daviddoria+vtk@gmail.com</a>><br>Cc: VTK Developers <<a href="mailto:vtk-developers@vtk.org">vtk-developers@vtk.org</a>><br></font><br></span><br>I'm all for VTK supporting as many file formats as possible, but only<br>
if the readers support at least the baseline prescribed for the<br>
format. For many years the old vtkTIFFReader was far below baseline,<br>
and could barely read any of the TIFF files out there. I'd rather not<br>
see a repeat of that unfortunate situation, with people wasting hours<br>
struggling to understand why the vtkTIFFReader refused to read their<br>
TIFF files.<br>
<br>
If it's incomplete, It's best to just advertise it and put the code<br>
out there, as you have done.<br>
<br>
David<br>
<div><div></div></div>> _______________________________________________<br>
> Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
><br>
> Visit other Kitware open-source projects at<br>
> <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
><br>
> Follow this link to subscribe/unsubscribe:<br>
> <a href="http://www.vtk.org/mailman/listinfo/vtk-developers" target="_blank">http://www.vtk.org/mailman/listinfo/vtk-developers</a><br>
><br>
><br>
><br>
<br>----------<br><span class="undefined"><font color="#000000">From: <b class="undefined">Sean McBride</b> <span dir="ltr"><<a href="mailto:sean@rogue-research.com">sean@rogue-research.com</a>></span><br>Date: Fri, Oct 16, 2009 at 12:31 AM<br>
To: David Gobbi <<a href="mailto:david.gobbi@gmail.com">david.gobbi@gmail.com</a>>, David Doria <<a href="mailto:daviddoria%2Bvtk@gmail.com">daviddoria+vtk@gmail.com</a>><br>Cc: VTK Developers <<a href="mailto:vtk-developers@vtk.org">vtk-developers@vtk.org</a>><br>
</font><br></span><br>Maybe VTK needs a /Review directory, like ITK has. A place for this<br>
type of code to live, be shared, and be improved.<br>
<font color="#888888"><br>
--<br>
____________________________________________________________<br>
Sean McBride, B. Eng <a href="mailto:sean@rogue-research.com">sean@rogue-research.com</a><br>
Rogue Research <a href="http://www.rogue-research.com" target="_blank">www.rogue-research.com</a><br>
Mac Software Developer Montréal, Québec, Canada<br>
<br>
<br>
<br>
</font><br>----------<br><span class="undefined"><font color="#000000">From: <b class="undefined">Mathieu Malaterre</b> <span dir="ltr"><<a href="mailto:mathieu.malaterre@gmail.com">mathieu.malaterre@gmail.com</a>></span><br>
Date: Fri, Oct 16, 2009 at 3:07 AM<br>To: Sean McBride <<a href="mailto:sean@rogue-research.com">sean@rogue-research.com</a>><br>Cc: David Gobbi <<a href="mailto:david.gobbi@gmail.com">david.gobbi@gmail.com</a>>, David Doria <<a href="mailto:daviddoria%2Bvtk@gmail.com">daviddoria+vtk@gmail.com</a>>, VTK Developers <<a href="mailto:vtk-developers@vtk.org">vtk-developers@vtk.org</a>><br>
</font><br></span><br>Can't this be done using the IJ ?<br>
<br>
2cts<br>
--<br>
<font color="#888888">Mathieu<br>
</font><br>----------------------------<br><br>The IJ is nice, but it seems rare (from my limited experience) that someone actual improves and resubmits code. I feel like developers would be much more likely to make a few improvements and then simply type "commit" than to repackage the whole thing for resubmission including updates to the tex paper etc. It also seems a bit silly to make a submission to such a journal with a 100 line source file and an even shorter "article" simply saying "this class can read basic OFF files". If that's the recommended process though, I'll partake.<br>
<br>Another thing (@David Gobbi) - sending these things to the list (as I did and you recommended) is a good idea, but I frequently hear people complaining about how the list is hard to search, etc. Also, the link to the files will certainly die at some point, at which point it is clearly no longer useful. To use the mailing list for archival, I guess you'd have to copy/paste code into an email, which seems like a bad idea. If not a Review directory, then what about an ftp server or something where at least these things can be archived in a semi-maintained place (at least one that won't accidentally die)?<br>
<br>Thanks,<br><br>David<br></div>