Using the Legion GUI

Table of Contents
1. Menu bar
2. View windows
3. Context folders
4. GUI text files vs. Legion BasicFileObjects
5. Memos
Other GUI pages
Other on-line tutorials & documentation
Other GUI pages:
Click on the to move to the selected text.

A note on this page's style conventions: context path names are in a fixed font and the GUI's main menu bar command options are in green. If you need to click a series of options, they will be separated by a "|" pipe. For example, File | Import indicates that you need to go to the menu bar, click "File" and then click "Import".

1. Menu bar

When you open the GUI, the main GUI menu bar is displayed across the top of your screen. It consists of a title bar and menu bar. Any new view windows or dialog boxes that are called up will appear below the main menu bar. In order to display context space information, the GUI creates a highly structured memory cache in your computer. It gets this data from the Legion host computer via the port specified in the <PPP> argument when you started the GUI.

Legion context space can be quite large and complex, so the initial view shows the first three levels of context space, starting at the session root. You can click the View | Branch extend or View | Tree extend commands on the main menu bar to see more levels.

2. View windows

You will also see a window displaying part of context space. This is known as a view window. Every view window has a view root. This will always be a context folder. The first view window displayed on startup uses the user context root path as its view root. This path is also called the session root and it represents the highest level of data contained in the GUI cache. Figure 2 shows a view window that uses /home/lcohen as its session root. A selected context, such as /home/lcohen/programs could act as view root in a new window, so that different windows could show different parts of context space. You can open multiple view windows from the main menu bar by clicking View | Add. Each view window's title bar shows its view root's context path (use this path to determine the full context path of any folder or member displayed in the view window). This view can be extended by selecting View | Extend on the main menu bar.

To close a view window, click the closure icon on the right side of the title bar. This will remove the view from the screen entirely. It cannot be recovered. If you have closed the last view window, use the View | Initiate command to open a new view window.

3. Context folders

Legion context space is represented in the GUI as a collection of context names. These names identify objects in your Legion system (classes, executables, basic files, etc.) and are organized into sets of context folders (such as /hosts, /class, or /users: the /class name is highlighted in Figure 1). All of the elements in a context folder can be generically referred to as context members or more simply as members (since they are all members of a common folder).
Figure 1: GUI view window

When you first start the GUI you see an outline of your context space. A folder's contents are shown just to the right and below. A folder can hold other folders: in Figure 2, the / root context folder contains holds the /home context folder, which in turn holds /Bill. The tree view uses various icons to distinguish between folders and members (i.e, the folder icon identifies a context folder). The (Empty) notation indicates that a folder is empty. If the GUI doesn't know whether or not a context contains any members it will include a (Not Opened) to indicate that the GUI has not yet asked Legion to produce any context members at this level of the context space tree and therefore does not know whether or not any such members exist. You can double-click on the context folder or select View | Extend from the main menu to get member information.

The GUI does not update its display of a folder's status unless you manually update it (via double-clicking the folder icon or selecting View | Extend) or make changes in another view window. If an independent process creates or removes new members in a folder the GUI will not show this change until you manually update the folder's status. The GUI is not a real-time model of context space: it essentially takes a snapshot of the desired portion of context space. If another user deletes an object that you are working on, the GUI will not automatically reflect this change until you try to execute or save your changes.

4. GUI text files vs. Legion BasicFileObjects

A Legion BasicFileObject is an object that contains text. A GUI text file is a Legion BasicFileObject that has been marked as a text file via a text editor window. It will be then have a (Text file) notation in the GUI view window. By default, all BasicFileObjects will be marked as (Basic File) unless specifically notated differently through the text editor window. This notation is for user convenience only: all GUI text files are BasicFileObjects.

5. Memos

You can attach a memo to any member object. A memo is a BasicFileObject that contains notes, instructions, or information about an object. Memos can be created and edited in a text editor window. To start a new memo, double-click the object. To edit an existing memo, select the desired object and then click Edit | Memo.

Memos are automatically assigned the following context path in the GUI's context space:

/zzz_GUI_STORAGE_zzz/MEMO_FILES/<object context path>
The <object context path> part of this path is the full context path of the object to which the memo is attached.*

Please note that the zzz_GUI_STORAGE_zzz/ context won't show up in the GUI view windows but will be visible from the command line. This context is created the first time that you use that session root for a GUI session. It will persist between sessions (login with the same Legion user name and password and use the same session root in order to use it again).

* I.e., the memo is associated with the object's context path, not with the object itself. If an object has multiple context names, the memo will only appear next to the one name. If you remove that name, you remove the memo as well, whether or not though the object itself exists.

Other relevant on-line documents:
Click on the to go to the page.
Logging in to a running Legion system
Introduction to Legion context space
Context-related commands
Legion tty objects
Running a PVM code in Legion
Running a Legion MPI code
Running native MPI code
Quick list of all 1.7 Legion commands
Usage of all 1.7 Legion commands
FAQs for running programs in Legion
Starting a new Legion system
Legion security
Legion host and vault objects
Adding host and vault objects
Brief descriptions of all on-line tutorials

Last modified: Mon Apr 24 16:35:41 2000


[Home] [General] [Documentation] [Software]
[Testbeds] [Et Cetera] [Map/Search]