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

From KitwarePublic
Jump to navigationJump to search
Line 39: Line 39:
** an Image Series via itk::GDCMImageIO.  
** an Image Series via itk::GDCMImageIO.  
** because of the breadth and reliability of ImageIOFactory.  
** because of the breadth and reliability of ImageIOFactory.  
** ImageNode is not an abstract class here, and can handle any image.  
** ImageNodeGenerator is not an abstract class here, and can handle any image.  


=== Proposed Hierarchy ===
=== Proposed Hierarchy ===

Revision as of 18:53, 22 April 2010

Desired Format Support

DICOM (.dcm) Analyze (.hdr/.ima) XML (.vti)

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 ImageGenerator handles all relevant file formats.
  • Will have classes
    • Image-KWSGenerator, which can generate either
    • an image of most single-file types via itk::ImageIOFactory or
    • an Image Series via itk::GDCMImageIO.
    • because of the breadth and reliability of ImageIOFactory.
    • ImageNodeGenerator is not an abstract class here, and can handle any image.

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.