[vtk-developers] [InfoVis] Infovis and rendering kits

[Shepherd, Jason F]

We should consider removing Infovis/vtkTreeMapViewer.  It is basically duplicating functionality found in Views/vtkTreeMapView...

Jason 

> -----Original Message-----
> From: infovis-bounces at public.kitware.com 
> [mailto:infovis-bounces at public.kitware.com] On Behalf Of 
> Thompson, David C
> Sent: Wednesday, March 18, 2009 1:04 AM
> To: Jeff Baumes; Pebay, Philippe P
> Cc: vtk-developers at vtk.org; infovis at public.kitware.com
> Subject: Re: [InfoVis] Infovis and rendering kits
> 
> So... is Kitware OK with me moving these 5 classes from 
> Infovis to Rendering:
>     vtkGraphMapper.cxx
>     vtkInteractorStyleAreaSelectHover.cxx
>     vtkInteractorStyleTreeMapHover.cxx
>     vtkLabeledTreeMapDataMapper.cxx
>     vtkTreeMapViewer.cxx
> and this class from Infovis to Views:
>     vtkViewUpdater.cxx
> and then making VTK_USE_INFOVIS an independent option?
> 
>     David
> ________________________________________
> From: Thompson, David C
> Sent: Monday, March 16, 2009 08:25
> To: Jeff Baumes; Pebay, Philippe P
> Cc: infovis at public.kitware.com; vtk-developers at vtk.org
> Subject: RE: [InfoVis] Infovis and rendering kits
> 
> Jeff,
> 
> I'm not sure I understand why the vtkInteractorStyle 
> subclasses force Infovis to depend on Rendering any 
> differently than Parallel. The Parallel kit gets linked to 
> Rendering is VTK_USE_RENDERING is ON but VTK_USE_PARALLEL 
> does not require VTK_USE_RENDERING.
> If Rendering is built then vtkTreeCompositer and several 
> other classes are included in Parallel. I'm not 
> complaining... I just want to understand if something else is 
> going on.
> 
> In any event, the classes in Infovis that rely on Rendering are
>     vtkGraphMapper.cxx
>     vtkInteractorStyleAreaSelectHover.cxx
>     vtkInteractorStyleTreeMapHover.cxx
>     vtkLabeledTreeMapDataMapper.cxx
>     vtkTreeMapViewer.cxx
>     vtkViewUpdater.cxx
> and arguably vtkViewUpdater should not currently be in 
> Infovis because its implementation includes vtkView.h but the 
> Views kit depends on Infovis -- creating a circular dependency.
> 
>     David
> ________________________________________
> From: Jeff Baumes [jeff.baumes at kitware.com]
> Sent: Monday, March 16, 2009 07:17
> To: Pebay, Philippe P
> Cc: Thompson, David C; infovis at public.kitware.com; 
> vtk-developers at vtk.org
> Subject: Re: [InfoVis] Infovis and rendering kits
> 
> Infovis code contains vtkInteractorStyle subclasses, so must 
> depend on rendering (e.g. vtkInteractorStyleTreeMapHover), 
> and there is also a dependency on Widgets. The Infovis 
> directory is currently a catch-all for informatics-related 
> code. As I remember it, it was deemed more important to be 
> able to turn off infovis entirely than to make it easy to 
> turn off various components of infovis.
> 
> A possibility is to move some code to Rendering, Widgets, or Hybrid.
> This would let us change the dependencies.
> 
> Jeff
> 
> On Sun, Mar 15, 2009 at 10:47 PM, Pebay, Philippe P 
> <pppebay at sandia.gov> wrote:
> > Hello
> >
> > I had wondered about that a while ago (when looking at the 
> dependencies of Infovis, prior to writing the parallel 
> classes of the statistics engines).
> > However I thought there was a good reason for this 
> dependency on VTK_USE_RENDERING. If not, I would also be in 
> favour of removing the said dependency.
> >
> > P.
> >
> >
> > --
> > Philippe Pébay
> > Sandia National Laboratories
> >
> > ________________________________________
> > From: infovis-bounces at public.kitware.com 
> > [infovis-bounces at public.kitware.com] On Behalf Of Thompson, David C 
> > [dcthomp at sandia.gov]
> > Sent: Sunday, March 15, 2009 11:54 AM
> > To: infovis at public.kitware.com; vtk-developers at vtk.org
> > Subject: [InfoVis] Infovis and rendering kits
> >
> > Hi all,
> >
> > Is there a reason why VTK_USE_INFOVIS is dependent on 
> > VTK_USE_RENDERING? I would like to use some vtkStatisticsAlgorithm 
> > subclasses on a system where it isn't easy to build with 
> > VTK_USE_RENDERING turned ON.
> > There are plenty of filters in the Infovis kit that don't 
> require any 
> > rendering routines -- even the graph layout code could be useful 
> > without rendering.
> >
> > I have a locally modified version of VTK that fixes this 
> behavior but 
> > don't want to check it in if there is a real reason to keep Infovis 
> > dependent on Rendering.
> > It did require moving one class (vtkCoincidentPoints) from 
> Rendering 
> > to Graphics but was pretty clean other than that.
> >
> > On a side note, has anyone else had trouble building with 
> > VTK_USE_RENDERING off and VTK_USE_PARALLEL on? I get link errors 
> > complaining that vtkPImageWriter references vtkPipelineSize 
> -- which 
> > is not built when Rendering is off. Also, Parallel should 
> be linked to 
> > Graphics when Rendering is off. I've got a fix for this as well.
> >
> >    Thanks,
> >    David
> > _______________________________________________
> > Infovis mailing list
> > Infovis at public.kitware.com
> > http://public.kitware.com/cgi-bin/mailman/listinfo/infovis
> >
> >
> > _______________________________________________
> > Infovis mailing list
> > Infovis at public.kitware.com
> > http://public.kitware.com/cgi-bin/mailman/listinfo/infovis
> >
> 
> 
> 
> --
> Jeff Baumes, Ph.D.
> R&D Engineer, Kitware Inc.
> (518) 371-3971 x132
> jeff.baumes at kitware.com
> 
> 
> _______________________________________________
> Infovis mailing list
> Infovis at public.kitware.com
> http://public.kitware.com/cgi-bin/mailman/listinfo/infovis
> 
>