KWScene/Documentation/Supported Generators/ITK/PolyData: Difference between revisions

From KitwarePublic
Jump to navigationJump to search
No edit summary
Line 14: Line 14:
itkVTKPolyDataReader[URL="http://www.itk.org/Doxygen316/html/classitk_1_1VTKPolyDataReader.html"];
itkVTKPolyDataReader[URL="http://www.itk.org/Doxygen316/html/classitk_1_1VTKPolyDataReader.html"];
itkBYUPolyDataReader  
itkBYUPolyDataReader  
itkXMLPolyDataReader
itkProcessObject -> itkMeshSource  
itkProcessObject -> itkMeshSource  
itkMeshSource -> itkVTKPolyDataReader
itkMeshSource -> itkVTKPolyDataReader
itkMeshSource -> itkBYUPolyDataReader
itkMeshSource -> itkBYUPolyDataReader
itkMeshSource -> itkXMLPolyDataReader
}
}
</graphviz>
</graphviz>
Line 27: Line 29:
* Create a KWScene hierarchy where every class is dedicated to a specific file format.
* Create a KWScene hierarchy where every class is dedicated to a specific file format.
* Will have classes
* Will have classes
** STL-KWSGenerator
** BYU-KWSGenerator
** BYU-KWSGenerator
** XML-PolyData-KWSGenerator
** XML-PolyData-KWSGenerator
** PolyData-KWSGenerator
** VTK-PolyData-KWSGenerator
** (STL-KWSGenerator)
* Classes deriving from kwSurfaceNodeGenerator will implement a virtual method  
* Classes deriving from kwSurfaceNodeGenerator will implement a virtual method  
** bool CanReadFile() const
** bool CanReadFile() const
Line 39: Line 41:
<graphviz>
<graphviz>
digraph G {
digraph G {
kwsVTKGenerator
kwsITKGenerator
kwsVTKNodeGenerator
kwsITKNodeGenerator
kwsVTKSurfaceNodeGenerator
kwsITKSurfaceNodeGenerator
kwsVTKSTLSurfaceNodeGenerator
kwsITKVTKSurfaceNodeGenerator
kwsVTKBYUSurfaceNodeGenerator
kwsITKBYUSurfaceNodeGenerator
kwsVTKPolyDataSurfaceNodeGenerator
kwsITKXMLSurfaceNodeGenerator
kwsVTKXMLPolyDataSurfaceNodeGenerator
kwsITKSTLSurfaceNodeGenerator
kwsVTKGenerator -> kwsVTKNodeGenerator
kwsITKGenerator -> kwsVTKNodeGenerator
kwsVTKNodeGenerator -> kwsVTKSurfaceNodeGenerator
kwsITKNodeGenerator -> kwsVTKSurfaceNodeGenerator
kwsVTKSurfaceNodeGenerator -> kwsVTKSTLSurfaceNodeGenerator
kwsITKSurfaceNodeGenerator -> kwsITKSTLSurfaceNodeGenerator
kwsVTKSurfaceNodeGenerator -> kwsVTKBYUSurfaceNodeGenerator
kwsITKSurfaceNodeGenerator -> kwsITKBYUSurfaceNodeGenerator
kwsVTKSurfaceNodeGenerator -> kwsVTKPolyDataSurfaceNodeGenerator
kwsITKSurfaceNodeGenerator -> kwsITKPolyDataSurfaceNodeGenerator
kwsVTKSurfaceNodeGenerator -> kwsVTKXMLPolyDataSurfaceNodeGenerator
kwsITKSurfaceNodeGenerator -> kwsITKXMLPolyDataSurfaceNodeGenerator
}
}
</graphviz>
</graphviz>

Revision as of 19:20, 22 April 2010

Desired Format Support

  • PolyData from .vtk legacy files (.vtk)
  • BYU files (.byu)
  • XML PolyData (.vtp)
  • (STL files) (.stl)

Class Diagrams

This is a graph with borders and nodes. Maybe there is an Imagemap used so the nodes may be linking to some Pages.

Options

Option A

  • Create a KWScene hierarchy where every class is dedicated to a specific file format.
  • Will have classes
    • BYU-KWSGenerator
    • XML-PolyData-KWSGenerator
    • VTK-PolyData-KWSGenerator
    • (STL-KWSGenerator)
  • Classes deriving from kwSurfaceNodeGenerator will implement a virtual method
    • bool CanReadFile() const
    • and will be pure virtual in the kwsSurfaceNodeGenerator

Proposed Hierarchy

This is a graph with borders and nodes. Maybe there is an Imagemap used so the nodes may be linking to some Pages.