
INSTALLATION
============

Xplore requires the Xpm library (version 3.4 or later), Motif 2.0 and
G.M. Messner's Xg widget set (for the XgTabs widget) to compile. The Xg
library can be obtained from:
	http://www2.4dcomm.com/gmessner/htmldocs/xgwidgets.html
Before installing xplore, compile the Xg library and copy its include files
and the library itself to some appropriate location.

Then take a look at `Xplore.tmpl' and edit it as needed. In particular, make
sure that you give the correct include and library paths for the Xg
library. Furthermore, you can specify alternative destination paths if you do
not have write permissions for the standard X11 directories, by editing the
`Destination directories' section at the beginning of the `Xplore.tmpl' file
accordingly. The hairiest part probably is the `System dependencies' section,
which is needed to select the proper interface for accessing the file system
statistics and the mount table. If this doesn't work for your system, please
let me know so that we can try to fix it.

Now run `xmkmf -a' and `make', and hope for the best :). (If your xmkmf
program does not support the -a option, try `xmkmf; make Makefiles; make
depend' instead.) If all goes well, you can try out xplore by running the
`xplore-test' shell script in the source directory. To actually install the
programs along with appdefaults and configuration files, icons and manpages,
run `make install' and `make install.man'. (You may have to become root to
gain the necessary permissions if you install in the standard places.)

After this, xplore should be ready to be used with the standard setup as
described in the xplore(1) manual page. When the user invokes xplore for the
first time, xplore automatically runs the `setup' shell script in the xplore
library directory (usually `/usr/lib/X11/xplore', but this may vary from
system to system) to install a shelf directory in the user's home
directory. The setup script also creates some links to devices and
applications in the user's shelf directory. You might wish to adapt these
items to your local setup by editing the script accordingly.

The xplore library directory also contains the system-wide configuration files
(`system.xplorerc' and `magic'). You can edit these to customize the standard
setup according to your system and your preferences. Please refer to the
xplore(1) and xploretype(1) manual pages for a description of the
`system.xplorerc' and `magic' file syntax.

The application defaults file (`Xplore', usually in
`/usr/lib/X11/app-defaults') contains some application-specific resources
(mostly system-wide defaults for option settings) and the application widget
resources which control the appearance of xplore. Take a look at this file and
edit it as needed. In particular, you should make sure that the personal
resource file name and the command for merging resources into the resource
database are appropriate for your system (check this if the `Save setup'
option of the Options menu does not work as expected).


ICONS
=====

The distribution includes a fairly extensive collection of icons in XPM format
which I derived from material in the Cica archive and Juan D. Martin's
fileicon collection included in the xfm distribution. These icons are
installed in the `icons' subdirectory of the xplore library directory. Of
course you can also use your own icons by editing the `system.xplorerc' file
accordingly. To change xplore's icon search path, edit the `iconpath' resource
in the Xplore application defaults file. A few icons are hard-coded into
xplore; to change these, you will have to edit icons.c and recompile. Note
that xplore currently only supports icons in XPM format.


PERSONAL CUSTOMIZATION
======== =============

For personal customization, the user may provide `.xplorerc' and `.magic'
files in his home directory which override the system-wide configuration
files. For most purposes, however, it will be sufficient to provide some kind
of "hook" for the user's personal definitions in the global `system.xplorerc'
file. A simple way to accomplish this is to add the line

	#include <.xplore>

to the `system.xplorerc' file. This line should be placed where it allows the
user to override the "standard" definitions for the shelf, the command menu
and the file types contained in the `system.xplorerc' file. That is, it should
come *after* the macro definitions and the global definitions for the shelf,
the command menu and the `Default' file type, but *before* any specific file
types which you would allow the user to override with his own definitions. The
distributed `system.xplorerc' file actually contains such a "personal
customization hook", which can be enabled as follows:

- uncomment the line `#define USER_HOOK' at the beginning of the
  `system.xplorerc' file (or add the option `-D USER_HOOK' to the value of the
  `cppoptions' resource in the Xplore application defaults file)

- add `-I $HOME' as the first option in the value of the `cppoptions'
  resource, s.t. xplore finds the user's `.xplore' file when parsing the
  system-wide configuration file

- create an empty `.xplore' file in the xplore library directory which acts as
  the default if the user does not provide his own `.xplore' file

Given the setup sketched out above, the user can build his own configuration
on top of the standard setup (including the macros defined in the
`system.xplorerc' file) by providing a file `.xplore' in his home directory
which contains the private definitions. A typical example of such an `.xplore'
file can be found in the file `sample.xplore' contained in the distribution.
