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

From KitwarePublic
Jump to navigationJump to search
 
(4 intermediate revisions by the same user not shown)
Line 13: Line 13:
itkMeshSource [URL="http://www.itk.org/Doxygen316/html/classitk_1_1MeshSource.html"];
itkMeshSource [URL="http://www.itk.org/Doxygen316/html/classitk_1_1MeshSource.html"];
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
itkBYUReader
itkXMLPolyDataReader
itkXMLReader
itkProcessObject -> itkMeshSource  
itkProcessObject -> itkMeshSource  
itkMeshSource -> itkVTKPolyDataReader
itkMeshSource -> itkVTKPolyDataReader
itkMeshSource -> itkBYUPolyDataReader
itkMeshSource -> itkBYUReader
itkMeshSource -> itkXMLPolyDataReader
itkMeshSource -> itkXMLReader
}
}
</graphviz>
</graphviz>
Line 25: Line 25:


== Option A ==
== Option A ==


* 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
** BYU-KWSGenerator
** BYUSurface-KWSGenerator
** XML-PolyData-KWSGenerator
** XMLSurface-KWSGenerator
** VTK-PolyData-KWSGenerator
** VTKSurface-KWSGenerator
** (STL-KWSGenerator)
** (STLSurface-KWSGenerator)
* Classes deriving from kwSurfaceNodeGenerator will implement a virtual method
** SurfaceNodeGenerator is the base class here, to be consistent with nomenclature in VTK generators.
** bool CanReadFile() const
** and will be pure virtual in the kwsSurfaceNodeGenerator


=== Proposed Hierarchy ===
=== Proposed Hierarchy ===
Line 44: Line 41:
kwsITKNodeGenerator
kwsITKNodeGenerator
kwsITKSurfaceNodeGenerator
kwsITKSurfaceNodeGenerator
kwsITKVTKSurfaceNodeGenerator
kwsITKVTKPolyDataSurfaceNodeGenerator
kwsITKBYUSurfaceNodeGenerator
kwsITKBYUSurfaceNodeGenerator
kwsITKXMLSurfaceNodeGenerator
kwsITKXMLSurfaceNodeGenerator
Line 50: Line 47:
kwsITKGenerator -> kwsITKNodeGenerator
kwsITKGenerator -> kwsITKNodeGenerator
kwsITKNodeGenerator -> kwsITKSurfaceNodeGenerator
kwsITKNodeGenerator -> kwsITKSurfaceNodeGenerator
kwsITKSurfaceNodeGenerator -> kwsITKVTKPolyDataSurfaceNodeGenerator
kwsITKSurfaceNodeGenerator -> kwsITKBYUSurfaceNodeGenerator
kwsITKSurfaceNodeGenerator -> kwsITKXMLSurfaceNodeGenerator
kwsITKSurfaceNodeGenerator -> kwsITKSTLSurfaceNodeGenerator
kwsITKSurfaceNodeGenerator -> kwsITKSTLSurfaceNodeGenerator
kwsITKSurfaceNodeGenerator -> kwsITKBYUSurfaceNodeGenerator
kwsITKSurfaceNodeGenerator -> kwsITKPolyDataSurfaceNodeGenerator
kwsITKSurfaceNodeGenerator -> kwsITKXMLPolyDataSurfaceNodeGenerator
}
}
</graphviz>
</graphviz>

Latest revision as of 20:08, 25 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
    • BYUSurface-KWSGenerator
    • XMLSurface-KWSGenerator
    • VTKSurface-KWSGenerator
    • (STLSurface-KWSGenerator)
    • SurfaceNodeGenerator is the base class here, to be consistent with nomenclature in VTK generators.

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.