Atari ST - 1997
CAB - Crystal Atari Browser
_2_0_[clauss_alexander].png?v=1788853994)
- Genre
- Communications / Radio / Electronics
- Year
- 1997
- Language
- [unknown]
- Publisher
- [no publisher]
- Controls
- Mouse
- Distributor
- —
- Resolution
- Medium / High / VGA
- Developer
- [n/a]
- ST Type
- ST, STe, TT, Falcon030 / 0.5MB
- Licensed from
- —
- Programmer(s)
- Clauss, Alexander
- Country
- MIDI
- —
- Software
- English
- Version
- 2.0
- Box/Instructions
- English / French / German / Spanish
- Number of Disks
- 1 / Double Sided
- License
- PD / Freeware / Shareware
- Dump
- Download
- Serial
- —
- Dump format
- MSA
- Protection
- —
OTHER VERSIONS WITH THE SAME TITLE (5)
INSTRUCTIONS
The documentation to
CAB
Version 2.0 (Translation by Joe Connor)
21.01.1997
by
Alexander Clauss
Stresemannstraße 44
D-64297 Darmstadt
aclauss@rbg.informatik.th-darmstadt.de
Contents
========
1 A short introduction
2 Legal
3 Address
4 System requirements
5 Installation
5.1 Module for Internet access
5.2 The "modules" folder
5.3 The Cache folder
6 Operation
7 Navigating HTML documents
8 Some comments about HTML
8.1 Frames
8.2 Tables
9 Creating HTML files with OLGA installed
10 Description of menu items
10.1 Open URL...
10.2 Open local...
10.3 Reload
10.4 Print
10.5 New window
10.6 Close window
10.7 View source
10.8 Quit
10.9 Home page
10.10 Forward to next page
10.11 Back
10.12 Find keyword
10.13 Hotlist
10.14 Document -> Hotlist
10.15 General options
10.16 Display
10.17 Font selection
10.18 External viewers
10.19 Paths...
10.20 Cache
10.21 Internet programs
10.22 Server/Proxy
10.23 Save options
11 Button bar
12 Thanks
13 History
13.1 V0.8ß (20.04.1995)
13.2 V0.9ß (15.05.1995)
13.3 V0.93ß (07.06.1995)
13.4 V0.94ß (07.07.1995)
13.5 V0.95ß (04.08.1995)
13.6 V0.96ß (22.08.1995)
13.7 V0.98ß (03.10.1995)
13.8 V1.0 (01.11.1995)
13.9 V1.0a (12.12.1995)
13.10 V1.1a (01.04.1996)
13.11 V1.2 (10.04.1996)
13.12 V1.2a (16.04.1996)
13.13 V1.2b (19.04.1996)
13.14 V1.3 (20.05.1996)
13.15 V1.4 (19.09.1996)
13.16 V1.4a (01.10.1996)
13.17 V1.5 (20.10.1996)
13.18 V2.0 (05.01.1997)
1 A short introduction
***********************
*CAB* - The Taxi to the information highway!
*CAB* - Crystal Atari Browser
Formerly called HTML-Browser
This browser is capable of reading HTML format documents. The HTML
documents could be on disk or CD. Reading pages on-line to an Internet
World Wide Web (WWW) site requires a separate module.
2 Legal
********
CAB (HTML-Browser) is FREEWARE. It may be copied and used freely.
Distribution by BBSs and PD libraries is allowed. However, CAB (HTML-
Browser) may NOT under ANY circumstances be included in CD-ROM
collections or on magazine cover disks without my prior written
permission. CAB (HTML-Browser) and its documentation must always
remain together and complete with all its files and documentation.
Changes to the program and/or documentation is forbidden.
If you like CAB (HTML-Browser) and you use it regularly, please
register your copy, any currency is welcome.
If you would like to see this program developed please send some
feedback and register your copy. UK users can take advantage of local
support, refer to SUPPORT.TXT for more details. No feedback means no
development, it's that simple!
3 Address
**********
*My address:*
Alexander Clauss
Stresemannstr. 44
D-64297 Darmstadt
Germany
email: aclauss@rbg.informatik.th-darmstadt.de
WWW: http://www.student.informatik.th-darmstadt.de/~aclauss/
*Banking arrangements:*
Sparkasse Darmstadt
BLZ: 508 501 50
Kontonr: 0115032143
*UK support:*
Joe Connor
65 Mill Road
Colchester
CO4 5LJ
England
email: jconnor@cix.compulink.co.uk
4 System requirements
**********************
The program runs on any computer using the (Atari-) TOS operating
system with 1Mb or more memory. The memory requirements for images
depends on the colour depth. The greater the colour depth the more
memory required. Using a True colour graphic card (24 or 32 bit)
gobbles up memory and you're likely to need considerably more than
1Mb.
CAB is resolution independent with two limitations: At 320x200 (ST-
low) not all of the dialogs fit entirely on screen, at 640x200 (ST-
Medium) the screen display is distorted (half height). Consequently we
recommend using CAB at resolutions of 640x400 (ST-high) or higher with
any number of colours, a multitasking environment (e.g MagiC, Geneva
etc) is also desirable.
Although not absolutely necessary the use of vector fonts via NVDI
v3.x or SpeedoGDOS is recommended. The system font or bitmap GDOS
fonts can however be used if required.
5 Installation
***************
Copy the folder from the CAB distribution to your hard drive. CAB is
fundementally ready to run but your should select each of the dialogs
in the Options menu to configure CAB to your requirements.
5.1 Module for Internet access
===============================
In order to access HTML pages directly from the World Wide Web copy
the file CAB.OVL into the same folder as CAB.APP - or alternatively
into a folder named "modules" which must reside in the same folder as
CAB.APP. CAB.OVL includes the necessary routines to access the
Internet. On Minix partitions the x-flag of CAB.OVL file must be set,
otherwise the module cannot be executed. Currently there are two
different CAB.OVL files, one for MintNet and one for STiK. The MintNet
OVL file will NOT work with STiK and vice versa!
One reason CAB has no built-in routines to access the Internet is
because I don't own a modem and can't test on-line behaviour. CAB
includes an interface which allows external modules, like the ones for
STiK and MintNet to be added. If you'd like to program an external
module please do get in touch.
5.2 The "modules" folder
=========================
CAB accesses a variety of different files to perform different tasks.
Normally these are placed in the same folder as CAB.APP. In order to
tidy up the CAB folder most of these files can be moved to a folder
called "modules" where CAB will find them. The following files can be
placed in the "modules" folder:
∙ cab_jpeg.ovl (this file may also be called 'jpeg.ovl')
∙ cab.inf
∙ cab.ovl
∙ cache_ed.prg and cache_ed.rsc (program to manage the WWW cache)
∙ hotlist.html
5.3 The Cache folder
=====================
All data fetched from the Internet is initially written to disk - in
the cache directory. If the requested data is already in the cache it
is examined to check whether the data is current. If the data is
current it is read from the cache and not fetched from the Internet
again.
So that CAB knows where to save data the cache folder must be set in
the Paths dialog from the Options menu. If this directory is not set
and a CAB.OVL module is available (i.e. an Internet connection has
been established) CAB, after starting, displays this dialog so the
cache folder can be selected.
6 Operation
************
CAB works pretty much like any other enhanced GEM application with one
significant difference: To accomodate the popular frames extension
(which enables one window to be divided into numerous separate areas -
each with its own sliders) CAB could not rely on the standard GEM
window sliders. Consequently CAB employs its own slider routines which
adopt the colour and pattern as defined by the WCOLORS.CPX. This means
the sliders should look the same as any 'real' GEM window sliders.
Frame contents can be scrolled using the cursor keys including page-
by-page scrolling by holding down the [Shift] key during scrolling;
under MagicMac/MagiC PC? the "page-up" "page-down" "home" and "end"
keys are supported. If more than one frame displays sliders only the
active frame is scrolled. The active frame can be selected using the
[Tab] or [Shift]+[Tab] key to toggle between frames with sliders or by
clicking anywhere inside a frame using the mouse. The active frame
displays sliders according to the settings in WCOLORS.CPX for
foreground windows, inactive frames adopt the slider settings for
inactive windows. Both can be set as desired using WCOLORS.CPX.
Important!(!nl) A-MAN v1.6 (part of the WinCom v1.6 distribution) has
an error which causes CAB frame sliders to be displayed with the wrong
colour/pattern. Solution: Get hold of an updated version of WinCom or
don't use WinCom! MagiC <=4.x also doesn't interrogate the slider
colour/pattern correctly. This works properly in MagiC v5.x, MagiC Mac
v2.x and MagiC PC.
7 Navigating HTML documents
****************************
HTML documents typically include links to other files. These links, or
references, are differeniated from other text using a different colour
or by underlining (user-definable). A mouse click on a link displays
the corresponding page. When placed over a link the destination is
displayed in the window info line.
For every individual frame CAB retains a separate "history" list of
each file displayed. Using this ability it's easy to move back and
forth between previously viewed documents. A right click (optionally a
left-click) inside any frame displays a complete history list from
which entries can be directly selected.
The *Forward* and *Back* buttons in the window toolbar or "Navigate" menu
option can display the relevant page along with any frames it
contains. To navigate pages within frames, left-click anywhere inside
the frame (but not on a link) and a popup menu is displayed including
navigation functions. Generally the window toolbar buttons and menu
entries affect the parent document. Within frames the popup entries
only affect that frame. If a document has no frames the toolbar
buttons, menu entries and popup entries all perform the same functions
- there are only distinctions if the HTML document contains frames.
Browsing the Internet or CDs you're bound to find some pages you'd
like to look at again. The URL address of such pages can be added into
the *Hotlist* and can be recalled from the Hotlist with a single click
in the Hotlist dialog.
The Hotlist is saved by CAB as a normal HTML file and makes an ideal
start page which you can set to display on starting CAB.
8 Some comments about HTML
***************************
CAB understands the original HTML specification along with HTML 2,
HTML 3.2, parts of HTML 3 (despite this version never having been
formally agreed as a standard and is in any event outdated) and the
most important Netscape Navigator and Microsoft Internet Explorer HTML
extensions.
CAB does not understand nor support Java or JavaScript.
Unlike most langauges HTML is not an exact specification. It's up to
the browser author which HTML tags to support. An HTML author can
never be certain of the hardware/software used to view pages so anyone
creating would be well advised to err on the side of caution when
designing pages so the majority of browsers and people can read them.
8.1 Frames
===========
Frames (a Netscape HTML extension) offers some advantages for the
creation of HTML pages along with some significant disadvantages.
Consequently the use of frames should be carefully considered. The
most important advantage offered by frames is the ability to display
an index in one frame all the time using other frames to display the
contents. The main problem using frames is the integration of frames
in the HTML language. One of the fundamental concepts of the HTML
language was (and is) that new and unknown HTML tags could be ignored.
Frames infringe this concept because if browsers do not understand
frame tags or the hardware/software cannot display frames the content
cannot be viewed - there's no fallback position. A further
disadvantage is the navigation of HTML pages which include frames
isn't as straightforward as pages without frames. There is no longer a
single level where program functions (Hotlist, Forward, Back, History,
View source, Print, etc..) work globally. Each and every frame
displays its own document and they all need access to the global
functions. Additionally (in the case of badly designed pages) as
documents in frames access other documents with frames these can no
longer access the global functions and navigation exclusively using
the popup becomes tedious and impractical. One further disadvantage of
framed documents is they are often cramped when viewed on screens at
lower resolutions (640x400 or lower) with only a small area left
displaying meaningful content.
8.2 Tables
===========
An HTML browser can display normal text immediately before it has
calculated the end of the text. This means you can begin reading a
document while formatting continues. With tables this isn't possible,
tables can only be displayed after all the content has been
calculated.
9 Creating HTML files with OLGA installed
******************************************
Under a multitasking operating system (MagiC/MultiTOS/Geneva etc) it
is relatively easy to create HTML files. Apart from CAB consider using
the OLGA manager, programmed by Thomas Much, and a text editor which
understands the OLGA protocol, for example QED. Now CAB and the editor
can simultaneously display the same document. CAB displays the HTML
formatted page and the editor is used to enter the HTML source. Now,
if OLGA is installed, saving the HTML source text in the editor causes
CAB to automatically update to display the formatted HTML. This is
arranged by the OLGA manager. The editor tells the OLGA manager the
file has been changed and the OLGA manager informs all interested OLGA
clients so they can update themselves. This saves switching to CAB to
update the pages manually.
10 Description of menu items
*****************************
10.1 Open URL...
=================
The *Open URL...* option in the *File* menu displays the URL dialog
containing any URL (Universal Resource Locator) addresses you have set
up to access the WWW.
10.2 Open local...
===================
In principle all filetypes can be selected. CAB displays HTML text,
GIF and JPEG images itself and passes all other filetypes to external
helper applications, where installed. The contents of folders is
displayed as an HTML page with every file/folder defined as a
selectable reference.
10.3 Reload
============
Reloads the HTML page again.
If a page is loaded from the WWW this function can be used to fetch it
again - even if it's still in the cache.
10.4 Print
===========
If GDOS is available the document in the topped window can be output
as text. Bitmap fonts require matching screen and printer fonts
whereas vector fonts under NVDI 3.x or SpeedoGDOS are automatically
scaled as required.
In the dialog the margins can be set. These are in addition to any
offsets or margins attributable to either the printer or GDOS driver.
A popdown menu offers selection between any installed GDOS driver
including, so long as a suitable GDOS driver is available, GEM
Metafile (*.GEM) or bit image (*.IMG).
Successful image output relies on the GDOS printer driver supporting a
particular VDI function which may or may not be implemented in the
active driver. We recommend you try printing with images turned on and
if it doesn't work simply turn the option off for subsequent output.
If you're using a dot matrix printer activate the option to lighten
images otherwise the printed output is likely to be too dark.
10.5 New window
================
Opens a new window displaying the contents of the previously topped
window.
10.6 Close window
==================
Closes the window.
10.7 View source
=================
Displays the source text of the displayed HTML document. Also refer to
the *External programs* menu option.
10.8 Quit
==========
Exits the program.
10.9 Home page
===============
This menu option displays the home page, if available.
CAB tries to load the home page directly. Anyone who understands HTML
syntax can easily set any page as the home page and create a page to
reference other HTML documents. The file used as the home page can be
set in the *General options* dialog.
10.10 Forward to next page
===========================
Displays the next document in the history list.
10.11 Back
===========
Displays the previous document.
10.12 Find keyword
===================
This allows the user to perform a search for keywords in HTML files,
and can optionally be case sensitive. The search can be conducted over
one of the following ranges of documents:
1. Current document only. The text is searched for in the current
document (the top window). If the text is found the window is
scrolled so the text is displayed at the top of the window.
2. Local HTML Documents. The text is searched for in all local HTML
documents contained in the paths specified in the *Paths* dialog
box (and their subdirectories). The files that contain the text
is made into a list of links in an HTML file called result.html.
At the moment the HTML files searched by method two are searched
purely as text, so hidden text such as comments, HTML commands,
links and so are also found. Processing the files to ignore
hidden text would be very time costly. This also means that
special characters such as accents and so on which are written
into HTML code using commands like ä are not found. This
shortcoming may be addressed in a future version.
Hint! When searching for keywords which are commonly components
of HTML commands or URL addresses try adding a space character
before the search expression. For example, if you're searching
for the concept 'WWW', which is commonly part of URL addresses
(for access to other documents taking the form '/WWW/folder/etc'
you would be flooded with unwanted matches. Changing the search
expression by adding a preceding space character ' WWW'
eliminates URL addresses.
3. The c't-CDROM-database. Only of interest to anyone possessing the
German c't magazine database in CD-ROM format (1992 to 1996). The
search feature here searches not the HTML documents but the
database of the CD itself. So CAB knows, where the CD and the
database are located select the folders where the DEFAULT.HTM and
database documents (\UNIX\CT94.DAT, \UNIX\CT9293.DAT etc) are
located in the *Paths* dialog. For the database the wildcard (* and
?) are allowed. The expression \UNIX\CT*.DAT accesses all(!) c't
CD-ROMs. As for 2) the matches are displayed as a list with every
article defined as a selectable reference. The result will also
be saved to a file called result.html.
10.13 Hotlist
==============
The hotlist is a list of your most used HTML documents. This list
enables you to get quickly to you favourite pages, without having to
navigate through a long series of pages to get there.
The hotlist is divided into themed areas. Using the popup at the top
of the dialog it's easy to switch between different themes.
*The 'Theme...' popup:*
*Change theme:* Changes the name of the current theme area. The
/Miscellaneous/ area cannot be renamed.
*New theme:* Creates a new theme area.
*Delete theme:* Delete the current theme area. The /Miscellaneous/ area
cannot be deleted. All remaining entries in a deleted theme area
are moved to the /Miscellaneous/ theme area.
*The 'New theme...' popup:*
Using this option a selected entry can be moved to another
theme area.
*The 'Document...' popup:*
*Delete entry:* Deletes the selected entry.
*Change entry:* Changes the selected entry. Annotations to the page can
also be made.
*Open document:* Opens a document.
*Add current doc:* Copies the current document to the Hotlist.
*New entry:* Here a new entry can be entered. Neither the title or URL
are preset.
Double clicking on an entry opens the document.
The Hotlist is saved to disk as a normal HTML document which provides
an easy way for anyone not familiar with HTML syntax to create their
own home page.
10.14 Document -> Hotlist
==========================
The current document is inserted in the Hotlist provided it's not
already listed. It will be filed away in the /Miscellaneous/ theme area.
10.15 General options
======================
*Home page:* After launching CAB or by selecting the *Home page* menu
entry the specified HTML file will be displayed. Often it's
useful to create a home page containing references to frequently
used HTML pages. By default CAB attempts to load home.html as the
home page although any page can be set to be the home page
-simply enter the URL address. If the file is located in the
specified start directory for CAB.APP you can select the *Start
folder* button and using the *Search* button select the desired file
using the file selector.
*Popup menus:* CAB provides a row of popup menus to relieve the tedium
of navigating through HTML pages. Basic principle:
∙ Left click on a reference to branch to the corresponding
page.
∙ Click on the window background (not on a reference) to
display further popup menus.
You can set which menu will be displayed using the left and right
mouse clicks (with and without holding down the [Shift] key). The
following popup menus are available:
*History:* Lists the previously displayed documents.
*Menu:* Lists some menu items.
*file: protocol* The *load index.html automatically* only has an affect
on local references (ie to files/directories on your drive) If
the reference points to a directory on a drive the contents will
be displayed unless a file index.html exists in which case this
is loaded instead. On use for index.html is to set up a page
containing an index of all your favourite documents.
10.16 Display
==============
In this dialog you can configure various display options for HTML
documents.
*Colours:* This section allows you to configure the display colours,
for the foreground text, the background colour and link colour.
If you're using less than 16 colours, the window background will
always be white regardless of the settings here. In 16 colour
mode, only the first nine colours should be used as the last 7
may be changed for pictures etc. In more than 16 colours, any of
the first 16 can be used as they will not be changed.
Some HTML documents include information about which colours
should be used for text, references and the window background.
The option *Use guidelines in document* tells CAB to use this
information (if available).
*Links:* Links can be displayed in underlined and/or bold text (this is
important for monochrome systems which can't distinguish links by
colour).
*Images:* Controls image display.
*Don't show* Prevents images being loaded and displayed which
speeds up page loading.
*Monochrome* Images are displayed in monochrome using dithering.
It's the quickest method but this obviously the quality
suffers.
*Greyscale* Images are displayed as greyscales. Higher quality
display at the expense of speed.
*Colour* Images are displayed in colour depending on the hardware
available:
∙ 4-8 bitplanes (16-256 colours). Images are dithered if
the number of colours available is less than the number
of colours contained in the image. In 16 colour modes
greyscale display is often more suitable.
∙ 15/16 bit Highcolor (32768/65536 colours) eg Falcon
Truecolor mode
∙ 24 or 32 bit Truecolor (16.7 million colours)
*Text instead of images* The HTML language provides for text only
systems by allowing images to be accompanied by some text
which is displayed instead of the image. This enables WWW
Browsers which cannot display images to display text output
instead. If this option is active (crossed) only images for
which no alternative text is available are displayed as
images.
*Text width:* Text can either be formatted at a fixed width or
justified to fit the window width. Text justified to fit the
window width looks better but takes longer to display as the text
must be reformatted.
*Frames:* Select whether CAB evaluates frame definitions or not.
Unfortunately some pages can only be displayed using frames so
normally it's best to leave this option active. There are some
HTML pages which, despite employing frames, can be displayed with
frames turned off. For example Der Spiegel newspaper at:
http://www.spiegel.de/ (December 1996)
These pages displayed are loaded much faster without frames
except you don't get to read the adverts ;-)
10.17 Font selection
=====================
Wherever possible CAB (HTML-Browser) uses different fonts and point
sizes to display HTML files. Optimal output quality is provided using
vector fonts for which you'll need to install either NVDI v3.x or
SpeedoGDOS. Normal bitmap fonts can be used but they're not nearly as
nice.
Next you need to tell CAB (HTML-Browser) which (GDOS) fonts to use for
each corresponding style in an HTML document. Vector fonts as provided
by SpeedoGDOS or NVDI 3.x are recommended. You must specify three
fonts (sans-serif, serif and monospaced) in four different styles
(normal, bold, italic and bold and italic) making twelve selections
altogether.
For the bold and italic settings you should use a 'real' bold or
italic font wherever possible. If you don't have one available you'll
have to simulate these text effects using the corresponding buttons
adjacent to the font selection popup. If you're using vector fonts
then use the appropriate font from the font family, if available.
Some commands such as ..., ... etc will cause
display format problems with /proportional/ fonts. To avoid these
problems only use *non-proportional* fonts for *preformatted* text.
The supplied INF file has the following presets (for NVDI 3.x):
*Headings:* Swiss 721 (normal, bold, italic, bold+italic)
*Normal text:* Dutch 801 (normal, bold, italic, bold+italic)
*Formatted:* Letter Gothic 12 Pitch (normal, bold, italic, bold+italic)
If you don't like or haven't got these fonts, you'll have to select
alternatives.
The size of the body text can also be altered. Don't make this too
large or too small! Somewhere between 10 and 13 point is sensible (I
use 12 point).
If you haven't got access to vector fonts (i.e. you don't own a copy
of NVDI 3.x or SpeedoGDOS) then the point size won't change, but the
text can still be viewed using the system font, usually 10 point.
10.18 External viewers
=======================
If a link in an HTML document points to a file which is not in HTML
format, an external viewer can be called. These programs can be called
in one of two ways and are configurable via the *External programs...*
dialog via the *Options* menu.
Individual file types can be assigned to different programs. File
extensions are entered into the *Files* field. Several extensions can be
entered using a comma to separate each entry.
Programs are selected by clicking on the selection box to the right of
the *Files* field which displays the file selector to select the desired
viewer.
Finally each entry includes a *Supports VA_START* checkbox which should
be crossed if the viewer understands the VA_START message so CAB can
send a VA_START message to the viewer so the file can be viewed with
re-launching the viewer.
The *Default* program (*.*) is called to display any files for which no
program has been assigned.
If one or more file extensions have been defined without assigning a
helper application CAB.APP will display them - even if they are not
HTML format files. Apart from HTML files this only makes sense for
*.gif, *.jpeg,jpg, *.xbm and pure ASCII files such as *.txt, *.text,
*.C, *.H, *.doc, *.pas, *.tex etc.... because CAB.APP includes built-
in support for these filetypes. If CAB cannot recognise the filetype
it displays the file selector ready to copy the file to disk. This
means helper applications, although useful, can be omitted altogether
if desired.
CAB displays HTML source code itself. If you wish to edit the HTML
source simply assign a text editor (QED, Everest, Edith etc) for the
file extensions *.htm,html.
In the *binary file* field enter any file extensions to be handled as
binary files which CAB does not recognise. For example CAB would
recognise ASCII encoded binary files in *.uue and *.hqx and display
them. After entering these filetypes as binary CAB will display the
file selector ready to save the file to disk instead of displaying
them.
In the "Editor" field enter your prefered text editor (Everest, Edith,
QED), which can be used to send emails etc.
GEMJING will be used for sound output provided the corresponding calls
are made in the HTML document. This will only function under a
multitasking operating system. The path for GEMJING must be entered.
Furthermore GEMJING can be installed as a helper application for WAV
and AU sound files.
Double-click on the *Program path* box to open a further dialog where
the installed path can be deleted again.
Suggestions for external programs:
*.text,txt: ST-GUIDE, 1STGUIDE (or nothing, using CAB.APP as
viewer)
*.mpeg,mpg,mpe: 1STGUIDE (On a Falcon running single-TOS the fast
DSP-MPEG-Player is recommended)
*.jpeg,jpg,jpe: 1STGUIDE, GEM-VIEW (or nothing, using CAB.APP as
viewer)
*.tiff,tif: GEM-VIEW
*.gif,xbm: GEM-VIEW (or nothing, using CAB.APP as viewer)
*.dvi: DVI-display program from a TeX package
*.* (default): GEM-VIEW, LOOKNSEE (or other program capable of
displaying lots of filetypes)
*.html,htm: qed, Everest, Edith (or nothing, using CAB.APP as
viewer)
*.wav,*.au: GEMJING
10.19 Paths...
===============
If you have a copy of the c't ROM (1992 to 1996) (CD containing the
contents of the German magazine c't) then set the path for the field
c't CDROM.
Fill in the "c't CDROM" fields. *HTML folder* is the folder on the CD
where the DEFAULT.HTM resides (x:\HTML\, where x is the letter
representing the CD drive). *Database* is a file on the CD which
contains the contents of the CD (x:\UNIX\CT94.DAT, \UNIX\CT9293.DAT
etc. where x is again the letter representing the CD drive). For the
database the wildcard (* and ?) are allowed. The expression
"x:\UNIX\CT*.DAT" will allow access all c't CD-ROMs.
If you want to use CAB online to an Internet WWW site you should set
the *Cache folder* where all files downloaded from the Internet can be
stored. Ideally this folder should be on a Minix hard disk partition,
or other file system which supports long filenames to handle HTML
files because HTML files downloaded from WWW sites often include long
filenames which can easily result in duplication of filenames using
the basic TOS 8+3 character file system -and make sure the partition
has plenty of room!
In *HTML folders* you can enter the paths CAB (HTML-Browser) looks to
find HTML files.
HTML files contain absolute local paths (eg /path/file.html) which can
soon turn the root directory of your partition into choas. The HTML
folders help avoid this by telling HTML-Browser to look for HTML files
in the folders specified.
Here's an example:
*Entered HTML folders:*
∙ F:\HTML.DOC\
∙ G:\VARIOUS\
*Current drive:* F:\
*Path in HTML file:*
∙ /example/text/index.html
*Where CAB looks:*
1. F:\example\text\index.html
2. F:\HTML.DOC\example\text\index.html
3. G:\VARIOUS\example\text\index.html
Double clicking on the *program path* boxes opens a further dialog with
an option to clear the current path.
10.20 Cache
============
CAB (HTML-Browser) uses two caches to maximise the display of files.
The *Image cache* is used to avoid repeated unpacking and dithering
which both take a great deal of processing time. Images no longer
displayed are held in memory (RAM) in case they are needed again.
Naturally this takes memory so the maximum size of the cache can be
set in the *Maximum size* field. If the cache becomes full the least
used image is purged from the cache to free up more space. Using the
*Keep free* option it's also possible to set the minimim amount of
memory free for other applications. The cache can also be manually
purged using the *Free cache* button which can be useful to quickly free
up more memory for another application under a multitasking OS. The
cache remains empty until further images are displayed in CAB (HTML-
Browser).
*Attention*
The actual memory consumption for the Cache can be higher
than entered in the dialog.
The *Internet Cache* is used to store files downloaded from the Internet
on your disk to avoid repeatedly downloading the same files from the
Internet if they're viewed more than once. See also *Paths*
The *Maximum size* and *Keep free* options limit the amount of disk space
used by the cache and CAB (HTML-Browser) will purge the oldest files
from the cache to maintain the cache within the defined limits.
If the *Delete after 'quit'* option is active (crossed) the files in the
cache will be deleted on exiting CAB (HTML-Browser). Naturally unless
disk space is limited or you're sure you'll never need the files again
it's best to keep the files.
The *Free cache* button is for emergency use in case you need extra disk
space fast! Only files placed in the the cache directory placed there
by CAB (HTML-Browser) will be deleted.
10.21 Internet programs
========================
Normally all access to the Internet takes place via the CAB.OVL
module. Unfortunately not all the Internet protocols of CAB.OVL are
supported. From this dialog special programs can be installed for use
as desired. The only limitation is such programs must be able to
accept a URL address as a parameter.
10.22 Server/Proxy
===================
All entries in this dialogue are either evaluated exclusively via the
CAB.OVL module or not. The CAB.OVL module for MintNet still (December
1996) doesn't evaluate this information. The CAB.OVL for STiK is a
partial implementation. If one all entries in the STiK configuration
files of STiK i.e.. MintNet is activated, the dialog entries can be
left empty.
10.23 Save options
===================
Save the current settings
11 Button bar
**************
Each CAB window contains a button bar which provides an easy way to
access some of the more important functions:
*Forward* The next document is displayed.
*Back* Displays the previous document
*Home* Displays the home page
*URL* Select a document from a URL address
*File* Select a file using the file selector
*Source* Displays the source text of the currently displayed document
*New* Reloads the current document again
*Hotlist* Displays the hotlist dialog
If a 'sad' smiley appears to the right of the buttons it means the
displayed document is faulty in some way. Click on to the smiley to
display detailed error information. This is a particularly useful
option for anyone using CAB to author HTML pages. Only errors which
CAB can determine without wasting disk space or processing time will
be reported.
Faulty documents are not neccessarily displayed incorrectly in CAB but
may well exhibit display problems in other browsers (e.g. Mosaic,
Netscape, WebExplorer etc) may not display the document as you
intended.
12 Thanks
**********
I'd like to thank everyone who through their praise, criticism,
suggestions and bug reports have helped in the development of CAB
(HTML-Browser). In particular the following people deserve a mention:
∙ Dan Ackerman
∙ Mille Babic
∙ Stefan Becker
∙ Ben Bell
∙ Stephane Boisson
∙ Joe Connor
∙ Dieter Fiebelkorn
∙ Nicholas Flintham
∙ Stefan Haake
∙ Romuald Jouffrey
∙ Ulrich Kaiser
∙ Ton Ketting
∙ Antonio Lillo
∙ Graziano Morando
∙ Thomas Much
∙ Tim Newsome
∙ Fred Nicklisch
∙ Rosario Pignatelli
∙ Manfred Ssykor
∙ Andrew Versperman
∙ Lodovico Zanier
13 History
***********
13.1 V0.8ß (20.04.1995)
========================
∙ First release version
13.2 V0.9ß (15.05.1995)
========================
∙ Reduced memory requirements
∙ MTOS Drag&Drop (ARGS) supported
∙ External programs will now run under single TOS
∙ Error reports are now more descriptive
∙ Bugfix: when running as an accessory no longer tries to invert
(non-existant) menu items
∙ The .INF file is now found even if HTML is not started in it own
directory
∙ Is now a lot more tolerant of buggy HTML file syntax.
∙ home.html is now loaded on startup if possible
∙ Hotlist
∙ Configuration of window and text colours etc.
∙ Search (including searching c't CDROM)
∙ In-line images can be displayed as greyscales
13.3 V0.93ß (07.06.1995)
=========================
∙ Preparation for on-line operation implemented (although not
activated in this version)
∙ Bugfix: Problem with line spacing fixed
∙ Bugfix: Endless loop with defective gifs fixed
∙ Bugfix: fclose() for Hotlist was forgotton :-(
∙ A few other minor bugfixes
13.4 V0.94ß (07.07.1995)
=========================
∙ Bugfix: Deleting the last Hotlist entry caused a crash :-(
∙ Bugfix: CR/LF inside tags led to problems
∙ Bugfix: Last word in an HTML file gobbled
∙ Documents access using absolute path information, including
directories listed in the 'Paths...' dialog
∙ Contents of a drive can be displayed as an HTML document
(including launching programs and viewing files)!
∙ Support for the special Netscape tags
13.5 V0.95ß (04.08.1995)
=========================
∙ Inline colour images
∙ Configurable image cache (in RAM)
∙ Configurable WWW cache (on disk)
∙ Option to automatically format text to the window width
∙ ASCII, xbm and gif files can now be viewed directly in HTML-
Browser. Calling external programs is no longer required (but
naturally still available as an option)
∙ Interface for 'Internet module' implemented Using a suitable
module HTML-Browser could be used to display WWW pages on-line to
the Internet, naturally you'd need an Internet account to do
this!
∙ Support for xbm images
13.6 V0.96ß (22.08.1995)
=========================
∙ Lots of minor bugfixes
13.7 V0.98ß (03.10.1995)
=========================
∙ In colour resolutions with fewer than 16 colours the colour
palette is no longer altered
∙ Zero length files should no longer cause problems
∙ The program is now called:
CAB - The Taxi to the information highway!
CAB = Crystal Atari Browser
13.8 V1.0 (01.11.1995)
=======================
∙ Minor adjustments to accomodate the 3D look under Geneva release
4 (unfortunately Geneva is not entirely MultiTOS compatible)
∙ Multiple open windows may be opened
∙ Each window may individually configured with its own colour and
font
∙ Support for the following Netscape tags (commands):
-
-
-
-
-
∙ Support for the -area (forms)
∙ Tables (| - | - |
|---|