                    NAG - Not a GUI, but nice none-the-less

Welcome to the second public NAG release. This package has everything you need
to start NAGging.

Contact Info.
=============

For more info, contact rich@oester.com.

Contents
========

This release includes the NAG executable, Makefile, and object files - this
release also includes the source.

The object files are released in case you want to add c code functions - in
which case you will have to recompile hooks.c and relink. Note that as
shipped, nag is linked with a sample function defined in hooks.c; the purists
might want to remove it (though it hurts nothing if left in).

You do not have to muck with the source unless you want to.

Note that this version has been built on a bsdi 1.1 system - do not use on 1.0.

About nag.txt and nag.doc (in the doc dir)
------------------------------------------

I did not have time to prettify nag.doc so it produces neato text and ps
files. The nag.txt file ain't perfect but also ain't too bad. Ideally and 
hopefully you can get a hold of MS word and print out nag.doc however you 
wish (NOTE: you might have to redo the TOC).


Getting Started
===============

If you're using a bsdi 1.1 machine, you can go rigth to the nag directory and
start playing around. The following instructions assume you are in the nag
directory.

If you're not using a bsdi 1.1 machine, go to the src dir and rebuild - nag's
been built only on bsdi and SUN, but nag ain't rocket science coding; should
build easy enough anywhere. Once nag is built, copy the nag exe to the nag
dir (and the .o files to the obj dir).

This package comes with a sample script (the menumess file). To start NAG,
do one of the following:

1. Enter 'nag' (assumes . in PATH) - starts nag in dumb line mode
2. Enter 'nag -a' if you're sure your terminal session is ANSI/XTERM/VT102
3. Enter 'nag -t' to start with simple terminal test session - note that
   if results of test questions indicate ansi support, the .nagrc file
   is updated.

For initial fun, don't use any other options.

Also, make sure after unpacking that the file listmake.pl is executable!

Note the default presentation relies on NAG being in directory with all other
files as shipped in the tar.

Once you're ready to start munging NAG scripts of your own, remember that you
can invoke NAG with the -d option (debug); this enables the 0reload command
that reloads the menumess file. See the documnetation for details (section on
debugging a NAG presentation).

License Terms
=============

NAG is provided courtesy Oesterreich & Assc. Inc. It is provided on an 'as is'
basis without ANY warranty of ANY type regarding usefullness or potential
risk.

By virtue of using NAG, you agree to the terms enumerated in this 'License
Terms' section. In particular, you agree to indemnify and hold harmless all
agents of Oesterreich & Assc. from any and all loss caused by your use of
NAG. You agree to use NAG "AT YOUR OWN RISK". If this is not acceptable, do
NOT use this software - it's that simple.

Note that NAG is copyright software - any derivative works based on NAG must
credit Oesterreich & Assc. Inc.

NAG is also NOT free; it is shareware. Commercial/organizations (any type) 
cost for NAG use is $200. Individuals cost for NAG is $20.

As with most shareware, no one is going to hound you if you don't pay, but's
it's really advisable that commercial/organization users pay to avoid costlier
legal liabilities.


Reported Problems
-----------------

1. Problem - when run list manager demo:

  OK, listen up - this is a full power list manager example. When you enter
  {DOIT}, you'll be presented with a list of files. To select some,
  simply enter the corresponding letter; enter again to deselect.
  
  See the NAG script and listmake.pl for important details!


  listmake.pl: not found
  ^^^^^^^^^^^^^^^^^^^^^^
  Enter a TOPIC, or type HELP for instructions:

You get the above!

Problem is either current dir not in path or edit the following line in the
menumess file to specify current dir:

{_POPEN} ./listmake.pl ./list.list[home]

2. Problem - documentation or feature? The documentation file says:

               If the global config file does not exists, it is created. More
               info on global config file is presented shortly.

However, nag seems to simply fail if .nagrc doesn't exist:

For now, the .nagrc must exist even if it's empty.


