KWScene/Documentation/Supported Generators/VTK/PolyData: Difference between revisions
From KitwarePublic
< KWScene | Documentation | Supported Generators | VTK
Jump to navigationJump to search
(3 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) | ||
* BYU files (.byu) | |||
* BYU files | * XML PolyData (.vtp) | ||
* XML PolyData | * (STL files) (.stl) | ||
= Class Diagrams = | = Class Diagrams = | ||
Line 44: | Line 44: | ||
** XML-PolyData-KWSGenerator | ** XML-PolyData-KWSGenerator | ||
** 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 === | === Proposed Hierarchy === |
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
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