The O$Converter API

The functionality of the O$Converter is extendible, via the addition of Object Classes. Each of the conversion tasks is encapsulated in an Object Class. Modules can be added to the O$Converter library and must be identified using the naming convention "Module_YourTask". The O$Converter library executes such modules in name order, i.e. the Object Classes are called governed by the naming convention. This is because there are some modules which must be run before others e.g. The fixing of method and class names must be done second last and last, respectively.

e.g. ModuleAMustRunFirst, Module_NoMatterWhen, ModulezMustRunLast

Note that in order to order the modules as required the 1st "_" may be replaced by a single character (e.g. A, a, 1 etc.)

The Interface to the module is a $run method which is called by O$Converter once for each module.

Since some modules are carrying out a large number of tasks, a module may be broken down into a number of submodules each of which is called in turn by the parent module. Submodules use the naming convention "Submodule_YourTask_YourSubtask". The parent module in this case is "YourTask". Again the submodules are usually called in name order.

e.g. Submodule_YourTask_SubmoduleAMustRunFirst, Submodule_YourTask_Submodule_NoMatterWhen, Submodule_YourTask_SubmodulezMustRunLast

For a list of active Modules and Submodules select "About the Converter..." from the Help menu. The list forms part of the About window. This list also shows "Orphaned Submodules" whose names do not match any of the active Modules, and which will therefore never be called.

For information about adding new modules to the O$Converter see Adding a New Post-Conversion Module to 0$Converter.