+<HTML>
+<HEAD>
+<TITLE>fGIS installation instruction</TITLE>
+</HEAD>
+<BODY>
+
+
+<H1>fGIS installation instructions</H1>
+<B>Before compiling and installing fGIS you should have working
+installation of Tcl/Tk 8.0</B>
+<P>
+Pre-alpha snapshots of fGIS source tree do not include correct
+install target in makefile.
+<P>
+So, you must install it by hand. Source tree is organized such way that
+fGIS can be loaded directly from compilation directory.
+<P>
+fGIS library directory should reside somewhere Tcl can find its packages
+i.e. as subdirectory of one of directories in tcl_pkgPath.
+<P>
+Directory tree should have following structure:
+<PRE>
+ fgis
+ |
+ +-pkgIndex.tcl
+ +-fgis.so (fgis.dll)
+ +-fgis.rc
+ +-tcl/
+ | |
+ | +- various scripts
+ |
+ +--colors/
+ | |
+ | +-color palettes (*.clr)
+ |
+ +--symbols/
+ |
+ +-- symbol files (*.sym)
+
+</PRE>
+
+fGIS initialization code uses some heuristics to find where its support
+files are located, but sureest method is to set Tcl variable
+fGIS_HOME to the top of fGIS library directory before loading dynamic
+library.
+<P>
+your pkgIndex.tcl can look as
+<PRE>
+package ifneeded Fgis 1.0 {set fGIS_HOME /usr/local/lib/fgis; load /usr/local/lib/fgis/fgis.so}
+</PRE>
+<P>
+Directory tcl in fgis source tree contain two executable scripts -
+<CODE>mapview</CODE> and <CODE>hypermap</CODE>. They are sample fGIS
+applications. In Unix they can be easily moved to any directory in your
+PATH - with correctly set up pkgIndex.tcl they'll find support files
+anywhere. On windows they should be renamed to <CODE>mapview.tcl</CODE> and
+<CODE>hypermap.tcl</CODE> so they could be started with double click.
+<P>
+More to follow soon..
+</BODY>
+</HTML>
+
+
+
+
+