|
Manager components are used only once in any MAF based application and are usually stored in so called Manager modules, which are loaded by the TmafManagerLoader component placed on the application mainform.
|
 The TmafModuleController provides an interface to access everything a module wants to publish and helps to organize code and forms. It also can take over the standard tasks like returning static data to the caller or creating and destroying the published forms with no additional lines of code...
|
|
Read more...
|
 The TmafHookManager is probably the most important manager component in the MAF Components. It contains the DynamicCode, manages all modules in the application and provides a very powerful editor for the DynamicFunctionTable...
|
|
Read more...
|
 The TmafResourceManager is a monolith file manager for binary data, texts and SQL strings. With its client component TmafResourceClient it gives access to files inside a monolith file emulating a file system with a user defined folder structure. It also loads and provides localized strings to the application, if the programmer wants multi-language-support. Additionally it can host SQL strings to make it easier for programmer to work with databases.
|
|
Read more...
|
With the TmafLinkManager modules can connect to other parts of the application and through message slots communicate to keep each other up-to-date...
|
|
Read more...
|
 The Modular Application Framework Components are often Client/Server-Systems, where so called manager modules provide a server inside the application and all other modules use only a small client component. That preserves a lot of memory and centralizes the information about the current state of the system. The TmafManagerLoader loads the manager modules (which contain the server side) and is the link between the client component and their server.
|
|
Read more...
|
|
|
|
|