[vtkusers] The VTK Journal-New Submission

[Mike Jackson]

<sarcasm>
Because polydata => mapper => actor => renderer => renderWindows =>
OBJexporter is MUCH more intuitive and easy to figure out than
polydata=>objWriter.
</sarcasm>

There are many times where I setup a "conversion" pipeline in order to
read in some data (stack of images) and convert those to surface
meshes. A vtkRenderWindow is not an option on some systems.

 There are other Writers (such as STL and others) that do NOT need a
vtkRenderWindow in order to write the file. Why would the same be
needed for obj?
_________________________________________________________
Mike Jackson                  mike.jackson at bluequartz.net
BlueQuartz Software                    www.bluequartz.net
Principal Software Engineer                  Dayton, Ohio



On Sat, Jan 30, 2010 at 3:39 AM, Alexandre GOUAILLARD
<agouaillard at gmail.com> wrote:
> hi david,
>
> obj, as vrml is supposed to handle complete scenes. That explain the
> original difference between Reader/Writer of objects and
> Importer/Exporter of scenes.
>
> I know that obj is often used to store mesh objects only, but was it
> really necessary to add a class that somehow duplicate existing
> feature? I say that naively without having read your paper first, feel
> free to throw a stone at me :-)
>
> Basically you would have this:
> polydata => objwriter
>
> instead of that:
> polydata => mapper => actor => renderer => renderWindows => OBJexporter
>
> and it would only be interesting in the case where you only have a
> single polydata, and/or when you have a polydata processing pipeline
> that would not otherwise require a graphic pipeline,
>
> correct?
>
> alex.
>
> On Fri, Jan 29, 2010 at 11:01 PM, David Doria <daviddoria+vtk at gmail.com> wrote:
>> On Fri, Jan 29, 2010 at 9:57 AM, Francois Bertel
>> <francois.bertel at kitware.com> wrote:
>>> Hello,
>>>
>>> How is it different from VTK/Rendering/vtkOBJExporter ?
>>>
>>> On Fri, Jan 29, 2010 at 9:49 AM, VTK Journal
>>> <webmaster at insightsoftwareconsortium.org> wrote:
>>>> Hello,
>>>> A new submission has been added to the VTK Journal.
>>>>
>>>> Title: A Wavefront OBJ Writer for VTK
>>>> Author(s): Doria D.
>>>> Abstract:
>>>> The Wavefront OBJ format is a common file format for storing mesh data. It is convenient to be able to write VTK data structures out into this format, as the data can then be used in software that can read OBJ files.
>>>>
>>>> Download and Review the paper at: http://www.midasjournal.org/browse/publication/711
>>>>
>>>> Generated by the VTK Journal
>>>> You are receiving this email because you asked to be informed by the VTK Journal for new submissions.
>>>>
>>>> To change your email preference go to http://www.midasjournal.org .
>>>> _______________________________________________
>>>> Powered by www.kitware.com
>>>>
>>>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
>>>>
>>>> Please keep messages on-topic and check the VTK FAQ at: http://www.vtk.org/Wiki/VTK_FAQ
>>>>
>>>> Follow this link to subscribe/unsubscribe:
>>>> http://www.vtk.org/mailman/listinfo/vtkusers
>>>>
>>>
>>>
>>>
>>
>> It takes a vtkPolyData instead of a vtkRenderWindow.
>>
>> Thanks,
>>
>> David
>> _______________________________________________
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
>>
>> Please keep messages on-topic and check the VTK FAQ at: http://www.vtk.org/Wiki/VTK_FAQ
>>
>> Follow this link to subscribe/unsubscribe:
>> http://www.vtk.org/mailman/listinfo/vtkusers
>>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the VTK FAQ at: http://www.vtk.org/Wiki/VTK_FAQ
>
> Follow this link to subscribe/unsubscribe:
> http://www.vtk.org/mailman/listinfo/vtkusers
>