Non-standard Gsharp Web Configuration

The Gsharp Web Edition configuration process has been designed to be as flexible as possible.

The Gsharp Web Edition examples examine environment variables to see how the GsharpWE has been installed.

The following environment variables are used:

GsharpTmpFilesActualDir - the name of a directory where Gsharp should write temporary files
GsharpTmpFilesWebDir - how the above directory is named on the web server
GsharpWEcgi-binDir - how the Gsharp cgi-bin script directory is named on the web server.

The only place where we can't use environment variables is inside HTML files - which are fixed. The following files contain links to /Gsharp-bin/ which will need to be edited if you use a different name for your Gsharp cgi-bin directory ($UNIDIR refers to the Gsharp home directory):

• $UNIDIR/example/GsharpWE/app/command.html - in the link to gs_update.gsw
• $UNIDIR/example/GsharpWE/app/editor.html - in the link to gs_rendor.gsw
• $UNIDIR/example/GsharpWE/app/canvas.html - has many calls to gs_probe.gsw.
• $UNIDIR/example/GsharpWE/contour/editor.html- in the link to gs_contour.gsw.
• $UNIDIR/example/GsharpWE/gallery/index.html - in the link to gs_gallery.gsw.
• $UNIDIR/example/GsharpWE/seismic/index.html - in the link to gs_seismicArea.gsw.
  
• In $UNIDIR/example/GsharpWE/zoom/GsharpApp.java you will need to update the following line:

  private String _zoomScript="/Gsharp-bin/gs_zoom.gsw";

  and then compile the file into GsharpApp.class