Starting CodeGuide

 

Starting CodeGuide using the supplied VM

Windows

You can start CodeGuide by choosing Programs | Omnicore CodeGuide 6.1 | CodeGuide 6.1 in the start menu or by double-clicking on the CodeGuide 6.1 icon on your desktop.

Linux/Solaris

You can start CodeGuide by running the CodeGuide shell script which can be found in the application's root directory. You might have to adapt the CodeGuide shell script if you do not have the Sun J2SDK 1.4.1 installed at the default location.

 

Example (assuming the CodeGuide has been installed in /opt):

 

/opt/codeguide-6.1/CodeGuide

Mac OS X

You can start CodeGuide by clicking on the CodeGuide application bundle on your desktop.

 

 

Commandline arguments

 

 

You can supply either

 

 

 

 

If CodeGuide is already running and you start CodeGuide with commandline arguments, no second instance of CodeGuide will be started. Instead the arguments will be communicated to the instance of CodeGuide which is already running using socket communication.

 

You can supply either

 

 

If you do not supply any commandline arguments a second instance of CodeGuide will be started. However beware that both instances use the same configuration file. Thus the CodeGuide instance which is exited last will overwrite the previously saved configuration.

 

 

Opening files using the Windows Explorer

Java files and CodeGuide Project files (.cpr files) are automatically associated with CodeGuide during the installation.

 

Thus you can use the Windows Explorer to open project files and load Java files.

 

 

 

 

 

 

 

 

 

Drag and drop on Windows

While dragging project files or Java files onto the application window is not possible you can Drag Java files or CodeGuide project files onto the CodeGuide icon on the desktop. The behavior is the same as described in the previous section.