[Paraview] Accessing OpenGL from standard VTK filter
andy.bauer at kitware.com
Wed Oct 5 11:56:16 EDT 2011
Are you hoping that this will make its way into the main VTK repo or is this
personal code that you plan on maintaining yourself and plan on linking with
There are people that know more about this than me but this sounds like a
bad idea for the main VTK repo. A lot of the OpenGL specific calls are
hidden by factories which create them as needed. For example, you'd create
a vtkPolyDataMapper and the factory would create the
vtkOpenGLPolyDataMapper, vtkMesaPolyDataMapper, etc as needed by the build.
On Tue, Oct 4, 2011 at 6:34 PM, Sohail Shafii <sohailshafii at yahoo.com>wrote:
> If I were to write a typical VTK filter C++ (i.e. the type with
> VTKRequestData, not existing in the VTK/Rendering folder), would it be fine
> to have OpenGL calls in there? I'm guessing based on the way VTK is
> designed, most classes that access OpenGL directly might exist in the
> Rendering folder. This is more of a design question anyway and relates to
> how to VTK classes are designed.
> My class will add data structures to the pipeline but it may need a
> fragment shader for computations.
> Powered by www.kitware.com
> Visit other Kitware open-source projects at
> Please keep messages on-topic and check the ParaView Wiki at:
> Follow this link to subscribe/unsubscribe:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the ParaView