Micro Services Interfaces

Classes (interfaces) in this category are explicitly designed for usage with the MITK Micro Services. More...

Collaboration diagram for Micro Services Interfaces:

Classes
class	mitk::CustomMimeType
	The CustomMimeType class represents a custom mime-type which may be registered as a service object. It should only be used for mime-type registration, see also mitk::MimeType. More...
struct	mitk::IFileReader
	The common interface for all MITK file readers. More...
struct	mitk::IFileWriter
	The common interface of all MITK file writers. More...
struct	mitk::IMimeTypeProvider
	The IMimeTypeProvider service interface allows to query all registered mime types. More...
class	mitk::IPersistenceService
class	mitk::IPreferencesService
	A service for persistent application preferences. More...
class	mitk::IPropertyAliases
	Interface of property aliases service. More...
class	mitk::IPropertyDescriptions
	Interface of property descriptions service. More...
class	mitk::IPropertyDeserialization
	Interface of property deserialization service. More...
class	mitk::IPropertyExtensions
	Interface of property extensions service. More...
class	mitk::IPropertyFilters
	Interface of property filters service. More...
class	mitk::IPropertyPersistence
	Interface of property persistence service. More...
class	mitk::IPropertyRelations
	Interface of property relations service. More...
class	mitk::DICOMTagsOfInterestService
	DICOM tags of interest service. More...
class	mitk::IDICOMTagsOfInterest
	Interface of DICOM tags of interest service. More...
struct	mitk::IModelFitProvider
	The common interface for all model providers for model fitting. More...
struct	mitk::IDataStorageInspectorProvider
	The common interface for all DataStorage inspector providers. More...
class	mitk::InteractionEventObserver
	Base class to implement InteractionEventObservers. More...

Detailed Description

Classes (interfaces) in this category are explicitly designed for usage with the MITK Micro Services.

All classes in this category are structs with no non-static members and only pure virtual functions (except for an inlined virtual destructor). Such a class will be called a interface.

These interfaces are meant to be implemented by MITK module developers to enhance or overwrite certain aspects of the MITK toolkit. All implementations must be registered in the implementing module's activator (see mitk::ModuleActivator) using the module's mitk::ModuleContext instance.