Namespaces | Classes | Macros
Component concept

This concept allows to divide application into smaller modules. More...

Namespaces

 icomp
 Package with interfaces and class used for components concept.
 
 ipackage
 Package contains implementation for the management of ACF environment.
 

Classes

class  ibase::IApplication
 Interface for the main entry point of a component-based application. More...
 
class  icomp::CComponentAddress
 Represents global address of component. More...
 
class  icomp::CComponentBase
 Base class for component implementation. More...
 
class  icomp::IComponent
 Main component interface. More...
 
class  icomp::IComponentContext
 Provide session context of component. More...
 
class  icomp::IComponentStaticInfo
 This interface provide static information about component meta info. More...
 
class  icomp::ICompositeComponent
 Composite component interface. More...
 
class  icomp::IElementStaticInfo
 This interface provide static information about element meta info. More...
 
class  icomp::IRegistry
 Interface representing information stored in component registry. More...
 
class  icomp::IRegistryElement
 Represents element of registry describing component parameters. More...
 
class  icomp::TMakeComponentWrap< Base, Interface1, Interface2, Interface3, Interface4, Interface5, Interface6, Interface7, Interface8, Interface9, Interface10 >
 Simple wrapper making component from non-component class. More...
 
class  icomp::TModelCompWrap< Base >
 Makes component and model from some class implementing interface istd::IChangeable. More...
 
class  icomp::TSimComponentsFactory< Base >
 Simulation wrapper of component. More...
 
class  icomp::TSimComponentWrap< Base >
 Simulation wrapper of component. More...
 

Macros

#define I_TEXTATTR(member)
 Declare translatable text attribute member. More...
 
#define I_MULTITEXTATTR(member)
 Declare translatable multiple text attribute member. More...
 

Detailed Description

This concept allows to divide application into smaller modules.

At the implementation level you don't need to care about the application topology. The topology will be described separately using .acc files and can be started using runtime environment over ACF tool or compiled to C++ code using ARXC compiler. Additionally you can use component simulation to use components as "normal" classes.

Macro Definition Documentation

#define I_MULTITEXTATTR (   member)
Value:

Declare translatable multiple text attribute member.

Please use I_MULTIATTR with QString parameter for non translatable list of text attributes

Definition at line 252 of file CComponentBase.h.

#define I_TEXTATTR (   member)
Value:
typedef icomp::CTextAttributeMember member##_Type;\
typedef icomp::CTextAttributeMember::AttributeType member##_AttrType;\
icomp::CTextAttributeMember member

Declare translatable text attribute member.

Please use I_ATTR with QString parameter for non translatable text attributes

Definition at line 221 of file CComponentBase.h.

© 2007-2017 Witold Gantzke and Kirill Lepskiy