       Polisher for Visual Basic Version 1.0 
                 Copyright 1995      
               All rights reserved.    
                   
                 ***SUPPORT*** 
      
     CompuServe:  GO AARDVARK, 24 Hours-A-Day 
     E-mail: 73173.1137@compuserve.com, 24 Hours-A-Day 
     Fax:  1-201-833-1216, 24 Hours-A-Day    
     Voice:  1-610-524-2589, M-F, 9 AM - 6 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*** 
 
          Required: MSDOS 3.3 or later version. 
          Windows 3.1x, Windows for Workgroups 
          or Windows NT and compatibles. 
 
 
                 ***Installation*** 
 
Insert the disk in a floppy drive. If you have not already 
done so, start Microsoft Windows.  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. 
  
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, merely open Polisher.
After the About Notice has cleared the screen, click on the "File"
menu and select the "Open" menu item. An Open File Common Dialog Box
will be displayed. Select the project or file you wish to load, then
click the "OK" button. The input file will be displayed in the main
display area. To reformat the input file immediately - using the
program's default settings, click on the Process Menu and select
Polish - or click on the Polish toolbar button. The reformatted
file will now occupy the main display area. Save the polished
file, and that's all there is to it! 
 
       Polisher can only work with ASCII text files.  The Visual
Basic Programmer's Guide outlines the very real advantages of saving
your files in text format, and is worth reading.  To get your code
into text format do 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. 
 
       To refine the formatted output, click on the program's
"Option" menu; or Polish toolbar 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, use the Help
Search Utility Help, the Contents screen for this file, or press
F1 for context-sensitive help. 

                         ***New Features***

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: 
 
VBPOL directory: 
BASICLAN.KEY      Keyword file. 
README.TXT        This file. 
TEST1.BAS         Example for, and to test VBPOL. 
TEST2.FRM         Example for, and to test VBPOL. 
VBPOL.VTD         User Dictionary
VBPOL.EXE         Executable file. 
VBPOL.HLP         Help file. 
 
Windows\System directory 
AMERICAN.VTD      Main Dictionary
CMDIALOG.VBX 
COMMDLG.DLL 
SPIN.VBX
THREED.VBX
VBRUN300.DLL
VSVBX.VBX
VTSPELL.VBX
WINSIZE.DLL       Help support file.
 
These files are used by the setup processor and are  
normally present in the Windows\System directory: 
 
DDEML.DLL 
VER.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                 * 
            * Orders 1-800-482-2742             *
            * Voice: 1-201-833-4355             * 
            * Fax: 1-201-833-1216               * 
            * CIS: GO AARDVARK                  * 
            * E-mail: 70544.1372@compuserve.com * 
            * All rights reserved.              * 
            ************************************* 


