This is the HyperNeWS1.4 README file...the first thing you should
study before installing HyperNeWS.  If you've installed HyperNeWS1.3
before, that's no reason to skip reading this!  Lots has changed in
terms of installing HyperNeWS...hopefully for the better.

### Changes in HyperNeWS1.4 ###

HyperNeWS1.4 is different from HyperNeWS1.3 in the following ways,
which are also mentioned in the Introduction section of the manuals:

- It requires OpenWindows2.0.

- HyperNeWS has been split into a source & binary tree format.  There
  is also a Config script that should make installation easier.  The
  configure script lets you place the bin, lib, and fonts directories
  wherever you want, and it keeps the architecture-independent files
  in the $HNHOME tree.

- GoodNeWS has been merged with HyperNeWS.  Now there will be only one
  terminal emulator, etc.  Some things from GoodNeWS were ported to
  HyperNeWS stacks, others weren't.  At the present time, dvinews (the
  LaTeX previewer) has not been ported.  The clipboard, perfmon, and
  (the all-important) Pete's movie have been ported.

- The root menu is now the olwm menu, in a first step towards becoming
  better integrated with OpenWindows.

- The documentation now consists of a User Guide for beginning topics and
  a Reference Manual for more advanced topics.  It is not possible to get
  a hard copy of the online manual, but we'll be more than happy to sell
  you one at minimal cost.

- Clicking on the close button now causes the stack to be iconified.

- Stacks have been changed so that you can specify a minimum allowed
  size for resizable stacks.

- Stacks and drawings are now saved as 80 column lines, and the objects
  are saved in a consistent order.  This will make mailing stacks and
  using SCCS on stacks easier.

- Numerous bugs have also been exterminated.

### Things to watch out for ###

There are two things you may want to make a note of:

- Depending upon your hardware, you may get this message when you
  start OpenWindows:

  *** WARNING ***
	  The display device '/dev/fb' requires the GFX revision
	  of SunOS in order for OpenWindows to run properly.
	  Please contact your local Sun sales office for more
	  information.

  We haven't noticed any unusual behavior when this message appears.
  Also, OpenWindows now beeps once during initialization, so a beep
  isn't an indication that something has gone wrong.

- Sun has acknowledged a problem with input focus when you have both NeWS
  and X applications running.  So even if you have follow-mouse for a
  OpenWindows focus setting, you may sometimes have to click in the window
  to get the focus to change when you switch between X and NeWS appli-
  cations.

### Installation ###

Along with this README file, you will have the HyperNeWS source directory,
called src.  Cd to the src directory and run Config to install HyperNeWS.
It will ask you where you want things installed, and where a few important
things reside (like OpenWindows).  Unless you specify otherwise, it will
create bin, lib, Stacks, etc. subdirectories under HyperNeWS1.4.  Config
cannot handle "~" in pathnames, so type out the full pathname.

Of course, you can choose to put binaries in /usr/local and fonts in
/usr/local/lib.  But since you'll need to keep around a HyperNeWS dir-
ectory for the Stacks, share, etc, subdirectories anyway, we chose to
keep bin & lib there by default.

Once the script has asked you the questions, it will create a Makefile.param
file with the pathnames you entered.  It will also try to install a new
OLUI.ps file in $OPENWINHOME/etc/NeWS/NDE, if yours doesn't have our
changes for metakeys.  Finally, it will do the install if you want it to.
There are a couple of places along the way that Config lets you exit if
you want to.

During the "make install", you will get the following message while
installing the images subdirectory.  It is normal:

	* HyperNeWSCursor ./HpNWSCrr.ff (Encoding: unknown)

Hint:  If you install HyperNeWS for multiple architectures, be sure to
do a "make clean" in between, or else some of the steps will fail when
they try to use the object files left over from the last install.

Once the install is done, you'll have these directories under $HNHOME:

Stacks:  Consists of 3 subdirectories that hold all HyperNeWS stacks.

bin*:  All binaries for HyperNeWS.

etc:  Has a subdir called HyperNeWS where all the core PostScript lives.

include:  Contains hypernews.h, which you'll need when you write client
	  applications.

lib*:  Contains the code needed to link client applications.  It also
       is the home of the fonts* directory.

share:  Things that can be shared across architectures.  It has the dirs:
	draw:  HyperNeWS drawings
	hnman:  Online manual drawings and document
	images:  HyperNeWS images
	ps:  Supporting PostScript code
	examples: Sample stacks and C clients

* These directories are put here by default unless you specify otherwise
  when you run Config.

### Running HyperNeWS ###

Once you have HyperNeWS installed, each account that wants to use it will
need to customize his/her environment a little bit.  A good example of what
needs to be done can be found in the script $HNHOME/share/hn1.4.

While Sun claims that OpenWindows2.0 is faster, loading it can be sloooooow.
Be patient when you start HyperNeWS.  Use the old NeWS trick of moving the
mouse around as its loading.  If the cursor disappears and reappears, then
it's still chewing.  If the cursor is always visible, then something has gone
wrong and you should check for any error messages.

We hope that you enjoy using HyperNeWS1.4, and if you have comments, we'd
be happy to hear from you.  We can be reached via newsdev@turing.ac.uk.

Enjoy!


Jim Rudolf
Arthur van Hoff
Tim Niblett
Danny Pearce
