[vtk-developers] Fwd: vtkOFFReader / VTK archive system

[David Doria]

Forwarded conversation
Subject: vtkOFFReader
------------------------

From: *David Doria* <daviddoria+vtk at gmail.com <daviddoria%2Bvtk at gmail.com>>
Date: Thu, Oct 15, 2009 at 10:34 AM
To: VTK Developers <vtk-developers at vtk.org>


I wrote a VTK reader for simple .off files (
http://people.sc.fsu.edu/~burkardt/data/off/off.html<http://people.sc.fsu.edu/%7Eburkardt/data/off/off.html>
).
It only handles triangle meshes for now.
http://www.rpi.edu/~doriad/VTK_List/vtkOFFReader/<http://www.rpi.edu/%7Edoriad/VTK_List/vtkOFFReader/>

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.

Thanks,

David

----------
From: *David Gobbi* <david.gobbi at gmail.com>
Date: Thu, Oct 15, 2009 at 3:28 PM
To: David Doria <daviddoria+vtk at gmail.com <daviddoria%2Bvtk at gmail.com>>
Cc: VTK Developers <vtk-developers at vtk.org>


I'm all for VTK supporting as many file formats as possible, but only
if the readers support at least the baseline prescribed for the
format.  For many years the old vtkTIFFReader was far below baseline,
and could barely read any of the TIFF files out there.  I'd rather not
see a repeat of that unfortunate situation, with people wasting hours
struggling to understand why the vtkTIFFReader refused to read their
TIFF files.

If it's incomplete, It's best to just advertise it and put the code
out there, as you have done.

  David
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Follow this link to subscribe/unsubscribe:
> http://www.vtk.org/mailman/listinfo/vtk-developers
>
>
>

----------
From: *Sean McBride* <sean at rogue-research.com>
Date: Fri, Oct 16, 2009 at 12:31 AM
To: David Gobbi <david.gobbi at gmail.com>, David Doria <
daviddoria+vtk at gmail.com <daviddoria%2Bvtk at gmail.com>>
Cc: VTK Developers <vtk-developers at vtk.org>


Maybe VTK needs a /Review directory, like ITK has.  A place for this
type of code to live, be shared, and be improved.

--
____________________________________________________________
Sean McBride, B. Eng                 sean at rogue-research.com
Rogue Research                        www.rogue-research.com
Mac Software Developer              Montréal, Québec, Canada




----------
From: *Mathieu Malaterre* <mathieu.malaterre at gmail.com>
Date: Fri, Oct 16, 2009 at 3:07 AM
To: Sean McBride <sean at rogue-research.com>
Cc: David Gobbi <david.gobbi at gmail.com>, David Doria <
daviddoria+vtk at gmail.com <daviddoria%2Bvtk at gmail.com>>, VTK Developers <
vtk-developers at vtk.org>


Can't this be done using the IJ ?

2cts
--
Mathieu

----------------------------

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.

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)?

Thanks,

David
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/vtk-developers/attachments/20091016/e7d3e7da/attachment.html>