Pop-ART Software Pop-Tools V1.50-01 Additional Reference ****************************************************************************** This text contains important supplementary information regarding this release of Pop-Tools. Contents -------- Warning..... version 1.5 only Caution..... requires specific directories Examples.... notes and tips on using Licensing... application development requirements Corrections to documentation ****************************************************************************** WARNING!!! : ------------ This release of Pop-Tools is compatible with SmartWare II version 1.5 ONLY!!! Upgrades to versions later than this will be available through authorized Pop-Tools resellers and the ARTIST BBS Pop-Tools conference, and will be released following official Informix distribution of SmartWare II upgrades. CAUTION : --------- If Pop-Tools is not installed beneath the SmartWare II system path directory, i.e. "\smartii", please remove the installed files, then go through installation again. Proper operation of the Pop-Tools development system, including compatibility with future upgrades and enhancements, requires that Pop-Tools files are located in subdirectories beneath the SmartWare II directory (regardless of what that directory is named, i.e. "\smartii", "sm2", "sm2v102", or whatever). Following installation of this release of Pop-Tools, the directory structure should appear as such: \SmartII\PopTools\lib \data \examples \source \qkcreate \popmenu \utility In each of the list Pop-Tools directories is a "files.lst" file that lists the files that should be in that directory following installation. EXAMPLE PDL CODE : ------------------ The examples from the Pop-Tools manual that have a filename (i.e. EX?????.PF3), are all located in the "\smartii\poptools\examples" subdirectory following installation. These examples have not been compiled prior to release in order to save disk space on the installation diskettes. They must be compiled before use. It is recommended that they be compiled in the data base manager module, since some of the examples are "module specific". It is also recommended that the example code be compiled "no-debug" for optimum performance, then printed on your printer using "remember tools print". It may be easier to follow the execution of the example code from a print out as it is executed. BEFORE executing the example code, change to the "examples" subdirectory in SmartWare II by issuing the command tools directory new_directory "\smartii\poptools\examples" (where "\smartii" is the "SmartWare II system directory" that was specified during installation), then compile all of the example files. The "\examples" subdirectory should be the current SmartWare II path prior to executing any example project. Notes: Throughout the examples projects, the SmartWare II system path is assumed to be "\smartii\" and that Pop-Tools was installed under that subdirectory. If SmartWare II is actually installed in a different directory, the example code that makes reference to "\smartii\" must be changed to reflect the actual system path, i.e. "\sm2\", etc. The following information pertains to specific examples: ALL INDEX EXAMPLES (i.e. EXINDX01, EXINDX02, etc.) Execute EXINDX03.RF3 first (once after starting the data manager module) in order to "initialize" the external references to the PTSP environmental variables (dpath, lpath, etc.). EXINDX03.RF3 is a customized "setenv" for running index example projects. After it is executed once, its references to paths, colors, etc. will be module locked and available to the other index examples that require them. EXDFILE1.PF3 When compiled "as is" this example will produce error messages, since there are two variables that must defined by the developer. The example requires two specified data files, but there are no sample files provided. Once the names of two similar data files are entered into the example code, and it is compiled, the function getfields() will be demonstrated. It is recommended that the developer select a standard view to modify, then use "replicate data-file", if the required files do not already exist. EXDOS06.PF3 ----------- Do not try to add the "Shareable" attribute during execution of this example, unless SmartWare II is being used on a network. When the "Shareable" attribute is selected and a network driver is not active, setattrib() will fail and none of the attributes chosen will be set for the example file. APPLICATION DEVELOPMENT WITH POP-TOOLS (when Source Code is purchased) -------------------------------------- When the The Pop-Tools Source Code license is purchased, the libraries may be used as a "resource" in the creation of the Developer's function libraries (in accordance with the "Pop-Tools Development System and (certain) Source Code" licensing agreement). The Developer may use whatever functions that are needed out of the respective Pop-Tools libraries and include them with others. CAREFULLY READ THE LICENSING AGREEMENT - it outlines specific conditions for the distribution of ANY Pop-Tools libraries or Pop-Tools derivative libraries. Generally, the Developer will develop at least one PRIMARY Pop-Tools derivative library that remains "loaded" throughout an application, while grouping other functions in libraries that are loaded only when needed. It is suggested that this PRIMARY library contain a mixture of the display, file services, and user interface functions. It may contain other Pop-Tools function types (however, this is a design issue particular to the application). Note: Some of the libraries have duplications of functions that are found in other libraries. This is done to make each library "stand alone". Most of the time, these duplicate functions are string library functions. In all cases, the duplicate function name is a slight modification of the original function name and is initialized as a GLOBAL function. Ensure that any necessary, supplementary functions are included in a Pop-Tools derivitive library along with the original function. CORRECTIONS TO DOCUMENTATION : ------------------------------ User Guide APPLICATION DESIGN page 19 "Cloning" continued change both instances of "memunpack" in the example code segment to read "unpack" ------------------------------------------------------------------------------ Note: Any documentation pages enclosed with your Pop-Tools installation diskettes should replace those already in the manual.