| Prev | Next | Start of Chapter | End of Chapter | Contents | Index | (5 out of 14)

Setting Up an NOL Application

To set up an NOL application:

Setting Up the Workspace Hierarchy

Before you can create a schematic diagram, you must set up the workspace hierarchy for the application. You typically create separate workspaces for different parts of the application. For example, you might have several different workspaces for diagrams, which are linked via connection posts, and you might have a workspace for the input variables that the diagram uses, the rules that the diagram invokes, and the G2 schematic diagram that the NOL diagram monitors.

To set up the workspace hierarchy:

  1. Create a new workspace by selecting Main Menu > New Workspace.

  2. Choose KB Workspace > Setup Application Workspace to display the following workspace:


  3. Click on text labeled Enter title here, select the edit menu choice, enter a title, and press Return.

  4. Click on the background of the workspace, and select KB Workspace > Add Subworkspace Button to add as many subworkspaces as you need for your application.

  5. Go into Administrator mode.

  6. Click on the text of each subworkspace button, and select the edit. menu choice to edit the name of the subworkspace.

  7. Go back into Developer mode.

  8. Click on each subworkspace button to display its subworkspace.

  9. Edit the title of the subworkspace to match the subworkspace button.

Typically, the top-level workspace provides access to all the other subworkspaces of the application.

For example, here is the top-level workspace for a pH process application and the Training Data Sets subworkspace, which is initially empty:



Note: The top-level workspace is not a named workspace, therefore it does not appear in the list of named workspaces when you select Main Menu > Get Workspace. Therefore, you should not hide this workspace. If you do, you can retrieve it by using the Inspect facility and showing all the workspaces assigned to the nolapps module.

Creating an Application Menu Choice

As application developer, you might want to add menu choices to the menus that display the top-level workspaces of your application. In addition, end users will want to access application workspaces through the top menu bar. You can add menu choices automatically to the Applications submenu of the Show menu.

To add a menu choice to the Applications submenu:

Selecting this menu choice adds the name of the workspace to the Applications submenu of the Show menu.

To remove a menu choice from the Applications submenu:

To test the application menu choice:

  1. Hide the top-level workspace whose menu choice you added to the Application menu.

  2. Select the Show > Applications menu choice.

    The top-level workspace you just added appears as a menu choice.

  3. Click on the name of the application workspace to display it.

For example, here is the Applications menu with the pH Process menu choice added:



Note: If you delete a top-level workspace whose menu choice has been added to the Applications menu, NOL automatically removes the associated menu choice.

Setting the User Mode

Part of setting up an application is choosing the user mode in which you will operate. You can switch between these modes as you develop your application.

Different types of users interact with NOL in different modes:

To set the user mode:

Here is the User Mode submenu with Developer mode selected:


Renaming the Top-Level Module

When you initially load NOL, you load the knowledge base contained in the file gdaapps.kb. This creates an empty top-level module named nolapps, which requires all of the NOL modules.

You can rename the top-level module for a specific application.

To rename the top-level module for a specific application:

  1. Load the empty KB contained in file nolapps.kb located in the NOL directory.

  2. Select Main Menu > Inspect to display the G2 editor.

  3. Enter show on a workspace the module hierarchy in the editor.

    This shows a workspace containing the module hierarchy for the NOL application. The top-level module is called nolapps.

  4. Click on the top-level module to edit its name.

    This displays the G2 editor for entering a new name.

  5. Enter a new name for the top-level module.

When you save the NOL application, using Main Menu > Save KB, the top-level module whose name you supplied appears as the default module to save.

| Prev | Next | Start of Chapter | End of Chapter | Contents | Index | (5 out of 14)

Copyright © 1996, Gensym Corporation, Inc.