Context Navigation

Changes between Initial Version and Version 1 of Ticket #965

initial	v1
50	50	- build.xml would copy out the webswing-api.jar (if it exists) into the web/applet folder, as there are webswing library imports and calls being made in the GsdlCollageApplet and JPhind code now, so the webswing-api is needed during compile and runtime.
51	51
	52	- There's further a webswing.config.application and webswing.config.applet to swap between when running Phind/Collage as webswing applications versus webswing applets. Another change that must be made is in webswing-phind.xsl/webswing-collage.xsl: set isWebswingRunAsApplet to true if run as applet and to false if run as application.
	53
52	54	- It turned out that several Collage (but not Phind) applet parameters and even width and height as geometry dimensions were set as classifier options such as through GLI, appearing in collectionConfig.xml. These would need to appear in the applet element, so these were now pushed out by the perl code (buildConfig.xml) to be available in AbstractBrowse service as options subelements on the classifier, and AbstractBrowse then pushed any options available on classifiers out onto the pageResponse. The XSL then read these into the applet element.
53	55