Individual database fields are accessed with the [item_field] and
item[_data] elements, among others
The image name is based on the image database field (if present)
The [body] element controls the look
The order link is placed with the [order] element
Any data from an arbitrary database can be placed with the
[data ...] tag
catalog
This is the default page for the program
It should be compatible with both frame and non-frame browsers
Help messages (like this one) can be turned off in Control
The Control page will allow the user to control frames/non-frames operation
The background and/or color scheme was placed with the [body] element
The buttonbar below was placed with a [buttonbar] element
fr_greet
You should only see this page if you have a frame-based browser
The links above are done with [pagetarget] elements
The background pattern and/or color scheme are done with a [body] element
The buttonbar below is defined with a [buttonbar] element
It set a variable which initializes rotating messages in the catalog
pages
Help messages (like this one) can be turned off in Control
random
[random]
basket
basket.html - shopping basket page
Frame browsers can have another order page
There is an imagemap submit bar above, which is defined
in standard NCSA imagemap format with the hidden 'mv_todo.map'
variables
Order information is tracked, and can be entered automatically in
your order entry software with the Tracking and AsciiBackend capabilities
search
This page returns the search results
You could put another search form here if you wished
The entries above were built by the search engine
based on the HTML inside the search-list element
Match paging can be done with the [more_list] [/more_list]
element pair and [more] tag
control
This page shows examples of how to control the user presentation
You can enable and disable frames
You can enable and disable help messages (like this one)
Colors can be changed to meet user preference, or could
be defined to be several pre-set schemes
footer
checkout
This is where the user goes when they click CheckOut,
which is placed with the [finish_order] tag
MiniVend handles #name tags, as you can see
The user will receive a receipt once the order is placed,
located in ord/receipt.html
There is an imagemap submit bar above, which is defined
in standard NCSA imagemap format with the hidden 'mv_todo.map'
variables
Order information is tracked, and can be entered
automatically in your order entry software
query
Name: fr_comb.html - example search form for frame-based browsers
It is designed to let the user search the database for any text
Or select from a series of pre-defined categories
The product database, or any set of files, can be searched
for information using glimpse of fast binary search
You can customize if you wish, but make sure you don't
change the variable names beginning with 'mv_' unless you read the
documentation thoroughly
country_select
mc
Mastercard
amex
American Express
visa
Visa
discover
Discover/Novus