API specifications of NAB framework June 21, 2006 |
Contents
![]() ![]() |
Chapter 4 Explanations of Implementation Examples (Sample Tools) |
This section outlines each module.
This module in the NAB plug-in for MWT is implemented to call WSGFwsInitialize() for MWT initialization. For Xt, the module is implemented to call a function such as XtAppInitialize().
This module in the NAB plug-in for MWT creates an instance of the specified type by calling WSCbase::getNewInsntace().
This module in the NAB plug-in for MWT manages the pointer value of an instance as an instance ID and delivers it to a view through a high-level API.
This module in the NAB plug-in for MWT is implemented to call WSDappDev::lock()/unlock() to return a property value of an instance, and it returns this value in the form of String type or Long type.
The module is also implemented to call the WSCbase::setProperty() function and set a value for the specified property.
This module in the NAB plug-in for MWT is implemented to call a function such as WSCbase::addProcedure() that makes settings related to the event procedure of an instance, in order to incorporate required settings into the instance to call a high-level interface.
The module implements exclusive processing for an operation that must be performed in linkage with SWT.
This module in the NAB plug-in for MWT is implemented to call WSDappDev::lock()/unlock() to lock and stop an MWT-side thread during an MWT operation performed by an SWT-side thread.
This module in the NAB plug-in for MWT is implemented to manage the compile flags, libraries, build environment settings, target information, and other information required for building an MWT application.
This module in the NAB plug-in for MWT is implemented to create the source code required for building an MWT application according to application configuration information.
Contents
![]() ![]() |