This file has many main sections:

Easy Installation
Installing Chimera
Customizing the installation
Notes for X11R4 and X11R3 Sites
More Setup
NeXT notes
SOCKS notes
Term notes
Note for Sun users with linking problems
Environment variables
JPEG

-----------------
Easy Installation
-----------------

If you have a "standard" setup, type

./config

and answer the questions and follow the directions.  By standard setup
I mean that you are connected to the Internet directly, have X11R5
or better running on your machine, don't have a firewall, and
you are not going to use term.

------------------
Installing Chimera
------------------

If you have xmkmf on your machine then everything should go
smoothly.  Type:

			xmkmf
                        make Makefiles depend clean all

If the compile ran successfully, type:

			make -n install

The -n tells make to show you what it would do; it doesn't actually
do the install.  If everything looks OK, type:

			make install

At this point you should have a running chimera setup.

----------------------------
Customizing the installation
----------------------------

It is unlikely that you will want the default setup.  There are
five files that you should be concerned with:

                        Imakefile
                        Common.tmpl
			lib/content
			src/conf.h
			src/Chimera.ad

There are only a few changes that need to be made.

Imakefile
---------

The Imakefile in the top level directory is used to compile the
whole distribution.

Common.tmpl
------------

You can modify the installation directories and compiler flags
using this file.  Don't forget to type

		make Makefiles depend clean all

after you modify it.

lib/content
------------

The content file is used to specify what Chimera should do with
certain types of files.  The content file is also used to
specify conversions on inline images.  An example of a change you
may want to make is for GIF files.  The default is

*      .gif          !xv %s
*      ^image/gif    !xv %s

If you want to use xloadimage instead of xv to view GIF files you
may want to change the lines above to:

*      .gif          !xloadimage %s
*      ^image/gif    !xloadimage %s

The content file contains comments describing the format.  You should
at least browse the content file to make sure everything looks
reasonable.

src/conf.h
----------

This file contains some defaults which are compiled into Chimera.  You
do not have to modify this file as you can change the parameters using
the resources (except for DOC_TTL).

	DOC_TTL        the minimum lifetime of a cached document
                       (or something like that)
	CONTENT_FILE   the content file
	HOME_PAGE      the default document.  it can be local or remote.
                       example: http://www.unlv.edu/
	HELP_DOCUMENT  the location of the help document.
        PRINTER_NAME   the name of the default printer

I suggest that you make HOME_PAGE and HELP_DOCUMENT local files or
make them point to a local server to give users the best response time.

If you change CHIMERALIB then you will need to change CONTENT_FILE
and HELP_DOCUMENT to put point to SPITHRLIB.  For example, if
CHIMERALIB=/local/infosys/lib then use

#define CONTENT_FILE "/local/infosys/lib/content"
#define HELP_DOCUMENT "/local/infosys/lib/help.html"

You should use 'file:' when specifying local files as documents.  For
example,

#define HELP_DOCUMENT "file:/local/infosys/lib/help.html"

You will have to change CONTENT_FILE, HOME_PAGE,
and HELP_DOCUMENT because the defaults won't really work.

src/Chimera.ad
--------------

You can change the arrangement, color, and labels by changing
the resources in Chimera.ad.  You'll need to experiment if
you don't like the stock settings.

I'll try to make an explanation of the resources that are
reasonable to change.

One of the most important changes here is the contentPath resource.
You should change this to a string like:

Chimera.contentPath: $PATH:/local/pbm/bin:/local/viewers/bin

so that all of your external viewers can be found.

Note that some X servers do not like the colors I selected.
You can add them to your rgb database in X's lib directory
or you can change the colors in Chimera.ad.

-------------------------------
Notes for X11R4 and X11R3 Sites
-------------------------------

If you do not have X11R5 (or higher) installed then Chimera will not
remember the scroll bar position of previous documents.

The X release should be figured out for you so you shouldn't
have to change anything.  Changes should be automatic.

----------
More Setup
----------

I suggest that you use a local home page instead of, say, NCSA's
home page.  The reason for this is because it takes time to
access a remote home page and if the net is down it will take
a really long time.  You should also keep the help page local.

I think a local file is best.  A local server is probably
OK but not quite as good.

You can use my home page but it is probably best if you create
your own to reflect the needs of yourself or your users.

You can add links to neat things like NCSA's server, the WWW
virtual library, and CERN's server in your home document so
that you will have good access to the most interesting bits
of info.

----------
NeXT Notes
----------

Before you type xmkmf you may need to type:

export IMAKECPP=/etc/mouse-cpp

or

setenv IMAKECPP /etc/mouse-cpp

Keep in mind that you need X installed on your machine for Chimera
to work.

-----------
SOCKS NOTES
-----------

I don't live behind a firewall but I received instructions from
Jennine Townsend <aimla!jennine@uunet.UU.NET> which explains
what needs to be done.

You'll need to grab the socks.cstc release from syl.dl.nec.com
and uncomment -DSOCKS in the toplevel file Common.tmpl.

I can't test this so I would appreciate it if someone would
tell me how it goes. [note: I've heard that this works]

The config script will now prompt you for SOCKS information.

----------
Term Notes
----------

Chimera supports the use of "term" instead of normal socket connections,
for those who don't have Ethernet or SLIP connections. Term can be
used over a normal dialup shell; it can be obtained by anonymous
FTP from sunsite.unc.edu in /pub/Linux/apps/comm/term/term, and
it is compatible with most versions of Unix (not just Linux!).
If you want Web and don't have SLIP, this is for you.

To configure Chimera+term just answer the questions asked by the
config script. [This sentence added by John.  A description of
what actually goes on follows...]

To build Chimera+term [by hand], you must do the following:

A. Edit the TERMLIB line in Common.tmpl, removing the comment-character
at the beginning and correcting the directory specified to point to
the directory where you built client.a when installing term. (If
you've deleted this file, then rebuild term to recreate it.)
I keep mine in /usr/local/lib, but you almost certainly won't
find it there.

B. Edit the TERMINC line to point at the directory containing client.h,
which will probably be the same directory as TERMLIB above. Again,
if you have deleted it, reinstall term.

C. Uncomment -DTERM in the TERMFLAG line. IN ADDITION, if your machine
does not have networking support at all, *even in the kernel*, you
can undefine -DNONETWORK. This is not usually necessary, but is
provided for Linux users who have not installed networking support
in their kernels (as opposed to actually hooking up SLIP or Ethernet).

If you don't have to, then don't use -DNONETWORK. Why? Because
Chimera+term allows you to connect to a server on your own machine
*without* using term (ie, in loopback mode). This is very
useful if you are a Web server hacker. In order to do this,
open "http://noterm/....." INSTEAD OF "http://localhost/..."
(which would refer to the machine on the other end of
your term connection!).

Except for the special "noterm" host, chimera+term can now connect
to any host just like the normal-networking version, using
any access method Chimera supports (FTP, etc). Enjoy.

- Tom Boutell

---------
Sun Users
---------

Depending on your setup you may need to link Chimera with
-lresolv.  If you get undefined symbol errors for functions
name "res_*" then you will need to add

-lresolv

to src/Imakefile on the end of the LOCAL_LIBRARIES line.

---------------------
Environment Variables
---------------------

Chimera currently pays attention to two environment variables:
WWW_HOME and PRINTER.

WWW_HOME is used to specify the home page.

PRINTER is used to specify the default printer.

Environment variables override everything else except the command
line.

----
JPEG
----

You'll need to grab a package that will convert JPEG to
PPM files like The Independent JPEG Group's JPEG software.
To find it do an archie search for jpegsrc.  I haven't run across
any inline JPEG files but it is bound to happen and you can do
it with Chimera by using these instructions.

From Jim.Rees@umich.edu:

The problem is that you'll end up with too many colors (2^24), and chimera
throws out the old ones after the first 256.

Going through gif works since gif quantizes to 256 colors, but it's not a
good solution.

I quantize to 16 colors for grayscale, since my grayscale displays are all 4
bit, and to 50 for color, which is what Mosaic uses.  One problem is that
you'll get a different 50 colors for each image, so if you have lots of
inlines on a page, you might still run out.

For grayscale, the quantization should be done after converting to grayscale
instead of before, but I haven't done that yet.  It hasn't been a problem.

Here are my content file entries for inline jpeg:

mimg    ^image/jpeg |djpeg -P %s | ppmtopgm | pgmtopbm
mimg    .jpg       |djpeg -P %s | ppmtopgm | pgmtopbm

gimg    ^image/jpeg |djpeg -P -q 16 %s | ppmtopgm
gimg    .jpg       |djpeg -P -q 16 %s | ppmtopgm

cimg    ^image/jpeg |djpeg -P -q 50 %s
cimg    .jpg       |djpeg -P -q 50 %s
