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

[Thompson, David C]

Jeff,

Yes, I will start moving these classes around as the wiki page outlines.

   Thanks,
   David
________________________________________
From: Jeff Baumes [jeff.baumes at kitware.com]
Sent: Wednesday, March 18, 2009 08:07
To: Shepherd, Jason F
Cc: Thompson, David C; Pebay, Philippe P; vtk-developers at vtk.org; infovis at public.kitware.com
Subject: Re: [InfoVis] Infovis and rendering kits

> We should consider removing Infovis/vtkTreeMapViewer.  It is basically duplicating functionality found in Views/vtkTreeMapView...
I agree. The right thing to do is probably to mark all its methods as
deprecated until the next release, pointing the user to vtkTreeMapView
in the class comments, then we can remove the class.

>> So... is Kitware OK with me moving these 5 classes from
>> Infovis to Rendering:
>>     vtkGraphMapper.cxx
Depends on filters in Infovis.

>>     vtkInteractorStyleAreaSelectHover.cxx
Depends on vtkBalloonRepresentation (in Widgets).

>>     vtkInteractorStyleTreeMapHover.cxx
Depends on vtkBalloonRepresentation (in Widgets) and vtkTreeMapLayout
(in Infovis).

>>     vtkLabeledTreeMapDataMapper.cxx
It looks like this could move.

>>     vtkTreeMapViewer.cxx
Depends on vtkTreeMapLayout (in Infovis).

>> and this class from Infovis to Views:
>>     vtkViewUpdater.cxx
Yes, this should definitely happen.

I made a wiki page describing how we could move things in order to
change dependencies:

http://www.kitware.com/InfovisWiki/index.php/VTK_Kit_Dependencies

Dave, if you want to try to get this working, please feel free.

Jeff