Extending The Conversion Tool Functionality

The conversion tool has been written with the developer's needs in mind. The tools capability can be modified and enhanced by altering the current code modules or by using the API to create modules to handle newly identified conversion tasks.

The O7Analyser API

The O7Analyser permits the addition of code segments as Omnis procedures to handle pre-conversion tasks. The modules quite simply take a reference to a format as a parameter and require adding a call to the process format routine. See the section on O7Analyser for more Details

The O$Converter API

The O$SConverter also permits for the addition of functionality via the use of Object Classes. Each of the conversion tasks is encapsulated in an Object Class. Object classes may be modified or added as the developer wishes. The API allows for easy expansion of the tool's functionality. See the section on O$Converter for more details.

Since the size of these modules could potentially be rather large, some modules in the O$SConverter can own subordinate "sub-modules" each of which is called in turn to perform a specific task. These are also encapsulated in Object Classes communicating with the parent object class via a defined API. Sub-module Object classes may be modified or added as the developer wishes.

For other conversion tasks that could be automated using additional modules see Candidate Conversion Tasks.