--------------------------------------------------- Vermont Views Designer Main Code Generating Program --------------------------------------------------- Copyright 1990 Vermont Creative Software --------------------------------------------------- What is VVDCODE? ---------------- VVDCODE.EXE is a program that reads a Vermont Views Designer library report and produces the following: - the C source code for a prototype main program - a list of the choice list keywords - a list of the help keywords - warnings about inconsistent states in the Designer library How to use VVDCODE ------------------ Step 1: Using VVDRPT, generate a full report for the Designer library that includes all the forms in the library. Step 2: Run VVDCODE as follows: C:\> VVDCODE reportname where: 'reportname' is the full name of the report generated in Step 1 (for example, libname.rpt). The extension is required) The outputs are as follows: reportname.c - prototype source code reportname.cl - choice list keywords reportname.hlp - help keywords STDOUT - warning messages on the console Step 3: (Optional) Edit the reportname.cl and reportname.hlp files to replace the dummy information with real choices and help text. Step 4: Compile and link the reportname.c file and run the resulting executable. Stubs will have been defined for any installable functions. Press any key to pop the window down and continue form/menu processing. What VVDCODE doesn't do ----------------------- VVDCODE does not define memory for fields or scrollable regions with the OMITFROMSTRUCT flag set or call sf_datap() or ssr_datap() to resolve such fields. If a library contains omitted fields or scrollable regions the prototype code generated must be edited to take care of the fields before it is compiled and linked. VVDCODE does not yet understand the concept of data-entry form paging. What VVDCODE does do -------------------- Displays the following warning messages: (1) Data-entry form called by MENUCALL(). (2) Menu form called by FORMCALL(). (3) Referencing a form that is not defined in the forms library. (4) Inconsistent use of an installable function. This means that a function name is used more than once when the implied parameter lists are different--for example, using myfun() for both a begin field function (FORMPTR) and a field validation function (UCHAR *, UCHAR *, FORMPTR). Includes the required Vermont Views header files. Includes the required Designer-generated header files. Defines the structures used by data-entry forms. Defines the array of information about data-entry forms that is passed to dl_mnget(). This array gives information about the subforms for the menu that are called with FORMCALL(). The choice list memory file (cl_mfp) element for the array elements are also properly set. Gets, processes, and frees the head forms. Head forms are forms that are not called by FORMCALL() or MENUCALL() from another form or menu. Only the head forms are explicitly read from the library, any subforms will be be pulled out automatically. Defines, allocates, reads, and frees choice list and help memory files if they are required. Defines and frees any stub forms. Stub forms are subforms referenced by forms in the Designer library but not defined in the libaray. The stub forms identify themselves by name and can be exited by pressing [Enter]. Defines stubs for any installable functions. The installable function stubs pop up a window identifying the form/field and stub. The window goes away and the function returns on the next keystroke. Press any key to pop the window down and continue form/menu processing. ----------------------- End of file VVDCODE.TXT -----------------------