SGI RapidApp Migration Kit

Current Version: Version 1.10

Introduction

The RapidApp Migration Kit will take a UIL file generated by SGI's RapidApp builder tool (version 1.2 or higher) and convert any incompatible structures to forms acceptable to Builder Xcesory 5.0.

Additionally, the converter will scan any C++ source code generated by RapidApp and preserve any user modifications such that when source code is next generated by Builder Xcessory, all these modifications are preserved and inserted in the corresponding location in the BX-generated source code.

Prerequisites

The RapidApp Migration Kit requires both the BX Binary and Code Generation Updates Version 5.0.4 or higher. If you have not already installed these updates you should do so before running BX with any converted RapidApp UIL files.

The RapidApp Migration Kit only converts files generated by RapidApp version 1.2 or higher. Significant changes to the generated code and save file format between version 1.1 and version 1.2 prevent the RapidApp converter from accurately reading and migrating these older RapidApp files.

Click here to go to the BX Update Download page

Installation

• cd
• zcat raconvert-.tar.Z | tar xvf -

This will create a sub-directory named ra_convert which contains the migration kit binaries and data files.

Additional information about running the migration kit tools is located in /ra_convert/doc/index.html

Q & A

Q. Will the migration tool deal with VkSimpleWindow and VkWindow classes that are not explicitly subclassed?

A. Yes. The migration tool will convert them to an explicit class using the same naming convention as RapidApp.

Q. Will the migration tool handle menus properly?

A. Yes. RapidApp only pretends to support VkMenus. Most of the objects actually created by RapidApp are the Motif equivalents with the additional resources added. BX 5.0 supports all of the VkMenu classes. The migration tool spots menu structures and converts the widgets to the corresponding VkMenu objects. This also applies to VkOptionMenus.

Q. Will the migration tool handle OpenInventor components?

A. Yes. You must, however, open the Inventor palette in BX 5.0 before you can load the migrated UIL files into BX.

Q. When I migrate a VkGenericDialog subclass my dialog child widget is always made into a class. Why?

A. When RapidApp generates code it always makes the child a class even though you didn't build it that way in RapidApp. To make BX match the generated code structure of RapidApp the migration tool automatically makes the child of a VkGenericDialog into a class.

Q. Do I ever need to go back to RapidApp after the migration?

A. No. Once your application has been successfully migrated to BX 5.0, you should never need to go back to RapidApp.