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

From KitwarePublic
Jump to navigationJump to search
 
(12 intermediate revisions by 2 users not shown)
Line 1: Line 1:
= Desired Format Support =
= Desired Format Support =


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


= Class Diagrams =
= Class Diagrams =
Line 20: Line 20:
vtkXMLDataReader [URL="http://www.vtk.org/doc/nightly/html/classvtkXMLDataReader.html"];
vtkXMLDataReader [URL="http://www.vtk.org/doc/nightly/html/classvtkXMLDataReader.html"];
vtkXMLPolyDataReader [shape=box,URL="http://www.vtk.org/doc/nightly/html/classvtkXMLPolyDataReader.html"];
vtkXMLPolyDataReader [shape=box,URL="http://www.vtk.org/doc/nightly/html/classvtkXMLPolyDataReader.html"];
vtkXMLUnstructureDataReader [URL="http://www.vtk.org/doc/nightly/html/classvtkXMLUnstructureDataReader.html"];
vtkXMLUnstructureDataReader [URL="http://www.vtk.org/doc/nightly/html/classvtkXMLUnstructuredDataReader.html"];
vtkAlgorithm -> vtkDataReader
vtkAlgorithm -> vtkDataReader
vtkAlgorithm -> vtkPolyDataAlgorithm
vtkAlgorithm -> vtkPolyDataAlgorithm
Line 30: Line 30:
vtkXMLReader -> vtkXMLDataReader  
vtkXMLReader -> vtkXMLDataReader  
vtkAlgorithm -> vtkXMLReader
vtkAlgorithm -> vtkXMLReader
}
</graphviz>
= Options =
== Option A ==
* Create a KWScene hierarchy where every class is dedicated to a specific file format.
* Will have classes
** STL-KWSGenerator
** BYU-KWSGenerator
** XML-PolyData-KWSGenerator
** PolyData-KWSGenerator
* Classes deriving from kwSurfaceNodeGenerator will implement a virtual method
** bool CanReadFile() const
** and will be pure virtual in the kwsSurfaceNodeGenerator
=== Proposed Hierarchy ===
<graphviz>
digraph G {
kwsVTKGenerator
kwsVTKNodeGenerator
kwsVTKSurfaceNodeGenerator
kwsVTKSTLSurfaceNodeGenerator
kwsVTKBYUSurfaceNodeGenerator
kwsVTKPolyDataSurfaceNodeGenerator
kwsVTKXMLPolyDataSurfaceNodeGenerator
kwsVTKGenerator -> kwsVTKNodeGenerator
kwsVTKNodeGenerator -> kwsVTKSurfaceNodeGenerator
kwsVTKSurfaceNodeGenerator -> kwsVTKSTLSurfaceNodeGenerator
kwsVTKSurfaceNodeGenerator -> kwsVTKBYUSurfaceNodeGenerator
kwsVTKSurfaceNodeGenerator -> kwsVTKPolyDataSurfaceNodeGenerator
kwsVTKSurfaceNodeGenerator -> kwsVTKXMLPolyDataSurfaceNodeGenerator
}
}
</graphviz>
</graphviz>

Latest revision as of 19:02, 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
    • STL-KWSGenerator
    • BYU-KWSGenerator
    • XML-PolyData-KWSGenerator
    • PolyData-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.