Application Development Concepts

You can tailor the OPNET Development Kit user interface to your specific needs using three primary mechanisms: User Interface Customization, External Tool Support (ETS), and Object Customization.

  • User Interface Customization refers to the ability to create alternate versions of OPNET Development Kit basic tools (such as the Network Editor), as well as the ability to add and subtract these tools from the user interface.
  • ETS lets you augment OPNET Development Kit with external programs by adding or subtracting operations.
  • Object Customization uses active attributes and model handlers to add specific functionality to an object.

A series of configuration files controls the OPNET Development Kit user interface. You can alter these files to achieve specific effects, such as the addition of a new action button or the removal of a tool. The primary configuration files are:

  • editor configuration file. This is the top level configuration file. It tells OPNET Development Kit what tools to make available and points to the configuration files for each tool.
  • operation list file. These files contain the menu contents for a given editor, and also specify which items appear as buttons in the button bar.

When you start OPNET Development Kit, it first reads the editor configuration file to find out which tools to make available. In each tool's entry, you can specify buttons or actions that point to external programs. Operation List files may also refer to built-in functions or to Palette or Menu Definition files.

To be available to OPNET Development Kit programs, all ETS and configuration files must be in a directory named in the mod_dirs environment attribute of the application. In the examples provided in this chapter, ETS files are in a sub-directory of op_models called "ets". The standard configuration files that come with OPNET Development Kit are in the <reldir>/sys/configs directory.

In the following sections, the term user refers to the end-user of OPNET Development Kit programs that have been augmented with the help of the ETS package. The term developer refers to the model or tool developer who has used the ETS package to augment the GUI interface and behavior. The user and developer may be one and the same.