CD Actual 15

home *** CD-ROM | disk | FTP | other *** search

/ CD Actual 15 / CDACTUAL15.iso / cdactual / program / c / WP51SUP.ZIP / READ.ME < prev next >

Wrap

Text File | 1992-02-27 | 28.9 KB | 740 lines

WP Document Interface ToolKit (c) 1991, 1992 LumiNet Publishing Corporation Seamless interface from C and Clipper programs into WordPerfect Documents LumiNet Publishing Corporation 14832 Fireside Drive,Suite 100 Silver Spring, MD 20904 Sales............. (301) 384-6375 Technical Support. (301) 622-9642 Borland is a registered trademark of Borland Corporation Clipper and Nantucket are registered trademarks of Nantucket Corporation Microsoft is a registered trademark of Microsoft Corporation MS-DOS is a registered trademark of Microsoft Corporation WordPerfect is a registered trademark of WordPerfect Corporation What, Who and Why? What is the WP Document Interface ToolKit? The WP Document Interface ToolKit provides the developer with document creation and formatting functions that are fully compatable with WordPerfect version 5.1 standards, and can be accessed from any C or Clipper program. All WordPerfect codes created from the WP Document Interface ToolKit are identical to any formatting codes that you would create directly from within a WordPerfect document. These codes can be edited and deleted, just as if they were originally created from within WordPerfect! Who Should Use the WP Document Interface Toolkit? Any developer who is writing applications using C or Clipper, and has a requirement to merge application information into a WordPerfect document! Why Should I Use the WP Document Interface ToolKit? Seamless Interface! For any developer who is merging information from a database into WordPerfect documents, the WP Document Interface ToolKit is a MUST! If you have ever tried to write and debug a complex macro from within WordPerfect, you will appreciate this opportunity to avoid using the WP Macro features - and continue to write programs in the platform you are most comfortable! Sure, you can create a WordPerfect macro that merges ASCII delimited database information into your 'preset form'...but what happens if your macro runs slowly (especially on a LAN), or your users cancel from the macro before it has completed? A partically completed or an empty file! The routines that make up the WP Document Interface ToolKit allow you to merge database or text information from your application directly into a WordPerfect document - Quickly and Accurately! No more truncated macros, no more missing data! No more creating macros within WordPerfect! Compatability ------------- WordPerfect (version 5.1) The WP Document Interface Toolkit creates WordPerfect 5.1 compatable document files. Clipper (Summer '87 & 5.0) Using the WP Document Interface Toolkit's object files CLP2WP.OBJ and CLPSUP.OBJ, linked with your application provides compatability with Clipper Summer '87 and version 5.0. See Appendix B - Linking for more information on linking object files with your application. Microsoft C (through version 6.0) Using the WP Document Interface Toolkit's object file MSC2WP.OBJ, linked with your application provides compatability with Microsoft C (up to and including version 6.0). See Appendix B - Linking for more information on linking object files with your application. Borland C, C++ (through version 2.0) Using the WP Document Interface Toolkit's object file BCC2WP.OBJ, linked with your application provides compatability with Borland C and C++ (up to and including version 2.0). See Appendix B - Linking for more information on linking object files with your application. Terms and Syntax ---------------- argument....... parameter passed to the function <arg1c...arg#c> character argument, with the first argument identified with a '1', the second argument identified with a '2', etc. <arg1n...arg#n> numeric argument, with the first argument identified with a '1', the second argument identified with a '2', etc. Function Overview The following is a list of functions that can be called from C and Clipper rograms: Document File Handling ---------------------- Create/Open WPC file Close WPC file Document Formatting ------------------- Left Right Margins Top Bottom Margins Justification Page Numbering Text Formatting --------------- Centering Hard Return Attributes on Attributes off Indent Add text Tab Hard Page Return Graphics -------- Horizontal Line Vertical Line System ------ System Date System Time You can test the following routines by using the examples in the Function Reference Guide. Not all of the routines are covered in this readme file you must register your copy of the routines for the full Function Reference Guide. Function Reference Guide ------------------------------------------------------------------------------ Document File Handling Functions wpopen() ------------------------------------------------------------------------------ Function.................. wpopen(<arg1c>) Description............... Creates a WPC v5.1 document file, and then Opens the file that was created Arguments................. <arg1c>=character=file specification Return.................... logical <TRUE>=successful <FALSE>=unsucessful Comments/Example.......... This routine CREATES the WPC compatable document file - that is, a new document file will exist after this command has successfully completed. Once the document file is created, it remains open during the session until a WPClose() call is made. By leaving the file open, you have access to all document formatting, graphics and text commands. These commands will be placed into the document that is created and opened by using the WPOpen() call. Reminder: Do Not issue a WPClose() directly after a WPOpen() if you intend to add any formatting, graphics or text commands. The document file must remain open to insert text and formatting codes. Only issue a WPClose() command directly after a WPOpen() when you intend to create a WPC document with nothing in it. Clipper Example: filespec = "C:\WP51\DOCS\DOC00001.W51" If WpOpen (filespec) ?"Successfully created and opened document" Else ?"Unsuccessful" Endif C Example: int fspecsiz; fspecsiz=25; char filespec[fspecsiz+1]; filespec = "C:\WP51\DOCS\DOC00001.W51"; wpopen (filespec); ---------------------------------------------------------------------------- Document File Handling Functions wpclose() ---------------------------------------------------------------------------- Function.................. wpclose() Description............... Closes a WPC v5.1 document file, one that was previously created/opened from the WPOpen() function Arguments................. None Return.................... Nothing Comments/Example.......... This routine CLOSES the WPC compatable document file - a document file that had been previously opened by using the WPOpen() function. By issuing a WPClose(), all text, document, and graphic codes can no longer be written to the document file. Reminder: Do Not issue a WPClose() directly after a WPOpen() if you intend to add any formatting, graphics or text commands. The document file must remain open to insert text and formatting codes. Only issue a WPClose() command directly after a WPOpen() when you intend to create a WPC document with nothing in it. Clipper Example: filespec = "C:\WP51\DOCS\DOC00001.W51" If wpopen(filespec) ?"Successfully created and opened document" ... wpclose() Else ?"Unsuccessful" Endif C Example: int fspecsiz; fspecsiz=25; char filespec[fspecsiz+1]; filespec="C:\WP51\DOCS\DOC00001.W51"; wpopen(filespec); ... wpclose(); ---------------------------------------------------------------------------- Text Formatting Functions wpadd() ---------------------------------------------------------------------------- Function.................. wpadd(<arg1c>) Description............... Appends the text string specified in <arg1c> to the document. Arguments................. <arg1c>=text string Return.................... Nothing Comments/Example.......... This routine appends the text string into the opened WPC document. This string can be a field from a database - however it must be in character format. Clipper Example: filespec = "C:\WP51\DOCS\DOC00001.W51" If wpopen (filespec) ?"Successfully created and opened document" *-- Adds some text to the document --* wpadd("Please tell your friends ") wpadd("that they should buy this product!") ... wpclose() Else ?"Unsuccessful" Endif C Example: int fspecsiz,bold,italic; fspecsiz=25; char filespec[fspecsiz+1]; filespec = "C:\WP51\DOCS\DOC00001.W51"; wpopen(filespec); /* Adds some text to the document */; wpadd("Please tell your developer friends "); wpadd("that they should buy this product!"); ... wpclose(); ---------------------------------------------------------------------------- Text Formatting Functions wpcntr() ---------------------------------------------------------------------------- Function.................. wpcntr() Description............... Centers the next text string specified to the document. Arguments................. None Return.................... Nothing Comments/Example.......... This routine centers the next text string into the opened WPC document. Clipper Example: filespec = "C:\WP51\DOCS\DOC00001.W51" If wpopen (filespec) ?"Successfully created and opened document" *Adds some centered text to the document* wphrtn(1) wpcntr() wpadd("Centering this text") wphrtn() ... wpclose() Else ?"Unsuccessful" Endif C Example: int fspecsiz,bold,italic; fspecsiz=25; char filespec[fspecsiz+1]; filespec = "C:\WP51\DOCS\DOC00001.W51"; wpopen(filespec); /* Adds some centered text to the document */; wphrtn(1); wpcntr(); wpadd("Centering this text"); wphrtn(1); ... wpclose(); ----------------------------------------------------------------------------- Text Formatting Functions wphrtn() ----------------------------------------------------------------------------- Function.................. wphrtn(<arg1n>) Description............... Appends a WPC Hard Return into the document the number of times that is specified by <arg1n>. Arguments................. <arg1n>=the number of times to insert a hard return Return.................... Nothing Comments/Example.......... This routine appends the WPC compatable hard return code into the document that was created and opened using the wpopen() function. Clipper Example: filespec = "C:\WP51\DOCS\DOC00001.W51" If wpopen (filespec) ?"Successfully created and opened document" *-Add 2 hard returns to the document-* wphrtn(2) ... wpclose() Else ?"Unsuccessful" Endif C Example: int fspecsiz; fspecsiz=25; char filespec[fspecsiz+1]; filespec = "C:\WP51\DOCS\DOC00001.W51"; wpopen(filespec); /* Add 2 hard returns to the document */; wphrtn(2); ... wpclose(); ----------------------------------------------------------------------------- FILES WE SUPPLY FOR LINKING ----------------------------------------------------------------------------- CLP2WPC.OBJ REQUIRED FOR ALL CLIPPER LINKING CLPSUP.OBJ REQUIRED FOR ALL CLIPPER LINKING BCC2WPCS.OBJ BORLAND SMALL MODEL BCC2WPCM.OBJ BORLAND MEDIUM MODEL BCC2WPCL.OBJ BORLAND LARGE MODEL MSC2WPCS.OBJ MICROSOFT SMALL MODEL MSC2WPCM.OBJ MICROSOFT MEDIUM MODEL MSC2WPCL.OBJ MICROSOFT LARGE MODEL ----------------------------------------------------------------------------- Linking ----------------------------------------------------------------------------- CLIPPER 87 BLINKER EXAMPLE # wpclp000.LNK NOBELL BLINKER EXECUTABLE CLIPPER E0;F10;R25 BLINKER INCREMENTAL OFF BLINKER MEMORY PACK 10 OUTPUT wpclp000 FILE wpclp000 FILE clp2wpc FILE clpsup library \CLIPPER\EXTEND search \clipper\clipper search \clipper\overcl CLIPPER 87 MICROSOFT LINKER EXAMPLE LINK MYFILE+CLP2WPC+CLPSUP,MYFILE,,EXTEND+CLIPPER; MICROSOFT "C" v6.0 LINK EXAMPLE LINK @MYFILE.LNK This is myfile.lnk myfile+ <- your obj file msc2wpcs <- our interface routines myfile <- your exe name , <- default slibce; <- microsoft small model library BORLAND C++ v2.0 Refer to your Borland manual on the Integrated Development Environment as that would be the perfered method. If you need to link from the command line, the following example is for large model. tlink c:\bC\LIB c0l MYFILE bcc2wpcl, MYFILE, nul,emu mathl cl System Requirements The minimum equipment requirements to run WP Document Interface Toolkit are: IBM PC XT, AT, PS/2 or compatible computer with a hard disk, 512KB of RAM, MS/PC DOS 3.3 or later and, one of the following compilers: Clipper Summer '87 from Nantucket Clipper 5.0 from Nantucket Microsoft C (up through version 6.0) Borland C,C++ (up through version 2.0) Installation The WP Document Interface Toolkit is supplied on one 5.25 inch or one 3.5 inch diskette and consists of the following files: CLP2WPC.OBJ CLPSUP.OBJ........ Clipper Object Files MSC2WPC.OBJ....... Microsoft C Object File BCC2WPC.OBJ....... Borland C,C++ Object File MANUAL.DOC........ WP Document Interface Toolkit Manual READ.ME........... Notes on last minute changes To install WP Document Interface Toolkit files, copy the appropriate files (depending on your type of compiler) to your designated library directory. Software License Agreement Software: Refers to the toolkit files contained in the disk supplied as WP Document Interface Toolkit, together with any updates subsequently provided by LumiNet Publishing Corporation. Documentation: Refers to the printed materials provided with this toolkit or later supplied by LumiNet Publishing Corporation. Software Copies: Refers to the actual copies of all or any portion of the toolkit and may include updates and backups. Allowable Uses: WP Document Interface Toolkit is distributed as a shareware product. This allows you to try the product prior to registering/purchasing your own copy. The shareware version of WP Document Interface Toolkit contains small model C Object files, as well as limited documentation covering available functionality. If you like this product, you should become a registered user! To receive a complete set of documentation, large model C Object files, free technical support, and updates as they become available, you must be a registered user. LumiNet Publishing Corporation agrees to provide the registered user a non-exclusive and non-transferable license to use the Software contained herein for an unlimited duration. These rights granted herein are limited to use of the Software, Documentation and Software Copies as defined within the Agreement. All rights not specifically granted in this Agreement are reserved by LumiNet Publishing Corporation. The Licensed/registered user may use the Software in the following ways: 1. Load the Software into RAM and use it on a single workstation or terminal; 2. Install the Software onto a permanent storage device - a hard or fixed disk drive; 3. Make copies of the Software for backup purposes only, and the Licensee must keep possession of them at all times. The un-Licensed/non-registered user may freely use and distribute the Shareware version of the Software and Documentation. Prohibited Uses: Under any other circumstances attempt to rewrite, decompile, dis-assemble or reverse-engineer any of the Software or Software copies. Limitations: You, the user, has limited rights to use the Software, Documentation and Software Copies as expressly provided in this license. LumiNet Publishing Corporation, retains title to all the Software, Software Copies, and Documentation. The Licensed user agrees to protect the Software, Software Copies, and Documentation, from unauthorized publication, use, reproduction or distribution. Limited Warranty LumiNet Publishing Corporation warrants to the original Licensed user that the magnetic media that this toolkit is distributed on is free from defects in material and workmanship under normal use and service, for a period of thirty (30) days from date of purchase as contained in your receipt/invoice. LumiNet Publishing Corporation's entire liability and your exclusive remedy shall be replacement of the defective disk, provided the disk is returned to LumiNet Publishing Corporation with a copy of your dated receipt, invoice or serial number, name and address. LumiNet Publishing Corporation shall not be liable to the Licensee or any other person for any special, consequential, indirect or ther similar damages or claims including loss of profits, or any other commercial damage caused or imagined to have been caused directly or indirectly by the use of the Software. LumiNet Publishing Corporation specifically disclaims all other warranties, expressed or implied. LumiNet Publishing Corporation makes no representations or warranties with respect to the merchantability or fitness of the WP Document Interface Toolkit for any particular purpose, business or application. Implied warranties of merchantability are expressly and specifically disclaimed. In no event shall LumiNet Publishing Corporation's liability for damages to you or any other person exceed the price paid for the license to use the Software, regardless of the form of any claim. Updates and Revisions LumiNet Publishing Corporation reserves the right to modify and/or enhance WP Document Interface Toolkit and its documentation without obligation to notify any person or organization of such changes. Technical Support We offer free technical support in the U.S. as outlined below to registered users of WP Document Interface Toolkit. Please complete and mail the enclosed registration card to ensure you are entitled to technical support. Electronic Mail LumiNet Publishing Corporation provides unlimited technical support to registered users in the U.S. and Canada via an electronic bulletin board service - CompuServ address #. Suggestions for improvements are always welcome. Telephone You may contact us at (301) 622-9642 between the hours of 9:00AM and 5:00PM Eastern Standard Time. Mail Our address is: LumiNet Publishing Corporation 14832 Fireside Drive, Suite #100 Silver Spring, MD 20904 USA ┌────────────────────────────────────────────────────────────────────────┐ │ WP Document Interface Toolkit ORDER FORM │ └────────────────────────────────────────────────────────────────────────┘ Yes ! I want Seamless interfaces between C/Clipper and WordPerfect ! ┌──────────────────────────────────────────────────┐ │ Name:_______________________________________ │ │ │ │ Company:____________________________________ │ │ │ │ Street:_____________________________________ │ │ │ │ City:_______________________________________ │ │ │ │ State:______________ Zip:__________________ │ │ │ │ Country:____________________________________ │ │ │ │ Phone:______________________________________ │ │ │ │ FAX:________________________________________ │ │ │ ┌─────────────────────────────────────────────────────────────────────────┐ │ Please ship me _________ copies of WP Document Interface │ │ Toolkit @ $55.00/each │ │ _______________ │ │ │ │ Maryland Residents Only - add Sales Tax @ 4.5% --------------- │ │ │ │ U.S. Shipping ONLY : │ │ │ │ Federal Express 2nd Day Air @ $15.00 (US) _______________ │ │ │ │ Federal Express Next Day Air @ $25.00 (US) _______________ │ │ │ │ Regular Postal Service @ $ 3.00 (US) --------------- │ ├────────────────────────────────────────┐ │ │ Disk Size: 3.5"_____ 5.25"_____ │ Total : _______________ │ └────────────────────────────────────────┴────────────────────────────────┘ Please Ship COD _____ (in the US only) or Check Enclosed _____ Amount : US $________ Sorry no Credit cards accepted at this time. Please mail orders to : LumiNet Publishing Corporation 14832 Fireside Drive, Suite 100 Silver Spring, MD 20905 (301) 384-6375 Sales (301) 622-9642 Support 75140,1176 CompuServe Address If you need further information please call us.