Contents of this Section:

Overview of the Design Window

Menubar

• File
• Edit
• View
• Run
• Help

Toolbars

• File Action Toolbar
• Component Toolbars

Component Tree Panel

Design Layout Panel

Properties Panel

• Attributes Panel
• Layout Panel
• Events Panel

Status Panel

Overview of the Design Window

The Design Window is where the user interface for client applications is created. Graphical containers and components are added and arranged in a layout grid and their contents, attributes and event linkages are assigned. The Design Window is made up of several parts: a Menubar, Toolbars, Component Tree Panel, Design Layout Panel, Properties Panel, and a Status Panel. Each of these is discussed more fully below.

Menubar
The menubar at the top of the Design Window uses normal mouse or keyboard actions to select menu choices. Some of the menu choices may also be selected by clicking toolbar buttons or other buttons in other panels of the Design Window. Following is a detailed explanation of each menu choice.

File
Contains menu choices for creating, opening, saving and closing app files, and exiting the program. Also see "Working with XML Procedures" in Section 1.

File-->New
Create a new XML app file, with whatever default contents are specified by the XML template file "templates\NewApplicationTemplate.xml". (The name will be assigned when the first "Save" or "Save As" operation is done).

File-->Open
Open an existing app file.  In Version 2, app files can reside locally in any directory on the client system or a networked server, or they can be served remotely from the host's web server.

File-->Save
Save the app file that is currently displayed in the appname combobox (which is at the top of the leftmost panel, just below the toolbar). Note: when a new app is first saved, the "Save" choice will actually run the "Save As" choice, in order to assign a name to the new app file.

File-->Save As
Like Save, but requests a new appname. All appnames must end in ".xml".

File-->Close
Closes the appfile that is currently displayed in the appname combobox. Note that the "Close" choice will prompt for a "Save" before closing, if the app has changes that have not been saved.

File-->Close All
Closes all open appfiles (those that are listed in the appname combobox). Note that closing an app will prompt for a "Save" before closing, if the app has changes that have not been saved.

File-->Reopen App
Closes the appfile that is currently displayed in the appname combobox and then reopens it. This can be used to force Jargon Writer to use a "fresh" copy of an app. Note that the "Close" choice will prompt for a "Save" before closing, if the app has changes that have not been saved.

File-->Exit
Closes all open apps and then exits Jargon Writer. Note that closing an app will prompt for a "Save" before closing, if the app has changes that have not been saved.
 

Edit-->Cut
Copies the selected components into a temporary clipboard memory and flags them to be deleted from their current location when they are pasted into a new location.

Edit-->Copy
Copies the selected components into a temporary clipboard memory.

Edit-->Paste
Pastes the components in the temporary clipboard memory into the new container that is highlighted in the component tree.

View-->Task Editor
Displays the Task Editor Window where tasklists and tasks may be defined and changed.

View-->Preferences
This menu choice is not currently implemented.

View-->Error Console
Displays a "console" window where error messages and the session error log can be displayed. This windown is used primarily for debugging.

View-->Host Console
Displays a "console" window where messages sent to and received from a host are displayed. This windown is used primarily for debugging.

View-->Windows Style Look and Feel
Changes the visual display style and user interface behavior to the Microsoft Windows standard.

View-->Metal Look and Feel
Changes the visual display style and user interface behavior to Sun's new "metal" standard for Java.

View-->Motif Look and Feel
Changes the visual display style and user interface behavior to the motif (X-Windows) standard. Motif is used on many Unix workstations and X-Terminals.
 

Run-->Execute
Runs (executes) the currently active app whose root node in the component tree is highlighted.

Run-->Generate 4GL
This feature is used only when developing apps that will communicate with host procedures written in the Progress 4GL. It generates one or more Progress ".p" source programs, based on the program specs in host tasks that were defined in the Task Editor for the currently active app.
 

Help-->Help Topics
Starts the default Web browser on your system and loads the "Jargon Software Index to Online Help Documents". This document has links to all online documentation for Jargon Software products. The browser startup command and the location of the documentation directory are specified in several name/value parameters in the "system\preferences.ini" file.

Help-->About
Displays the current Jargon Writer version number and build number, license information and how to contact Jargon Software for product support.
 

These are "floating" toolbars, which means that each toolbar can be moved out of the Design Window and positioned anywhere on the screen. To detach ("undock") a toolbar, position the mouse cursor on the gray separator area between buttons, hold down the left mouse button, and drag the toolbar to a new location, then release the mouse button. To redock the toolbar, close the new toolbar frame by clicking the "X" close button to restore the toolbar to its original location in the Design Window.

File Action Toolbar

The first toolbar has five buttons, grouped into two sets, which perform file-related actions that are the same as their corresponding menubar choices.

The first button ("Create new application object") is the same as the "File-->New" menu choice.

The second button ("Open an existing application object") is the same as the "File-->Open" menu choice.

The third button ("Save application object") is the same as the "File-->Save" menu choice.

The fourth button ("Execute application object") is the same as the "Run-->Execute" menu choice.

The fifth button ("Generate 4GL source code") button is the same as the "Run-->Generate 4GL" menu choice. This feature is used only when developing apps that will communicate with host procedures written in the Progress 4GL. It generates one or more Progress ".p" source programs, based on the program specs in host tasks that were defined in the Task Editor.

Each generated program is designed to automatically parse all data parameters sent from the client to the host . The values are placed in normal Progress variables and temp-table fields and are immediately available for use, so developers do not have to write any logic to get input from the client.

Each generated program also contains references ("hooks") to include files in which developers can place all of the business logic needed for each host task, without any risk of changing or invalidating the automatically generated source code. Likewise, if the source code is regenerated for some reason (such as adding another parameter to be sent to the host), there is no risk that doing so will damage any of the business logic written by the developers.

Component Toolbars

The second toolbar contains eight separate toolbars, each with one or more related components, that are used when adding visual objects (containers and components) to the Design Layout Panel or when adding nonvisual objects to the Component Tree Panel. The toolbar with the desired group of components is selected from the drop-down combo box to the left of these toolbars.

Unlike the first 5 buttons, these visual object selector buttons stay depressed once clicked, until a different button within this group is clicked. Whichever button is depressed represents the type of  object that will be added when you click on a grid cell within the Design Layout Panel or click the "+" button in the Component Tree Panel.

User Tip: The first button in each of the component group toolbars is an upward-pointing arrow, similar to the image used as a mouse cursor. This is a "do-nothing" button that simply shuts off selection of the other buttons in that toolbar. It is useful to click this when you are done adding a certain type of component, in order to avoid adding more instances of that component by accidentally clicking in an empty grid cell in the middle layout panel.

1. Containers Toolbar

The "Frame" button selects a frame container object. Frames can only be added under the app "root" node. An app can contain any number of frames. Each frame can contain any of the following objects: menubar, toolbar, panel, cardpanel, tabpanel,  label, textfield, passwordfield, textarea, textpane, combobox, listbox,  button, togglebutton, checkbox, radiobutton, buttonGroupPanel, table, tree, internal frame container, and progressbar.

The "Internal Frame Container" button selects a parent container for "nested" frames (frames that have the "isInternalFrame" attribute set to "true"). This container can hold one or multiple child frames that can be overlaid, tiled or cascaded within this container. In essence, it allows a regular frame to contain multiple "sub-frames", and follows the MDI (Multiple Document Interface) standard.

The "Panel" button selects a single panel container object. The panel, cardpanel and tabpanel containers are normally used inside frames (or nested within other panels) to contain other components. Components allowed within a panel, card, tab or buttongroup panel are: menubar, toolbar, panel, cardpanel, tabpanel, label, textfield, passwordfield, textarea, textpane, combobox, listbox, button, togglebutton, checkbox, radiobutton, buttonGroupPanel, table, tree, internal frame container, and progressbar.

The "Card Panel" button selects a "parent" panel that can contain a "stacked" set of 1 or more regular panels, of which only one is "on top" of the stack at any one time. This is like a deck of cards stacked face-up; only the top card is visible, but any card can be brought to the top by pulling it out of the deck and placing it on the top of the stack.

The "Card" button selects a special panel that is one of the individual cards in a cardpanel.

The "Tabpanel" button selects a "parent" tabpanel that can contain a "tabbed" set of 1 or more panels, similar to a cardpanel but with a tab for each panel displayed at the top, side or bottom, so that the user can directly select a specific panel to be displayed ("on top").

The "Tab" button selects a special panel that is one of the individual tabs (a special panel with a tab on its top, side or bottom) in a tabpanel.
 

The "MiscContainer" button selects a non-visual container to hold miscellaneous components such as the message handler and button group components.

The "MsgHandler" button selects a non-visual component to be contained within a MiscContainer. This message handler allows client and host procedures to display messages in the system message area in the status panel at the bottom of the Jargon Writer frame.

The "MathUtility" button selects a non-visual component to be contained within a MiscContainer. This math utility contains various methods for integer math (add/subtract/multiply/divide) and data type conversions (integer to string, string to integer, etc.)

The "ProgressBar" button selects a small panel that contains two versions of an activity status image, one still and one animated. By default, this progress bar is provided at the bottom of each frame and is animated during loading of xml apps and during host task execution.
 

The "Menubar" button selects a menu bar like the one at the top of the Jargon Writer Design Window. A menu bar can contain any number of menu choices, as long as they fit on one line. Each choice on a menu bar must have at least one menu item or submenu within it. Submenus may be nested arbitrarily deep (or at least as deep as good design would dictate).

The "Menu" button selects a menu within a menubar, or a submenu within a menu.

The "MenuItem" button selects a menu item within a menu or submenu.
 

The "Toolbar" button selects a special panel with one or more buttons. These buttons have limited visual layout attributes, and so toolbars are best used when their buttons will contain only images that are all the same pixel size (such as 25 by 25 pixels), in order to obtain a uniform appearance. The Jargon Writer toolbar being discussed here is a good example of an appropriate design and use of this object. Normally a ToggleButton is used within a Toolbar. The Toolbar also has the special property that all ToggleButtons, Radio buttons and Checkboxes placed within it are automatically members of the same (unnamed) button group.

The "Button" button selects a rectangular button that can contain an image, a caption, or both.

The "ToggleButton" button selects a button that, like a regular button, can contain an image, a caption, or both. It also has the special property that when clicked, it stays selected. That is, it continues to display the "selected" icon. If no special image is used for the "selected" icon, the default image is a 3D shaded rectangle that looks "depressed".

The "Radio button" button selects a special button with a small, round box that toggles between "bulleted" and empty, plus a caption and/or an image. Radio buttons are normally placed in a named button group, so that when one is pressed, any other button in the same group that was previously selected is cleared. Thus these buttons act like the buttons used to select stations on a car radio.

Trivia: Some readers (such as your "chronologically challenged" author [no personal references! - ED.]) may recall when the radio buttons in cars actually stayed physically depressed when pushed. It's all electronics now, and the analogy is much weaker!

The "Checkbox" button selects a special button with a small, square box that toggles between "checked" and empty, plus a caption and/or an image.

Technical Note: The ToggleButton, Radio button and Checkbox are all members of the same "abstract button" class and have very similar properties. For example, any of these button types can be placed in a button group, not just radio buttons, although this may not be the UI behavior that users normally expect. In fact, the buttons in each component group toolbar are really ToggleButtons in a button group, which is why they stay depressed when clicked.

The "ButtonGroupPanel" button selects a panel that is like a regular panel in all respects but with the additional special property that all ToggleButtons, Radio buttons and Checkboxes contained in a ButtonGroupPanel automatically become members of the same (unnamed) button group.

The "ButtonGroup" button selects a special non-visual container that is contained within a MiscContainer. One of its two properties is a "memberList" whose value is a space-separated list of the buttons that are members of this button group. ToggleButtons, Radio buttons and Checkboxes can all be members of a button group, although Radio buttons are normally used.

User Tip: The ButtonGroupPanel and ButtonGroup provide two different ways to accomplish the same goal, namely to group two or more buttons into a common button group, so that when one is selected, it automatically de-selects any previously selected button within that group. A ButtonGroup provides a way to group buttons that may not be located next to each other, or where there are other buttons within the same area that should not be part of the button group. Generally, though, the easiest way to group buttons is by placing a ButtonGroupPanel in the appropriate grid location, and then adding Radio Buttons or other button types in it.

5. Table Toolbar

The "Table" button selects a spreadsheet-like Table with multiple rows and columns, which can be used for displaying browse results, for data entry, and for other purposes. Tables can have both horizontal and vertical scrolling, column headings, single or multiple row selection, column selection, and other features. To add columns to a table, highlight it in the component tree, then select one of the next two buttons and click the "+" button above the component tree.

The "TextCellEditor" button selects a table column in which text can be entered and displayed, similar to a regular textfield.

The "ComboCellEditor" button selects a table column containing a combo box, similar to a regular combo box. The values in the combo box can be dynamically added by a client or host task, or you can add static choices under a ComboCellEditor by using the "ListItem" button in the Lists Toolbar.

6. Text Toolbar

The "Label" button selects a label with an image or text caption.

The "Textfield" button selects a single-line field in which text can be entered and displayed.

The "Passwordfield" button selects a single-line field in which text can be entered but which displays asterisks (****) in place of the characters entered or displayed, for security purposes.

The "Textarea" button selects a multi-line textfield, with optional word wrapping.

The "Textpane" button selects a multi-line textpane for display of text, much like a multi-line label. A textpane does not have a border and has the same background as the frame iteself, so it does not look like a textarea or other data entry fields.

The "Spinner" button selects a specialized textfield object with an integer-only value that can be incremented or decremented by clicking the up or down arrows on its right side.

The "Combobox" button selects an object similar to a text field, but with an arrow at the right that, when clicked, "drops down" a scrollable list of choices. Combo box selections can be populated with static initial values that are assigned by adding ListItem components to the Combobox, or with dynamically assigned values supplied by a host or client task.

The "Listbox" button selects an object somewhat similar in functionality to a combo box, except that it always displays multiple choices in a scrollable vertical list (the list is always "dropped down"). Also, the selected item is highlighted, but it is not redisplayed at the top of the list the way a combo box does.

The "ListItem" button selects a component with a text label and/or an image that is used as one choice within a Combobox, a Listbox, or a table ComboCellEditor.
 

The "Tree" button selects a tree object similar to the trees used in Jargon Writer, such as the Component Tree Panel in the Design Window.

The "TreeNode" button selects a node that can be added under a Tree object or nested under another TreeNode object (to any level of nesting). To add a node, highlight (in Jargon Writer's component tree) the component that is the tree root or node that you want to be the parent node for the new node, then select this TreeNode button and click the "+" button above the component tree.
 

The left-hand panel in the center of the Design Window is the Component Tree Panel. This panel is used to select the currently active "app", and to select a specific component object within the app so that you can modify its layout, properties, events and attributes in the two panels to the right of the Component Tree Panel.

At the top of this panel is a combo box which shows the currently active app,  or a blank entry if no app has been opened or created yet within this session. This combo box is also used to select a different app as the currently active app. You can select any app that has previously been opened or created in this session, and not yet closed, which makes it very easy to work on multiple related apps in one session.

The currently active app is the one whose tree structure, layout, properties and tasks will be displayed in the corresponding panels and windows.  To modify an app, it must be opened and currently active.

Below the combo box is a tree representation of the visual objects that make up the app, starting with the "root" object which is the app itself. To expand the root object, double-click on it. Unlike all other tree nodes, the root object does not have a "+/-" sign that can be single-clicked to expand or contract the node.

When you expand the root icon, you will see one or more frames and/or miscellaneous containters that are the first level containers within the app. By clicking on the "+" sign in front of a frame, or by double-clicking on the frame icon or name, you can see the next level of contents within the frame, such as panels, menubars and other objects. This process may be continued recursively within a branch of the tree, until it is fully expanded (all branches are fully opened down to each individual "leaf").

User Tip: A faster way to completely expand or collapse a tree or one of its "branches" is to click with the right mouse button on the name of the container. This will alternately fully expand or fully collapse the contents of the container on which you click.

Each type of container object and component object has its own icon. Frames and non-visual containers are shown in the order they were defined. Most other types of objects are displayed in the same order as their layout in the Design Layout Panel, reading from left to right and top to bottom. Objects that are defined in list boxes in the Properties Tabpanel rather than in the Design Layout Panel (such as tabs in a tab panel) are displayed in the same order as in the list box.

To select an object to work on, single-click it within this tree. If it is a container which is not expanded, you can double-click the icon or name, which will both select the object and expand its first-level tree contents.

When a frame or panel is selected, its first-level contents are displayed in the Design Layout Panel (the center panel), and the Properties Tabpanel (the right-hand panel) shows the various properties of the frame or panel selected.

When a tabpanel or card panel is selected, the center panel will be blank, and the panels that make up the tabpanel or card panel will be shown only in the component tree. This is because the panels contained in a tabpanel or card panel are not laid out in a grid pattern, but rather are all overlaid or "stacked" on top of each other, so a grid layout is not appropriate.

Table cell editors, misc. containers, message handlers, button groups, trees, tree nodes, menubars, submenus and menu items also do not display anything in the center panel, only in the component tree.

When you select other components such as buttons, checkboxes, radio buttons, labels, textfields, textareas, combo boxes and list boxes, the selected component will be displayed in the center panel along with all other "sibling" components that have the same parent container, and the selected component will be highlighted in blue. Also, the righthand tabpanel will display the properties and attributes of the selected component.

User Tip: The Component Tree Panel can be automatically scrolled horizontally or vertically as needed. You can also make it wider by slowly moving the mouse cursor over the right-hand boundary between this panel and the center panel until the cursor changes to a double-headed horizontal arrow, then holding down the left mouse button and dragging it to the right, then releasing the mouse button. It will auto-size to fully display the widest element of the tree as it is currently expanded.

If you are using a screen resolution higher than 800 by 600, you can also double-click on the "Jargon Writer" frame title at the top of the Design Window to go to full-screen mode. Double-clicking again will restore the display to normal mode. Of course, you can also use the corresponding buttons in the upper right-hand corner of the frame to do the same thing, or to minimize the Design Window temporarily while working on something else.

!! IMPORTANT: Deletes are "recursive". That is, if you delete a panel, it will also delete all components within that panel.

Design Layout Panel
The Design Layout Panel is the center panel in the Design Window. Here you can add menubars, toolbars,  panels, tabpanels, card panels, and other components such as labels, textfields and buttons within frames and panels. You can also control the relative positioning of a group of two or more components within a container by specifying their location, height and width in the grid of cells that make up this panel.

When starting a new app, you begin by clicking the "New" toolbar button or selecting "File-->New" from the menubar. When this is done, you will see one frame (with a default name such as "Frame0") appear in the Component Tree Panel. If you click on this frame node in the component tree, you will see a checkerboard-type grid pattern in this Design Layout Panel.

To begin adding containers and components to this frame, first click (depress) the toolbar button for the type of container you want (such as a panel) from the appropriate toolbar group (such as Containers), then click in the upper leftmost cell of the Design Layout Panel grid. A panel will be added within the frame, and the tree node for Frame0 will be expanded so you can see the Panel0 node, which is highlighted. Notice that the grid layout is cleared; this is because you are now viewing the contents of Panel0, and can begin adding components to it.

To practice, click the "Label" toolbar button, then click in the upper leftmost grid cell to add a label, then click the "Textfield" toolbar button and click in the grid cell to the right of the label cell. Congratulations, you have just created your first screen layout in Jargon Writer!

To view your screen as it will appear, highlight the root object in the component tree, then click the "Execute" toolbar button. You will see that a very small frame has been created, just large enough to hold the label and textfield and the panel. This is the default layout behavior for the Java-based layout system used in Jargon Software products: the "GridBag Layout Manager". Components are placed right next to each other, and containers shrink to the smallest size that can hold all of their contents.

This default layout can be changed by selecting various layout attributes (or "constraints") in the Layout Panel within the Properties Panel. For a more detailed explanation of the layout system (called the "GridBag Layout Manager") used in this panel, refer to the GridBag Layout Manager document.

You can close the execution window by clicking the "X" button in the upper right-hand corner. To save the appfile you have just created, click the "Save" toolbar button or select "File-->Save" from the menubar, then assign a name such as "myapp.xml" and click Save. Notice that the appnames in the combo box and root node of the Component Tree change to "myapp".

Notice that you can select a component in a container by either clicking on its node in the Component Tree or by clicking on its cell icon in the Design Layout Panel.

To move an object from one grid cell to another, drag it with the left mouse button depressed until the upper left-hand corner of the object is inside the destination cell, then release the mouse button. You don't have to position it exactly over the grid cell, if the upper lefthand corner is inside the cell, it will "snap to" when released.

To make an object taller or wider relative to the other sibling objects in the same container, position the mouse cursor over an edge of the object until it changes to a horizontal or vertical two-headed arrow, then drag the edge until it is inside the cell you want to exand it into. It will "snap to" the outer edger of that cell; you do not need to get the edge of the object positioned over the edge of the destination cell.

User Tip: When designing any screen with more than a few components, a useful technique is to leave every other row and column blank; in other words, leave an empty cell between any two components. While this may require some scrolling at times, it will make it much easier to rearrange components if the need arises.

Properties Panel

This panel on the right side of the Design Window contains three panels: an Attributes Panel, a Layout Panel, and an Events Panel. The Events Panel is always displayed at the bottom, while the other two panels can be viewed by selecting either the Attributes or Layout radio buttons at the top of this Properties Panel.

Attributes Panel

The Attributes panel contains a wide range of properties specific to the type of object to which they apply. For example, the properties of textfields include initial value, column width, various edit mask options, and text alignment options. By contrast, the properties of buttons include button caption, caption alignment, icon images for various button states (normal, pressed, selected, etc.), and button group options.

The meanings of most of these various object properties are self-explanatory. For a detailed explanation of each property of each object type, refer to the Component Properties section.

The only property that is common to every container and component is the object name, which must be unique for every object (container or component) within an app.

IMPORTANT: All object names in Jargon Software apps are case-sensitive, which means that "Frame0" and "frame0" are the names of two different frame objects and cannot be used interchangeably. This is the opposite of some other languages (like the Progress 4GL) which are case-insensitive (where the compiler does not care how upper and lower case letters are used for variable names, procedure names, or table and field names). Similarly, the Unix operating system IS case-sensitive, while DOS and Windows are not. For this reason, it is important to adopt a consistent set of rules for naming objects within your app, and these rules should also specify upper or lower case.

• The toolTipText field in the Attributes Tab is where you may enter a one-line context-sensitive help message that will be displayed when the application is run and the mouse cursor is left motionless over an object for a few seconds. Also see the User Tip regarding tool tips in Section 1.

• The isVisible property determines whether an object is displayed on the screen or is hidden (only exists in memory). One use for this property is to add a "secondary" frame that initially will be nonvisible, such as a "browse" frame. When a hidden object is needed, a local or host task can change the isVisible property to "true".

• The isEnabled property determines whether an object is initially enabled for input or disabled when it is first created and displayed.

• The foreground and background properties specify the RGB (Red/Green/Blue) color values for the text and background of a component. When one of these property fields is clicked, a small button is displayed at the right which, when clicked, opens the Color Editor window.

The Layout Panel contains the various GridBag constraints which control the placement and resizing behavior of an object. For more details on each of these constraints, refer to the GridBag Layout Manager document.
 

The GridX, GridY, GridW and GridH values are read-only. These values are determined by the placement of an object in the Design Layout Panel (its X/Y coordinates) and by how many cells it occupies (its height/width).

The Fill combobox controls whether an object will grow to fill its cell horizontally, vertically, both or neither, if it is smaller than its cell.

The Anchor combobox controls the placement of an object within its cell, if it is smaller than its cell. The default is "Northwest".

The Pad X and Pad Y fields are used to add a fixed number of pixels to the width (Pad X) or height (Pad Y) of an object. The values must be integers, and the defaults are zero.

The Top, Left, Bottom and Right Inset values are used to add a fixed number of pixels between the specified edge of a cell and the adjacent edge of the object in it. The values must be integers, and the defaults are zero.

The WeightX and WeightY values are used when a frame is resized, to determine how many pixels will be added to a component's cell, relative to other components within the same container. The values are decimal values with up to 2 decimal places, and the defaults are zero (no resizing).

Events Panel

The Events Panel is used to identify which events Jargon Reader will respond to on a specific object, and which  tasklists will be executed when those events occur. For a more detailed discussion of events and tasks, see the Overview of Tasks and Events section.

The Event name combobox lists all of the events that Jargon Reader can "listen for" on an object. The events in the list vary depending on the type of object. Some objects have no events.

To see or change the tasklists associated with a given event, select that event in the Event Name combobox.

To associate an Event with a Tasklist, first select the event in the combobox, then click the desired tasklist name in the Available Tasklists listbox (scrolling if necessary), then click the "+" button in the bottom set of buttons. This will add the specified tasklist to the Tasklists to execute listbox (the bottom listbox). You may associate an event with more than one Tasklist, so this step can be repeated with the same event and a different tasklist.

To unassociate (remove) a tasklist from an event, first select the event in the combobox, then select the Tasklist in the Tasklists to execute listbox, then click the "-" button in the bottom set of buttons.

To rearrange the tasklists associated with a specific event, first highlight the event, then highlight the tasklist to be moved in the Selected Tasklists listbox, then click the up or down arrow buttons. Tasklists for a given event are processed in the order shown in the Selected Tasklists listbox

To add, change or delete the tasklists which are shown in the Available Tasklists box, select View-->Task Editor  from the top menubar to bring up the Task Editor Window.

User Tip: When you first select an object, the Events Panel will show the first Event that has associated Tasklists (if there is one). This makes it easy to see if an object has any defined actions for any of its events, without selecting each possible event to see if that event has any associated tasklists. Note that there could be more than one Event with associated Tasklists; only the first one in the list will be shown initially.

Status Panel

The Status Panel at the bottom of the Design Window contains a one-line message area at the lower left in which various Jargon Writer status messsages are displayed, and a progress bar at the lower right which graphically indicates the completion status of various actions such as opening, closing and executing apps. No input fields are used in the Status Panel.