![]() |
ICF 3.0.5.47
Technical documentation of ICF Libraries
|
The main use-case of this concept is to provide component-oriented software development. More...
Topics | |
Component concept macros | |
This is a list of macros for defining component in component class. | |
Packaging the concepts | |
To create the package you have to use set of mechanisms and macros in the separated project generating .arp file (physically it is a shared library, depending on the operating system). | |
Namespaces | |
namespace | icomp |
Package with interfaces and class used for components concept. | |
namespace | ipackage |
Package contains implementation for the management of ICF environment. | |
Classes | |
class | icomp::CComponentBase |
Base class for component implementation. More... | |
class | icomp::IComponent |
Main component interface. 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... | |
The main use-case of this concept is to provide component-oriented software development.
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 ICF tool or compiled to C++ code using Icrc compiler. Additionally you can use component simulation to use components as "normal" classes.
Compositor.exe
.Icf.exe
tool is available to test a prototype topology.Icrc.exe
generates C++ code for direct use of the topology file. © Witold Gantzke and Kirill Lepskiy