[vtk-developers] material files patch for vtkOBJReader

[Berk Geveci]

I apologize for missing your Gitlab comment Bill. I have been in report
land and have not been paying attention to development for a few weeks.

If Peter is considering further contributions to VTK in the future, adding
him to the developer list in Gitlab sounds great to me. VTK could use more
developers like Peter :-) If this is a one time thing, someone else should
probably merge it. Peter: what say you?

Best,
-berk


On Thu, Apr 16, 2015 at 12:29 PM, Bill Lorensen <bill.lorensen at gmail.com>
wrote:

> Berk,
>
> Peter has done an excellent job creating the OBJImporter. He has been
> very responsive to suggestions. Although there may be some minor
> cleanup necessary, I think his gitlab topic is ready to merge.
> However, he does not have permission to do the merge. I suggest he be
> added to the approved developer list.
>
> Bill
>
> https://gitlab.kitware.com/vtk/vtk/merge_requests/26
>
>
> On Mon, Dec 22, 2014 at 2:44 PM, Berk Geveci <berk.geveci at kitware.com>
> wrote:
> > My preference would be to develop a new OBJ importer that uses the OBJ
> > reader. Making the OBJ reader depend on rendering may impact some folks
> > negatively. By the way, I would defer this for a few months if possible.
> We
> > have a project targeted towards importing material properties for ray
> > tracing etc. I don't think that we will follow the importer route and we
> > will probably develop a new infrastructure. It may fit better here.
> >
> > Best,
> > -berk
> >
> > On Mon, Dec 22, 2014 at 12:32 PM, Peter Karasev <karasevpa at gmail.com>
> wrote:
> >>
> >> Hi,
> >>
> >>       I'm hoping to get an update for vtkOBJReader integrated in that
> >> enables reading material-texture-library (.mtl) files. These are
> typically
> >> distributed along with the .obj file that contains geometry data.
> >>
> >>       There's an issue with the module structure of VTK in doing this,
> >> however: having the MTL file means that you basically must generate not
> only
> >> geometry but the entire actors with vtkProperty*'s set on them.
> >>
> >>       I propose moving vtkOBJReader into the same area as
> vtk3DSImporter,
> >> where it is allowed to access things in vtkRenderingCore like vtkActor
> >> class. Alternatively, a dependency(ies) could be added to vtkIOGeometry
> to
> >> allow creating actors. Any views on which way to go here?
> >>
> >> --
> >>
> >> _______________
> >> Peter  Karasev
> >> karasevpa at gmail.com
> >>
> >> _______________________________________________
> >> 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://public.kitware.com/mailman/listinfo/vtk-developers
> >>
> >>
> >
> > _______________________________________________
> > 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://public.kitware.com/mailman/listinfo/vtk-developers
> >
> >
>
>
>
> --
> Unpaid intern in BillsBasement at noware dot com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/vtk-developers/attachments/20150416/57da04a7/attachment.html>