Difference between revisions of "CWASA Local Installation"
John.Glauert (talk | contribs) (Update for new version numbering approach.) |
John.Glauert (talk | contribs) |
||
| (10 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | [[Main Page|Home]] >> [[ | + | [[Main Page|Home]] >> [[CWA Signing Avatars|CWASA]] |
---- | ---- | ||
| − | = | + | = CWASA Local Installation = |
| − | + | == CWASA on localhost server == | |
| − | The [[ | + | 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] | ||
| − | * [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 | ||
| − | with the year, | + | 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. | ||
| − | 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. | ||
'''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 | + | 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. |
| + | |||
| + | == 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. | ||
| + | |||
| + | * [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 and potentially run from files stored on the local filesystem. | ||
| + | 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. | ||
| + | |||
| + | 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 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 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'''. | ||
| + | |||
| + | == Commercial Use == | ||
| − | For enquires about public and commercial use of the software | + | For enquires about public and commercial use of the software, please see [[CWASA Conditions of Use]]. |
| − | |||
| − | [ | ||
---- | ---- | ||
| − | [[Main Page|Home]] >> [[ | + | [[Main Page|Home]] >> [[CWA Signing Avatars|CWASA]] |
Latest revision as of 13:33, 18 January 2021
CWASA Local Installation
CWASA on localhost server
The 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:
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, for example http://localhost/jas/loc2021 should provide access to a local version of the standard JASigning installation, but with a limited number of avatars.
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. 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.
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 including .jnlp, .properties, .vert, .frag, and .sigml. Examination of server logs should reveal whether pages are being blocked or not.
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.
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. 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 XMLHttpRequests 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 the software uses an ActiveX object for XMLHttpRequests. 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.
Commercial Use
For enquires about public and commercial use of the software, please see CWASA Conditions of Use.