

             		  Installation Notes
			       for the
	                  moog gopher client


These notes describe moog version 0.0, written in October 1992.  moog is 
based on Xgopher version 1.1, completed in April 1992.  moog adds some 
features, and takes others away!  Consult the manpage for more information.

Please report any problems, suggestions, or flames to the author:

	Martin Hamilton
	Department of Computer Studies
	Loughborough University of Technology
	Leics. LE11 3TU, UK

	Voice:     +44.(0)509.224151
	E-Mail:    M.T.Hamilton@lut.ac.uk


System Requirements
-------------------

moog requires at least Release 4 of the X window system, version 11.  It 
uses the Motif widget set, the X toolkit intrinsics, and the X library.

moog has been compiled and run on

 . Sun 4 (SparcStation) running SunOS 4.1.1, and SunOS 4.1.2 - compiled
   with the bundled cc, and linked with IXI's Motif 1.1 distribution
   and both MIT X11R4 and X11R5 libraries

 . HP 9000 series 855 and 870, running HP-UX 8.0 with HP's distribution
   of X11R4 and Motif 1.1

 . Various X servers have been tested including Sun's OpenWindows 3,
   MIT X11R5, an NCD X terminal and various sizes and shapes of PC
   running Vista eXceed under MS-Windows 3.1


Installation
------------

moog will likely be obtained as a Unix tar file.

After using tar to extract the contents of this file, perform
the following steps.

1. Modify the makefile (Makefile).  It will probably be necessary
   to change the settings of CFLAGS and LIBS.

2. Modify the configuration file (conf.h).  The comments in the
   file tell you what is expected.  Possibly little change will 
   be necessary, but at least consider changing the default
   top-level gopher server host name and port number.  These
   are just the compiled-in defaults, many can still be changed
   at run-time to accommodate individual preferences.

3. Modify the application defaults file (Moog.ad).
   Little change may be necessary.  However, entries in this
   file for host name, port number, help file name, etc., 
   override those defaults compiled into moog through
   the configuration file (step 3).

4. make
   (this will compile the 15 or so source files and link them
   with the X libraries to produce the executable file moog.)

5. With root privileges,

   make install

   - this should install the 4 files needed by moog.  If you wish
   to install them manually, the four files that need to be installed are:

   moog		This is the moog program itself.  
		Default - /usr/local/bin/moog

   moog.help	Help text.
		Default - /usr/lib/X11/moog.help

   Moog.ad	Application defaults.
		Default - /usr/lib/X11/app-defaults/Moog

   moog.man	User documentation (man page).
		Default - /usr/local/man/manl/moog.l
  

Yet to come?
------------

Automagical selection of appropriate colours and fonts based on 
the display server characteristics - perhaps by use of class names 
(e.g. SmallMoog, MediumMoog, BigMoog...), or widget naming (e.g.
smallTextDisplay...).

More support for visual feedback, and abort-ion, in cso and index
searches.

Auto-loading and saving of bookmarks.

Fallback resources, to make moog independent of its app-defaults.

Command line selection of startup server and port number, 
e.g. moog -host hill.lut.ac.uk -port 5000

Options dialogue for the most useful app-defaults

Binary file transfer

Support for multiple views of gopherspace, e.g. tree/digraph, 3D,
fisheye...  

Recycled text windows, with a 'keep' button which lets you hang on
to something interesting.

Go to an arbitrary path in gopherspace

Built-in support for MIME, e.g. a multipart MIME document might be
represented as folder rather than a single object.

Conformance to the Motif Style Guide (no, only kidding :-)


Contributors
------------

From the Xgopher README:

"Thanks to all people who took the time to send me their comments,
suggestions, and problems in the versions of Xgopher 1.0, especially
John Franks.  All bug reports and most of the suggestions have been
incorporated into Xgopher 1.1.  A couple of the more time consuming
requests will show up in a future release.

Versions 1.0 and beyond of Xgopher are by and large a total rewrite
of a beta version supplied by the University of Minnesota.  It
does however re-use some code and ideas from previous versions.
I cannot determine from older versions who did what, so I want
to credit:

  . jonathan@Think.COM  (apparently responsible for WAIS
    software that had been included in xgopher)
  . Paul Lindner at University fo Minnesota who wrote the 
    original Xgopher client.

Of course, the present author assumes responsibility for any
problems introduced."


