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

From KitwarePublic
Jump to navigationJump to search
Line 33: Line 33:
== Option A ==
== Option A ==


* Create a KWScene hierarchy where every class is dedicated to a specific file format.
* Create a KWScene hierarchy where ImageGenerator handles all specific file formats.
* Will have classes
* Will have classes
** Image-KWSGenerator, which can generate either an image of most single-file types via itk::ImageIOFactory  
** Image-KWSGenerator, which can generate either an image of most single-file types via itk::ImageIOFactory  

Revision as of 18:52, 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 specific 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 reliability of ImageIOFactory, ImageNode 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.