		     Welcome to Graphic Vision 
		     -------------------------

Copyright (c) 1995,1996 Jason Burgon
All rights reserved
All rights not expressly licensed to the user are reserved to the developer.

Version 1.01 (25:03:96)



OVERVIEW
===========

Graphic Vision is a graphical application framework modeled on Borland 
International's pascal version of Turbo Vision 2.0.  It has almost exactly 
the same functionality, user and programmer interface as Turbo Vision, but 
uses a 256 VGA or SVGA graphics screen for its visual output instead of TV's 
text-only screen.  

Graphic Vision (GV) is not "Turbo Vision on a graphics screen".  There would 
be little point in making Graphic Vision *look* like TV.  GV just *works* 
like TV.  GV's visual appearance is similar to that of OWL, though it's 
appearance can easily be altered for specialist applications, such as games, 
by simply re-writing or overriding some of the draw methods.

All existing Turbo Vision applications should convert to Graphic Vision,
most of them quite easily.  You can also use GV applications that you would
never have considered using TV for, such as games "front ends".  Like TV, 
Graphic Vision fully supports real and 16-bit DOS protected mode programs.  
Later versions will also support 32-bit DPMI if Borland ever get round to 
releasing a 32-bit DPMI Pascal compiler.

Graphic Vision uses its own (very fast) graphics engine (including mouse
cursor animation) which is VESA VBE compliant.  This allows Graphic Vision 
applications to use any screen resolution from 320x200 to 1600x1200 with 
almost every SVGA graphics card ever made. The mouse is fully supported in 
all GV compatible video modes, which can be up to 32 x 32 pixels in size 
when the target CPU is a 386 or better (16 x 32 on a 286).


MINIMUM SYSTEM REQUIREMENTS
==============================

DOS 3.0
286 processor
640K RAM (2MB for the DPMI version)
SVGA Graphics card capable of 640 x 480 x 256 colours
VESA BIOS or TSR conforming version 1.0 or higher (UniVESA driver supplied)
Hard Drive with at least 2MB free
Turbo Pascal for DOS (version 7.0)

Recomended System Requirements

DOS 6.2
Fast 386 processor or better
Microsoft compatible mouse (Version 8.0 or better)
SVGA video card with capable of 800 x 600 x 256 colours
VESA BIOS or TSR conforming version 1.0 or higher
Hard Drive with at least 10M free
Borland Pascal (version 7.0)

Graphic Vision only supports 256 colour VGA/SVGA video modes. I did think
about supporting other modes, but this is looking unlikely at the moment.





INSTALLATION
===============

This product comes with its own interactive installer/demo program which 
allows you to specify which parts of the product you want to install and the 
directories you want to put them into.  Not only that, the installation 
program is itself a Graphic Vision application, so you can have a look at
GV in action before deciding to install it!

INSTALL.EXE will make a temporary directory (\GV$) on your hard drive then 
copy all the files needed to run the demo/installer into it.  These files 
and the temporary directory it makes will be deleted when you exit the 
installer.

Installing from a download
--------------------------

Unzip all the files contained in the .zip file into a (empty) directory on 
your hard drive or onto a floppy disk. You can now follow the steps in the 
following section.

Installing from floppy disk
---------------------------

Run INSTALL.EXE that is on the distribution disk (eg A:INSTALL).  This 
program will check your machine is GV compatible, then copy and run the 
GV demonstation/installation program on your hard drive.  Choosing 
Options|Install will then display the install screen where you can choose 
the parts of this product you want to install and the directories you want 
to install them into.

See the WHEN THE DEMO WON'T RUN section if it won't.


GRAPHIC VISION, BORLAND AND BORLAND PASCAL.
==============================================

Graphic Vision was written for Pascal applications programmers using Borland 
or Turbo Pascal 7.0. It was written with Borland Pascal 7.0 and TASM 3.2.
Graphic Vision is not a Borland product, so please don't go ringing their 
hotline about it! See the HOW TO GET HELP section if you have problems.

I started writing GV about two years ago with just the Turbo Vision source
code that came with Turbo Vision 6.0 for guidance.  Since then I have
upgraded to Borland Pascal 7.0 which comes with their source code for all
the Turbo Vision units. I have, as a consequence, replaced much of my
original code with modified Turbo Vision source code.

The above has had two consequences:-

  1. Graphic Vision is more Turbo Vision compatible than it otherwise would
     have been.

  2. I cannot truly call Graphic Vision all my own work.

The second point means that I cannot ship complete copies of the source code
because Borland's lawyers would be on me like a ton-of-lawyers.  The
solution was simple:

What I provide you with in the registered and licenced versions are all the 
DIFFERENCES between the Turbo Vision source code and its Graphic Vision 
equivalent.  The GV installation program makes copies of your Borland run-
time-library source files and "patches" my code into them.  Hey presto, you 
have the Graphic Vision source code and I still have a shirt on my back.

This does mean you need the Borland RTL disk (supplied with Borland Pascal
with Objects 7.0) if you want the Graphic Vision source.  You can still
program in Graphic Vision using the supplied TPU's if you do not have
Borland's RTL disk. Note that some of the Turbo Vision RTL files are also
supplied with TP7.  The install program can also use these to recreate the
GV RTL source files.

Sorry, You don't get the source code for the graphics engine, but you do get
detailed information on how to write supplemental graphics functions when
you register.


RUN-TIME LIBRARY SOURCE CODE INSTALLATION (registered version only).
=======================================================================

You will need the Borland Pascal with Objects 7.0 run-time-library files
(exactly as extracted from the Borland RTL floppy disk) on your hard drive
if you want the Graphic Vision RTL source.  If you have made modifications 
to any file in the TV directory or to VALIDATE.PAS in the COMMON directory 
you will have to install the Borland RTL again.  You should specify a 
different base directory (eg C:\TEMP) if you do not want your modified 
Borland RTL files overwritten.  These files can then be deleted after GV has 
been installed. 

Note that the installation program assumes you have the same RTL directory 
structure as created by the BP7 RTL disk.  This means your Turbo Vision 
RTL source code files must be in the \TV sub-directory. ie, by default, the
installer is looking for the TV RTL source files in the C:\BP\RTL\TV 
directory and VALIDATE.PAS in C:\BP\RTL\COMMON.

Special Note
------------

There have been two versions of BP7 and TP7 released by Borland
International Inc.  There are 5 run-time-library files in BP7.00 (and
required by the Graphic Vision installation program) that were changed by
Borland in the 7.01 revision. The GV installer can automatically handle 
either version of 4 of these files, but you will need to manually patch the 
7.00 version of DIALOGS.PAS with the following patch, otherwise the GV installer 
will not be able to recreate GDIALOGS.PAS.  Please make sure you copy the 2 
patches exactly as they appear here, including the same white-space.


You can find out which version of Borland Pascal you have by looking at the 
time stamps of your RTL files. Version 7.00 files have a time stamp of 
07:00:00 while 7.01 files are stamped 07:01:00.

Just cut and paste the following 2 patches into DIALOGS.PAS if you are on 7.00. 
Be careful to keep the white-space the same.  This will bring DIALOGS.PAS upto 
7.01.


[-----------Change line 1058 of DIALOGS.PAS to this--------------]
      if AppendError(Validator) or not Validator^.Valid(Data^) then
[---------------------End of first patch-------------------------]



function TInputLine.Valid(Command: Word): Boolean;
[----Insert at 1039 including blank line at beginning and end----]

  function AppendError(Validator: PValidator): Boolean;
  begin
    AppendError := False;
    with Validator^ do
      if (Options and voOnAppend <> 0) and (CurPos <> Length(Data^))
	  and not IsValidInput(Data^, True) then
      begin
	Error;
	AppendError := True;
      end;
  end;

[---------------------end of second patch------------------------]
begin

You can now run INSTALL.EXE and continue reading this file from there by
selecting File|Open from the menu bar.



RE-COMPILING THE GRAPHIC VISION RTL
======================================

The following two sections assume you have installed this package into the
default directories (as recommended by the installer program).

1  From the DOS prompt, change to the GV base directory (C:\BP\GV)
2  invoke BP.EXE by typing BP (BP.EXE must be in your DOS path).
3  The C:\BP\GV directory contains IDE startup files appropriate for
   re-compiling the Graphic Vision RTL files.
4  Use FILE:OPEN to open the BUILDGV.PAS file, and read what it says.
5  Set the Primaray file to BUILDGV.PAS
6  Select the appropriate platform (Real-mode or Protected-mode), then
   Re-build the RTL by selecting COMPILE|BUILD from the IDE menu bar.
7  All the GV run-time TPU's / TPP's have now been built and are residing
   in the C:\BP\GV\UNITS directory.  Make sure this directory is in your
   IDE's UNITS path when compiling a Graphic Vision unit or application.
   

COMPILING THE DEMO PROGRAMS
================================

Copy BP.TP and/or TURBO.TP from \BP\GV into the DEMOS directory, but change 
the directories as appropriate.  Make sure that the GV units directory 
(which is C:\BP\GV\UNITS by default) is in the UNITS directory list.  

Change to the DEMOS directory and invoke BP.EXE.
Edit the OPTIONS|DIRECTORIES so that:

EXE and TPU directory is blank (ie put the EXE into the DEMOS directory)
UNIT Directories contains "..\UNITS;\BP\UNITS"

Set the primary file to GVDEMO.EXE and hit F9.  GVDEMO should then compile 
without error.  I'm sure you're capable of figuring out any problems you 
might have.  Let me know if you do get stuck or if the installer doesn't 
work properly.

I do not recommend using TPW when writing GV apps because it does not give
you access to the Graphic Vision IDE on-line help.

Please read the GV2TV.DOC (C:\BP\GV\DOCS) document. It gives helpful
tips on converting your Turbo Vision programs.


HOW TO GET HELP
===================

The GVISION.TPH file on the distribution disk is a Borland IDE compatible 
help file that documents all the differences between Turbo and Graphic 
Vision.  You should add this to the help file list in your Turbo or Borland
Pascal IDE (HELP|FILES).  You should also have TVISION.TPH in this list.
Any Graphic Vision method, procedure, variable, object, type or constant that 
is functionally the same as its Turbo Vision equivalent does not make an 
appearance in GVISION.TPH.  Having both the TV and GV help files in the help
files list allows you to determine if an identifier is the same as the TV 
equivalent, is new to GV or works differently to its TV equivalent:

(1)     If Ctrl-F1 takes you straight to a Turbo Vision help screen, the
	identifier has the same function in both GV and TV (eg TScroller).

(2)     If Ctrl-F1 takes you straight to a Graphic Vision help screen, the
	identifier is new to Graphic Vision (eg UnderLineXY).

(3)     If Ctrl-F1 takes you to the help index which is showing both a Turbo
	Vision and a Graphic Vision entry for the same topic then the 
	identifier has a different function, or works differently in GV than
	it does in TV (eg ScreenMode).  Note that some Graphic Vision 
	drawing functions have the same name as those in the Graph unit.

The Graphic Vision objects inheritance diagrams only provide hotlinks to 
the fields and methods that are new to GV, or work differently to their TV
equivalent.  This makes them easy to spot since they appear in a different
colour to the other fields and methods that are functionally equivalent to
the TV identifier of the same name.  You can get the help screen for these
by double-clicking on them.

If you have any problems with this product, please read this file, the 
documentation files, the online help file, the Turbo Vision 2.0 help file 
and the Borland Pascal manuals first. If you still have a question and need 
assistance you can contact me as follows:-

Jason Burgon
11 Thorsby Close
Brant Road
Lincoln
England. 
LN5 9DF

Internet: gvision@jayman.demon.uk

If you find a genuine bug (and document and isolate it enough for me to be 
able to reproduce it) I will send you a free copy of the registered version 
of Graphic Vision as soon as it becomes available.  When documenting bugs 
please tell me what machine you are using, the amount of memory it has, the 
video card in it and the contents of your AUTOEXEC.BAT and CONFIG.SYS files 
and whether you are running a DOS or DPMI application.   

I would prefer emails or a 3.5" floppy (straight ASCII or WRI format for 
documents please) to written documentation.  Please do not use <TAB> 
characters in your source files (Switch the "Use tab Characters" option off) 
because both BP and BPW are hopeless at printing a decent listing, and the 
way BP uses tab characters causes havoc with word processors.



WHEN THE DEMO WON'T RUN
==========================

INSTALL.EXE should run on any DOS machine ever built that has more memory
than the original ZX80.  You know it is running when you get the copyright
message.  

If INSTALL.EXE is OK it will produce a meaningfull error message if it is 
unable to run the demo/installation program.  Use this information to 
correct the problem and then try running INSTALL again.

Please note that the installation program proper is a Graphic Vision 
application, and as such it requires an SVGA video card and VESA Video Bios 
Extensions in order to run.  If you have an SVGA video card, but no VESA 
BIOS you can use the UNIVESA TSR on the distribution disk to provide them. 
Copy it into a sensible directory such as C:\DOS\DRIVERS and then add the 
following line in your AUTOEXEC.BAT file:

  C:\DOS\DRIVERS\UNIVESA.EXE

After you re-boot you can use VESAINFO.EXE (also on the distribution disk) 
to verify you now have VESA bios extensions.  Type "VESAINFO 101" to verify 
that your graphics card can support 640x480x256.  Just type "VESAINFO" for a
list of all VESA video modes your card supports.  Please note that I 
recommend using the VESA VBE (Version 1.2 or better) driver written for your 
specific video card in preference to the UniVesa driver if you can get it.  
Compuserve members might find a suitable driver in the VESA section of the 
PC Programming+ forum (GO VESA).  UniVesa is a FreeWare program written by
Kendall Bennett.  I do not recommend the UniVbe51 driver from SciTech 
software as it is not, in my opinion, a very good product.


