INSTALLING MCARD -- I really don't want to bother reading all this.
================

1. Issue "make"
You may get lucky. All the includes and libraries are located in standard
places.

INSTALLING MCARD -- For those who fully understand
================

1. Change INCLUDE in the Makefile
2. Change LDLIBS in the Makefile
3. Issue "make"

Sorry, no Imakefile available yet.

INSTALLING MCARD -- Verbose Instructions
================

To install mcard, please follow these steps:

1. Depending on how the program was delivered to you. You will need to
   uudecode it, GNU unzip (or uncompress), and untar it. Example commands
   follow:
     uudecode mcard1.x.tar.gz.uue
     gzip -d -n mcard1.x.tar.gz
     tar vcf mcard1.x.tar

   Tar will create a directory "mcard" from the current working directory.
   Make sure you have write access to the directory.

   The uuencoded file is about 70K, the gzip'ed file is about 50K, the
   tar file is about 450K, same for the directory after untarring the
   source (pretty good compression), and the final executable is about
   300K to 1M for RISC processors, depending on how you link the libraries.

   You can remove the compressed file and tar file after the source
   directory (mcard) is created.
 
Steps 2 to 4 are optional if everything is set up correctly in your
environment, but read just in case.

2. Make sure you have access to a C compiler. I have tried gcc version 2.3.3
   2.6.3 and the Sun cc compiler.

   From your favorite shell (sh and csh work), Try "which cc" or "which gcc"
   You will have to change your path if you cannot execute a C compiler.

3. Make sure you have access to the "make" utility. Same as above, "which make"
   will tell you where the utility resides and if it's in your execution
   path. mcard was compiled with the "GNU make" utility. I am not sure how
   your native "make" will affect the compilation, but the Makefile should
   be generic enough for any make utility. GNU make is recommended.

4. Discover where the include files reside. Typically, includes
   are found in /usr/include. This may be different on your
   system. It is critical that the Motif includes, for example,
   "Xm.h" are found. There is usually a sub-directory "Xm"
   which it and all Motif includes are found.  Additionally, the "X11"
   include files, like "Xlib.h" also need to be referenced. Typically,
   they are not far from Xm. Hopefully, one directory up, over, and
   down. For example,"Xm.h" may be located in "/local/include/motif/Xm"
   and "Xlib.h" should be in /local/include/motif/X11".

   If the includes are not in /usr/include/X11, you will have to edit the
   "Makefile" and change the INCLUDE variable to reference the
   directory. See examples in the Makefile.

5. Discover where the libraries reside. Similar to above, the libraries
   can be found in: /usr/lib.  I believe that most compilers will look
   here  first. Check this directory or the directory you know has the
   Motif libraries and look for "libXm.a","libXt", "libX11".  Check
   closely, "libXol.a" is for Sun Open Look.

   If the libraries are not in /usr/lib, you will have to edit the
   "Makefile" and change the LDLIBS variable to reference the
   directory. See Makefile for examples.

6. Copy the resource declaration file to the appropriate place.
   Generally, resource files are located under "~/.app-defaults",
   but you may use a different location. The important point
   is that the application must be able to find this file when
   executed. This will require that the XAPPLRESDIR environment
   variable be set or the resource file be copied to a globally
   accessible location ("/usr/X11/lib/$LANG/app-defaults"), where
   LANG is the optional language specifier. It is recommended that
   the resource file be moved to the global app-defaults directory
   after you become familiar with mcard. The command below assumes
   you are in the directory which holds the source.

   "cp ./Mcard ~/.app-defaults/Mcard"
   "setenv XAPPLRESDIR ~/.app-defaults/MCARD"

   The "Mcard" file contains all the (English) text, keyboard
   accelerators, and colors. Other languages are supported.

   "Mcard.german" - This is the german resource file.
   Others to be added soon. If you can help, email "mjo@ai.net".
   
   The procedure is the same for other languages, except that
   the file is copied to a language directory specified by the
   LANG environment variable.

   "cp ./Mcard.german ~/.app-defaults/german/Mcard"
   "setenv XAPPLRESDIR ~/.app-defaults/MCARD"

   For more information about the resource file, See below.

7. Issue the "make" command from the directory which holds the source.

8. Issue the command "mcard" or if your path is set correctly "./mcard".

9. If that doesn't work, issue "make clean", and then try the steps above,
   again.

10. Try the example cardfile "Relative.crd". You will see 19 Cards.

IT STILL DOESN'T WORK
=====================

Don't keep looping through steps 1 & 9. :-)
Please see the file, OH-NO in the "docs" directory.
You can also e-mail me, mjo@ai.net

THE "Mcard" RESOURCE FILE
==========================

This file specifies what mcard looks likes. All text and colors for
virtually all widgets are defined here.

mcard was created with a pretty harsh combination of colors, yellow,
orange and green. Two reasons: I wanted to introduce people to the
configurability of X. Second, it cannot be missed. I dream of the day
I walk by a desk and see someone using mcard.

I would recommend that you search for "background" in the "Mcard"
resource file and change the colors to something more pleasing to you.

Lastly, as you become more familar with mcard and gain some trust. The
resource file should be moved the app-defaults directory and the
resources made globally available on your system.

-Mike 
