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

From KitwarePublic
Jump to navigationJump to search
Line 10: Line 10:
<graphviz>
<graphviz>
digraph G {
digraph G {
itk::ProcessObject [URL="http://www.itk.org/Doxygen316/html/classitk_1_1ProcessObject.html"];
itkProcessObject [URL="http://www.itk.org/Doxygen316/html/classitk_1_1ProcessObject.html"];
itk::ImageSource<> [URL="http://www.itk.org/Doxygen316/html/classitk_1_1ImageSource.html"];
itkImageSource [URL="http://www.itk.org/Doxygen316/html/classitk_1_1ImageSource.html"];
itk::ImageSeriesReader [URL="http://www.itk.org/Doxygen316/html/classitk_1_1ImageSeriesReader.html"];
itkImageSeriesReader [URL="http://www.itk.org/Doxygen316/html/classitk_1_1ImageSeriesReader.html"];
itk::ImageFileReader [URL="http://www.itk.org/Doxygen316/html/classitk_1_1ImageFileReader.html"];
itkImageFileReader [URL="http://www.itk.org/Doxygen316/html/classitk_1_1ImageFileReader.html"];
itk::ImageIOBase [URL="http://www.itk.org/Doxygen316/html/classitk_1_1ImageIOBase.html"];
itkImageIOBase [URL="http://www.itk.org/Doxygen316/html/classitk_1_1ImageIOBase.html"];
itk::VTKImageIO[URL="http://www.itk.org/Doxygen316/html/classitk_1_1VTKImageIO.html"];
itkVTKImageIO[URL="http://www.itk.org/Doxygen316/html/classitk_1_1VTKImageIO.html"];
itk::VTKGDCMImageIO[URL="http://www.itk.org/Doxygen316/html/classitk_1_1GDCMImageIO.html"];
itkVTKGDCMImageIO[URL="http://www.itk.org/Doxygen316/html/classitk_1_1GDCMImageIO.html"];
itk::VTKAnalyzeImageIO[URL="http://www.itk.org/Doxygen316/html/classitk_1_1AnalyzeImageIO.html"];
itkVTKAnalyzeImageIO[URL="http://www.itk.org/Doxygen316/html/classitk_1_1AnalyzeImageIO.html"];
itk::VTKMetaImageIO[URL="http://www.itk.org/Doxygen316/html/classitk_1_1MetaImageIO.html"];
itkVTKMetaImageIO[URL="http://www.itk.org/Doxygen316/html/classitk_1_1MetaImageIO.html"];
itk::ProcessObject -> itk::ImageSource<>  
itkProcessObject -> itkImageSource<>  
itk::ImageSource<> -> itk::ImageSeriesReader<>
itkImageSource -> itkImageSeriesReader<>
itk::ImageSource<> -> itk::ImageFileReader<>
itkImageSource -> itkImageFileReader<>
itk::ImageIOBase -> itk::GDCMImageIO
itkImageIOBase -> itkGDCMImageIO
itk::ImageIOBase -> itk::AnalyzeImageIO
itkImageIOBase -> itkAnalyzeImageIO
itk::ImageIOBase -> itk::VTKImageIO
itkImageIOBase -> itkVTKImageIO
itk::ImageIOBase -> itk::MetaImageIO
itkImageIOBase -> itkMetaImageIO
}
}
</graphviz>
</graphviz>

Revision as of 18:50, 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 every class is dedicated to a specific file format.
  • 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.