This is a great suggestion. The interesting thing is that besides the paraview specific xml file, the module looks like pure VTK.
Modifications include changing the module.vtk namesspace variables from
VTK:: ( Not sure if that was necesary? )
and made an option called “VISIT_BUILD_READER_Paraview” that defaults to
ON so that when it’s off it skips the paraview specific macro.
Does that seem like a reasonable approach?
Can one suggestion a “best practice” to support this approach internally.
e.g. have a vtk branch that tracks upstream with the additional module files?
and a branch for the VisItBridge repo with the same?
with this module
magic, I think self support is doable.