Setting Up and Running Rogue Wave Views Studio on UNIX Systems

To launch Rogue Wave Views Studio on UNIX for the first time, you must set the environment variable ILVHOME to the root directory where Rogue Wave Views was installed.

Rogue Wave Views Foundation Studio, a generic version of Rogue Wave Views Studio using shared libraries, is provided in the following directory:

where <system> indicates the name of the platform you are using, such as ultraspcr32_10_11, x64_thel5.0_4.1, and so on. <subsystem> indicates the name of the subplatform you are using, such as static_pic, shared, and so on.

When you use ivfstudio for Rogue Wave Views for the first time, ivfstudio prompts you to select the plug-ins it has detected.

Select the plug-ins you want to load by checking the corresponding toggle buttons. Then click OK. The plug-ins you use in this session will be loaded again the next time you launch ivfstudio.

If you want to select the plug-ins before ivfstudio starts running, you can launch ivfstudio with the -selectPlugIns argument. The Rogue Wave Views Studio Plug-Ins dialog box will appear and you can specify again the plug-ins you want to load.

Studio provides you with the SelectPlugIns command that you can use to select plug-ins. To use this command, choose SelectPlugIns from the Tools menu in the Main window. Studio displays the Rogue Wave Views Studio Plug-Ins dialog box for you to make your selections. You will then have to exit Studio and launch it again to load the plug-ins you just selected.

You can also specify either a list of the modules you want to load or a directory containing all the modules you want to load. When you do this, the plug-ins loaded in the previous session are ignored.

Upon initialization, Studio loads the extension modules declared in the user's preferences. These preferences can be changed using the Select Plug-ins choice from the Tools menu of Studio. The new choices will be loaded the next time Studio is launched.

You can use the ILVSTPLUGINS environment variable to indicate a list of the modules you want to load. You can specify the full paths or the paths relative to the working directory, separated by a “;” character (a semicolon character).

Some Rogue Wave Views packages come with their own plug-ins for Rogue Wave Views Studio. For more information, see the documentation of the Rogue Wave Views packages you are using.

The following is a list of some common plug-ins located in the $ILVHOME/studio/<system>/<subsystem> directory:

With the Rogue Wave Views Gadgets package, you can use the Rogue Wave Views Studio GUI Application plug-in to edit GUI applications with gadgets panels. The corresponding dynamic package is libsmguiapp.<ext>, where <ext> is .so, .sl, and so on, according to your platform. You can also use the Rogue Wave Views Studio GUI Generation plug-in to generate the C++ code for the GUI part of your application. The corresponding dynamic package is libsmguigen.<ext>, where <ext> is .so, .sl, and so on, according to your platform.

With the Rogue Wave Views Grapher package, you can use the Rogue Wave Views Studio Grapher plug-in to edit your graphers, nodes, and links. The corresponding dynamic package is libsmgrapher.<ext>, where <ext> is .so, .sl, and so on, according to your platform.

With the Rogue Wave Views Prototypes package, you can use the Rogue Wave Views Studio Prototypes plug-in to edit your business graphic objects. The corresponding dynamic package is libsmproto.<ext>, where <ext> is .so, .sl, and so on, according to your platform.

If for any reason you have to build an executable of Rogue Wave Views Studio, go to the $ILVHOME/studio/<system>/<subsystem> directory and run the make utility passing the name of the executable you want to build as the only argument.

The provided ivfstudio can be used with plug-ins which bring the capabilities of the other Studio executables you can build.