Greetings from the halls of pakkorky!
API Reference
An OMF
must
export at least one function, and it
must
have the following prototype:
DWORD go( int argc, char *argv[] );
An OMF
should
be thread-safe
An OMF
should
return one of the meaningful return codes defined in the header files
An OMF
should
accurately show usage information when invoked without parameters (or with bogus ones)
This information
should
note any dependencies (i.e., other .OMFs or external modules)
If you do these things, then all you need to do is drop your new .OMF in the same directory with OWNR.EXE
No messy installation/uninstallation
No conflicts with other items
Each .OMF has full access to the functionality of all others
This page is maintained by Foofus. Please direct comments and questions to foofus <at> foofus.net.