       Polisher for Visual Basic Version 4.0 
                 Copyright 1995      
               All rights reserved.    
                   
              
     PLEASE READ the Installation section   !
                  
                 ***SUPPORT***
     
     CompuServe:  GO AARDVARK, 24 Hours-A-Day
     E-mail: 73173.1137@compuserve.com, 24 Hours-A-Day
     Fax:  201-833-1216, 24 Hours-A-Day   
     Voice:  201-862-1446, M-F, 9 AM - 5 PM ET 

 
               ***File Contents*** 
 
            Overview 
            System Requirements 
            Installation 
            Getting Started 
            New Features
            Compatibility Issues 
            Frequently Asked Questions 
            File Distribution 
 
 
     ***Polisher for Visual Basic Overview*** 
 
AARDVARK Software thanks you for your interest in Polisher. 
 
        Polisher is 100% Visual Basic® code, and demonstrates
the enormous power Visual Basic brings to the Windows® developer.
Polisher adds to Visual Basic's strengths by automatically
formatting code files. Now, the individual programmer or a project
manager can professionalize the "look and feel" of source code.
Using Polisher, output files will will have a code structure and
attain a level of standardization that would please the most
meticulous programmer. Project managers may establish guidelines
for formatting code and comments with the expectation of those
standards being easily maintained. 
        
        Polisher gives you a wide choice of formatting options to
professionalize and standardize your code output. You may set the
indentation, and the number and placement of blank lines for any
code structure or comment style. Multiple line declarations may be
split - listing each declaration on it own line, while the "As<type>"
statements are aligned in a column of your choosing. Single line If
statements may be split into a If block structure. Code instructions
such as Option Explicit may be inserted, and "Next" variables removed.
Another big plus, Polisher will spell check the input and output files,
based on your pre-defined preferences. 
        
        While Polisher was designed for use with Visual Basic 3.0,
it will produce polished code for other versions of Visual Basic -
and other Basic dialects. In that regard, the information in this
help file presumes the reader is knowledgeable of the Windows and
Visual Basic standard conventions. If you are new to either, we
strongly recommend you become familiar with the appropriate user's
guide(s).        
        
               
              ***System Requirements*** 
 
                    16 Bit Version
          
          Required: MSDOS 3.3 or later version, with
            Windows 3.1x or Windows for Workgroups.
                         
                    32 Bit Version
               
                Windows95 / Windows NT
         
          Note:  The 16 Bit Version will run under
                 Windows95 / Windows NT.

                 ***Installation***

     Windows 3.x and Windows NT: Insert the disk in a floppy
drive. Choose "Run" from the Program Manager File menu.  At the
command line type: "A:\Setup" (If "A" is not your floppy drive
letter, substitute the appropriate letter). Follow the setup
instructions on the screen.

     Windows 95: Open the Control Panel, then double mouse click
on the "Add/Remove Programs" icon. Click on the Install/Uninstall
tab's "Install Button." Insert the disk 1 in a floppy drive, then
click on the Install Program dialog's "Next" button. Follow the
setup instructions on the screen.       

     Three are three setup options:
     
     1. Typical (Recommended). Selecting this option installs on
     your hard disk all of the files listed below - in the File
     Distribution paragraph.

     2. Custom. Choosing this option allows you to select which
     supporting files will be installed. You may use this option
     to omit the installation of dynamic-linked libraries (*.dll),
     custom controls (*.ocx) and similar files to the "Windows/
     System" directory/folder. Warning: Pretty Printer requires the
     "System" files normally installed by the installation program.
     You should only omit their installation if those files already
     exist on your system, and you do not want the existing files
     replaced.  
     
     3. Minimal. Installs only the executable and BASICLAN files, 
     and the required system files.

     With the introduction of Visual Basic 4.0, it became necessary
to make changes in the file naming protocol. Because of these file
name changes, installed upgrades do not overwrite older files.
Therefore, if you are upgrading from an earlier version of Pretty
Printer, it is recommended that you delete the current directory
containing the Polisher files before installing the upgrade.  
Not deleting the files will have no affect on the Pretty Printer's
performance; however, the older files will continue to occupy hard
disk space.  

Note: By default, the 16 bit version is installed in a sub-
directory/folder named VBPOL. Also by default, the 32 bit
version installs to Program Files\Aardvark\Polisher.
You may change these default paths during the installation
process. And both versions may be installed in the same sub-
directory/folder.  
  
     If you have problems with the installation, check the
"Compatibility Issues" select below.  Also check to see if
your device drivers and *.DLL files are current.  Updating
drivers and *.DLL files to the latest versions has fixed 
all sorts of odd problems.  If you can not resolve your 
installation problems, contact AARDVARK Software for 
assistance.    
              
             ***Getting Started*** 
      
     To format a chosen project or file, open Polisher. After
the About Notice has cleared the screen. An Open File Common
Dialog Box will be displayed. Using standard Windows conventions,
select the project or file you wish to load, then click the 'OK'
button. If you have selected a individual input file, it will be
displayed in the main display area. If you have selected a project,
the Project Dialog will be displayed. From the 'Project Dialog',
select the files to be reformatted, then click on the 'Process All
Selected Files' button. The first input file will be displayed in
the main display area.

     To immediately reformat the displayed input file, using the
program's default settings, click on the 'Process' menu and select
'Polish' - or click on the 'Polish' toolbar button. The reformatted
output file will now occupy the main display area. Save the polished
file, and that's all there is to it!

     To refine the formatted output, click on the program's 'Process -
Option' menu item; or Polisher's toolbar 'Option' button. The 'Option'
tabs will be displayed. Each tab provides the user with the opportunity
to define specific output styles. To get a better understanding of these,
and other features supported by Polisher, press F1 for context-sensitive
help.
 
       Polisher can only work with ASCII text files.  Visual
Basic 4.0 saves code files in ASCII text; however, Visual Basic
3.0 and earlier versions save code files as binary by default. To
get those code files into text format do one of the following:
 
(1) For a new project, go to the Visual Basic  
Options Menu - Environment Dialog Box.  Select  
the option to save all of your project's code in  
text format. 
(2) To convert existing code files saved in binary 
format, go to the Visual Basic File Menu, and 
select the Save File As entry.  When the dialog 
box appears, check the Save as Text box, then 
save the file using standard Windows conventions. 
 
       
                         ***New Features***

New features in 4.0 (2/96)
      
     Supports Visual Basic version 4.0.
     Adds 1,800 keywords.
     Supports long file names.
     Supports line numbers.
     Enhanced user interface.
     16 and 32 bit versions now available.
     Supports right mouse button.
     Enhanced "Line Continuation" support added.
     Enhanced "File Extension" support added.
     Enhanced "Dialect" support added.
     Updated Help File.

New features version 1.0b

     Fixed alignment bugs:
          AlignAs
          Stand alone comments
          'End Select'
      Fixed spell checking bugs:
          Multiple files and use of custom dictionary
          One-character words
          Literals in declare statements
      Fixed miscellaneous bugs
      Help file updated
      Interface improvements:
          Toolbar
          Status bar
          Splash screen

New features  version 1.0a
     Bugs fixed 


***Polisher for Visual Basic Compatibility Issues*** 

       Polisher rearranges your code, and there is always a small
chance the reformatted program will not compile exactly the same as
the original version. This situation might occur as a result of a bug
in Polisher, or a bug in the Visual Basic compiler. Sometimes adding
or removing even a single space can affect results. It is always a good
idea to revalidate your program after processing.  If you find a problem,
please let us know.

       Polisher allows you to insert "Option Explicit" in the reformatted
output, where it was not coded in the input file. Selection of this option
might cause compilation problems due to undeclared variables in the input
file.  

       ***Frequently Asked Questions*** 
 
Q:  Does Polisher require Windows? 
 
A:  Yes.  It has been tested on Windows 3.1, Windows for  
Workgroups, Windows NT 3.5, OS/2 2.1 and beta versions  
of Windows 95.  It should work on other versions of Windows. 
 
Q:  Does Polisher require Visual Basic 3.0? 
 
A:  Polisher does not require any version of Visual Basic to be  
installed, it is self-contained and only requires Windows. 
 
Q:  What dialects of BASIC does Polisher handle? 
 
A:  Polisher is primarily designed for Visual Basic for 
Windows 3.0, and its keyword lists are set to that dialect.  
However, it will attempt to process any Basic dialect as
long as the file is saved in ASCII format. It often achieves good
results with Visual Basic for Windows 1.0 (you must save text) and
2.0; Visual Basic for DOS, Quick BASIC, QBasic, and even GWBASIC code.
It has some knowledge of Visual Basic for Applications, Word
Basic and Access Basic.   
 
Q:  Is the product guaranteed? 
 
A:  Yes, if you are not satisfied, you may return it within  
90 days for a full refund. 
 
Q:  Is Polisher integrated into Visual Basic?   
 
A:  Polisher is a separate application from Visual Basic and runs  
in a separate window.  Polisher is manipulating your Visual Basic  
files and these files cannot be opened inside Visual Basic during the 
Polishing process. 
 
Q:  Does Polisher work on binary files? 
 
A:  Polisher uses text files.  That means that you  
should set your Options/Environment/Save As Default Format  
to Text.  Existing projects can be quickly converted by  
using File/Save As/ and checking the "Save as Text" box. 
Whether you use Polisher or not, Microsoft advises  
that you use text rather than binary format.  If the binary  
format is corrupted, it is unrecoverable, while the text  
format can often be repaired with a text editor. 
 
Q:  Can the demo version be enabled as production?  Can you  
electronically ship the production version to me? 
 
***A:  While the demo version cannot be changed to production,  
we can e-mail the production version of the product to you  
via CompuServe for an additional $10.00. We need your  
CompuServe address. Sorry, we cannot ship to Internet,  
Prodigy, America OnLine or other services.  We still ship  
the regular version to you.   
 
 
           ***File Distribution*** 
 
Polisher for Visual Basic SETUP installs files on your 
hard disk as follows: 


Note: By default, the 16 bit version is installed in a sub-directory/folder
named VBPP. Also by default, the 32 bit version installs to Program
Files\Aardvark\Pretty Printer. You may change these default paths during
the installation process. And both versions may be installed in the same
sub-directory/folder.    

VBPP directory (16 bit):

README.TXT           This file.
TEST1.BAS            Example for, and to test VBPP16.
TEST2.FRM            Example for, and to test VBPP16.
VBPOL16.HLP          Help file.
VBPOL16.EXE          Executable file.
BASICLAN.KEY         Keyword file.
VBPOL16.CNT          Windows95/NT help support file.
VBPOL.VTD            Custom Dictionary
_isREG16.DLL         Installation file.
_deisREG.ISR         Installation file.
deisLL.ISU           Installation/Uninstall file.    

Pretty Printer folder (32 bit):

README.TXT           This file.
TEST1.BAS            Example for, and to test VBPP16.
TEST2.FRM            Example for, and to test VBPP16.
VBPOL32.HLP          Help file.
VBPOL32.EXE          Executable file.
BASICLAN.KEY         Keyword file.
VBPOL32.CNT          Windows95/NT help support file.
VBPOL.VTD            Custom Dictionary
_isREG32.DLL         Installation file.
_deisREG.ISR         Installation file.
deisLL.ISU           Installation/Uninstall file.    


16 BIT: Windows\System (Winnt/system) directory

AMERICAN.VTD
VSPELL16.DLL
VSPELL16.OCX
COMDLG32.OCX
COMDLG16.OCX
OLE2.REG
OLE2PROX.DLL
TABCTL16.OCX
VB40016.DLL
VAEN21.OLB
CTL3DV2.DLL
OC25.DLL
OLE2.DLL
TYPELIB.DLL
OLE2DISP.DLL
OLEEPROX.DLL
OLE2CONV.DLL
STORAGE.DLL
COMPOBJ.DLL
OLE2NLS.DLL
STDOLE.TLB
SCP.DLL

32 BIT: Windows\System (Winnt/system32) folder

AMERICAN.VTD
VSPELL32.DLL
VSPELL32.OCX
COMDLG32.OCX
TABCTL32.OCX
VB40032.DLL
VEN2232.OLB
OLEPRO32.DLL
MSVCRT40.DLL
MSVCRT20.DLL
MFC40.DLL
CTL3D32.DLL


Please send us your comments, suggestions and bug reports.
If you like what we do, please tell your friends.  If you
        don't like what we do, please tell us.
           
            ***************************************************
            *          Polisher for Visual Basic              *
            *             Copyright 1993-1995                 *
            *            AARDVARK Software, Inc.              *
            *              972 Sheffield Road                 *
            *              Teaneck, NJ 07666                  *
            *             Voice: 201-833-4355                 *
            *             Fax:   201-833-1216                 *
            *              CIS: GO AARDVARK                   *
            *       E-mail: 70544.1372@compuserve.com         *
            *                                                 *
            *                                                 *
            *                ***SUPPORT***                    *
            *                                                 *  
            *    CompuServe:  GO AARDVARK, 24 Hours-A-Day     *
            *E-mail: 73173.1137@compuserve.com, 24 Hours-A-Day*
            *     Fax:    201-833-1216, 24 Hours-A-Day        *
     	    *   Voice:  201-862-1446, M-F, 9 AM - 5 PM ET     *  
            ***************************************************

