Member createHistogramData (QString const &name, iAValueType xValueType, QVector< typename itk::Image< PixelT, 3 >::Pointer > const &imgs, size_t numBin, PixelT min, PixelT max)

move to a separate file?

Class iAFast3DMagicLensWidget

refactor:

split up into basic 3D renderer widget functionality to iARendererImpl
magic lens stuff to separate class (similar to iAMagicLens)

Class iAFileParamDlg

: check whether it makes sense to use this or something similar for similar purposes, e.g. for asking for filter parameters?

Class iAImageCoordConverter

maybe merge with stuff from DynamicVolumeLines?

Class iAImageCoordinate

Maybe use iAVec3i instead?

Class iAImageStackFileIO

merge with modules/MetaFilters/iAStackReaderFilter ?

Class iAitkCommand

hide from iAProgress users (maybe via PIMPL idiom)

Class iAMultiStepProgressObserver

should be merged/consolidated with iAProgress!

Class iAScatterPlotWidget

minimize duplication between iAScatterPlotWidget and iAQSplom!

Class iATFTableWidgetItem

maybe this could be done via a standalone operator?