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

From KitwarePublic
Jump to navigationJump to search
Line 50: Line 50:
kwsITKGenerator -> kwsITKNodeGenerator
kwsITKGenerator -> kwsITKNodeGenerator
kwsITKNodeGenerator -> kwsITKSurfaceNodeGenerator
kwsITKNodeGenerator -> kwsITKSurfaceNodeGenerator
kwsITKSurfaceNodeGenerator -> kwsITKVTKSurfaceNodeGenerator
kwsITKSurfaceNodeGenerator -> kwsITKBYUSurfaceNodeGenerator
kwsITKSurfaceNodeGenerator -> kwsITKXMLSurfaceNodeGenerator
kwsITKSurfaceNodeGenerator -> kwsITKSTLSurfaceNodeGenerator
kwsITKSurfaceNodeGenerator -> kwsITKSTLSurfaceNodeGenerator
kwsITKSurfaceNodeGenerator -> kwsITKBYUSurfaceNodeGenerator
kwsITKSurfaceNodeGenerator -> kwsITKPolyDataSurfaceNodeGenerator
kwsITKSurfaceNodeGenerator -> kwsITKXMLPolyDataSurfaceNodeGenerator
}
}
</graphviz>
</graphviz>

Revision as of 19:22, 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.