CWASA Local Installation - Revision history

John.Glauert at 13:33, 18 January 2021

2021-01-18T13:33:53Z

← Older revision		Revision as of 13:33, 18 January 2021
Line 1:		Line 1:
	[[Main Page\|Home]] >> [[~~JASigning~~]]		[[Main Page\|Home]] >> [[CWA Signing Avatars\|CWASA]]
	----		----
	= ~~JASigning~~ Local Installation =		= CWASA Local Installation =

	== ~~JASigning~~ on localhost server ==		== CWASA on localhost server ==
	The [[~~JASigning~~]] software supports web pages containing interactive virtual signing. ~~Such~~ web pages use a release of the software hosted on the same server as the pages themselves. In order to support development of new web pages, for evaluation or individual research, a ~~release~~ of the software, along with some example pages, is provided as ZIP archives:		The [[CWA Signing Avatars\|CWASA]] software supports web pages containing interactive virtual signing. For the legacy [[JASigning]] software, such web pages use a release of the software hosted on the same server as the pages themselves. In order to support development of new web pages, for evaluation or individual research, a Legacy Release of the software, along with some example pages, is provided as ZIP archives:

	* [http://vhg.cmp.uea.ac.uk/tech/jas/local/jas.zip jas.zip]		* [http://vhg.cmp.uea.ac.uk/tech/jas/local/jas.zip jas.zip]
Line 10:		Line 10:

	The files in '''jas.zip''' should be extracted and the '''jas''' folder and contents placed so it is served from the root of the local webserver. Installations are tagged		The files in '''jas.zip''' should be extracted and the '''jas''' folder and contents placed so it is served from the root of the local webserver. Installations are tagged
	with the year, so [http://localhost/jas/loc2021 http://localhost/jas/loc2021]		with the year, for example [http://localhost/jas/loc2021 http://localhost/jas/loc2021]
	should provide access to a local version of the standard [[JASigning]] installation, but with a limited number of avatars.		should provide access to a local version of the standard [[JASigning]] installation, but with a limited number of avatars.

Line 20:		Line 20:
	may need some configuration in order to serve files with extensions including '''.jnlp''', '''.properties''', '''.vert''', '''.frag''', and '''.sigml'''. Examination of server logs should reveal whether pages are being blocked or not.		may need some configuration in order to serve files with extensions including '''.jnlp''', '''.properties''', '''.vert''', '''.frag''', and '''.sigml'''. Examination of server logs should reveal whether pages are being blocked or not.

	== ~~JASigning~~ Examples using the VHG Server ==		== CWASA Examples using the VHG Server ==

	A version of the BSL Examples site is available as a demonstration using the standard VHG installation via CORS.		A version of the BSL Examples site is available as a demonstration using the standard VHG installation via CORS.
Line 38:		Line 38:

	== Commercial Use ==		== Commercial Use ==
	For enquires about public and commercial use of the software ~~and the virtual~~
	~~characters Anna and Marc~~, please ~~email~~		For enquires about public and commercial use of the software, please see [[CWASA Conditions of Use]].
	[~~mailto:CMP_VirtualSigning@uea.ac.uk CMP_VirtualSigning@uea.ac.uk~~].

	----		----
	[[Main Page\|Home]] >> [[~~JASigning~~]]		[[Main Page\|Home]] >> [[CWA Signing Avatars\|CWASA]]

John.Glauert: John.Glauert moved page JASigning Local Installation to CWASA Local Installation

2021-01-18T13:26:51Z

John.Glauert moved page JASigning Local Installation to CWASA Local Installation

← Older revision	Revision as of 13:26, 18 January 2021
(No difference)

John.Glauert: /* JASigning on localhost server */

2021-01-15T18:41:37Z

JASigning on localhost server

← Older revision		Revision as of 18:41, 15 January 2021
Line 10:		Line 10:

	The files in '''jas.zip''' should be extracted and the '''jas''' folder and contents placed so it is served from the root of the local webserver. Installations are tagged		The files in '''jas.zip''' should be extracted and the '''jas''' folder and contents placed so it is served from the root of the local webserver. Installations are tagged
	with the year, so [http://localhost/jas/~~loc2017~~ http://localhost/jas/~~loc2017~~]		with the year, so [http://localhost/jas/loc2021 http://localhost/jas/loc2021]
	should provide access to a local version of the standard [[JASigning]] installation, but with a limited number of avatars.		should provide access to a local version of the standard [[JASigning]] installation, but with a limited number of avatars.

John.Glauert: Add .vert and .frag to extensions needed on files served from IIS

2017-10-02T18:39:22Z

Add .vert and .frag to extensions needed on files served from IIS

← Older revision		Revision as of 18:39, 2 October 2017
Line 18:		Line 18:

	'''Note''': The installation does not rely on any special functionality of the web server, which is only required to deliver static content. However, web servers (such as IIS)		'''Note''': The installation does not rely on any special functionality of the web server, which is only required to deliver static content. However, web servers (such as IIS)
	may need some configuration in order to serve files with extensions ~~such as~~ '''.jnlp''', '''.properties''', and '''.sigml'''. Examination of server logs should reveal whether pages are being blocked or not.		may need some configuration in order to serve files with extensions including '''.jnlp''', '''.properties''', '''.vert''', '''.frag''', and '''.sigml'''. Examination of server logs should reveal whether pages are being blocked or not.

	== JASigning Examples using the VHG Server ==		== JASigning Examples using the VHG Server ==

John.Glauert: Clarification on Internet Explorer

2017-02-07T11:53:47Z

Clarification on Internet Explorer

← Older revision		Revision as of 11:53, 7 February 2017
Line 34:		Line 34:
	** On OS X a script can be used to open the application with the parameter. Such a script can replace the binary that is normally launched, opening a copy of the binary with the additional parameter.		** On OS X a script can be used to open the application with the parameter. Such a script can replace the binary that is normally launched, opening a copy of the binary with the additional parameter.
	** On Windows a shortcut can be customised to add the parameter.		** On Windows a shortcut can be customised to add the parameter.
	* For Internet Explorer ~~it is necessary to use~~ an ActiveX object for '''XMLHttpRequest'''s ~~and~~ to set some Internet options. These seem to work: On Advanced tab: '''Allow active content to run in files on My Computer'''; On Security tab, in Custom Level: '''Access data sources across domains'''.		* For Internet Explorer the software uses an ActiveX object for '''XMLHttpRequest'''s. It is necessary to set some Internet options. These seem to work: On Advanced tab: '''Allow active content to run in files on My Computer'''; On Security tab, in Custom Level: '''Access data sources across domains'''.
	* For Safari install the Develop menu and select '''Disable Local File Restrictions'''.		* For Safari install the Develop menu and select '''Disable Local File Restrictions'''.

John.Glauert: /* JASigning Examples using the VHG Server */

2017-01-31T14:21:08Z

JASigning Examples using the VHG Server

← Older revision		Revision as of 14:21, 31 January 2017
Line 35:		Line 35:
	** On Windows a shortcut can be customised to add the parameter.		** On Windows a shortcut can be customised to add the parameter.
	* For Internet Explorer it is necessary to use an ActiveX object for '''XMLHttpRequest'''s and to set some Internet options. These seem to work: On Advanced tab: '''Allow active content to run in files on My Computer'''; On Security tab, in Custom Level: '''Access data sources across domains'''.		* For Internet Explorer it is necessary to use an ActiveX object for '''XMLHttpRequest'''s and to set some Internet options. These seem to work: On Advanced tab: '''Allow active content to run in files on My Computer'''; On Security tab, in Custom Level: '''Access data sources across domains'''.
	* For Safari install the Develop menu and select '''Disable Local ~~FileRestrictions~~'''.		* For Safari install the Develop menu and select '''Disable Local File Restrictions'''.

	== Commercial Use ==		== Commercial Use ==

John.Glauert: Clarify Safari information

2017-01-31T14:20:41Z

Clarify Safari information

← Older revision		Revision as of 14:20, 31 January 2017
Line 30:		Line 30:

	Only Firefox will handle pages stored on the local filesystem by default, but placing files on a '''localhost''' server will work for major browsers.		Only Firefox will handle pages stored on the local filesystem by default, but placing files on a '''localhost''' server will work for major browsers.
	Most browsers will not handle '''XMLHttpRequest'''s for '''file:''' URLs as it can be seen as a security risk. However, this limitation can be overcome if desired. For ~~Safari,~~ Chrome, and Opera it is necessary to launch the browser with the '''--allow-file-access-from-files''' parameter. On OS X a script can be used to open the application with the parameter. Such a script can replace the binary that is normally launched, opening a copy of the binary with the additional parameter. On Windows a shortcut can be customised to add the parameter. For Internet Explorer it is necessary to use an ActiveX object for '''XMLHttpRequest'''s and to set some Internet options: On Advanced tab: '''Allow active content to run in files on My Computer'''; On Security tab, in Custom Level: '''Access data sources across domains'''.		Most browsers will not handle '''XMLHttpRequest'''s for '''file:''' URLs as it can be seen as a security risk. However, this limitation can be overcome if desired:
			* For Chrome and Opera it is necessary to launch the browser with the '''--allow-file-access-from-files''' parameter.
			** On OS X a script can be used to open the application with the parameter. Such a script can replace the binary that is normally launched, opening a copy of the binary with the additional parameter.
			** On Windows a shortcut can be customised to add the parameter.
			* For Internet Explorer it is necessary to use an ActiveX object for '''XMLHttpRequest'''s and to set some Internet options. These seem to work: On Advanced tab: '''Allow active content to run in files on My Computer'''; On Security tab, in Custom Level: '''Access data sources across domains'''.
			* For Safari install the Develop menu and select '''Disable Local FileRestrictions'''.

	== Commercial Use ==		== Commercial Use ==

John.Glauert: Explanation of opening web pages stored on the local filesystem.

2017-01-30T20:24:35Z

Explanation of opening web pages stored on the local filesystem.

← Older revision		Revision as of 20:24, 30 January 2017
Line 26:		Line 26:
	* [http://vhg.cmp.uea.ac.uk/tech/jas/local/BSLExamples.zip BSLExamples.zip]		* [http://vhg.cmp.uea.ac.uk/tech/jas/local/BSLExamples.zip BSLExamples.zip]

	The files in '''BSLExamples.zip''' should be extracted and the '''BSLExamples''' folder can be placed on a web server or run as local ~~files~~.		The files in '''BSLExamples.zip''' should be extracted and the '''BSLExamples''' folder can be placed on a web server and potentially run from files stored on the local filesystem.
	Resources will be fetched from the standard VHG release.		Resources will be fetched from the standard VHG release. It is also possible to use example web pages in the VHG distribution in the same way. The file '''cwaclientcfg.json''' must be placed beside the web pages.

	~~It is also possible to use example web~~ pages in the ~~VHG distribution in the same way~~. ~~The~~ file '''~~cwaclientcfg~~.~~json~~''' ~~must~~ be ~~placed beside~~ the ~~web pages~~.		Only Firefox will handle pages stored on the local filesystem by default, but placing files on a '''localhost''' server will work for major browsers.
			Most browsers will not handle '''XMLHttpRequest'''s for '''file:''' URLs as it can be seen as a security risk. However, this limitation can be overcome if desired. For Safari, Chrome, and Opera it is necessary to launch the browser with the '''--allow-file-access-from-files''' parameter. On OS X a script can be used to open the application with the parameter. Such a script can replace the binary that is normally launched, opening a copy of the binary with the additional parameter. On Windows a shortcut can be customised to add the parameter. For Internet Explorer it is necessary to use an ActiveX object for '''XMLHttpRequest'''s and to set some Internet options: On Advanced tab: '''Allow active content to run in files on My Computer'''; On Security tab, in Custom Level: '''Access data sources across domains'''.

	== Commercial Use ==		== Commercial Use ==

John.Glauert: /* Commercial USe */

2017-01-27T12:46:02Z

Commercial USe

← Older revision		Revision as of 12:46, 27 January 2017
Line 31:		Line 31:
	It is also possible to use example web pages in the VHG distribution in the same way. The file '''cwaclientcfg.json''' must be placed beside the web pages.		It is also possible to use example web pages in the VHG distribution in the same way. The file '''cwaclientcfg.json''' must be placed beside the web pages.

	== Commercial ~~USe~~ ==		== Commercial Use ==
	For enquires about public and commercial use of the software and the virtual		For enquires about public and commercial use of the software and the virtual
	characters Anna and Marc, please email		characters Anna and Marc, please email

John.Glauert: Extra BSLExamples distribution accessing VHG resources

2017-01-27T12:44:55Z

Extra BSLExamples distribution accessing VHG resources

← Older revision		Revision as of 12:44, 27 January 2017
Line 3:		Line 3:
	= JASigning Local Installation =		= JASigning Local Installation =

			== JASigning on localhost server ==
	The [[JASigning]] software supports web pages containing interactive virtual signing. Such web pages use a release of the software hosted on the same server as the pages themselves. In order to support development of new web pages, for evaluation or individual research, a release of the software, along with some example pages, is provided as ZIP archives:		The [[JASigning]] software supports web pages containing interactive virtual signing. Such web pages use a release of the software hosted on the same server as the pages themselves. In order to support development of new web pages, for evaluation or individual research, a release of the software, along with some example pages, is provided as ZIP archives:

	* [http://vhg.cmp.uea.ac.uk/tech/jas/local/jas.zip jas.zip]		* [http://vhg.cmp.uea.ac.uk/tech/jas/local/jas.zip jas.zip]
	* [http://vhg.cmp.uea.ac.uk/tech/jas/local/BSLExamples.zip BSLExamples.zip]		* [http://vhg.cmp.uea.ac.uk/tech/jas/local/BSLExamples.loc.zip BSLExamples.loc.zip]

	The files in '''jas.zip''' should be extracted and the '''jas''' folder and contents placed so it is served from the root of the local webserver. Installations are tagged		The files in '''jas.zip''' should be extracted and the '''jas''' folder and contents placed so it is served from the root of the local webserver. Installations are tagged
Line 13:		Line 13:
	should provide access to a local version of the standard [[JASigning]] installation, but with a limited number of avatars.		should provide access to a local version of the standard [[JASigning]] installation, but with a limited number of avatars.

	The files in '''BSLExamples.zip''' should be extracted in the same way and the '''BSLExamples''' folder placed at the root, and the examples can be viewed from [http://localhost/BSLExamples http://localhost/BSLExamples].		The files in '''BSLExamples.loc.zip''' should be extracted in the same way and the '''BSLExamples''' folder placed at the root, and the examples can be viewed from [http://localhost/BSLExamples http://localhost/BSLExamples].
	In fact the examples site can be renamed and placed at any other location on the local web server as long as the paths		In fact the examples site can be renamed and placed at any other location on the local web server as long as the paths
	constructed by the '''startPlayer''' function in '''appletframe.html''' are adjusted to match the chosen location for SiGML files.		constructed by the '''startPlayer''' function in '''appletframe.html''' are adjusted to match the chosen location for SiGML files.
Line 20:		Line 20:
	may need some configuration in order to serve files with extensions such as '''.jnlp''', '''.properties''', and '''.sigml'''. Examination of server logs should reveal whether pages are being blocked or not.		may need some configuration in order to serve files with extensions such as '''.jnlp''', '''.properties''', and '''.sigml'''. Examination of server logs should reveal whether pages are being blocked or not.

			== JASigning Examples using the VHG Server ==

			A version of the BSL Examples site is available as a demonstration using the standard VHG installation via CORS.

			* [http://vhg.cmp.uea.ac.uk/tech/jas/local/BSLExamples.zip BSLExamples.zip]

			The files in '''BSLExamples.zip''' should be extracted and the '''BSLExamples''' folder can be placed on a web server or run as local files.
			Resources will be fetched from the standard VHG release.

			It is also possible to use example web pages in the VHG distribution in the same way. The file '''cwaclientcfg.json''' must be placed beside the web pages.

			== Commercial USe ==
	For enquires about public and commercial use of the software and the virtual		For enquires about public and commercial use of the software and the virtual
	characters Anna and Marc, please email		characters Anna and Marc, please email