Start-up Tutorial
				Version 1.100


1.Download
Download the file getgo100.exe from the GetGO Download Page. 

2. Unzip
Run executable (self extracting zip file) in a temp directory. 

3.Install exes

Your ISP, who must be running a Windows NT or Windows 95 web server, must first 
install this file on your hosting server. 

Copy the file getgo.exe from your temp directory to your web server CGI directory. 
(For PWS that is c:\webshare\scripts\) 

Also copy the files blat.exe, ship.exe, getgo.cfg, ship.ini, from your temp 
directory to your web server
CGI directory. 

4. Create Directories
create the following directories in your webserver directory (In PWS that is
c:\webshare\wwwroot\):  /BATCH/, /MAIL/, /TABLE/, /BASKET/ , /STYLES/ 

5. Edit config 
Edit your getgo.cfg. Note: (If your ISP does not provide you with access to your 
CGI-BIN directory, make sure that the getgo.cfg file has been edited to your specs 
before you hand it over to the ISP.) Look at the sample configuration file
Included in this zip file (config.txt).

6.Configuring Store Layout

GetGO was designed in such a way that keeping your entire store in one directory 
is the fastest and most effecient way to build and maintain an online catalog.  
GetGO relies on tracking a customer through a catalog by giving each patron a 
unique 'basket'. To do so, you will need to call the standard command 'newbasket' 
either from a form or by using the command-line call (CLI). GetGO will then assign 
the customer their own basket with which to shop in your store. At this point the 
customer has a fresh basket but needs some place to see your products.  Part of 
the newbasket command is the ability to send the customer to any page you specify. 
An important thing to remember here is that the page is located 'relative' to the 
location you named in the webdir line of the GetGO configuration. 

If webdir=c:\website\catalog\, and your newbasket call wants to send a customer to 
t-shirt.html, GetGO will expect the file to be located at 
c:\website\catalog\t-shirt.html. 
If GetGO does not find the file, it will stop and display an error message. 
If t-shirt.html is in a subdirectory...for example, shirts\ 
then you can send the customer there by including the subdirectory as 
shirts/t-shirt.html which will 
cause GetGO to look in c:\website\catalog\shirts\t-shirt.html.

example newbasket code:

<form method="POST" action="/cgi-internal/getgo/getgo.exe">
<input type=hidden name=command value="newbasket">
<input type=hidden name=where value="1.HTM">
<input type=submit value=" ENTER STORE  ">
</form>

Once a customer has been given a basket, there is no need to call 'newbasket' at 
any other point in the catalog. If you do so, it will strip away the customer's 
current basket and give them a new empty one. You may decide to provide that 
feature on your site deliberately, but generally a site will only need one 
call to newbasket.

Now that you've learned how to send a customer to an initial catalog page, they 
will need the ability to see all the rest of the pages in your catalog. To do this, 
GetGO provides a command called "goto". It's name implies exactly what it does. It 
takes a page that you have predetermined and when a customer calls the command, 
either thru a button or link, they will be transported to the page you specified. 
The reason GetGO needs to do this is to keep track of the customer as they navigate 
your site. If your site is simple and has only one page, you will not need a goto 
command at all.

sample "goto" code:

<form method=post action="/cgi-internal/getgo/getgo.exe">
<input type=hidden name=command value="goto">
<input type=hidden name=basket value="{SHOPPER}">
<input type=hidden name=where value="page2.htm">
<input type=submit value=" Goto Page 2 ">
</form>

Perhaps the most important task of all is the add2basket and it's similar commands. 
These commands provide the mechanism for the customer to add an item to their 
shopping basket with single click ease. There are several ways to accomplish this 
and it is entirely in the hands of you, the web designer how you want GetGO
to perform this task.

sample add2basket code:
<form method="POST" action="/cgi-internal/getgo/getgo.exe">
<input type=hidden name=command value="add2basket">
<input type=hidden name=where value="page1.htm">
<input type=hidden name=basket value="{SHOPPER}">
<input type=hidden name=name value="Big Red Shirt">
<input type=hidden name=item value="BR1001">
<input type=hidden name=price value="15.00">
<input type=hidden name=ship value="1.50">
Quantity <input type=text name=qty value="1" size=4>
<input type=submit value="Add to Basket">
</form>


7. dbfile and Style options - Version 1.100
The latest version of GetGO gives the developer an option when building the storefront
HTML.  Through the use of an external db file (actually in the "INI" test format), the 
actual GetGO Add2Basket HTML will be parsed into the catatog pages.  Once inside the 
catalog, GetGO will always parse the page being called for Item-Tags.  An Item-tag takes
the form {ITEM=123XYZ} , where "123XYZ" is the individual item code for the product 
specified in the external db file.  
A sample db file:

[123XYZ]
name=Golf Calendar
price=10.99
ship=1.00
desc=A beautiful calendar full of the most popular golf courses.
picture=http://www.veracruz.net/my-store/images/calendars/2888.jpg
style=a2b

In the above example, GetGO replaces the {ITEM=123XYZ} code with an add2basket
code template called "a2b" (which is found in the styles directory specified in the 
config file.) It includes all the specific item information from the db file.