11.07.2015 Views

Upgrade Guide - Prolifics

Upgrade Guide - Prolifics

Upgrade Guide - Prolifics

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Upgrading the Operating EnvironmentColor AliasesSupport for color aliases has now moved from the GUI resource and initialization filesto the JAM configuration map file, clrcmap. Any color aliases that you added shouldtherefore be moved to the configuration map file. Remember to use the utilitycmap2bin to convert this file to binary format.Update Your Data Dictionary into a Repository and LDBLDB InitializationWhile the format of most configuration files has not changed, an important exceptionis the Data Dictionary. In fact, both its role and its name have changed. JAM 7 usesthis file as a development tool; a repository of reusable widget definitions, stored inJAM library format. It is no longer used to create the runtime Local Data Block (LDB).You must use the dd5upg utility to convert your Data Dictionary to a repository. Ifyour application relies on the LDB, use dd5upg -l to create a JAM 7 library (ldb.lib)which is automatically loaded into the LDB at runtime. For details on using dd5upg,refer to “The dd5upg Utility” on page 4-21.JAM 7 no longer supports LDB initialization through ini files. We do however providesample code that you can use to mimic JAM 5 behavior. You must choose whether toconvert over to the new JAM 7 conventions or simply link in the sample code.An LDB in JAM 7 is simply a library of screens. JAM 7 performs initialization byeither setting the initial text of the LDB widgets or by explicitly placing values intothem through JPL statements. The sample code we provide, sm5ldb.c, enables inifiles to work as they did in JAM 5, providing near seamless compatibility. Similarsupport is available for LDB scopes, Form structures, Data Dictionary records, and theold menu bar API.Update Your Main RoutinesAny changes that you made to the main routines in JAM 5, jmain.c and jxmain.c,should be reevaluated and transferred to the main routines provided with JAM 7. Oneway to locate these changes is to compare the distributed JAM 5 main routines withthe JAM 5 main routines that you have been using. Then carry these changes forwardto the JAM 7 main routines, if appropriate.<strong>Upgrade</strong> <strong>Guide</strong> 4-5

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!