[vtkusers] The VTK Journal-New Submission

[Bill Lorensen]

I  think it is reasonable to have an OBJWriter. As long as the
OBJExporter is refactored to use it. It covers the simple use case. It
probably should optionally create material files. Tye materials could
be defined with a vtkProperty passed in to a SetProperty method.

On Mon, Feb 1, 2010 at 12:06 PM, David Doria <daviddoria+vtk at gmail.com> wrote:
> On Mon, Feb 1, 2010 at 11:57 AM, Bill Lorensen <bill.lorensen at gmail.com>
> wrote:
>>
>> The OBJExporter could be refactored to use the OBJReader internally.
>> Then there would be no code duplication between the Exporter and
>> Reader.
>
> I'd agree with that (I think you meant to replace all instances of 'Reader'
> with 'Writer', to say "The OBJExporter can use OBJWriter internally"), but
> it sounds like code duplication is not what Alexandre is worried about, it's
> more of a "OBJ is not supposed to be used for this" thing. The problem is
> that obj IS used for this type of thing, so I was trying to support it even
> though it is not "correct".
> 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
>
>