Upgrade Guide - Prolifics

Converting an ApplicationTable 4-4 Source code for backward compatibility (Continued)Functionsm5strct.csm5mbar.cf2struct.cPurposeSupport for JAM 5 bulk load/unload functions.Support for JAM 5 menu bar API.Converts screens to C structures for use with sm5strct.cfunctions.The design and features in your particular application dictate which utilities and sourcemodules are required in your conversion.When a Feature is Missing...As you work to establish a configuration and executable for your application you willundoubtedly notice that some features of JAM 5 are no longer supported in JAM 7.When this happens you must chose among converting to the new JAM 7 conventions,finding a new approach, or linking in sample code we've provided to mimic the JAM5 behavior.As mentioned before, LDB initialization is a prime example of this. JAM 7 supportsthis directly through the initial text property of an LDB widget. However, analternative, and perhaps more flexible, approach is to explicitly place values into thewidgets through JPL or C statements. Finally you can continue to use the ini files fromJAM 5 by linking with the sample code we provide (sm5ldb.c) and callingsm5_ldb_init from your main routine. The choice is yours. Different applicationsand schedules require different choices.Screens and Related TopicsOnce you've built a JAM 7 environment for your application, the next step is gettingyour screens to operate within it. Here the differences between migration andconversion become apparent.All JAM 5 screens will execute under JAM 7 without conversion. JAM 7 recognizesthat the screen was created in JAM 5 and translates fields, attributes and edits intowidgets and properties. Widgets of this type are called “Release 5” widgets. You canUpgrade Guide 4-9