Browser Project Menu

The Browser Project menu allows you to construct your interface in Build Mode, test look and feel in Play Mode, run and debug generated code in Debug Mode using your environment's debugger, launch a build of the application you are building in Builder Xcessory, check files in and out of your environment's source code control system, and edit files.

Select Project from the Browser menu bar to display the following menu:

Browser Project Menu

Build Mode (Ctrl+B)


Note: Default mode of Builder Xcessory.

Allows you to use the Palette, Browser, and Resource Editor to create interface objects and edit their resource values.

Play Mode (Ctrl+P)

Allows interface objects to appear as if you compiled and linked your interface, without connected callback structures. All widgets behave normally, and menus, accelerators, mnemonics, and geometry management function as they will in the completed application. The Palette and Resource Editor are withdrawn. Pre-defined callbacks are invoked while Builder Xcessory is in Play Mode. Other callbacks display a message in the Browser Message Window.

If you change resource values while in Play Mode, these values are not necessarily retained when you return to Build Mode (thus allowing you to experiment without changing the values in your interface).


Note: Geometry resource changes are reflected in the interface when you return to Build Mode.

All resource values listed in the Resource Editor (except those for which Placement is set to None) will be Saved or Generated.

Debug Mode (Ctrl+D)

Allows you to launch a build-and-debug session with your environment's debugger. If your environment's build tool is not an integral part of the debugging tool, selecting Debug Mode first launches a build, waits for the build to complete successfully, and loads the debugger with the just compiled application.

Builder Xcessory can make use of the following debuggers.

Development Environment

Debugger

Version Number

Platform

Any environment

CodeCenter

4.x

SunOS, Solaris, and HP-UX

Any environment

ObjectCenter

2.x

SunSoft Workshop

debugger

2.0, 3.0

SunOS and Solaris

SGI Developer Magic

Debugger

2.3 and higher

IRIX

Builder Xcessory actions in Debug Mode

When you select Debug Mode, Builder Xcessory performs the following operations:

· Generates code for your interface.

If you changed your interface since the last code generation, Builder Xcessory automatically regenerates your source code depending on your currently selected language.

· Builds the interface code, as necessary.

Builder Xcessory causes the source code to be compiled. If your build tool is an integral part of you debugger, the build is performed by the debugger. Otherwise, the separate tool is used.

· Starts your debugger, as necessary.

Upon successful compilation, Builder Xcessory starts your debugger (if not already running) using the start command on the Tools Customization dialog.

Note: You can edit the start command on the Debugger & Build tab of the Tools Customization dialog. Refer to Debugger & Build Manager .
When your debugger starts up, the Builder Xcessory main windows are withdrawn, although you may still make selections from the Browser menus.

· Connects to your debugger.

You can manage or modify the connection between Builder Xcessory and your debugger on the Debugger & Build tab of the Tools Customization dialog. Refer to Debugger & Build Manager .

· Unmaps Builder Xcessory product windows.

· Passes control to your debugger, which runs your interface.

Run, test, and debug your interface. Return to Builder Xcessory to continue development by selecting Build Mode or Play Mode from the Browser Project menu. If you return to Builder Xcessory while your debugger is running your program, Builder Xcessory sends a reset command which might interrupt program run without ending the session.


Note: You can set this reset command for the CenterLine debuggers.

Returning to Builder Xcessory

When you return to Builder Xcessory in either Play Mode or Build Mode, the session remains active. At any time, you can automatically load your interface program back into the debugger/interpreter by selecting Debug Mode from the Browser Project menu.

Changing interfaces

If you are using CodeCenter/ObjectCenter with one interface already loaded, and you want to load an entirely different interface from Builder Xcessory, follow these steps:

1. On CodeCenter/ObjectCenter's command line, enter the following

unload user

2. Select Debug Mode from the Browser Project menu to load and run the new interface.


Note: You must select the Use CenterLine Tools debugger option on the Debugger & Build tab of the Tools Customization dialog. See Debugger & Build Manager .

If you initiate a session from Builder Xcessory and then Exit the Builder Xcessory, the session remains running.

Exiting CodeCenter/
ObjectCenter

To exit CodeCenter/ObjectCenter, enter:

quit

at the CodeCenter/ObjectCenter command line.

Make Application

Launches a build of the application for which you are constructing an interface. Builder Xcessory generates code for the application, and causes your environment's build tool to build the application, as shown in the following table:

Platform

Build Tool

Version

Platform

SunSoft Workshop

MakeTool

2.0 and 3.0

SunOS and Solaris

FUSE

Builder

2.0 and higher

DEC UNIX

Developer Magic

Build View

2.3 and higher

IRIX

Any Environment

Code/ObjectCenter

4.x and 2.x

SunOS, Solaris, and HP-UX


Note: The Browser message window displays reports of the build status.

Check Out Source

Displays the Check Out dialog.

Check Out Dialog

Allows you to check out any file from your environment's source code control system. The default directories and files displayed at the top of the dialog are those in the current working directory. To select a directory and display its files, double-click on the directory name. To select a file, click on the file name.

Selection

The Selection input box displays the currently selected file.

Changing the displayed file

You can change the displayed file by selecting a new file, or by performing the following steps:

1. Click in the input box.

2. Delete its contents.

3. Enter the full pathname of the file you want to check out.

Check Out Options

Use the Check Out Options to determine how the file will be checked out:

· Check Out Locked

Allows you to lock the file. Another user cannot check out the file until you check it back in.

· Check Out Read Only

Allows you to check out a read-only version of the file. This checks out the file without locking it.

· Cancel Lock

Removes a lock. Use this option if you locked a file and no longer need to keep the lock.

· Specify Version String

Allows you to request a specific version number of the file, if more than one version exists. Enter the version number in the input box.

· Overwrite Existing File

Allows you to overwrite a read-write version of a currently checked out file.

Note: Before checking out a file, you must select your source code control system. See Tools Preferences for more information about selecting a system.

Check In Source

Displays the Check In dialog:

Check In Dialog

Allows you to check a file back into your environment's source code control system. The default directories and files displayed at the top of the dialog are those in the current working directory.

To select a directory and display its files, double-check on the directory name. To select a file, click on the file name.

Selection

The Selection input box displays the currently selected file.

Changing the displayed file

You can change the displayed file by selecting a new file, or by performing the following steps:

1. Click in the input box.

2. Delete its contents.

3. Enter the full pathname of the file you want to check in.

Check In Options

Use the Check In Options to determine how the file will be checked in.

· Specify Version String

Allows you to assign a new version number or name to the file, if more than one version exists. Enter the version number in the input box.

· Keep File Copy

Allows you to maintain a read-only copy of the file you are checking back into the source code control system.

· Comments

Add comments describing your modifications.

Note: Before checking a file in, select your source code control system. See Tools Preferences .

Edit File


Note: You must select an editor from the Tools Customization dialog before using this options. See Tools Preferences for more information about selecting editors.

Allows you to select a file to edit. Select Edit file to display the Edit File file selection dialog:

Edit File Dialog

Filter field

By default, the Filter field of the File Selection dialog contains the name of the directory from which you are running Builder Xcessory.

Files box

The Files box lists the files in the directory which match the file filter, set to "*" by default.

Directories box

To display the contents of a different directory, enter the directory name in the Filter field and click the Filter button. You can specify match strings using regular expressions. For example, *.uil lists only files ending in the characters .uil. Click OK to open the specified file or Cancel to remove the File Selection dialog.

Selection field

To select a file, click on the file name in the File box, or enter the full pathname in the Selection field.

 

Documentation: