Upgrading from Standalone OmniMark Studio

Feature

Standalone Studio

Studio for Eclipse

OmniMark Project

A project is the encapsulation of the command line used to run the program.

Eclipse provides a launch configuration in which you can specify the command line parameters of the program. You can create and edit launch configurations by selecting “Run…” or “Debug…” from the “Run” menu, or using the equivalent button on the tool bar.

Eclipse project

In standalone Studio there is no concept of a project in the sense of a group of files that belong together.

In Eclipse, everything is in done a project, and a project is a file structure and includes all files within that file structure. To begin a program, you must create a project using “New…” on the “File” menu. You can import existing files into your project using “Import” on the “File” menu.

Eclipse workspace

Standalone Studio has no concept of a workspace. You simply work in the file system.

Eclipse maintains its own workspace. See the Workbench documentation for more information.

Run the current program file

In standalone Studio, you can run the “Active Window Project” without creating a project file.

In Eclipse, you can run a program without creating a launch configuration by choosing “Debug as…” from the Run menu or the Debug button and then selecting “OmniMark program”

Open a file

You can open any file in Studio.

You must import a file into the Eclipse environment before you can view or edit it.

Preferences

Edit -> Preferences

Select “Windows” -> “Preferences…” and choose OmniMark from the list.

Paths

Set during install

Must be set by user using preferences mechanism specified above.

Compile XVC

File -> Create Virtual machine Code File

File -> Export -> OmniMark bytecode export Wizard

Debugging

Hit the Start button or choose Start Debugging from the Run menu.

In the OmniMark edit or debug perspective, choose either the Run or Debug buttons on the tool bar or choose Run or Debug from the Run menu.

More than one OmniMark debug instance of the same program can be run simulataneously with the same or different command line parameters using one of the Debug run methods list above.

Program output

The log window captures both the standard output and standard error output from the program.

The console window captures both the standard output and standard error output from the program but displays them in different colors.

Finding compile time errors

Click the error flag on the tool bar or choose “Next Error” from the Search menu.

Errors are displayed in the problems window. Select the error to move to it in the edit window.

An error icon also appears in the gutter before the line number in the edit window on the lines which have errors. Placing the cursor over the error icon will display the associated error message in a pop up window.

Breakpoints

Click in the left margin to set or clear a breakpoint. Breakpoints are lost when you close the file or close Studio.

Right click in the left margin and choose “Add breakpoint”. Breakpoints are persistent from one Eclipse session to another. There is a specific breakpoint window which displays all of the set breakpoints and it provides a mechanism to enable and disable the beakpoints.

Variables and datascopes.

Select from the view menu.

Select the appropriate window in the OmniMark debug perspective. Some Java specific windows may be visible but inactive. Some windows, such as the breakpoints window, are shared. If you debug a Java program and an OmniMark program at the same time, they will share this window.

Throttle

Allows you to control the speed at which your program executes. Select from the View menu.

There is no throttle in OmniMark Studio for Eclipse.

Stepping

The stepping buttons on the debug toolbar let you step through your program one action at a time.

The stepping buttons in the debug window let you step through your program one action at a time. Some Java specific stepping buttons may be shown, but are not enabled.

Running multiple programs

In standalone Studio, you can only run or debug one program at a time. If you need to run more than one program at once, (for instance, to debug a client and a server) you can open two copies of Studio.

In Studio for Eclipse, you can debug multiple programs in parallel. You can only open one copy of Eclipse, however you can spawn a new Eclipse window using Window -> New window.

Execute at full speed.

By default, standalone Studio runs a program in debug mode, which is slow. You can run at full speed (without debug information being tracked) by choosing “Execute project” from the Run menu.

In Studio for Eclipse, you can choose either to Run (a program at full speed) or Debug it using either the Run menu or the tool bar buttons.

Documentation

Standalone Studio includes full OmniMark language documentation in WinHelp format. No fulltext searching.

Studio for Eclipse includes full OmniMark language documentation in the Eclipse help system. The Eclipse help system has integrated full text searching.