Virtual Humans - User contributions [en-gb]

CWASA Release Notes

2026-04-04T14:57:13Z

John.Glauert: Add vhg2024 standard and development links.

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

= CWA Signing Avatars Release Notes =

From 2021 the standard Open [[CWA Signing Avatars|CWASA]] release, found at
[http://vhg.cmp.uea.ac.uk/tech/jas/std/ http://vhg.cmp.uea.ac.uk/tech/jas/std/],
allows personal, public, and commercial use of the software when accessed, unmodified, from the UEA server. See [[CWASA Conditions of Use|Conditions of Use]].

These notes, and the notes for [[JASigning Release Notes|JASigning]], include Legacy releases with additional avatars and earlier deprecated [[JASigning]] resources. There is also a Development release containing components that cannot be guaranteed to be stable and should only be used for evaluation.

See [[CWA Signing Avatars|CWASA]] for other resources and documentation, including the [[CWASA Local Installation]], a version that can be installed on a localhost web server for evaluation.

Users are welcome to provide feedback via the [[JASigning Issue Reporting|Issue Reporting]] page. Documentation of the system is a work in progress so please send questions and comments to [mailto:cmp_virtualsigning@uea.ac.uk cmp_virtualsigning@uea.ac.uk] so that we can update these pages.

= Table of Contents =

__TOC__

= CWASA Release Notes =

All [[JASigning]] releases before 2021 are available only for evaluation and research, as for the current Legacy and Development releases. The Standard Version is an Open Release which will be based on a Legacy Release but omitting most deprecated software based on Java. The Development Version is a Development Release, potentially containing experimental features.

= CWASA 2026 =

== CWASA 2026 (Standard Version) ==

Open Release found at [//vhg.cmp.uea.ac.uk/tech/jas/vhg2026/ vhg.cmp.uea.ac.uk/tech/jas/vhg2026].

This release is based on the Legacy Release [[#CWASA_2025a_(2025-02)| CWASA 2025a]].

In modern browsers the appearance of the Anna avatar with fully closed eyes is rather dark.
This may have been true for some time and will be investigated when time permits.

== CWASA 2026z (Development Version) ==

Development Release found at [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2026z/ vhg.cmp.uea.ac.uk/tech/jas/vhg2026z].

This release is based on the Legacy Release [[#CWASA_2025a_(2025-02)| CWASA 2025a]].

In modern browsers the appearance of the Anna avatar with fully closed eyes is rather dark.
This may have been true for some time and will be investigated when time permits.

Users are encouraged to try the development release and report any issues encountered.

= CWASA 2025 =

== CWASA 2025 (Standard Version) ==

Open Release found at [//vhg.cmp.uea.ac.uk/tech/jas/vhg2025/ vhg.cmp.uea.ac.uk/tech/jas/vhg2025].

This release is based on the Legacy Release [[#CWASA_2025a_(2025-02)| CWASA 2025a]].

In modern browsers the appearance of the Anna avatar with fully closed eyes is rather dark.
This may have been true for some time and will be investigated when time permits.

== CWASA 2025z (Development Version) ==

Development Release found at [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2025z/ vhg.cmp.uea.ac.uk/tech/jas/vhg2025z].

This release is based on the Legacy Release [[#CWASA_2025a_(2025-02)| CWASA 2025a]].

In modern browsers the appearance of the Anna avatar with fully closed eyes is rather dark.
This may have been true for some time and will be investigated when time permits.

Users are encouraged to try the development release and report any issues encountered.

== CWASA 2025a (2025-02) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2025a/ vhg.cmp.uea.ac.uk/tech/jas/vhg2025a].

These are the main differences between this version and [[#CWASA_2024d_(2024-11)| CWASA 2024d]]:

* Index page has instructions on handling excessive quarantining for Apple Silicon apps.

= CWASA 2024 =

== CWASA 2024 (Standard Version) ==

Open Release found at [//vhg.cmp.uea.ac.uk/tech/jas/vhg2024/ vhg.cmp.uea.ac.uk/tech/jas/vhg2024].

This release is based on the Legacy Release [[#CWASA_2024d_(2024-11)| CWASA 2024d]].

In modern browsers the appearance of the Anna avatar with fully closed eyes is rather dark.
This may have been true for some time and will be investigated when time permits.

== CWASA 2024z (Development Version) ==

Development Release found at [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2024z/ vhg.cmp.uea.ac.uk/tech/jas/vhg2024z].

This release is based on the Legacy Release [[#CWASA_2024d_(2024-11)| CWASA 2024d]].

In modern browsers the appearance of the Anna avatar with fully closed eyes is rather dark.
This may have been true for some time and will be investigated when time permits.

Users are encouraged to try the development release and report any issues encountered.

== CWASA 2024d (2024-11) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2024d/ vhg.cmp.uea.ac.uk/tech/jas/vhg2024d].

These are the main differences between this version and [[#CWASA_2024c_(2024-08)| CWASA 2024c]]:

* Animgen transpiled using current version of Emscripten
* Functionality should be unchanged.

== CWASA 2024c (2024-08) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2024c/ vhg.cmp.uea.ac.uk/tech/jas/vhg2024c].

These are the main differences between this version and [[#CWASA_2024b_(2024-05)| CWASA 2024b]]:

* Accessing URLs now using the fetch interface
* Animgen processing by CGI script server reinstated: See [[Animgen Server]]
* Server using Node.js tool '''sigtool''' to convert h-SiGML to g-SiGML if requested

== CWASA 2024b (2024-05) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2024b/ vhg.cmp.uea.ac.uk/tech/jas/vhg2024b].

These are the main differences between this version and [[#CWASA_2024a_(2024-04)| CWASA 2024a]]:

* Offline transformation of h-SiGML to g-SiGML simplified using Node.js tool installed using npm
* Node.js software using Saxon for XSLT processing

== CWASA 2024a (2024-04) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2024a/ vhg.cmp.uea.ac.uk/tech/jas/vhg2024a].

The release should have the same features as the Legacy Release [[#CWASA_2023a_(2023-06)| CWASA 2023a]].

= CWASA 2023 =

== CWASA 2023 (Standard Version) ==

Open Release found at [//vhg.cmp.uea.ac.uk/tech/jas/vhg2023/ vhg.cmp.uea.ac.uk/tech/jas/vhg2023].

This release is based on the Legacy Release [[#CWASA_2022b_(2022-07)| CWASA 2022b]].

== CWASA 2023z (Development Version) ==

Development Release found at [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2023z/ vhg.cmp.uea.ac.uk/tech/jas/vhg2023z].

This release is based on the Legacy Release [[#CWASA_2023a_(2023-06)| CWASA 2023a]].

Users are encouraged to try the development release and report any issues encountered.

== CWASA 2023a (2023-06) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2023a/ vhg.cmp.uea.ac.uk/tech/jas/vhg2023a].

These are the main differences between this version and [[#CWASA_2022b_(2022-07)| CWASA 2022b]]:

* Electron apps now using better maintained framework using Electron and Vite
* Improved handling of Port 8052 for streamed SiGML data

= CWASA 2022 =

== CWASA 2022 (Standard Version) ==

Open Release found at [//vhg.cmp.uea.ac.uk/tech/jas/vhg2022/ vhg.cmp.uea.ac.uk/tech/jas/vhg2022].

This release is based on the Legacy Release [[#CWASA_2022a_(2022-01)| CWASA 2022a]].

== CWASA 2022z (Development Version) ==

Development Release found at [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2022z/ vhg.cmp.uea.ac.uk/tech/jas/vhg2022z].

This release is based on the Legacy Release [[#CWASA_2022b_(2022-07)| CWASA 2022b]].

Users are encouraged to try the development release and report any issues encountered.

== CWASA 2022b (2022-07) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2022b/ vhg.cmp.uea.ac.uk/tech/jas/vhg2022b].

These are the main differences between this version and [[#CWASA_2022a_(2022-01)| CWASA 2022a]]:

* C++ code for Animgen transpiled with a newer release of Emscripten
* Base directory for SiGML files for JWS apps now based on release installation
* Frame capture for video generation in JWS apps adapts to display resolution for Retina displays
* A new version of the video generation server is documented at [[JASigning Video Generator]]

== CWASA 2022a (2022-01) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2022a/ vhg.cmp.uea.ac.uk/tech/jas/vhg2022a].

This version is the same as [[#CWASA_2021f_(2021-12)| CWASA 2021f]].

= CWASA 2021 =

== CWASA 2021 (Standard Version) ==

Open Release found at [//vhg.cmp.uea.ac.uk/tech/jas/vhg2021/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021].

This release is based on the Legacy Release [[#CWASA_2021f_(2021-12)| CWASA 2021f]].

== CWASA 2021z (Development Version) ==

Development Release found at [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2021z/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021z].

This release is based on the Legacy Release [[#CWASA_2021f_(2021-12)| CWASA 2021f]].

Users are encouraged to try the development release and report any issues encountered.

== CWASA 2021f (2021-12) ==

Legacy Release found at [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2021f/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021f].

These are the main differences between this version and [[#CWASA_2021e_(2021-11)| CWASA 2021e]]:

* Recover from errors in URL specification for SiGML file URL
* Recover from errors in SiGML code from URL or text

== CWASA 2021e (2021-11) ==

Legacy Release found at [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2021e/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021e].

These are the main differences between this version and [[#CWASA_2021d_(2021-09)| CWASA 2021d]]:

* Using just https: URLs to support file: URLs for accessing the release
* Reports changes in camera settings that can later be used to change the initial camera setting
* Reports changes in signing speed that can later be used to change the initial speed setting
* See [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2021e/cwa/OneAvClientTest.html OneAvClientTest.html] for an example

== CWASA 2021d (2021-09) ==

Legacy Release found at [//vhg.cmp.uea.ac.uk/tech/jas/vhg2021d/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021d].

These are the main differences between this version and [[#CWASA_2021c_(2021-02)| CWASA 2021c]]:

* Employs protocol-relative URLs for HTTP and HTTPS support

The UEA server now supports just HTTPS. Older releases will mostly fail. We are, however, able to generate distributions using only HTTP or only HTTPS if required.

== CWASA 2021c (2021-02) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2021c/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021c].

These are the main differences between this version and [[#CWASA_2021b_(2021-01)| CWASA 2021b]]:

* New GUI element '''CWASAAmbBox''' to enable and disable ambient animation when an avatar is idle
* Configuration setting '''ambIdle''' providing default for ambient anumation

== CWASA 2021b (2021-01) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2021b/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021b].

These are the main differences between this version and [[#CWASA_2021a_(2021-01)| CWASA 2021a]]:

* Rearranged build process for Open, Legacy, and Development releases

== CWASA 2021a (2021-01) ==

Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2021a/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021a].

This version is the same as [[JASigning_Release_Notes#JASigning_2020c_(2020-11)|JASigning 2020c]].

= JASigning Release Notes =

See [[JASigning Release Notes]] for information on earlier legacy releases.

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

CWASA Release Notes

2026-04-04T14:21:03Z

John.Glauert: Intooduces vhg2026.

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

= CWA Signing Avatars Release Notes =

From 2021 the standard Open [[CWA Signing Avatars|CWASA]] release, found at
[http://vhg.cmp.uea.ac.uk/tech/jas/std/ http://vhg.cmp.uea.ac.uk/tech/jas/std/],
allows personal, public, and commercial use of the software when accessed, unmodified, from the UEA server. See [[CWASA Conditions of Use|Conditions of Use]].

These notes, and the notes for [[JASigning Release Notes|JASigning]], include Legacy releases with additional avatars and earlier deprecated [[JASigning]] resources. There is also a Development release containing components that cannot be guaranteed to be stable and should only be used for evaluation.

See [[CWA Signing Avatars|CWASA]] for other resources and documentation, including the [[CWASA Local Installation]], a version that can be installed on a localhost web server for evaluation.

Users are welcome to provide feedback via the [[JASigning Issue Reporting|Issue Reporting]] page. Documentation of the system is a work in progress so please send questions and comments to [mailto:cmp_virtualsigning@uea.ac.uk cmp_virtualsigning@uea.ac.uk] so that we can update these pages.

= Table of Contents =

__TOC__

= CWASA Release Notes =

All [[JASigning]] releases before 2021 are available only for evaluation and research, as for the current Legacy and Development releases. The Standard Version is an Open Release which will be based on a Legacy Release but omitting most deprecated software based on Java. The Development Version is a Development Release, potentially containing experimental features.

= CWASA 2026 =

== CWASA 2026 (Standard Version) ==

Open Release found at [//vhg.cmp.uea.ac.uk/tech/jas/vhg2026/ vhg.cmp.uea.ac.uk/tech/jas/vhg2026].

This release is based on the Legacy Release [[#CWASA_2025a_(2025-02)| CWASA 2025a]].

In modern browsers the appearance of the Anna avatar with fully closed eyes is rather dark.
This may have been true for some time and will be investigated when time permits.

== CWASA 2026z (Development Version) ==

Development Release found at [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2026z/ vhg.cmp.uea.ac.uk/tech/jas/vhg2026z].

This release is based on the Legacy Release [[#CWASA_2025a_(2025-02)| CWASA 2025a]].

In modern browsers the appearance of the Anna avatar with fully closed eyes is rather dark.
This may have been true for some time and will be investigated when time permits.

Users are encouraged to try the development release and report any issues encountered.

= CWASA 2025 =

== CWASA 2025 (Standard Version) ==

Open Release found at [//vhg.cmp.uea.ac.uk/tech/jas/vhg2025/ vhg.cmp.uea.ac.uk/tech/jas/vhg2025].

This release is based on the Legacy Release [[#CWASA_2025a_(2025-02)| CWASA 2025a]].

In modern browsers the appearance of the Anna avatar with fully closed eyes is rather dark.
This may have been true for some time and will be investigated when time permits.

== CWASA 2025z (Development Version) ==

Development Release found at [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2025z/ vhg.cmp.uea.ac.uk/tech/jas/vhg2025z].

This release is based on the Legacy Release [[#CWASA_2025a_(2025-02)| CWASA 2025a]].

In modern browsers the appearance of the Anna avatar with fully closed eyes is rather dark.
This may have been true for some time and will be investigated when time permits.

Users are encouraged to try the development release and report any issues encountered.

== CWASA 2025a (2025-02) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2025a/ vhg.cmp.uea.ac.uk/tech/jas/vhg2025a].

These are the main differences between this version and [[#CWASA_2024d_(2024-11)| CWASA 2024d]]:

* Index page has instructions on handling excessive quarantining for Apple Silicon apps.

= CWASA 2024 =

== CWASA 2024d (2024-11) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2024d/ vhg.cmp.uea.ac.uk/tech/jas/vhg2024d].

These are the main differences between this version and [[#CWASA_2024c_(2024-08)| CWASA 2024c]]:

* Animgen transpiled using current version of Emscripten
* Functionality should be unchanged.

== CWASA 2024c (2024-08) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2024c/ vhg.cmp.uea.ac.uk/tech/jas/vhg2024c].

These are the main differences between this version and [[#CWASA_2024b_(2024-05)| CWASA 2024b]]:

* Accessing URLs now using the fetch interface
* Animgen processing by CGI script server reinstated: See [[Animgen Server]]
* Server using Node.js tool '''sigtool''' to convert h-SiGML to g-SiGML if requested

== CWASA 2024b (2024-05) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2024b/ vhg.cmp.uea.ac.uk/tech/jas/vhg2024b].

These are the main differences between this version and [[#CWASA_2024a_(2024-04)| CWASA 2024a]]:

* Offline transformation of h-SiGML to g-SiGML simplified using Node.js tool installed using npm
* Node.js software using Saxon for XSLT processing

== CWASA 2024a (2024-04) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2024a/ vhg.cmp.uea.ac.uk/tech/jas/vhg2024a].

The release should have the same features as the Legacy Release [[#CWASA_2023a_(2023-06)| CWASA 2023a]].

= CWASA 2023 =

== CWASA 2023 (Standard Version) ==

Open Release found at [//vhg.cmp.uea.ac.uk/tech/jas/vhg2023/ vhg.cmp.uea.ac.uk/tech/jas/vhg2023].

This release is based on the Legacy Release [[#CWASA_2022b_(2022-07)| CWASA 2022b]].

== CWASA 2023z (Development Version) ==

Development Release found at [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2023z/ vhg.cmp.uea.ac.uk/tech/jas/vhg2023z].

This release is based on the Legacy Release [[#CWASA_2023a_(2023-06)| CWASA 2023a]].

Users are encouraged to try the development release and report any issues encountered.

== CWASA 2023a (2023-06) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2023a/ vhg.cmp.uea.ac.uk/tech/jas/vhg2023a].

These are the main differences between this version and [[#CWASA_2022b_(2022-07)| CWASA 2022b]]:

* Electron apps now using better maintained framework using Electron and Vite
* Improved handling of Port 8052 for streamed SiGML data

= CWASA 2022 =

== CWASA 2022 (Standard Version) ==

Open Release found at [//vhg.cmp.uea.ac.uk/tech/jas/vhg2022/ vhg.cmp.uea.ac.uk/tech/jas/vhg2022].

This release is based on the Legacy Release [[#CWASA_2022a_(2022-01)| CWASA 2022a]].

== CWASA 2022z (Development Version) ==

Development Release found at [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2022z/ vhg.cmp.uea.ac.uk/tech/jas/vhg2022z].

This release is based on the Legacy Release [[#CWASA_2022b_(2022-07)| CWASA 2022b]].

Users are encouraged to try the development release and report any issues encountered.

== CWASA 2022b (2022-07) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2022b/ vhg.cmp.uea.ac.uk/tech/jas/vhg2022b].

These are the main differences between this version and [[#CWASA_2022a_(2022-01)| CWASA 2022a]]:

* C++ code for Animgen transpiled with a newer release of Emscripten
* Base directory for SiGML files for JWS apps now based on release installation
* Frame capture for video generation in JWS apps adapts to display resolution for Retina displays
* A new version of the video generation server is documented at [[JASigning Video Generator]]

== CWASA 2022a (2022-01) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2022a/ vhg.cmp.uea.ac.uk/tech/jas/vhg2022a].

This version is the same as [[#CWASA_2021f_(2021-12)| CWASA 2021f]].

= CWASA 2021 =

== CWASA 2021 (Standard Version) ==

Open Release found at [//vhg.cmp.uea.ac.uk/tech/jas/vhg2021/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021].

This release is based on the Legacy Release [[#CWASA_2021f_(2021-12)| CWASA 2021f]].

== CWASA 2021z (Development Version) ==

Development Release found at [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2021z/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021z].

This release is based on the Legacy Release [[#CWASA_2021f_(2021-12)| CWASA 2021f]].

Users are encouraged to try the development release and report any issues encountered.

== CWASA 2021f (2021-12) ==

Legacy Release found at [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2021f/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021f].

These are the main differences between this version and [[#CWASA_2021e_(2021-11)| CWASA 2021e]]:

* Recover from errors in URL specification for SiGML file URL
* Recover from errors in SiGML code from URL or text

== CWASA 2021e (2021-11) ==

Legacy Release found at [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2021e/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021e].

These are the main differences between this version and [[#CWASA_2021d_(2021-09)| CWASA 2021d]]:

* Using just https: URLs to support file: URLs for accessing the release
* Reports changes in camera settings that can later be used to change the initial camera setting
* Reports changes in signing speed that can later be used to change the initial speed setting
* See [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2021e/cwa/OneAvClientTest.html OneAvClientTest.html] for an example

== CWASA 2021d (2021-09) ==

Legacy Release found at [//vhg.cmp.uea.ac.uk/tech/jas/vhg2021d/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021d].

These are the main differences between this version and [[#CWASA_2021c_(2021-02)| CWASA 2021c]]:

* Employs protocol-relative URLs for HTTP and HTTPS support

The UEA server now supports just HTTPS. Older releases will mostly fail. We are, however, able to generate distributions using only HTTP or only HTTPS if required.

== CWASA 2021c (2021-02) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2021c/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021c].

These are the main differences between this version and [[#CWASA_2021b_(2021-01)| CWASA 2021b]]:

* New GUI element '''CWASAAmbBox''' to enable and disable ambient animation when an avatar is idle
* Configuration setting '''ambIdle''' providing default for ambient anumation

== CWASA 2021b (2021-01) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2021b/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021b].

These are the main differences between this version and [[#CWASA_2021a_(2021-01)| CWASA 2021a]]:

* Rearranged build process for Open, Legacy, and Development releases

== CWASA 2021a (2021-01) ==

Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2021a/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021a].

This version is the same as [[JASigning_Release_Notes#JASigning_2020c_(2020-11)|JASigning 2020c]].

= JASigning Release Notes =

See [[JASigning Release Notes]] for information on earlier legacy releases.

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

JASigning Video Generator

2025-09-19T18:23:05Z

John.Glauert: macOS quarantine

'''The software described on this page is © UEA and is for evaluation use only. Please contact the Virtual Humans Group at UEA [mailto:VirtualSigning@cmp.uea.ac.uk VirtualSigning@cmp.uea.ac.uk] if you wish to use this facility for other purposes.'''
 
----
[[Main Page|Home]] >> [[JASigning]]
----

 
== Video Generation using JASigning ==

JASigning is able to generate a video of an animation using a video video generation server application. The server needs to be installed on the same computer system as the main JASigning application being used. Video files are generated as '''.mp4''' files in '''H.264''' format.

This page gives information on installing the Video Generation Server and explains how to use the SiGML Player application to create videos. As the JASigning SiGML Player is only available for macOS and Windows, videos cannot currently be generated on Linux.

An earlier system was based on the Xuggler package which is no longer supported. See [[Xuggler Video Generator]].

== Installing the Video Generation Server ==

* Ensure that you have a 64-bit Java installation: See Java Preferences app
* Download the [https://vhg.cmp.uea.ac.uk/tech/jas/vid/javacv-vg-server-1.0-assemble.zip Video Generator installation ZIP file]
* Unpack the ZIP file to a suitable location. It will be unpacked in a folder '''VideoGen'''
* On macOS see [[macOS Quarantine]] to release the VideoGen folder from quarantine
* If necessary configure the '''run-jas-video-gen-server''' script file for your platform to match the Java installation
* Use of Java has become very restricted. See [[JASigning Platform Issues]]

== Launching the Video Generation Server ==

* Use the '''run-jas-video-gen-server''' script file appropriate to the platform, Mac or Windows, to launch the server
* The server app should launch with a '''Test''' and '''Quit''' button
* '''Test''' runs a test client that uses the server to generate a video from frames held in the '''frames''' subfolder of the VideoGen folder
* '''Quit''' is used to terminate the server

== Using the SiGML Player to Generate Video Files ==

* Once the video generation server is running, a video of an animation can be generated using the Java Web Start SiGML Player app, accessible from https://vhg.cmp.uea.ac.uk/tech/jas/vhg2025a or a more recent Legacy Release found at [[CWASA Release Notes]]
* Use the SiGML Player's <code>File->Video Generation...</code> menu item to generate a video of the most recently played signing animation
* The SiGML Player accomplishes this by transmitting the animation's frame data to the video generation server, which produces the <code>.mp4</code> file
* The SiGML Player should refuse to attempt video generation if it is not feasible, e.g. when there is no current animation, or when the server is not running
* Some videos may be larger than expected due to high resolution displays such as Apple Retina displays

== Configuring the Video Server ==
* The <code>Log</code> checkbox can be used to provide more verbose logging of server operation
* The <code>Video</code> checkbox, selected by default, causes a movie to be generated in a specified location
* The <code>Frames</code> checkbox causes a folder to be created containing a set of <code>PNG</code> images for the frames sent to the server
* Frames are placed in a folder whose name is the same as the movie with ".frames" appended
* Files are created in XML and Java Properties formats recording settings sent to the server: movie name, width and height, frames per second, and frame count

== Adapting the Video Server ==
* The server uses JavaCV, a Java interface to FFmpeg, and has been built with Maven on NetBeans
* The VideoGen folder contains a NetBeans project containing sources and assembly information
* In order to support older macOS releases, such as High Sierra, older versions of JavaCV are used
* The Netbeans project should assemble a new installation ZIP file but may fail to run the server directly from NetBeans
 
----
[[Main Page|Home]] >> [[JASigning]]

CWASA Platform Issues

2025-09-19T18:15:14Z

John.Glauert: macOS Quarantine

[[Main Page|Home]] >> [[CWA Signing Avatars|CWASA]]
----
= Downloading Software =

==== macOS ====
Security measures in macOS make it increasingly hard to distribute software. See [[macOS Quarantine]].

= Core Software : JavaScript =

== Web Applications : HTML5 JavaScript and WebGL ==
The core [[CWA Signing Avatars|CWASA]] software uses JavaScript for HTML5 web pages using WebGL. It functions on macOS, Windows, Linux, iOS, and some Android devices. It may work on other platforms. Linux usage has been tested only on Ubuntu at present.

==== macOS ====
CWASA software should work with '''Firefox''', '''Chrome''', '''Opera''', and '''Safari'''.

==== Windows ====
CWASA software should work with '''Firefox''', '''Chrome''', '''Opera''', and '''Edge'''. <br/>It can also be used with '''Internet Explorer''', but using scripts transpiled for an earlier version of JavaScript.

==== Linux ====
CWASA software should work with '''Firefox''', '''Chrome''', '''Opera''', '''Chromium''', and '''Vivaldi'''.

==== iOS ====
CWASA software should work with '''Safari'''.

== Standalone Applications : Node.js and Electron ==
Applications based on the HTML5 JavaScript and WebGL implementation can be installed on macOS, Windows, and Linux. Linux usage has been tested only on Ubuntu. Experience of use on other versions of Linux would be welcomed.

In addition to being able to animate SiGML data provided as text or via a URL, the applications act as a server, receiving SiGML data from any host on port 8052. See [[Driving the SiGML Player App]] and [[SiGML Tools]] for tools and apps to communicate with the player.

==== macOS ====
The software is provided in a Disk Image via a '''.dmg''' file. The image should be mounted and the application copied to disk. Security preferences will prevent the application being opened immediately because they do not come from the App Store or an identified developer. See [[macOS Quarantine]] for information.

==== Windows ====
The software is provided as an executable '''.exe''' file that can be run to install and launch the software. A shortcut to the application will then be placed on the desktop.

==== Linux ====
The software is provided in an application image '''.AppImage''' file which is program that will install the software. The downloaded application image file must be made executable and then run. This may be done by right-clicking the file, selecting Properties, selecting the Permissions tab, and choosing to allow executing the file as program. Alternatively, the command <code>chmod +x SiGML-Player.AppImage</code> can be entered in a shell.

= Legacy Software : Java =

== Java Web Start ==

Legacy [[JASigning]] applications and applets are launched using [http://en.wikipedia.org/wiki/Java_Web_Start Java Web Start] through Java Network Launching Protocol (JNLP) files. The use of JNLP files for applets is deprecated in modern browsers so the software can only be used in exceptional circumstances. See [[JASigning Platform Issues]] for further details.

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

MacOS Quarantine

2025-09-19T18:08:08Z

John.Glauert:

= macOS Quarantine =
Files downloaded by macOS are tagged with an extended attribute <code>com.apple.quarantine</code> which will block applications from being launched.

On earlier macOS versions it was possible to use a right-click to bring up a dialogue that could bypass the quarantine.

Later version of macOS simply block access when the attribute is present.

This attribute can be removed by launching '''Terminal''' and entering the command
xattr -dr com.apple.quarantine file
This will remove the attribute from a file, or application, or all contents of a directory. Access will then be permitted unhindered.

MacOS Quarantine

2025-09-19T18:07:12Z

John.Glauert: Using xattr to remove quarantine restrictions

= macOS Quarantine =
Files downloaded by macOS are tagged with an extended attribute <code>com.apple.quarantine</code> which will block applications from being launched.

On earlier macOS versions it was possible to use a right-click to bring up a dialogue that could bypass the quarantine.

Later version of macOS simply block access when the attribute is present.

This attribute can be removed by launching '''Terminal''' end entering the command
xattr -dr com.apple.quarantine file
This will remove the attribute from a file, or application, or all contents of a directory. Access will then be permitted unhindered.

JASigning Platform Issues

2025-09-19T18:01:20Z

John.Glauert: macOS Quarantine

[[Main Page|Home]] >> [[JASigning]]
----

= Core Software : JavaScript =

== CWA Signing Avatars ==
The core [[CWA Signing Avatars]] software is implemented in JavaScript for HTML5 web pages using WebGL. It functions on most platforms: Windows, macOS, Linux, and smart phones and tablets. See [[CWASA Platform Issues]] for details.

= Legacy Software : Java =

A 64bit Java Runtime Environment (JRE) must be installed. In the Security settings of the Java Control Panel you may need to add https://vhg.cmp.uea.ac.uk to the Exception Site List.

The software is supported on Windows and macOS, but not Linux.

==== macOS ====

Security measures in macOS make it increasingly hard to distribute software. See [[macOS Quarantine]]

== Java Web Start ==

JASigning applications and applets are launched using [https://en.wikipedia.org/wiki/Java_Web_Start Java Web Start] through Java Network Launching Protocol (JNLP) files, which have extension <code>.jnlp</code>. Web pages using the more recent JASigning implementation for HTML5 using JavaScript and WebGL is not dependent on JNLP.

The use of JNLP files for applets is deprecated in modern browsers. Where it is supported, it is fairly seamless, but changes to the Java security regime mean that some messages will be seen for the latest release of JASigning with older Java versions.

For applications, launching of Java Web Start is sometimes automatic, but sometimes requires further action. Apple makes it increasingly difficult to deploy components using JNLP so for recent versions of macOS it is necessary to override the default protection regime even though the components are correctly signed. See below for notes on using particular browsers.

== Code Signing ==

JASigning components are digitally signed using a Code Signing Certificate issues by [https://www.globalsign.com/code-signing/ GlobalSign] to [https://www.uea.ac.uk/business/consultancy UEA Consulting Ltd]. Before 2014, certificates were issued to [http://www.sys-consulting.co.uk/ SYS Consulting Limited]. When installing applications or applets, users will be asked to confirm that they trust the publisher. Users can choose to trust the publisher permanently to avoid future confirmation requests.

The certificates have a limited lifetime and have now expired. Unfortunately, it is therefore necessary to ignore security warnings to use the software. Components can still be used if https://vhg.cmp.uea.ac.uk is added to the Exception Site List via the Security tab on the Java control panel.

== Legacy Standalone Applications : Java ==
The security constraints on running Java-based applications mean that the [[CWA Signing Avatars]] applications are strongly preferred. At present, however, some functionality is only available in the Java software.

Java-based applications for the [https://vhg.cmp.uea.ac.uk/tech/jas/std/ current version of JASigning] are intended to run on Windows (XP, Vista, 7, 10) and on the latest releases of macOS 10.5 and later. Java-based JASigning apps are ''not'' supported on Linux. It is preferable to run JASigning with an up-to-date Java 8 run-time (JRE), although it should run with Java 7 and later versions of Java 6.

On the supported platforms, that is, Windows and macOS, JASigning supports both 32-bit and 64-bit operation. Which of this modes it actually runs in on any given occasion depends on several factors:

* Whether or not the processor supports 64-bit operation.
* Whether or not the operating system supports 64-bit operation.
* Whether the system has a 32-bit or a 64-bit Java installation (or both) -- and what options are set in the Java Control Panel (Windows) or Java Preferences app (macOS).
* For a JASigning applet: whether the browser is running in 32-bit or 64-bit mode.

==== Windows ====
[[JASigning|Home]] applications and applets
(apart from the SiGML Service Client) on Windows may require the appropriate
<em>Microsoft Visual Studio C++ 2010 Redistributable Package</em>
to be installed on the system.

On many Windows systems the required Redistributable package will already
have been installed.
But if not, each JASigning application and applet will display a message
at launch time giving the URLs from which the package can easily be
downloaded and installed.
These URLs can be copied from the Java console and pasted into
a web browser.

There is a 32-bit ([https://www.microsoft.com/en-us/download/details.aspx?id=5555 x86]) and a 64-bit ([https://www.microsoft.com/en-us/download/details.aspx?id=14632 x64])
version of the Redistributable package.
One or both of these should be installed, to match the system's
JRE (Java Runtime Environment) installation(s).

==== macOS ====

Before installing and running JASigning applications, the corresponding JNLP file must be downloaded. The application is then launched using Java Web Start. The user will be warned that the application (its JNLP file) has been downloaded from the Internet. The user will also be asked to confirm that they trust the publisher.

Under the default settings for GateKeeper on macOS 10.7.5 Lion and onwards, JASigning applications are blocked from running because they do not come from the App Store or an identified developer. To run blocked applications it is necessary to locate the JNLP file, typically in the Downloads folder, and open it by double-clicking with the control-key down or by right-clicking and choosing ''Open''. On some versions, GateKeeper can be disabled using the General tab of Security & Privacy in the System Preferences.

As documented in [[JASigning Release Notes]], on macOS 10.6 Snow Leopard and later some rendering artefacts can appear with the freestanding SiGML URL Player and SiGML Service Player.

== Legacy Web Applications : Java Applets ==
Support for Java Applets is now minimal and the HTML5 approach should be used wherever possible.

JASigning applets may work with browsers other than those mentioned below, but our testing in such cases is at best limited. Let us know!

==== Windows ====
JASigning web applets should work with '''Internet Explorer'''. The 32-bit (x86) release of Java should be installed.

==== macOS ====
JASigning web applets should work with '''Safari'''.

'''Safari''' will block applets by default but clicking on the avatar display area will allow the applet plug-in to be enabled. '''Safari 7''' and later impose a ''safe'' mode which blocks access to the local disk even though requested by the Java security settings. JASigning will operate in safe mode but will operate more slowly and will not work so well offline as a local cache will be disabled. The Safari Security preferences can be used to disable safe mode for JASigning applets, allowing the local cache to be used.

If GateKeeper is active, launching of applications will be blocked. See the Platforms section above. Even if GateKeeper is disabled: Safari does not consider Java Web Start to be safe so JNLP files may be downloaded to a temporary area and can only be launched by clicking on the icon for the downloaded file in the Downloads window; JNLP files for applications can be downloaded and launched from '''Chrome''' but a warning suggests that JNLP files can be harmful.

----
[[Main Page]] >> [[JASigning]]

JASigning Platform Issues

2025-09-19T17:47:39Z

John.Glauert: /* CWA Signing Avatars */

[[Main Page|Home]] >> [[JASigning]]
----

= Core Software : JavaScript =

== CWA Signing Avatars ==
The core [[CWA Signing Avatars]] software is implemented in JavaScript for HTML5 web pages using WebGL. It functions on most platforms: Windows, macOS, Linux, and smart phones and tablets. See [[CWASA Platform Issues]] for details.

= Legacy Software : Java =

A 64bit Java Runtime Environment (JRE) must be installed. In the Security settings of the Java Control Panel you may need to add https://vhg.cmp.uea.ac.uk to the Exception Site List.

The software is supported on Windows and macOS, but not Linux.

== Java Web Start ==

JASigning applications and applets are launched using [https://en.wikipedia.org/wiki/Java_Web_Start Java Web Start] through Java Network Launching Protocol (JNLP) files, which have extension <code>.jnlp</code>. Web pages using the more recent JASigning implementation for HTML5 using JavaScript and WebGL is not dependent on JNLP.

The use of JNLP files for applets is deprecated in modern browsers. Where it is supported, it is fairly seamless, but changes to the Java security regime mean that some messages will be seen for the latest release of JASigning with older Java versions.

For applications, launching of Java Web Start is sometimes automatic, but sometimes requires further action. Apple makes it increasingly difficult to deploy components using JNLP so for recent versions of macOS it is necessary to override the default protection regime even though the components are correctly signed. See below for notes on using particular browsers.

== Code Signing ==

JASigning components are digitally signed using a Code Signing Certificate issues by [https://www.globalsign.com/code-signing/ GlobalSign] to [https://www.uea.ac.uk/business/consultancy UEA Consulting Ltd]. Before 2014, certificates were issued to [http://www.sys-consulting.co.uk/ SYS Consulting Limited]. When installing applications or applets, users will be asked to confirm that they trust the publisher. Users can choose to trust the publisher permanently to avoid future confirmation requests.

The certificates have a limited lifetime and have now expired. Unfortunately, it is therefore necessary to ignore security warnings to use the software. Components can still be used if https://vhg.cmp.uea.ac.uk is added to the Exception Site List via the Security tab on the Java control panel.

== Legacy Standalone Applications : Java ==
The security constraints on running Java-based applications mean that the [[CWA Signing Avatars]] applications are strongly preferred. At present, however, some functionality is only available in the Java software.

Java-based applications for the [https://vhg.cmp.uea.ac.uk/tech/jas/std/ current version of JASigning] are intended to run on Windows (XP, Vista, 7, 10) and on the latest releases of macOS 10.5 and later. Java-based JASigning apps are ''not'' supported on Linux. It is preferable to run JASigning with an up-to-date Java 8 run-time (JRE), although it should run with Java 7 and later versions of Java 6.

On the supported platforms, that is, Windows and macOS, JASigning supports both 32-bit and 64-bit operation. Which of this modes it actually runs in on any given occasion depends on several factors:

* Whether or not the processor supports 64-bit operation.
* Whether or not the operating system supports 64-bit operation.
* Whether the system has a 32-bit or a 64-bit Java installation (or both) -- and what options are set in the Java Control Panel (Windows) or Java Preferences app (macOS).
* For a JASigning applet: whether the browser is running in 32-bit or 64-bit mode.

==== Windows ====
[[JASigning|Home]] applications and applets
(apart from the SiGML Service Client) on Windows may require the appropriate
<em>Microsoft Visual Studio C++ 2010 Redistributable Package</em>
to be installed on the system.

On many Windows systems the required Redistributable package will already
have been installed.
But if not, each JASigning application and applet will display a message
at launch time giving the URLs from which the package can easily be
downloaded and installed.
These URLs can be copied from the Java console and pasted into
a web browser.

There is a 32-bit ([https://www.microsoft.com/en-us/download/details.aspx?id=5555 x86]) and a 64-bit ([https://www.microsoft.com/en-us/download/details.aspx?id=14632 x64])
version of the Redistributable package.
One or both of these should be installed, to match the system's
JRE (Java Runtime Environment) installation(s).

==== macOS ====

Before installing and running JASigning applications, the corresponding JNLP file must be downloaded. The application is then launched using Java Web Start. The user will be warned that the application (its JNLP file) has been downloaded from the Internet. The user will also be asked to confirm that they trust the publisher.

Under the default settings for GateKeeper on macOS 10.7.5 Lion and onwards, JASigning applications are blocked from running because they do not come from the App Store or an identified developer. To run blocked applications it is necessary to locate the JNLP file, typically in the Downloads folder, and open it by double-clicking with the control-key down or by right-clicking and choosing ''Open''. On some versions, GateKeeper can be disabled using the General tab of Security & Privacy in the System Preferences.

As documented in [[JASigning Release Notes]], on macOS 10.6 Snow Leopard and later some rendering artefacts can appear with the freestanding SiGML URL Player and SiGML Service Player.

== Legacy Web Applications : Java Applets ==
Support for Java Applets is now minimal and the HTML5 approach should be used wherever possible.

JASigning applets may work with browsers other than those mentioned below, but our testing in such cases is at best limited. Let us know!

==== Windows ====
JASigning web applets should work with '''Internet Explorer'''. The 32-bit (x86) release of Java should be installed.

==== macOS ====
JASigning web applets should work with '''Safari'''.

'''Safari''' will block applets by default but clicking on the avatar display area will allow the applet plug-in to be enabled. '''Safari 7''' and later impose a ''safe'' mode which blocks access to the local disk even though requested by the Java security settings. JASigning will operate in safe mode but will operate more slowly and will not work so well offline as a local cache will be disabled. The Safari Security preferences can be used to disable safe mode for JASigning applets, allowing the local cache to be used.

If GateKeeper is active, launching of applications will be blocked. See the Platforms section above. Even if GateKeeper is disabled: Safari does not consider Java Web Start to be safe so JNLP files may be downloaded to a temporary area and can only be launched by clicking on the icon for the downloaded file in the Downloads window; JNLP files for applications can be downloaded and launched from '''Chrome''' but a warning suggests that JNLP files can be harmful.

----
[[Main Page]] >> [[JASigning]]

JASigning Platform Issues

2025-09-19T17:46:45Z

John.Glauert: /* Legacy Software : Java */

[[Main Page|Home]] >> [[JASigning]]
----

= Core Software : JavaScript =

== CWA Signing Avatars ==
The core [[CWA Signing Avatars]] software is implemented in JavaScript for HTML5 web pages using WebGL. It functions on most platforms. See [[CWASA Platform Issues]] for details.

= Legacy Software : Java =

A 64bit Java Runtime Environment (JRE) must be installed. In the Security settings of the Java Control Panel you may need to add https://vhg.cmp.uea.ac.uk to the Exception Site List.

The software is supported on Windows and macOS, but not Linux.

== Java Web Start ==

JASigning applications and applets are launched using [https://en.wikipedia.org/wiki/Java_Web_Start Java Web Start] through Java Network Launching Protocol (JNLP) files, which have extension <code>.jnlp</code>. Web pages using the more recent JASigning implementation for HTML5 using JavaScript and WebGL is not dependent on JNLP.

The use of JNLP files for applets is deprecated in modern browsers. Where it is supported, it is fairly seamless, but changes to the Java security regime mean that some messages will be seen for the latest release of JASigning with older Java versions.

For applications, launching of Java Web Start is sometimes automatic, but sometimes requires further action. Apple makes it increasingly difficult to deploy components using JNLP so for recent versions of macOS it is necessary to override the default protection regime even though the components are correctly signed. See below for notes on using particular browsers.

== Code Signing ==

JASigning components are digitally signed using a Code Signing Certificate issues by [https://www.globalsign.com/code-signing/ GlobalSign] to [https://www.uea.ac.uk/business/consultancy UEA Consulting Ltd]. Before 2014, certificates were issued to [http://www.sys-consulting.co.uk/ SYS Consulting Limited]. When installing applications or applets, users will be asked to confirm that they trust the publisher. Users can choose to trust the publisher permanently to avoid future confirmation requests.

The certificates have a limited lifetime and have now expired. Unfortunately, it is therefore necessary to ignore security warnings to use the software. Components can still be used if https://vhg.cmp.uea.ac.uk is added to the Exception Site List via the Security tab on the Java control panel.

== Legacy Standalone Applications : Java ==
The security constraints on running Java-based applications mean that the [[CWA Signing Avatars]] applications are strongly preferred. At present, however, some functionality is only available in the Java software.

Java-based applications for the [https://vhg.cmp.uea.ac.uk/tech/jas/std/ current version of JASigning] are intended to run on Windows (XP, Vista, 7, 10) and on the latest releases of macOS 10.5 and later. Java-based JASigning apps are ''not'' supported on Linux. It is preferable to run JASigning with an up-to-date Java 8 run-time (JRE), although it should run with Java 7 and later versions of Java 6.

On the supported platforms, that is, Windows and macOS, JASigning supports both 32-bit and 64-bit operation. Which of this modes it actually runs in on any given occasion depends on several factors:

* Whether or not the processor supports 64-bit operation.
* Whether or not the operating system supports 64-bit operation.
* Whether the system has a 32-bit or a 64-bit Java installation (or both) -- and what options are set in the Java Control Panel (Windows) or Java Preferences app (macOS).
* For a JASigning applet: whether the browser is running in 32-bit or 64-bit mode.

==== Windows ====
[[JASigning|Home]] applications and applets
(apart from the SiGML Service Client) on Windows may require the appropriate
<em>Microsoft Visual Studio C++ 2010 Redistributable Package</em>
to be installed on the system.

On many Windows systems the required Redistributable package will already
have been installed.
But if not, each JASigning application and applet will display a message
at launch time giving the URLs from which the package can easily be
downloaded and installed.
These URLs can be copied from the Java console and pasted into
a web browser.

There is a 32-bit ([https://www.microsoft.com/en-us/download/details.aspx?id=5555 x86]) and a 64-bit ([https://www.microsoft.com/en-us/download/details.aspx?id=14632 x64])
version of the Redistributable package.
One or both of these should be installed, to match the system's
JRE (Java Runtime Environment) installation(s).

==== macOS ====

Before installing and running JASigning applications, the corresponding JNLP file must be downloaded. The application is then launched using Java Web Start. The user will be warned that the application (its JNLP file) has been downloaded from the Internet. The user will also be asked to confirm that they trust the publisher.

Under the default settings for GateKeeper on macOS 10.7.5 Lion and onwards, JASigning applications are blocked from running because they do not come from the App Store or an identified developer. To run blocked applications it is necessary to locate the JNLP file, typically in the Downloads folder, and open it by double-clicking with the control-key down or by right-clicking and choosing ''Open''. On some versions, GateKeeper can be disabled using the General tab of Security & Privacy in the System Preferences.

As documented in [[JASigning Release Notes]], on macOS 10.6 Snow Leopard and later some rendering artefacts can appear with the freestanding SiGML URL Player and SiGML Service Player.

== Legacy Web Applications : Java Applets ==
Support for Java Applets is now minimal and the HTML5 approach should be used wherever possible.

JASigning applets may work with browsers other than those mentioned below, but our testing in such cases is at best limited. Let us know!

==== Windows ====
JASigning web applets should work with '''Internet Explorer'''. The 32-bit (x86) release of Java should be installed.

==== macOS ====
JASigning web applets should work with '''Safari'''.

'''Safari''' will block applets by default but clicking on the avatar display area will allow the applet plug-in to be enabled. '''Safari 7''' and later impose a ''safe'' mode which blocks access to the local disk even though requested by the Java security settings. JASigning will operate in safe mode but will operate more slowly and will not work so well offline as a local cache will be disabled. The Safari Security preferences can be used to disable safe mode for JASigning applets, allowing the local cache to be used.

If GateKeeper is active, launching of applications will be blocked. See the Platforms section above. Even if GateKeeper is disabled: Safari does not consider Java Web Start to be safe so JNLP files may be downloaded to a temporary area and can only be launched by clicking on the icon for the downloaded file in the Downloads window; JNLP files for applications can be downloaded and launched from '''Chrome''' but a warning suggests that JNLP files can be harmful.

----
[[Main Page]] >> [[JASigning]]

JASigning Platform Issues

2025-09-19T17:42:55Z

John.Glauert: Use macOS for Mac OS X

[[Main Page|Home]] >> [[JASigning]]
----

= Core Software : JavaScript =

== CWA Signing Avatars ==
The core [[CWA Signing Avatars]] software is implemented in JavaScript for HTML5 web pages using WebGL. It functions on most platforms. See [[CWASA Platform Issues]] for details.

= Legacy Software : Java =

A Java Runtime Environment (JRE) must be installed. In the Security settings of the Java Control Panel you may need to add https://vhg.cmp.uea.ac.uk to the Exception Site List.

== Java Web Start ==

JASigning applications and applets are launched using [https://en.wikipedia.org/wiki/Java_Web_Start Java Web Start] through Java Network Launching Protocol (JNLP) files, which have extension <code>.jnlp</code>. Web pages using the more recent JASigning implementation for HTML5 using JavaScript and WebGL is not dependent on JNLP.

The use of JNLP files for applets is deprecated in modern browsers. Where it is supported, it is fairly seamless, but changes to the Java security regime mean that some messages will be seen for the latest release of JASigning with older Java versions.

For applications, launching of Java Web Start is sometimes automatic, but sometimes requires further action. Apple makes it increasingly difficult to deploy components using JNLP so for recent versions of macOS it is necessary to override the default protection regime even though the components are correctly signed. See below for notes on using particular browsers.

== Code Signing ==

JASigning components are digitally signed using a Code Signing Certificate issues by [https://www.globalsign.com/code-signing/ GlobalSign] to [https://www.uea.ac.uk/business/consultancy UEA Consulting Ltd]. Before 2014, certificates were issued to [http://www.sys-consulting.co.uk/ SYS Consulting Limited]. When installing applications or applets, users will be asked to confirm that they trust the publisher. Users can choose to trust the publisher permanently to avoid future confirmation requests.

The certificates have a limited lifetime and have now expired. Unfortunately, it is therefore necessary to ignore security warnings to use the software. Components can still be used if https://vhg.cmp.uea.ac.uk is added to the Exception Site List via the Security tab on the Java control panel.

== Legacy Standalone Applications : Java ==
The security constraints on running Java-based applications mean that the [[CWA Signing Avatars]] applications are strongly preferred. At present, however, some functionality is only available in the Java software.

Java-based applications for the [https://vhg.cmp.uea.ac.uk/tech/jas/std/ current version of JASigning] are intended to run on Windows (XP, Vista, 7, 10) and on the latest releases of macOS 10.5 and later. Java-based JASigning apps are ''not'' supported on Linux. It is preferable to run JASigning with an up-to-date Java 8 run-time (JRE), although it should run with Java 7 and later versions of Java 6.

On the supported platforms, that is, Windows and macOS, JASigning supports both 32-bit and 64-bit operation. Which of this modes it actually runs in on any given occasion depends on several factors:

* Whether or not the processor supports 64-bit operation.
* Whether or not the operating system supports 64-bit operation.
* Whether the system has a 32-bit or a 64-bit Java installation (or both) -- and what options are set in the Java Control Panel (Windows) or Java Preferences app (macOS).
* For a JASigning applet: whether the browser is running in 32-bit or 64-bit mode.

==== Windows ====
[[JASigning|Home]] applications and applets
(apart from the SiGML Service Client) on Windows may require the appropriate
<em>Microsoft Visual Studio C++ 2010 Redistributable Package</em>
to be installed on the system.

On many Windows systems the required Redistributable package will already
have been installed.
But if not, each JASigning application and applet will display a message
at launch time giving the URLs from which the package can easily be
downloaded and installed.
These URLs can be copied from the Java console and pasted into
a web browser.

There is a 32-bit ([https://www.microsoft.com/en-us/download/details.aspx?id=5555 x86]) and a 64-bit ([https://www.microsoft.com/en-us/download/details.aspx?id=14632 x64])
version of the Redistributable package.
One or both of these should be installed, to match the system's
JRE (Java Runtime Environment) installation(s).

==== macOS ====

Before installing and running JASigning applications, the corresponding JNLP file must be downloaded. The application is then launched using Java Web Start. The user will be warned that the application (its JNLP file) has been downloaded from the Internet. The user will also be asked to confirm that they trust the publisher.

Under the default settings for GateKeeper on macOS 10.7.5 Lion and onwards, JASigning applications are blocked from running because they do not come from the App Store or an identified developer. To run blocked applications it is necessary to locate the JNLP file, typically in the Downloads folder, and open it by double-clicking with the control-key down or by right-clicking and choosing ''Open''. On some versions, GateKeeper can be disabled using the General tab of Security & Privacy in the System Preferences.

As documented in [[JASigning Release Notes]], on macOS 10.6 Snow Leopard and later some rendering artefacts can appear with the freestanding SiGML URL Player and SiGML Service Player.

== Legacy Web Applications : Java Applets ==
Support for Java Applets is now minimal and the HTML5 approach should be used wherever possible.

JASigning applets may work with browsers other than those mentioned below, but our testing in such cases is at best limited. Let us know!

==== Windows ====
JASigning web applets should work with '''Internet Explorer'''. The 32-bit (x86) release of Java should be installed.

==== macOS ====
JASigning web applets should work with '''Safari'''.

'''Safari''' will block applets by default but clicking on the avatar display area will allow the applet plug-in to be enabled. '''Safari 7''' and later impose a ''safe'' mode which blocks access to the local disk even though requested by the Java security settings. JASigning will operate in safe mode but will operate more slowly and will not work so well offline as a local cache will be disabled. The Safari Security preferences can be used to disable safe mode for JASigning applets, allowing the local cache to be used.

If GateKeeper is active, launching of applications will be blocked. See the Platforms section above. Even if GateKeeper is disabled: Safari does not consider Java Web Start to be safe so JNLP files may be downloaded to a temporary area and can only be launched by clicking on the icon for the downloaded file in the Downloads window; JNLP files for applications can be downloaded and launched from '''Chrome''' but a warning suggests that JNLP files can be harmful.

----
[[Main Page]] >> [[JASigning]]

CWASA Release Notes

2025-02-12T15:05:33Z

John.Glauert: Introduces vhg2025a

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

= CWA Signing Avatars Release Notes =

From 2021 the standard Open [[CWA Signing Avatars|CWASA]] release, found at
[http://vhg.cmp.uea.ac.uk/tech/jas/std/ http://vhg.cmp.uea.ac.uk/tech/jas/std/],
allows personal, public, and commercial use of the software when accessed, unmodified, from the UEA server. See [[CWASA Conditions of Use|Conditions of Use]].

These notes, and the notes for [[JASigning Release Notes|JASigning]], include Legacy releases with additional avatars and earlier deprecated [[JASigning]] resources. There is also a Development release containing components that cannot be guaranteed to be stable and should only be used for evaluation.

See [[CWA Signing Avatars|CWASA]] for other resources and documentation, including the [[CWASA Local Installation]], a version that can be installed on a localhost web server for evaluation.

Users are welcome to provide feedback via the [[JASigning Issue Reporting|Issue Reporting]] page. Documentation of the system is a work in progress so please send questions and comments to [mailto:cmp_virtualsigning@uea.ac.uk cmp_virtualsigning@uea.ac.uk] so that we can update these pages.

= Table of Contents =

__TOC__

= CWASA Release Notes =

All [[JASigning]] releases before 2021 are available only for evaluation and research, as for the current Legacy and Development releases. The Standard Version is an Open Release which will be based on a Legacy Release but omitting most deprecated software based on Java. The Development Version is a Development Release, potentially containing experimental features.

= CWASA 2025 =

== CWASA 2025 (Standard Version) ==

Open Release found at [//vhg.cmp.uea.ac.uk/tech/jas/vhg2025/ vhg.cmp.uea.ac.uk/tech/jas/vhg2025].

This release is based on the Legacy Release [[#CWASA_2025a_(2025-02)| CWASA 2025a]].

In modern browsers the appearance of the Anna avatar with fully closed eyes is rather dark.
This may have been true for some time and will be investigated when time permits.

== CWASA 2025z (Development Version) ==

Development Release found at [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2025z/ vhg.cmp.uea.ac.uk/tech/jas/vhg2025z].

This release is based on the Legacy Release [[#CWASA_2025a_(2025-02)| CWASA 2025a]].

In modern browsers the appearance of the Anna avatar with fully closed eyes is rather dark.
This may have been true for some time and will be investigated when time permits.

Users are encouraged to try the development release and report any issues encountered.

== CWASA 2025a (2025-02) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2025a/ vhg.cmp.uea.ac.uk/tech/jas/vhg2025a].

These are the main differences between this version and [[#CWASA_2024d_(2024-11)| CWASA 2024d]]:

* Index page has instructions on handling excessive quarantining for Apple Silicon apps.

= CWASA 2024 =

== CWASA 2024d (2024-11) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2024d/ vhg.cmp.uea.ac.uk/tech/jas/vhg2024d].

These are the main differences between this version and [[#CWASA_2024c_(2024-08)| CWASA 2024c]]:

* Animgen transpiled using current version of Emscripten
* Functionality should be unchanged.

== CWASA 2024c (2024-08) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2024c/ vhg.cmp.uea.ac.uk/tech/jas/vhg2024c].

These are the main differences between this version and [[#CWASA_2024b_(2024-05)| CWASA 2024b]]:

* Accessing URLs now using the fetch interface
* Animgen processing by CGI script server reinstated: See [[Animgen Server]]
* Server using Node.js tool '''sigtool''' to convert h-SiGML to g-SiGML if requested

== CWASA 2024b (2024-05) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2024b/ vhg.cmp.uea.ac.uk/tech/jas/vhg2024b].

These are the main differences between this version and [[#CWASA_2024a_(2024-04)| CWASA 2024a]]:

* Offline transformation of h-SiGML to g-SiGML simplified using Node.js tool installed using npm
* Node.js software using Saxon for XSLT processing

== CWASA 2024a (2024-04) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2024a/ vhg.cmp.uea.ac.uk/tech/jas/vhg2024a].

The release should have the same features as the Legacy Release [[#CWASA_2023a_(2023-06)| CWASA 2023a]].

= CWASA 2023 =

== CWASA 2023 (Standard Version) ==

Open Release found at [//vhg.cmp.uea.ac.uk/tech/jas/vhg2023/ vhg.cmp.uea.ac.uk/tech/jas/vhg2023].

This release is based on the Legacy Release [[#CWASA_2022b_(2022-07)| CWASA 2022b]].

== CWASA 2023z (Development Version) ==

Development Release found at [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2023z/ vhg.cmp.uea.ac.uk/tech/jas/vhg2023z].

This release is based on the Legacy Release [[#CWASA_2023a_(2023-06)| CWASA 2023a]].

Users are encouraged to try the development release and report any issues encountered.

== CWASA 2023a (2023-06) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2023a/ vhg.cmp.uea.ac.uk/tech/jas/vhg2023a].

These are the main differences between this version and [[#CWASA_2022b_(2022-07)| CWASA 2022b]]:

* Electron apps now using better maintained framework using Electron and Vite
* Improved handling of Port 8052 for streamed SiGML data

= CWASA 2022 =

== CWASA 2022 (Standard Version) ==

Open Release found at [//vhg.cmp.uea.ac.uk/tech/jas/vhg2022/ vhg.cmp.uea.ac.uk/tech/jas/vhg2022].

This release is based on the Legacy Release [[#CWASA_2022a_(2022-01)| CWASA 2022a]].

== CWASA 2022z (Development Version) ==

Development Release found at [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2022z/ vhg.cmp.uea.ac.uk/tech/jas/vhg2022z].

This release is based on the Legacy Release [[#CWASA_2022b_(2022-07)| CWASA 2022b]].

Users are encouraged to try the development release and report any issues encountered.

== CWASA 2022b (2022-07) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2022b/ vhg.cmp.uea.ac.uk/tech/jas/vhg2022b].

These are the main differences between this version and [[#CWASA_2022a_(2022-01)| CWASA 2022a]]:

* C++ code for Animgen transpiled with a newer release of Emscripten
* Base directory for SiGML files for JWS apps now based on release installation
* Frame capture for video generation in JWS apps adapts to display resolution for Retina displays
* A new version of the video generation server is documented at [[JASigning Video Generator]]

== CWASA 2022a (2022-01) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2022a/ vhg.cmp.uea.ac.uk/tech/jas/vhg2022a].

This version is the same as [[#CWASA_2021f_(2021-12)| CWASA 2021f]].

= CWASA 2021 =

== CWASA 2021 (Standard Version) ==

Open Release found at [//vhg.cmp.uea.ac.uk/tech/jas/vhg2021/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021].

This release is based on the Legacy Release [[#CWASA_2021f_(2021-12)| CWASA 2021f]].

== CWASA 2021z (Development Version) ==

Development Release found at [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2021z/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021z].

This release is based on the Legacy Release [[#CWASA_2021f_(2021-12)| CWASA 2021f]].

Users are encouraged to try the development release and report any issues encountered.

== CWASA 2021f (2021-12) ==

Legacy Release found at [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2021f/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021f].

These are the main differences between this version and [[#CWASA_2021e_(2021-11)| CWASA 2021e]]:

* Recover from errors in URL specification for SiGML file URL
* Recover from errors in SiGML code from URL or text

== CWASA 2021e (2021-11) ==

Legacy Release found at [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2021e/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021e].

These are the main differences between this version and [[#CWASA_2021d_(2021-09)| CWASA 2021d]]:

* Using just https: URLs to support file: URLs for accessing the release
* Reports changes in camera settings that can later be used to change the initial camera setting
* Reports changes in signing speed that can later be used to change the initial speed setting
* See [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2021e/cwa/OneAvClientTest.html OneAvClientTest.html] for an example

== CWASA 2021d (2021-09) ==

Legacy Release found at [//vhg.cmp.uea.ac.uk/tech/jas/vhg2021d/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021d].

These are the main differences between this version and [[#CWASA_2021c_(2021-02)| CWASA 2021c]]:

* Employs protocol-relative URLs for HTTP and HTTPS support

The UEA server now supports just HTTPS. Older releases will mostly fail. We are, however, able to generate distributions using only HTTP or only HTTPS if required.

== CWASA 2021c (2021-02) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2021c/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021c].

These are the main differences between this version and [[#CWASA_2021b_(2021-01)| CWASA 2021b]]:

* New GUI element '''CWASAAmbBox''' to enable and disable ambient animation when an avatar is idle
* Configuration setting '''ambIdle''' providing default for ambient anumation

== CWASA 2021b (2021-01) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2021b/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021b].

These are the main differences between this version and [[#CWASA_2021a_(2021-01)| CWASA 2021a]]:

* Rearranged build process for Open, Legacy, and Development releases

== CWASA 2021a (2021-01) ==

Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2021a/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021a].

This version is the same as [[JASigning_Release_Notes#JASigning_2020c_(2020-11)|JASigning 2020c]].

= JASigning Release Notes =

See [[JASigning Release Notes]] for information on earlier legacy releases.

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

CWASA Release Notes

2025-01-14T15:24:58Z

John.Glauert:

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

= CWA Signing Avatars Release Notes =

From 2021 the standard Open [[CWA Signing Avatars|CWASA]] release, found at
[http://vhg.cmp.uea.ac.uk/tech/jas/std/ http://vhg.cmp.uea.ac.uk/tech/jas/std/],
allows personal, public, and commercial use of the software when accessed, unmodified, from the UEA server. See [[CWASA Conditions of Use|Conditions of Use]].

These notes, and the notes for [[JASigning Release Notes|JASigning]], include Legacy releases with additional avatars and earlier deprecated [[JASigning]] resources. There is also a Development release containing components that cannot be guaranteed to be stable and should only be used for evaluation.

See [[CWA Signing Avatars|CWASA]] for other resources and documentation, including the [[CWASA Local Installation]], a version that can be installed on a localhost web server for evaluation.

Users are welcome to provide feedback via the [[JASigning Issue Reporting|Issue Reporting]] page. Documentation of the system is a work in progress so please send questions and comments to [mailto:cmp_virtualsigning@uea.ac.uk cmp_virtualsigning@uea.ac.uk] so that we can update these pages.

= Table of Contents =

__TOC__

= CWASA Release Notes =

All [[JASigning]] releases before 2021 are available only for evaluation and research, as for the current Legacy and Development releases. The Standard Version is an Open Release which will be based on a Legacy Release but omitting most deprecated software based on Java. The Development Version is a Development Release, potentially containing experimental features.

= CWASA 2025 =

== CWASA 2025 (Standard Version) ==

Open Release found at [//vhg.cmp.uea.ac.uk/tech/jas/vhg2025/ vhg.cmp.uea.ac.uk/tech/jas/vhg2025].

This release is based on the Legacy Release [[#CWASA_2024d_(2024-11)| CWASA 2024d]].

In modern browsers the appearance of the Anna avatar with fully closed eyes is rather dark.
This may have been true for some time and will be investigated when time permits.

== CWASA 2025z (Development Version) ==

Development Release found at [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2025z/ vhg.cmp.uea.ac.uk/tech/jas/vhg2025z].

This release is based on the Legacy Release [[#CWASA_2024d_(2024-11)| CWASA 2024d]].

In modern browsers the appearance of the Anna avatar with fully closed eyes is rather dark.
This may have been true for some time and will be investigated when time permits.

Users are encouraged to try the development release and report any issues encountered.

= CWASA 2024 =

== CWASA 2024d (2024-11) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2024d/ vhg.cmp.uea.ac.uk/tech/jas/vhg2024d].

These are the main differences between this version and [[#CWASA_2024c_(2024-08)| CWASA 2024c]]:

* Animgen transpiled using current version of Emscripten
* Functionality should be unchanged.

== CWASA 2024c (2024-08) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2024c/ vhg.cmp.uea.ac.uk/tech/jas/vhg2024c].

These are the main differences between this version and [[#CWASA_2024b_(2024-05)| CWASA 2024b]]:

* Accessing URLs now using the fetch interface
* Animgen processing by CGI script server reinstated: See [[Animgen Server]]
* Server using Node.js tool '''sigtool''' to convert h-SiGML to g-SiGML if requested

== CWASA 2024b (2024-05) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2024b/ vhg.cmp.uea.ac.uk/tech/jas/vhg2024b].

These are the main differences between this version and [[#CWASA_2024a_(2024-04)| CWASA 2024a]]:

* Offline transformation of h-SiGML to g-SiGML simplified using Node.js tool installed using npm
* Node.js software using Saxon for XSLT processing

== CWASA 2024a (2024-04) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2024a/ vhg.cmp.uea.ac.uk/tech/jas/vhg2024a].

The release should have the same features as the Legacy Release [[#CWASA_2023a_(2023-06)| CWASA 2023a]].

= CWASA 2023 =

== CWASA 2023 (Standard Version) ==

Open Release found at [//vhg.cmp.uea.ac.uk/tech/jas/vhg2023/ vhg.cmp.uea.ac.uk/tech/jas/vhg2023].

This release is based on the Legacy Release [[#CWASA_2022b_(2022-07)| CWASA 2022b]].

== CWASA 2023z (Development Version) ==

Development Release found at [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2023z/ vhg.cmp.uea.ac.uk/tech/jas/vhg2023z].

This release is based on the Legacy Release [[#CWASA_2023a_(2023-06)| CWASA 2023a]].

Users are encouraged to try the development release and report any issues encountered.

== CWASA 2023a (2023-06) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2023a/ vhg.cmp.uea.ac.uk/tech/jas/vhg2023a].

These are the main differences between this version and [[#CWASA_2022b_(2022-07)| CWASA 2022b]]:

* Electron apps now using better maintained framework using Electron and Vite
* Improved handling of Port 8052 for streamed SiGML data

= CWASA 2022 =

== CWASA 2022 (Standard Version) ==

Open Release found at [//vhg.cmp.uea.ac.uk/tech/jas/vhg2022/ vhg.cmp.uea.ac.uk/tech/jas/vhg2022].

This release is based on the Legacy Release [[#CWASA_2022a_(2022-01)| CWASA 2022a]].

== CWASA 2022z (Development Version) ==

Development Release found at [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2022z/ vhg.cmp.uea.ac.uk/tech/jas/vhg2022z].

This release is based on the Legacy Release [[#CWASA_2022b_(2022-07)| CWASA 2022b]].

Users are encouraged to try the development release and report any issues encountered.

== CWASA 2022b (2022-07) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2022b/ vhg.cmp.uea.ac.uk/tech/jas/vhg2022b].

These are the main differences between this version and [[#CWASA_2022a_(2022-01)| CWASA 2022a]]:

* C++ code for Animgen transpiled with a newer release of Emscripten
* Base directory for SiGML files for JWS apps now based on release installation
* Frame capture for video generation in JWS apps adapts to display resolution for Retina displays
* A new version of the video generation server is documented at [[JASigning Video Generator]]

== CWASA 2022a (2022-01) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2022a/ vhg.cmp.uea.ac.uk/tech/jas/vhg2022a].

This version is the same as [[#CWASA_2021f_(2021-12)| CWASA 2021f]].

= CWASA 2021 =

== CWASA 2021 (Standard Version) ==

Open Release found at [//vhg.cmp.uea.ac.uk/tech/jas/vhg2021/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021].

This release is based on the Legacy Release [[#CWASA_2021f_(2021-12)| CWASA 2021f]].

== CWASA 2021z (Development Version) ==

Development Release found at [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2021z/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021z].

This release is based on the Legacy Release [[#CWASA_2021f_(2021-12)| CWASA 2021f]].

Users are encouraged to try the development release and report any issues encountered.

== CWASA 2021f (2021-12) ==

Legacy Release found at [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2021f/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021f].

These are the main differences between this version and [[#CWASA_2021e_(2021-11)| CWASA 2021e]]:

* Recover from errors in URL specification for SiGML file URL
* Recover from errors in SiGML code from URL or text

== CWASA 2021e (2021-11) ==

Legacy Release found at [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2021e/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021e].

These are the main differences between this version and [[#CWASA_2021d_(2021-09)| CWASA 2021d]]:

* Using just https: URLs to support file: URLs for accessing the release
* Reports changes in camera settings that can later be used to change the initial camera setting
* Reports changes in signing speed that can later be used to change the initial speed setting
* See [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2021e/cwa/OneAvClientTest.html OneAvClientTest.html] for an example

== CWASA 2021d (2021-09) ==

Legacy Release found at [//vhg.cmp.uea.ac.uk/tech/jas/vhg2021d/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021d].

These are the main differences between this version and [[#CWASA_2021c_(2021-02)| CWASA 2021c]]:

* Employs protocol-relative URLs for HTTP and HTTPS support

The UEA server now supports just HTTPS. Older releases will mostly fail. We are, however, able to generate distributions using only HTTP or only HTTPS if required.

== CWASA 2021c (2021-02) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2021c/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021c].

These are the main differences between this version and [[#CWASA_2021b_(2021-01)| CWASA 2021b]]:

* New GUI element '''CWASAAmbBox''' to enable and disable ambient animation when an avatar is idle
* Configuration setting '''ambIdle''' providing default for ambient anumation

== CWASA 2021b (2021-01) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2021b/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021b].

These are the main differences between this version and [[#CWASA_2021a_(2021-01)| CWASA 2021a]]:

* Rearranged build process for Open, Legacy, and Development releases

== CWASA 2021a (2021-01) ==

Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2021a/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021a].

This version is the same as [[JASigning_Release_Notes#JASigning_2020c_(2020-11)|JASigning 2020c]].

= JASigning Release Notes =

See [[JASigning Release Notes]] for information on earlier legacy releases.

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

CWASA Release Notes

2024-11-23T13:51:16Z

John.Glauert: Introduces vhg2024d

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

= CWA Signing Avatars Release Notes =

From 2021 the standard Open [[CWA Signing Avatars|CWASA]] release, found at
[http://vhg.cmp.uea.ac.uk/tech/jas/std/ http://vhg.cmp.uea.ac.uk/tech/jas/std/],
allows personal, public, and commercial use of the software when accessed, unmodified, from the UEA server. See [[CWASA Conditions of Use|Conditions of Use]].

These notes, and the notes for [[JASigning Release Notes|JASigning]], include Legacy releases with additional avatars and earlier deprecated [[JASigning]] resources. There is also a Development release containing components that cannot be guaranteed to be stable and should only be used for evaluation.

See [[CWA Signing Avatars|CWASA]] for other resources and documentation, including the [[CWASA Local Installation]], a version that can be installed on a localhost web server for evaluation.

Users are welcome to provide feedback via the [[JASigning Issue Reporting|Issue Reporting]] page. Documentation of the system is a work in progress so please send questions and comments to [mailto:cmp_virtualsigning@uea.ac.uk cmp_virtualsigning@uea.ac.uk] so that we can update these pages.

= Table of Contents =

__TOC__

= CWASA Release Notes =

All [[JASigning]] releases before 2021 are available only for evaluation and research, as for the current Legacy and Development releases. The Standard Version is an Open Release which will be based on a Legacy Release but omitting most deprecated software based on Java. The Development Version is a Development Release, potentially containing experimental features.

= CWASA 2024 =

== CWASA 2024 (Standard Version) ==

Open Release found at [//vhg.cmp.uea.ac.uk/tech/jas/vhg2024/ vhg.cmp.uea.ac.uk/tech/jas/vhg2024].

This release is based on the Legacy Release [[#CWASA_2024b_(2024-05)| CWASA 2024b]].

In modern browsers the appearance of the Anna avatar with fully closed eyes is rather dark.
This may have been true for some time and will be investigated when time permits.

== CWASA 2024z (Development Version) ==

Development Release found at [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2024z/ vhg.cmp.uea.ac.uk/tech/jas/vhg2024z].

This release is based on the Legacy Release [[#CWASA_2024d_(2024-11)| CWASA 2024d]].

In modern browsers the appearance of the Anna avatar with fully closed eyes is rather dark.
This may have been true for some time and will be investigated when time permits.

Users are encouraged to try the development release and report any issues encountered.

== CWASA 2024d (2024-11) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2024d/ vhg.cmp.uea.ac.uk/tech/jas/vhg2024d].

These are the main differences between this version and [[#CWASA_2024c_(2024-08)| CWASA 2024c]]:

* Animgen transpiled using current version of Emscripten
* Functionality should be unchanged.

== CWASA 2024c (2024-08) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2024c/ vhg.cmp.uea.ac.uk/tech/jas/vhg2024c].

These are the main differences between this version and [[#CWASA_2024b_(2024-05)| CWASA 2024b]]:

* Accessing URLs now using the fetch interface
* Animgen processing by CGI script server reinstated: See [[Animgen Server]]
* Server using Node.js tool '''sigtool''' to convert h-SiGML to g-SiGML if requested

== CWASA 2024b (2024-05) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2024b/ vhg.cmp.uea.ac.uk/tech/jas/vhg2024b].

These are the main differences between this version and [[#CWASA_2024a_(2024-04)| CWASA 2024a]]:

* Offline transformation of h-SiGML to g-SiGML simplified using Node.js tool installed using npm
* Node.js software using Saxon for XSLT processing

== CWASA 2024a (2024-04) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2024a/ vhg.cmp.uea.ac.uk/tech/jas/vhg2024a].

The release should have the same features as the Legacy Release [[#CWASA_2023a_(2023-06)| CWASA 2023a]].

= CWASA 2023 =

== CWASA 2023 (Standard Version) ==

Open Release found at [//vhg.cmp.uea.ac.uk/tech/jas/vhg2023/ vhg.cmp.uea.ac.uk/tech/jas/vhg2023].

This release is based on the Legacy Release [[#CWASA_2022b_(2022-07)| CWASA 2022b]].

== CWASA 2023z (Development Version) ==

Development Release found at [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2023z/ vhg.cmp.uea.ac.uk/tech/jas/vhg2023z].

This release is based on the Legacy Release [[#CWASA_2023a_(2023-06)| CWASA 2023a]].

Users are encouraged to try the development release and report any issues encountered.

== CWASA 2023a (2023-06) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2023a/ vhg.cmp.uea.ac.uk/tech/jas/vhg2023a].

These are the main differences between this version and [[#CWASA_2022b_(2022-07)| CWASA 2022b]]:

* Electron apps now using better maintained framework using Electron and Vite
* Improved handling of Port 8052 for streamed SiGML data

= CWASA 2022 =

== CWASA 2022 (Standard Version) ==

Open Release found at [//vhg.cmp.uea.ac.uk/tech/jas/vhg2022/ vhg.cmp.uea.ac.uk/tech/jas/vhg2022].

This release is based on the Legacy Release [[#CWASA_2022a_(2022-01)| CWASA 2022a]].

== CWASA 2022z (Development Version) ==

Development Release found at [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2022z/ vhg.cmp.uea.ac.uk/tech/jas/vhg2022z].

This release is based on the Legacy Release [[#CWASA_2022b_(2022-07)| CWASA 2022b]].

Users are encouraged to try the development release and report any issues encountered.

== CWASA 2022b (2022-07) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2022b/ vhg.cmp.uea.ac.uk/tech/jas/vhg2022b].

These are the main differences between this version and [[#CWASA_2022a_(2022-01)| CWASA 2022a]]:

* C++ code for Animgen transpiled with a newer release of Emscripten
* Base directory for SiGML files for JWS apps now based on release installation
* Frame capture for video generation in JWS apps adapts to display resolution for Retina displays
* A new version of the video generation server is documented at [[JASigning Video Generator]]

== CWASA 2022a (2022-01) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2022a/ vhg.cmp.uea.ac.uk/tech/jas/vhg2022a].

This version is the same as [[#CWASA_2021f_(2021-12)| CWASA 2021f]].

= CWASA 2021 =

== CWASA 2021 (Standard Version) ==

Open Release found at [//vhg.cmp.uea.ac.uk/tech/jas/vhg2021/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021].

This release is based on the Legacy Release [[#CWASA_2021f_(2021-12)| CWASA 2021f]].

== CWASA 2021z (Development Version) ==

Development Release found at [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2021z/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021z].

This release is based on the Legacy Release [[#CWASA_2021f_(2021-12)| CWASA 2021f]].

Users are encouraged to try the development release and report any issues encountered.

== CWASA 2021f (2021-12) ==

Legacy Release found at [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2021f/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021f].

These are the main differences between this version and [[#CWASA_2021e_(2021-11)| CWASA 2021e]]:

* Recover from errors in URL specification for SiGML file URL
* Recover from errors in SiGML code from URL or text

== CWASA 2021e (2021-11) ==

Legacy Release found at [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2021e/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021e].

These are the main differences between this version and [[#CWASA_2021d_(2021-09)| CWASA 2021d]]:

* Using just https: URLs to support file: URLs for accessing the release
* Reports changes in camera settings that can later be used to change the initial camera setting
* Reports changes in signing speed that can later be used to change the initial speed setting
* See [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2021e/cwa/OneAvClientTest.html OneAvClientTest.html] for an example

== CWASA 2021d (2021-09) ==

Legacy Release found at [//vhg.cmp.uea.ac.uk/tech/jas/vhg2021d/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021d].

These are the main differences between this version and [[#CWASA_2021c_(2021-02)| CWASA 2021c]]:

* Employs protocol-relative URLs for HTTP and HTTPS support

The UEA server now supports just HTTPS. Older releases will mostly fail. We are, however, able to generate distributions using only HTTP or only HTTPS if required.

== CWASA 2021c (2021-02) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2021c/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021c].

These are the main differences between this version and [[#CWASA_2021b_(2021-01)| CWASA 2021b]]:

* New GUI element '''CWASAAmbBox''' to enable and disable ambient animation when an avatar is idle
* Configuration setting '''ambIdle''' providing default for ambient anumation

== CWASA 2021b (2021-01) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2021b/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021b].

These are the main differences between this version and [[#CWASA_2021a_(2021-01)| CWASA 2021a]]:

* Rearranged build process for Open, Legacy, and Development releases

== CWASA 2021a (2021-01) ==

Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2021a/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021a].

This version is the same as [[JASigning_Release_Notes#JASigning_2020c_(2020-11)|JASigning 2020c]].

= JASigning Release Notes =

See [[JASigning Release Notes]] for information on earlier legacy releases.

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

CWASA Conditions of Use

2024-10-17T10:20:50Z

John.Glauert: 2021 -> 2024

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

== CWASA Software ==

The [[CWA Signing Avatars]] software (CWASA) animates natural sign language in web browsers using HTML5, JavaScript, and WebGL. Some example web pages are given in the [http://vhg.cmp.uea.ac.uk/tech/jas/std/ CWASA release]. CWASA applications are also provided for leading operating systems.

CWASA is hosted on a web server at UEA, giving access to the resources used by the example pages. No warranty is given for the performance of the software or the UEA Server.

The [[CWASA Release Notes]] provide some documentation of current and legacy releases.

== CWASA Conditions of Use and Licensing ==

The [[CWA Signing Avatars|CWASA]] software is
'''Copyright UEA (2005-2024)'''. It includes script files, configuration files, avatar definitions, signing notation files, and example web pages.

The CWASA example web pages are covered by the [https://creativecommons.org/licenses/by-sa/4.0/ Creative Commons BY-SA] licence. This allows development of new pages for personal, public, and commercial purposes. The underlying CWASA software must be used without modification, on terms equivalent to [https://creativecommons.org/licenses/by-nd/4.0/ Creative Commons BY-ND]

For enquiries about commercial support of the software, including customisation for corporate use and licensing of additional avatars, please contact
[mailto:cmp_virtualsigning@uea.ac.uk cmp_virtualsigning@uea.ac.uk].

Development of the CWASA software was supported by the
EU Framework 7 project [[Dicta-Sign]] FP7-ICT-3-231135.

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

CWASA Release Notes

2024-08-09T19:07:36Z

John.Glauert:

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

= CWA Signing Avatars Release Notes =

From 2021 the standard Open [[CWA Signing Avatars|CWASA]] release, found at
[http://vhg.cmp.uea.ac.uk/tech/jas/std/ http://vhg.cmp.uea.ac.uk/tech/jas/std/],
allows personal, public, and commercial use of the software when accessed, unmodified, from the UEA server. See [[CWASA Conditions of Use|Conditions of Use]].

These notes, and the notes for [[JASigning Release Notes|JASigning]], include Legacy releases with additional avatars and earlier deprecated [[JASigning]] resources. There is also a Development release containing components that cannot be guaranteed to be stable and should only be used for evaluation.

See [[CWA Signing Avatars|CWASA]] for other resources and documentation, including the [[CWASA Local Installation]], a version that can be installed on a localhost web server for evaluation.

Users are welcome to provide feedback via the [[JASigning Issue Reporting|Issue Reporting]] page. Documentation of the system is a work in progress so please send questions and comments to [mailto:cmp_virtualsigning@uea.ac.uk cmp_virtualsigning@uea.ac.uk] so that we can update these pages.

= Table of Contents =

__TOC__

= CWASA Release Notes =

All [[JASigning]] releases before 2021 are available only for evaluation and research, as for the current Legacy and Development releases. The Standard Version is an Open Release which will be based on a Legacy Release but omitting most deprecated software based on Java. The Development Version is a Development Release, potentially containing experimental features.

= CWASA 2024 =

== CWASA 2024 (Standard Version) ==

Open Release found at [//vhg.cmp.uea.ac.uk/tech/jas/vhg2024/ vhg.cmp.uea.ac.uk/tech/jas/vhg2024].

This release is based on the Legacy Release [[#CWASA_2024b_(2024-05)| CWASA 2024b]].

In modern browsers the appearance of the Anna avatar with fully closed eyes is rather dark.
This may have been true for some time and will be investigated when time permits.

== CWASA 2024z (Development Version) ==

Development Release found at [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2024z/ vhg.cmp.uea.ac.uk/tech/jas/vhg2024z].

This release is based on the Legacy Release [[#CWASA_2024c_(2024-08)| CWASA 2024c]].

In modern browsers the appearance of the Anna avatar with fully closed eyes is rather dark.
This may have been true for some time and will be investigated when time permits.

Users are encouraged to try the development release and report any issues encountered.

== CWASA 2024c (2024-08) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2024c/ vhg.cmp.uea.ac.uk/tech/jas/vhg2024c].

These are the main differences between this version and [[#CWASA_2024b_(2024-05)| CWASA 2024b]]:

* Accessing URLs now using the fetch interface
* Animgen processing by CGI script server reinstated: See [[Animgen Server]]
* Server using Node.js tool '''sigtool''' to convert h-SiGML to g-SiGML if requested

== CWASA 2024b (2024-05) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2024b/ vhg.cmp.uea.ac.uk/tech/jas/vhg2024b].

These are the main differences between this version and [[#CWASA_2024a_(2024-04)| CWASA 2024a]]:

* Offline transformation of h-SiGML to g-SiGML simplified using Node.js tool installed using npm
* Node.js software using Saxon for XSLT processing

== CWASA 2024a (2024-04) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2024a/ vhg.cmp.uea.ac.uk/tech/jas/vhg2024a].

The release should have the same features as the Legacy Release [[#CWASA_2023a_(2023-06)| CWASA 2023a]].

= CWASA 2023 =

== CWASA 2023 (Standard Version) ==

Open Release found at [//vhg.cmp.uea.ac.uk/tech/jas/vhg2023/ vhg.cmp.uea.ac.uk/tech/jas/vhg2023].

This release is based on the Legacy Release [[#CWASA_2022b_(2022-07)| CWASA 2022b]].

== CWASA 2023z (Development Version) ==

Development Release found at [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2023z/ vhg.cmp.uea.ac.uk/tech/jas/vhg2023z].

This release is based on the Legacy Release [[#CWASA_2023a_(2023-06)| CWASA 2023a]].

Users are encouraged to try the development release and report any issues encountered.

== CWASA 2023a (2023-06) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2023a/ vhg.cmp.uea.ac.uk/tech/jas/vhg2023a].

These are the main differences between this version and [[#CWASA_2022b_(2022-07)| CWASA 2022b]]:

* Electron apps now using better maintained framework using Electron and Vite
* Improved handling of Port 8052 for streamed SiGML data

= CWASA 2022 =

== CWASA 2022 (Standard Version) ==

Open Release found at [//vhg.cmp.uea.ac.uk/tech/jas/vhg2022/ vhg.cmp.uea.ac.uk/tech/jas/vhg2022].

This release is based on the Legacy Release [[#CWASA_2022a_(2022-01)| CWASA 2022a]].

== CWASA 2022z (Development Version) ==

Development Release found at [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2022z/ vhg.cmp.uea.ac.uk/tech/jas/vhg2022z].

This release is based on the Legacy Release [[#CWASA_2022b_(2022-07)| CWASA 2022b]].

Users are encouraged to try the development release and report any issues encountered.

== CWASA 2022b (2022-07) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2022b/ vhg.cmp.uea.ac.uk/tech/jas/vhg2022b].

These are the main differences between this version and [[#CWASA_2022a_(2022-01)| CWASA 2022a]]:

* C++ code for Animgen transpiled with a newer release of Emscripten
* Base directory for SiGML files for JWS apps now based on release installation
* Frame capture for video generation in JWS apps adapts to display resolution for Retina displays
* A new version of the video generation server is documented at [[JASigning Video Generator]]

== CWASA 2022a (2022-01) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2022a/ vhg.cmp.uea.ac.uk/tech/jas/vhg2022a].

This version is the same as [[#CWASA_2021f_(2021-12)| CWASA 2021f]].

= CWASA 2021 =

== CWASA 2021 (Standard Version) ==

Open Release found at [//vhg.cmp.uea.ac.uk/tech/jas/vhg2021/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021].

This release is based on the Legacy Release [[#CWASA_2021f_(2021-12)| CWASA 2021f]].

== CWASA 2021z (Development Version) ==

Development Release found at [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2021z/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021z].

This release is based on the Legacy Release [[#CWASA_2021f_(2021-12)| CWASA 2021f]].

Users are encouraged to try the development release and report any issues encountered.

== CWASA 2021f (2021-12) ==

Legacy Release found at [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2021f/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021f].

These are the main differences between this version and [[#CWASA_2021e_(2021-11)| CWASA 2021e]]:

* Recover from errors in URL specification for SiGML file URL
* Recover from errors in SiGML code from URL or text

== CWASA 2021e (2021-11) ==

Legacy Release found at [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2021e/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021e].

These are the main differences between this version and [[#CWASA_2021d_(2021-09)| CWASA 2021d]]:

* Using just https: URLs to support file: URLs for accessing the release
* Reports changes in camera settings that can later be used to change the initial camera setting
* Reports changes in signing speed that can later be used to change the initial speed setting
* See [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2021e/cwa/OneAvClientTest.html OneAvClientTest.html] for an example

== CWASA 2021d (2021-09) ==

Legacy Release found at [//vhg.cmp.uea.ac.uk/tech/jas/vhg2021d/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021d].

These are the main differences between this version and [[#CWASA_2021c_(2021-02)| CWASA 2021c]]:

* Employs protocol-relative URLs for HTTP and HTTPS support

The UEA server now supports just HTTPS. Older releases will mostly fail. We are, however, able to generate distributions using only HTTP or only HTTPS if required.

== CWASA 2021c (2021-02) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2021c/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021c].

These are the main differences between this version and [[#CWASA_2021b_(2021-01)| CWASA 2021b]]:

* New GUI element '''CWASAAmbBox''' to enable and disable ambient animation when an avatar is idle
* Configuration setting '''ambIdle''' providing default for ambient anumation

== CWASA 2021b (2021-01) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2021b/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021b].

These are the main differences between this version and [[#CWASA_2021a_(2021-01)| CWASA 2021a]]:

* Rearranged build process for Open, Legacy, and Development releases

== CWASA 2021a (2021-01) ==

Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2021a/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021a].

This version is the same as [[JASigning_Release_Notes#JASigning_2020c_(2020-11)|JASigning 2020c]].

= JASigning Release Notes =

See [[JASigning Release Notes]] for information on earlier legacy releases.

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

CWASA Release Notes

2024-08-09T19:04:21Z

John.Glauert: Introduces vhg2024c

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

= CWA Signing Avatars Release Notes =

From 2021 the standard Open [[CWA Signing Avatars|CWASA]] release, found at
[http://vhg.cmp.uea.ac.uk/tech/jas/std/ http://vhg.cmp.uea.ac.uk/tech/jas/std/],
allows personal, public, and commercial use of the software when accessed, unmodified, from the UEA server. See [[CWASA Conditions of Use|Conditions of Use]].

These notes, and the notes for [[JASigning Release Notes|JASigning]], include Legacy releases with additional avatars and earlier deprecated [[JASigning]] resources. There is also a Development release containing components that cannot be guaranteed to be stable and should only be used for evaluation.

See [[CWA Signing Avatars|CWASA]] for other resources and documentation, including the [[CWASA Local Installation]], a version that can be installed on a localhost web server for evaluation.

Users are welcome to provide feedback via the [[JASigning Issue Reporting|Issue Reporting]] page. Documentation of the system is a work in progress so please send questions and comments to [mailto:cmp_virtualsigning@uea.ac.uk cmp_virtualsigning@uea.ac.uk] so that we can update these pages.

= Table of Contents =

__TOC__

= CWASA Release Notes =

All [[JASigning]] releases before 2021 are available only for evaluation and research, as for the current Legacy and Development releases. The Standard Version is an Open Release which will be based on a Legacy Release but omitting most deprecated software based on Java. The Development Version is a Development Release, potentially containing experimental features.

= CWASA 2024 =

== CWASA 2024 (Standard Version) ==

Open Release found at [//vhg.cmp.uea.ac.uk/tech/jas/vhg2024/ vhg.cmp.uea.ac.uk/tech/jas/vhg2024].

This release is based on the Legacy Release [[#CWASA_2024b_(2024-05)| CWASA 2024b]].

In modern browsers the appearance of the Anna avatar with fully closed eyes is rather dark.
This may have been true for some time and will be investigated when time permits.

== CWASA 2024z (Development Version) ==

Development Release found at [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2024z/ vhg.cmp.uea.ac.uk/tech/jas/vhg2024z].

This release is based on the Legacy Release [[#CWASA_2024c_(2024-08)| CWASA 2024c]].

In modern browsers the appearance of the Anna avatar with fully closed eyes is rather dark.
This may have been true for some time and will be investigated when time permits.

Users are encouraged to try the development release and report any issues encountered.

== CWASA 2024c (2024-08) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2024c/ vhg.cmp.uea.ac.uk/tech/jas/vhg2024c].

These are the main differences between this version and [[#CWASA_2024b_(2024-05)| CWASA 2024b]]:

* Animgen processing by CGI script server reinstated: See [[Animgen Server]]
* Server using Node.js tool '''sigtool''' to convert h-SiGML to g-SiGML if requested

== CWASA 2024b (2024-05) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2024b/ vhg.cmp.uea.ac.uk/tech/jas/vhg2024b].

These are the main differences between this version and [[#CWASA_2024a_(2024-04)| CWASA 2024a]]:

* Offline transformation of h-SiGML to g-SiGML simplified using Node.js tool installed using npm
* Node.js software using Saxon for XSLT processing

== CWASA 2024a (2024-04) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2024a/ vhg.cmp.uea.ac.uk/tech/jas/vhg2024a].

The release should have the same features as the Legacy Release [[#CWASA_2023a_(2023-06)| CWASA 2023a]].

= CWASA 2023 =

== CWASA 2023 (Standard Version) ==

Open Release found at [//vhg.cmp.uea.ac.uk/tech/jas/vhg2023/ vhg.cmp.uea.ac.uk/tech/jas/vhg2023].

This release is based on the Legacy Release [[#CWASA_2022b_(2022-07)| CWASA 2022b]].

== CWASA 2023z (Development Version) ==

Development Release found at [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2023z/ vhg.cmp.uea.ac.uk/tech/jas/vhg2023z].

This release is based on the Legacy Release [[#CWASA_2023a_(2023-06)| CWASA 2023a]].

Users are encouraged to try the development release and report any issues encountered.

== CWASA 2023a (2023-06) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2023a/ vhg.cmp.uea.ac.uk/tech/jas/vhg2023a].

These are the main differences between this version and [[#CWASA_2022b_(2022-07)| CWASA 2022b]]:

* Electron apps now using better maintained framework using Electron and Vite
* Improved handling of Port 8052 for streamed SiGML data

= CWASA 2022 =

== CWASA 2022 (Standard Version) ==

Open Release found at [//vhg.cmp.uea.ac.uk/tech/jas/vhg2022/ vhg.cmp.uea.ac.uk/tech/jas/vhg2022].

This release is based on the Legacy Release [[#CWASA_2022a_(2022-01)| CWASA 2022a]].

== CWASA 2022z (Development Version) ==

Development Release found at [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2022z/ vhg.cmp.uea.ac.uk/tech/jas/vhg2022z].

This release is based on the Legacy Release [[#CWASA_2022b_(2022-07)| CWASA 2022b]].

Users are encouraged to try the development release and report any issues encountered.

== CWASA 2022b (2022-07) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2022b/ vhg.cmp.uea.ac.uk/tech/jas/vhg2022b].

These are the main differences between this version and [[#CWASA_2022a_(2022-01)| CWASA 2022a]]:

* C++ code for Animgen transpiled with a newer release of Emscripten
* Base directory for SiGML files for JWS apps now based on release installation
* Frame capture for video generation in JWS apps adapts to display resolution for Retina displays
* A new version of the video generation server is documented at [[JASigning Video Generator]]

== CWASA 2022a (2022-01) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2022a/ vhg.cmp.uea.ac.uk/tech/jas/vhg2022a].

This version is the same as [[#CWASA_2021f_(2021-12)| CWASA 2021f]].

= CWASA 2021 =

== CWASA 2021 (Standard Version) ==

Open Release found at [//vhg.cmp.uea.ac.uk/tech/jas/vhg2021/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021].

This release is based on the Legacy Release [[#CWASA_2021f_(2021-12)| CWASA 2021f]].

== CWASA 2021z (Development Version) ==

Development Release found at [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2021z/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021z].

This release is based on the Legacy Release [[#CWASA_2021f_(2021-12)| CWASA 2021f]].

Users are encouraged to try the development release and report any issues encountered.

== CWASA 2021f (2021-12) ==

Legacy Release found at [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2021f/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021f].

These are the main differences between this version and [[#CWASA_2021e_(2021-11)| CWASA 2021e]]:

* Recover from errors in URL specification for SiGML file URL
* Recover from errors in SiGML code from URL or text

== CWASA 2021e (2021-11) ==

Legacy Release found at [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2021e/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021e].

These are the main differences between this version and [[#CWASA_2021d_(2021-09)| CWASA 2021d]]:

* Using just https: URLs to support file: URLs for accessing the release
* Reports changes in camera settings that can later be used to change the initial camera setting
* Reports changes in signing speed that can later be used to change the initial speed setting
* See [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2021e/cwa/OneAvClientTest.html OneAvClientTest.html] for an example

== CWASA 2021d (2021-09) ==

Legacy Release found at [//vhg.cmp.uea.ac.uk/tech/jas/vhg2021d/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021d].

These are the main differences between this version and [[#CWASA_2021c_(2021-02)| CWASA 2021c]]:

* Employs protocol-relative URLs for HTTP and HTTPS support

The UEA server now supports just HTTPS. Older releases will mostly fail. We are, however, able to generate distributions using only HTTP or only HTTPS if required.

== CWASA 2021c (2021-02) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2021c/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021c].

These are the main differences between this version and [[#CWASA_2021b_(2021-01)| CWASA 2021b]]:

* New GUI element '''CWASAAmbBox''' to enable and disable ambient animation when an avatar is idle
* Configuration setting '''ambIdle''' providing default for ambient anumation

== CWASA 2021b (2021-01) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2021b/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021b].

These are the main differences between this version and [[#CWASA_2021a_(2021-01)| CWASA 2021a]]:

* Rearranged build process for Open, Legacy, and Development releases

== CWASA 2021a (2021-01) ==

Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2021a/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021a].

This version is the same as [[JASigning_Release_Notes#JASigning_2020c_(2020-11)|JASigning 2020c]].

= JASigning Release Notes =

See [[JASigning Release Notes]] for information on earlier legacy releases.

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

Animgen Server

2024-08-09T09:44:50Z

John.Glauert: /* Animgen Server */

[[Main Page|Home]] >> [[SiGML Tools]]
----
== Animgen Server ==

During development of the [[CWASA]] software, a CGI script was developed to call the freestanding [[Animgen]] application to convert SiGML to CAS, the format of animation data used by CWASA.

The [https://vhg.cmp.uea.ac.uk/tech/jas/dev CWASA development distribution] includes web pages that exploit this server. Now that the Animgen software is embedded in the script for CWASA, there is little benefit in using this server.

The server can be driven by curl using a command such as:
<nowiki>curl -s "https://vhg.cmp.uea.ac.uk/cgi-bin/animgen/sigmlserver.pl?avatar=luna&fps=50" -F sigml=@mysigns.sigml</nowiki>
The parameters accepted are:
* avatar: defaults to anna
* fps: defaults to 25
* htog: defaults to "false" (0)
The '''htog''' parameter controls conversion of H-SiGML, SiGML based on a sequence of HamNoSys tokens, to G-SiGML, SiGML ready for animation using Animgen. The Node tool '''sigtool''' is used to perform the conversion. This phase is omitted by default.

The original implementation used Java code to convert SiGML with a script named '''animgenserver.pl'''. If the script '''testanimgenserver.pl''' is used, a web page is returned documenting the processing performed.

----
[[Main Page|Home]] >> [[SiGML Tools]]

Animgen Server

2024-08-09T09:44:08Z

John.Glauert: Document use of sigmlserver.

[[Main Page|Home]] >> [[SiGML Tools]]
----
== Animgen Server ==

During development of the [[CWASA]] software, a CGI script was developed to call the freestanding [[Animgen]] application to convert SiGML to CAS, the format of animation data used by CWASA.

The [https://vhg.cmp.uea.ac.uk/tech/jas/dev CWASA development distribution] includes web pages that exploit this server. Now that the Animgen software is embedded in the script for CWASA, there is little benefit in using this server.

The server can be driven by curl using a command such as:
<nowiki>curl -s "https://vhg.cmp.uea.ac.uk/cgi-bin/animgen/animgenserver.pl?avatar=luna&fps=50" -F sigml=@mysigns.sigml</nowiki>
The parameters accepted are:
* avatar: defaults to anna
* fps: defaults to 25
* htog: defaults to "false" (0)
The '''htog''' parameter controls conversion of H-SiGML, SiGML based on a sequence of HamNoSys tokens, to G-SiGML, SiGML ready for animation using Animgen. The Node tool '''sigtool''' is used to perform the conversion. This phase is omitted by default.

The original implementation used Java code to convert SiGML with a script named '''animgenserver.pl'''. If the script '''testanimgenserver.pl''' is used, a web page is returned documenting the processing performed.

----
[[Main Page|Home]] >> [[SiGML Tools]]

Animgen Server

2024-08-05T14:42:04Z

John.Glauert:

[[Main Page|Home]] >> [[SiGML Tools]]
----
== Animgen Server ==

During development of the [[CWASA]] software, a CGI script was developed to call the freestanding [[Animgen]] application to convert SiGML to CAS, the format of animation data used by CWASA.

The [https://vhg.cmp.uea.ac.uk/tech/jas/dev CWASA development distribution] includes web pages that exploit this server. Now that the Animgen software is embedded in the script for CWASA, there is little benefit in using this server.

The server can be driven by curl using a command such as:
<nowiki>curl -s "https://vhg.cmp.uea.ac.uk/cgi-bin/animgen/animgenserver.pl?avatar=luna&fps=50" -F sigml=@mysigns.sigml</nowiki>
The parameters accepted are:
* avatar: defaults to anna
* fps: defaults to 25
* htog: defaults to "false" (0)
The '''htog''' parameter controls conversion of H-SiGML, SiGML based on a sequence of HamNoSys tokens, to G-SiGML, SiGML ready for animation using Animgen. This phase is omitted by default.

If the script '''testanimgenserver''' is used, a web page is returned documenting the processing performed.

----
[[Main Page|Home]] >> [[SiGML Tools]]

Animgen Server

2024-08-05T10:16:26Z

John.Glauert: Documentation of legacy Animgen Server via CGI

[[Main Page|Home]] >> [[SiGML Tools]]
----
== Animgen Server ==

During development of the [[CWASA]] software, a CGI script was developed to call the freestanding [[Animgen]] application to convert SiGML to CAS, the format of animation data used by CWASA.

The [https://vhg.cmp.uea.ac.uk/tech/jas/dev CWASA development distribution] includes web pages that exploit this server. Now that the Animgen software is embedded in the script for CWASA, there is little benefit in using this server.

The server can be driven by curl using a command such as:
<nowiki>curl -s "https://vhg.cmp.uea.ac.uk/cgi-bin/animgen/animgenserver.pl?avatar=luna&fps=50" -F sigml=@mysigns.sigml</nowiki>
The parameters accepted are:
* avatar: defaults to anna
* fps: defaults to 25
* htog: defaults to "false" (0)
The '''htog''' parameter controls conversion of H-SiGML, SiGML based on a sequence of HamNoSys tokens, to G-SiGML, SiGML ready for animation using Animgen. This is phase is omitted by default.

If the script '''testanimgenserver''' is used, a web page is returned documenting the processing performed.

----
[[Main Page|Home]] >> [[SiGML Tools]]

SiGML Tools

2024-08-05T09:47:24Z

John.Glauert: Introduce Online Server entry

[[Main Page|Home]]
----

A number of tools are available for creating and editing [[SiGML]] data to represent signing gestures. As [[SiGML]] is based on [[HamNoSys]], many of these allow entry using the
[https://vhg.cmp.uea.ac.uk/tech/hamnosys/HamNoSysUnicode.ttf HamNoSys Unicode font].

== [[CWA Signing Avatars|CWASA]] SiGML Player ==

The CWASA SiGML Player animates [[SiGML]] data sent to it over TCP sockets. See [[Driving the SiGML Player App]]. The application, or the legacy [[JASigning]] SiGML Service Player, can be used in conjunction with the [[JASigning]] SiGML Service Client
and other SiGML Tools mentioned below.

== [https://vhg.cmp.uea.ac.uk/tech/hamnosys/HamNoSysUnicode.ttf HamNoSysUnicode.ttf] ==

HamNoSys Unicode font as a TrueType font that should be installed in the usual way on systems using [[HamNoSys]].

== [[JASigning]] SiGML Service Client ==

Displays and allows Editing of [[SiGML]] files.
* Mac and PC tool
* Install the [https://vhg.cmp.uea.ac.uk/tech/hamnosys/HamNoSysUnicode.ttf HamNoSysUnicode.ttf]
* Sends [[SiGML]] data to a SiGML Player

== [https://vhg.cmp.uea.ac.uk/tech/ham2hpsg/Ham2HPSG22.zip Ham2HPSG Tool] ==

* Tool for entering [[HamNoSys]] on PC
* Mac Tool included for legacy (pre Mac OS X) Classic environment
* Sends [[SiGML]] data to a SiGML Player
* "..." button brings up [[HamNoSys]] entry panels
* Down Arrow button prepares [[HamNoSys]] for animation
* "V!" button sends data to player
* Limited documentation in Ham2HPSG ReadMe.txt file
* Download [https://vhg.cmp.uea.ac.uk/tech/ham2hpsg/Ham2HPSG22.zip Ham2HPSG Tool]

== [https://vhg.cmp.uea.ac.uk/tech/esigneditor/eSignEditor.zip eSIGN Editor] ==
The eSIGN Editor was developed for the [[eSIGN]] project at the IDGS, University of Hamburg.
See [https://www.sign-lang.uni-hamburg.de/dgs-korpus/index.php/welcome.html DGS Corpus] project for contacts with the authors of this tool.

* Mac and PC tool for creating [[SiGML]] signs
* Maintains a database of signs in [[HamNoSys]] notation
* Allows creation and modification of signing sequences
* Allows animation of signing sequences using a SiGML Player
* Limited documentation through [https://vhg.cmp.uea.ac.uk/tech/esigneditor/eSIGN-D23rev2.pdf Editor Manual]
* A [https://vhg.cmp.uea.ac.uk/tech/esigneditor/eSIGN%20Editor.exe Windows Installer] for an older version exists
** The installer creates Shortcuts and Start Menu items
** It appears safe to replace installed files with newer ones from [https://vhg.cmp.uea.ac.uk/tech/esigneditor/eSignEditor.zip eSIGN Editor Zip]
** The PC application must be renamed for the shortcuts to work
* Download [http://vhg.cmp.uea.ac.uk/tech/esigneditor/eSignEditor.zip eSIGN Editor]

== Online HamNoSys/SiGML Conversion Tools ==

Some services based on CGI scripts are available for processing forms of SiGML and potentially creating animation data.

* [[Animgen Server]] for converting SiGML files to animation data (CAS)

== Manual HamNoSys/SiGML Conversion Tools ==

Ralph Elliott has produced some simple tools to convert different forms of manual HamNoSys, and to do a bit of related SiGML processing. They are limited in various ways, but they could be useful to others:

* [https://vhg.cmp.uea.ac.uk/tech/hamnosys/convert/hns-sigml-convert-2011-04-12.zip Executables, source code and Javadoc], Java classes plus shell and Python scripts.<br>Includes a README file explaining roughly what's on offer and how to use it.<br>'''Original 2010-11-05''', '''Updated 2010-12-07''', '''2011-01-19''' and '''2011-04-12'''

If you want to do some conversion not provided by these tools, you're welcome to modify them to suit your needs, but in some cases it may prove easier to augment them by writing a suitable bit of python or perl. We request that you share any tools developed from this package in the same way.

The HNS characters, their <tt>ham..</tt>names and the numeric encodings used for them can be seen using this
[http://vhg.cmp.uea.ac.uk/tech/hamnosys/convert/HNS-Table-App.jar HNS Table App].
To run it, double-click its jar file after downloading.

----
[[Main Page|Home]]

Configuring CWASA for HTML5 web pages

2024-07-31T09:46:22Z

John.Glauert:

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

== CWASA Development ==

The [[JASigning]] (Java Avatar Signing) software was a reimplementation of earlier work based on C++ and Visual Basic. [[JASigning]] uses Java to create freestanding applications and web applets that can be scripted through JavaScript on web pages. [[SiGML]] data is converted to motion data for animation using the [[Animgen]] software, written in C++. Animation data is rendered using an OpenGL renderer written in Java using the JOGL bindings.

With the advent of '''HTML5''' and '''WebGL''' it has become practical to create software for use in web pages that is not dependent on Java. This development has become essential as Java is now deprecated in browsers and unsupported on major browsers such as '''Chrome''' and '''Opera'''.

Development took place in a number of stages:

* Introduction of a WebGL renderer in place of OpenGL via Java. [[SiGML]] processing continued via a simplified Java applet.
* [[SiGML]] processing delegated to an [[Animgen]] server located at UEA using a CGI script.
* Preprocessing in JavaScript of the [[HamNoSys]] variant of [[SiGML]] to the Gestural variant.
* Fully client-side operation using a JavaScript implementation of [[Animgen]].

== CWASA Installation ==

An open installation of [[CWASA]] contains a number of index web pages, web pages with embedded signing avatars, and several directories containing resources.

* '''avatars''' contains JARs with avatar definition data.
* '''sigml''' contains example [[SiGML]] files.
* '''cwa''' contains scripts used by HTML5 pages and further example web pages.

The use of CORS allows an installation to be used from other servers and even, in some circumstances, from files on a local file system.
See [[JASigning Local Installation]].

== CWASA (CoffeeScript WebGL ARP Signing Avatars) ==

The CWASA software is largely written in CoffeeScript which generates JavaScript that is combined into a single script file in the '''cwa''' directory.
CWASA is configured using settings in JSON objects. Up to four sources of settings are consulted, with earlier settings overriding later ones:

* Initial settings provided as an optional argument when the CWASA software is initialised. This allows web pages to be self contained.
* Client settings held in an optional file '''clientcfg.json''' at the same level as the webpage. Normally bypassed if Initial settings are given.
* Installation settings held in a file '''cwacfg.json''' in the '''cwa''' folder of the installation.
* Installation-depended default settings applied by the CWASA initialisation code.

Parameters are in three classes:

* Settings determining which configuration files are consulted.
* Installation settings providing locations for installation directories.
* Settings for configuring a GUI for one or more avatar panels.

Full example configuration files are given below. Initial settings are provided using a similar JavaScript JSON object as in '''appletframe.html''' in BSLExamples ([[CWASA Local Installation]]).
Unrecognised settings (such as '''description''') are ignored without comment.

== Configuration Consultation Settings ==

Users can use these settings to change the normal pattern of consulting configuration files:

* '''useClientConfig''': Controls whether '''clientcfg.json''' is consulted. Default '''true''' but bypassed if Initial settings are given unless explicitly overridden.
* '''useCwaConfig''': Controls whether '''cwacfg.json''' is consulted. Default '''true'''.

Hence '''useClientConfig''' should be set to '''true''' by pages using Initial settings that also wish to consult a '''clientcfg.json''' file.

== CWASA Installation Settings ==

It is unlikely that users will need to change installation settings as these will be picked up from the installation when initialising CWASA. The settings are:

* '''jasBase''': Base installation directory.
* '''jasVersionTag''': Parameter used by deprecated Java applet.
* '''sigmlBase''': Directory for example [[SiGML]] files. Resolved relative to '''jasBase'''.
* '''avJARBase''': Directory for JAR files containing avatar definitions. Resolved relative to '''jasBase'''.
* '''avJSONBase''': Directory for JSON files containing avatar definitions. Resolved relative to '''jasBase'''.
* '''useAvatarJARs''': Flag choosing between JAR and JSON representation for avatars. Currently needs to be set '''true'''.
* '''animgenFPS''': Frames per Second of generated animation data. Defaults to '''50'''.
* '''animgenServer''': Path to CGI script for [[Animgen]] server if used.

The default is to specify no [[Animgen]] server and client-side JavaScript will implement [[Animgen]].
Some example web pages specify a server that will be used instead. The public server is
[http://vhg.cmp.uea.ac.uk/cgi-bin/animgen/animgenserver.pl http://vhg.cmp.uea.ac.uk/cgi-bin/animgen/animgenserver.pl].
The deprecated Java Applet implementing [[Animgen]] can be accessed using a pseudo-server '''stoca:'''.
Processing will fall back to the client-side implementation if Java is not supported in the chosen browser.

== CWASA GUI Settings ==

A CWASA web page can display several avatars identified as '''av0''', '''av1''', etc. Each avatar has an associated list of possible avatar characters to be displayed.
Named avatar lists can be included in the CWASA parameters. By default, '''avs''' names the list of standard avatars that can be used freely: '''anna''', '''marc''', and '''francoise'''.
The list '''avsfull''' contains all available avatars, but should only be used for evaluation.

Parameters for the avatars are given by entries in '''avSettings''', an array of JSON objects. The settings for an avatar are:

* '''width''': Width in pixels of avatar canvas. This is mainly used when a complete GUI is generated automatically.
* '''height''': Height in pixels of avatar canvas. This is mainly used when a complete GUI is generated automatically.
* '''avList''': Name of parameter holding avatar list. This will be '''avs''' by default.
* '''initAv''': Name of avatar that is loaded initially. Should normally be already present in the '''avList'''.
* '''ambIdle''': Flag controlling whether ambient motion accompanies an idle avatar.
* '''background''': By default the canvas will have a transparent background but valid text for a style background in HTML can be provided. Set to '''null''' to force a transparent background.
* '''initCamera''': Nine numbers that define the initial camera position when the avatar is loaded.
* '''initSpeed''': Initial speed setting. See below.
* '''rateSpeed''': Rate of change to speed in GUI. See below.

Note that an '''ambIdle''' setting may be given at installation level and will be inherited by each panel that does not provide its own setting.

The actual animation speed is given by '''2^(currSpeed/rateSpeed)''' where '''currSpeed''' is initially set to '''initSpeed''' and may be increased or decreased in the GUI. The rate determines how many steps are needed to change the speed by a factor of 2.

The remaining parameters are mostly needed when a GUI is generated automatically as a full panel:

* '''allowFrameSteps''': Includes buttons to suspend and resume playing, and to step forward and backwards, a frame at a time.
* '''initSiGMLURL''': Initial value for URL of [[SiGML]] file to display. No field or URL play button is displayed if the value is missing or '''null'''.
* '''allowSiGMLText''': Flag selecting whether a field for entry of [[SiGML]] text is displayed. No field or text play button is displayed if the value is '''false'''.

== CWASA Configuration Examples ==
=== Example: cwa/cwacfg.json ===
Example installation configuration:
{
"description" : "======== CWASA installation configuration data : Main release ========",
"jasBase" : "http://vhg.cmp.uea.ac.uk/tech/jas/vhg2021/",
"jasVersionTag" : "vhg2021",

"sigmlBase" : "sigml",
"avJARBase" : "avatars",
"avJSONBase" : "avjson",
"useAvatarJARs" : true,

"animgenFPS" : 30,

"avs" : [
"anna", "marc", "francoise"
],

"avsfull" : [
"anna", "marc", "francoise",
"luna", "siggi"
],

"avSettings" : [
{
"description": "Default if client configuration is missing or restricted",
"width": 384,
"height": 320,
"avList": "avs",
"initAv": "anna",
"initCamera": [ 0, 0.23, 3.24, 5, 18, 30, -1, -1 ],
"initSpeed": 0,
"rateSpeed": 5
"allowFrameSteps": true,
"initSiGMLURL": "iTakeMug.sigml",
"allowSiGMLText": true
}
]
}

=== Example: cwa/clientcfg.json ===
Configuration for Clients using client-side [[Animgen]] processing:
{
"description" : "======== CWASA client configuration data. No Animgen server ========",
"animgenServer": null,
"avSettings" : [
{
"width": 384,
"height": 320,
"avList": "avsfull",
"initAv": "luna",
"initSiGMLURL": "scotland-H.sigml"
},
{
"width": 228,
"height": 208,
"background": "Salmon",
"avList": "avs",
"initAv": "francoise",
"allowFrameSteps": false,
"allowSiGMLText": false,
"initSiGMLURL": "welkom-ngt.sigml"
}
]
}

== CWASA GUI Creation ==
There are four approaches to incorporating the CWASA software on a web page. The installation contains example web pages, built using the different approaches:

* Complete GUI: '''WebGLAvTwo.html'''. A single '''div''' is populated with a panel containing an avatar canvas and GUI elements.
* GUI Panels: '''CWASA-plus-gui-panel.html'''. A '''div''' for the avatar canvas and a separate '''div''' for the GUI.
* GUI Elements: '''CWASA-plus-gui-elements.html'''. A number of '''div'''s and '''span'''s arranging different sections of the GUI.
* Bespoke GUI: '''CWASA-plus-bespoke-gui.html'''. Individual HTML elements defining an equivalent GUI.

The first example displays two avatars on a page.
The first two approaches select elements according to layout parameters in the configuration, while the final approaches choose elements directly.
The final three examples have very similar appearance, illustrating the alternative approaches.

A CSS stylesheet controls appearance in all cases. The '''class''' attribute is also used by the CWASA script to identify elements of the GUI
for attaching handlers and to change enabled state during animation. For a page that might use the Java applet it is necessary to include one instance of:
<pre><div class="SToCA"></div></pre>
This will be ignored if an [[Animgen]] server is used or the browser does not support Java.

A '''div''' or '''span''' that forms part of the CWASA GUI will have a class which identifies the GUI component and the avatar concerned. For example, a complete GUI panel for the first avatar would be specified by:
<pre><div class="CWASAPanel av0"></div></pre>

=== Complete GUI ===
* '''CWASAPanel''': A GUI, '''CWASAGUI''', to the left of an avatar canvas, '''CWASAAvatar'''.
=== GUI Panels ===
* '''CWASAGUI''': A combination of GUI elements, some omitted according to the avatar settings in the configuration.
* '''CWASAAvatar''': A canvas for a WebGL avatar. The canvas fills the size of the enclosing element.
=== GUI Elements ===
* '''CWASAAvMenu''': A menu listing avatars in the expanded '''avList''' for the avatar.
* '''CWASAAmbBox''': A checkbox controlling whether ambient motion is seen for an idle avatar.
* '''CWASASpeed''': Controls for decreasing, increasing, and resetting the speed of animation.
* '''CWASASiGMLURL''': Input to hold a SiGML URL. Omitted by '''CWASAGUI''' if no initial URL is given.
* '''CWASASiGMLText''': Text area for entry of SiGML. Omitted by '''CWASAGUI''' if SiGML text is not allowed.
* '''CWASAPlay''': Play and Stop buttons. Only included if corresponding SiGML URL or Text fields are present.
* '''CWASAPlayExtra''': Suspend and Resume buttons. Only included if Play buttons are present. Omitted by '''CWASAGUI''' if frame steps are not allowed.
* '''CWASAFrames''': Frame single step buttons. Only included if Play buttons are present. Omitted by '''CWASAGUI''' if frame steps are not allowed.
* '''CWASAProgress''': Display of current sign and frame number, sign gloss, and actual FPS.
* '''CWASAStatus''': Display of status information.
=== Bespoke GUI ===
Users are encouraged to use the defined GUI elements as these are not expected to change significantly. Localisation does not require the use of a bespoke GUI.
For details on creating a bespoke GUI, if desired, examine the HTML file '''CWASA-plus-bespoke-gui.html'''.
Essentially, the example shows the HTML generated for GUI elements by CWASA. In order that the CWASA code will link to the GUI HTML elements it is necessary to use the appropriate classes where an avatar code is also given.

Regrettably, some of the low-level GUI elements use classes with names that might clash with those already in use in an existing application.

Some examples illustrate that certain GUI elements, such as buttons, menus, and output fields, can be duplicated. CWASA will copy information to all fields and enable and disable all duplicated buttons.

== CWASA Web Pages ==

To use CWASA, include the following CSS file and JavaScript code, relative to the JASigning installation:
<pre><link rel="stylesheet" href="http://vhg.cmp.uea.ac.uk/tech/jas/vhg2021/cwa/cwasa.css" />
<script type="text/javascript" src="http://vhg.cmp.uea.ac.uk/tech/jas/vhg2021/cwa/allcsa.js"></script></pre>
The method '''CWASA.init();''' should be called on loading the body of the page:
<pre><body onload="CWASA.init();"></pre>
Initial configuration parameters can be specified using a JSON object passed as a parameter to '''CWASA.init''', such
as for example pages using a server or Java applets. To disable ambient animation by default, but use other '''clientcfg.json''' settings:
<pre><body onload="CWASA.init({ambIdle:false,useClientConfig:true});"></pre>
To change the initial camera position and make signing slightly slower:
<pre><body onload="CWASA.init({useClientConfig:true,
avSettings:{initCamera:[0.00,0.53,2.06,-12.50,18.00,30.00,-1.00,-1.00],initSpeed:-1}});"></pre>

All methods to be used are found in the '''CWASA''' object. Examples of direct calls to CWASA are illustrated in the BSLExamples demo mentioned above,
which also illustrates use of a JSON object for initial settings. The methods supported are:
* '''CWASA.init(cfg)''': Initialise CWASA with optional configuration parameters as a JSON object.
* '''CWASA.playSiGMLText(sigtext, av)''': Play SiGML given as text. The avatar panel index is given by the second parameter, defaulting to zero.
* '''CWASA.playSiGMLURL(sigurl, av)''': Play SiGML at given URL. The avatar panel index is given by the second parameter, defaulting to zero.
* '''CWASA.stopSiGML(av)''': Stop playing SiGML. The avatar panel index is given by the parameter, defaulting to zero.
* '''CWASA.getLogger(logger, loggerlevel)''': Configure and receive a CWASA logger.
* '''CWASA.addHook(typ fun, av)''': Install a hook function to be called on specific events for specific avatars.
* '''CWASA.callHook(typ, msg, av)''': Post an event to be passed to appropriate hook functions.

==== Testing for Initialisation ====
A call to '''CWASA.init''' sets up a promise at '''CWASA.ready''' that will be resolved when all the configuration data has been loaded.

To test when an avatar is loaded and rendered, it is possible to add a hook for the '''avatarready''' event. This will be called for each avatar panel and on switching avatars on a panel.

==== Examples ====
Examples of use of these methods will be found on the '''OneAvClientTest.html''' example web page. The logging and event hook facilities are described under [[Logging and Event Hooks]].

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

CWA Signing Avatars

2024-05-19T17:52:42Z

John.Glauert: Add SiGML Tools to CWASA page

[[Main Page|Home]]

----
CWA Signing Avatars, or CWASA, is our virtual signing system that sythesises natural sign language performance using virtual human characters. CWASA supersedes the earlier [[JASigning]] and SiGMLSigning system developed during the ViSiCAST and eSIGN projects.

Further development took place as part of our work on the Dicta-Sign project. CWASA is based on HTML5 using JavaScript and WebGL. The earlier [[JASigning]] system was largely based on using Java JNLP apps for freestanding use and in web pages.

To report issues with CWASA, please see [[JASigning Issue Reporting|Issue Reporting]].

== CWASA Topics ==

* [https://vhg.cmp.uea.ac.uk/tech/jas/std CWASA Standard Release]

* [[CWASA Conditions of Use|Conditions of Use]]

* [[CWASA Release Notes|Release Notes]]

* [[CWASA Platform Issues|Platform Issues]]

* [[CWASA Issue Reporting|Issue Reporting]]

== CWASA Facilities ==
* [[SiGML Tools]]

* [[SiGML Extensions|CWASA SiGML Extensions]]

* [[Driving the SiGML Player App]]

* [[JASigning Local Installation|Local Installation]]

* [[Configuring CWASA for HTML5 web pages|Configuring HTML5 web pages]]

* [[Logging and Event Hooks]]

----

[[Main Page|Home]]

CWASA Release Notes

2024-05-18T11:41:32Z

John.Glauert: Move vhg2024 to vhg2024b

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

= CWA Signing Avatars Release Notes =

From 2021 the standard Open [[CWA Signing Avatars|CWASA]] release, found at
[http://vhg.cmp.uea.ac.uk/tech/jas/std/ http://vhg.cmp.uea.ac.uk/tech/jas/std/],
allows personal, public, and commercial use of the software when accessed, unmodified, from the UEA server. See [[CWASA Conditions of Use|Conditions of Use]].

These notes, and the notes for [[JASigning Release Notes|JASigning]], include Legacy releases with additional avatars and earlier deprecated [[JASigning]] resources. There is also a Development release containing components that cannot be guaranteed to be stable and should only be used for evaluation.

See [[CWA Signing Avatars|CWASA]] for other resources and documentation, including the [[CWASA Local Installation]], a version that can be installed on a localhost web server for evaluation.

Users are welcome to provide feedback via the [[JASigning Issue Reporting|Issue Reporting]] page. Documentation of the system is a work in progress so please send questions and comments to [mailto:cmp_virtualsigning@uea.ac.uk cmp_virtualsigning@uea.ac.uk] so that we can update these pages.

= Table of Contents =

__TOC__

= CWASA Release Notes =

All [[JASigning]] releases before 2021 are available only for evaluation and research, as for the current Legacy and Development releases. The Standard Version is an Open Release which will be based on a Legacy Release but omitting most deprecated software based on Java. The Development Version is a Development Release, potentially containing experimental features.

= CWASA 2024 =

== CWASA 2024 (Standard Version) ==

Open Release found at [//vhg.cmp.uea.ac.uk/tech/jas/vhg2024/ vhg.cmp.uea.ac.uk/tech/jas/vhg2024].

This release is based on the Legacy Release [[#CWASA_2024b_(2024-05)| CWASA 2024b]].

In modern browsers the appearance of the Anna avatar with fully closed eyes is rather dark.
This may have been true for some time and will be investigated when time permits.

== CWASA 2024z (Development Version) ==

Development Release found at [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2024z/ vhg.cmp.uea.ac.uk/tech/jas/vhg2024z].

This release is based on the Legacy Release [[#CWASA_2024b_(2024-05)| CWASA 2024b]].

In modern browsers the appearance of the Anna avatar with fully closed eyes is rather dark.
This may have been true for some time and will be investigated when time permits.

Users are encouraged to try the development release and report any issues encountered.

== CWASA 2024b (2024-05) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2024b/ vhg.cmp.uea.ac.uk/tech/jas/vhg2024b].

These are the main differences between this version and [[#CWASA_2024a_(2024-04)| CWASA 2024a]]:

* Offline transformation of h-SiGML to g-SiGML simplified using Node.js tool installed using npm
* Node.js software using Saxon for XSLT processing

== CWASA 2024a (2024-04) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2024a/ vhg.cmp.uea.ac.uk/tech/jas/vhg2024a].

The release should have the same features as the Legacy Release [[#CWASA_2023a_(2023-06)| CWASA 2023a]].

= CWASA 2023 =

== CWASA 2023 (Standard Version) ==

Open Release found at [//vhg.cmp.uea.ac.uk/tech/jas/vhg2023/ vhg.cmp.uea.ac.uk/tech/jas/vhg2023].

This release is based on the Legacy Release [[#CWASA_2022b_(2022-07)| CWASA 2022b]].

== CWASA 2023z (Development Version) ==

Development Release found at [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2023z/ vhg.cmp.uea.ac.uk/tech/jas/vhg2023z].

This release is based on the Legacy Release [[#CWASA_2023a_(2023-06)| CWASA 2023a]].

Users are encouraged to try the development release and report any issues encountered.

== CWASA 2023a (2023-06) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2023a/ vhg.cmp.uea.ac.uk/tech/jas/vhg2023a].

These are the main differences between this version and [[#CWASA_2022b_(2022-07)| CWASA 2022b]]:

* Electron apps now using better maintained framework using Electron and Vite
* Improved handling of Port 8052 for streamed SiGML data

= CWASA 2022 =

== CWASA 2022 (Standard Version) ==

Open Release found at [//vhg.cmp.uea.ac.uk/tech/jas/vhg2022/ vhg.cmp.uea.ac.uk/tech/jas/vhg2022].

This release is based on the Legacy Release [[#CWASA_2022a_(2022-01)| CWASA 2022a]].

== CWASA 2022z (Development Version) ==

Development Release found at [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2022z/ vhg.cmp.uea.ac.uk/tech/jas/vhg2022z].

This release is based on the Legacy Release [[#CWASA_2022b_(2022-07)| CWASA 2022b]].

Users are encouraged to try the development release and report any issues encountered.

== CWASA 2022b (2022-07) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2022b/ vhg.cmp.uea.ac.uk/tech/jas/vhg2022b].

These are the main differences between this version and [[#CWASA_2022a_(2022-01)| CWASA 2022a]]:

* C++ code for Animgen transpiled with a newer release of Emscripten
* Base directory for SiGML files for JWS apps now based on release installation
* Frame capture for video generation in JWS apps adapts to display resolution for Retina displays
* A new version of the video generation server is documented at [[JASigning Video Generator]]

== CWASA 2022a (2022-01) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2022a/ vhg.cmp.uea.ac.uk/tech/jas/vhg2022a].

This version is the same as [[#CWASA_2021f_(2021-12)| CWASA 2021f]].

= CWASA 2021 =

== CWASA 2021 (Standard Version) ==

Open Release found at [//vhg.cmp.uea.ac.uk/tech/jas/vhg2021/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021].

This release is based on the Legacy Release [[#CWASA_2021f_(2021-12)| CWASA 2021f]].

== CWASA 2021z (Development Version) ==

Development Release found at [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2021z/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021z].

This release is based on the Legacy Release [[#CWASA_2021f_(2021-12)| CWASA 2021f]].

Users are encouraged to try the development release and report any issues encountered.

== CWASA 2021f (2021-12) ==

Legacy Release found at [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2021f/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021f].

These are the main differences between this version and [[#CWASA_2021e_(2021-11)| CWASA 2021e]]:

* Recover from errors in URL specification for SiGML file URL
* Recover from errors in SiGML code from URL or text

== CWASA 2021e (2021-11) ==

Legacy Release found at [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2021e/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021e].

These are the main differences between this version and [[#CWASA_2021d_(2021-09)| CWASA 2021d]]:

* Using just https: URLs to support file: URLs for accessing the release
* Reports changes in camera settings that can later be used to change the initial camera setting
* Reports changes in signing speed that can later be used to change the initial speed setting
* See [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2021e/cwa/OneAvClientTest.html OneAvClientTest.html] for an example

== CWASA 2021d (2021-09) ==

Legacy Release found at [//vhg.cmp.uea.ac.uk/tech/jas/vhg2021d/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021d].

These are the main differences between this version and [[#CWASA_2021c_(2021-02)| CWASA 2021c]]:

* Employs protocol-relative URLs for HTTP and HTTPS support

The UEA server now supports just HTTPS. Older releases will mostly fail. We are, however, able to generate distributions using only HTTP or only HTTPS if required.

== CWASA 2021c (2021-02) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2021c/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021c].

These are the main differences between this version and [[#CWASA_2021b_(2021-01)| CWASA 2021b]]:

* New GUI element '''CWASAAmbBox''' to enable and disable ambient animation when an avatar is idle
* Configuration setting '''ambIdle''' providing default for ambient anumation

== CWASA 2021b (2021-01) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2021b/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021b].

These are the main differences between this version and [[#CWASA_2021a_(2021-01)| CWASA 2021a]]:

* Rearranged build process for Open, Legacy, and Development releases

== CWASA 2021a (2021-01) ==

Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2021a/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021a].

This version is the same as [[JASigning_Release_Notes#JASigning_2020c_(2020-11)|JASigning 2020c]].

= JASigning Release Notes =

See [[JASigning Release Notes]] for information on earlier legacy releases.

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

CWASA Release Notes

2024-05-15T09:29:47Z

John.Glauert: Introduces vhg2024b

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

= CWA Signing Avatars Release Notes =

From 2021 the standard Open [[CWA Signing Avatars|CWASA]] release, found at
[http://vhg.cmp.uea.ac.uk/tech/jas/std/ http://vhg.cmp.uea.ac.uk/tech/jas/std/],
allows personal, public, and commercial use of the software when accessed, unmodified, from the UEA server. See [[CWASA Conditions of Use|Conditions of Use]].

These notes, and the notes for [[JASigning Release Notes|JASigning]], include Legacy releases with additional avatars and earlier deprecated [[JASigning]] resources. There is also a Development release containing components that cannot be guaranteed to be stable and should only be used for evaluation.

See [[CWA Signing Avatars|CWASA]] for other resources and documentation, including the [[CWASA Local Installation]], a version that can be installed on a localhost web server for evaluation.

Users are welcome to provide feedback via the [[JASigning Issue Reporting|Issue Reporting]] page. Documentation of the system is a work in progress so please send questions and comments to [mailto:cmp_virtualsigning@uea.ac.uk cmp_virtualsigning@uea.ac.uk] so that we can update these pages.

= Table of Contents =

__TOC__

= CWASA Release Notes =

All [[JASigning]] releases before 2021 are available only for evaluation and research, as for the current Legacy and Development releases. The Standard Version is an Open Release which will be based on a Legacy Release but omitting most deprecated software based on Java. The Development Version is a Development Release, potentially containing experimental features.

= CWASA 2024 =

== CWASA 2024 (Standard Version) ==

Open Release found at [//vhg.cmp.uea.ac.uk/tech/jas/vhg2024/ vhg.cmp.uea.ac.uk/tech/jas/vhg2024].

This release is based on the Legacy Release [[#CWASA_2023a_(2023-06)| CWASA 2023a]].

In modern browsers the appearance of the Anna avatar with fully closed eyes is rather dark.
This may have been true for some time and will be investigated when time permits.

== CWASA 2024z (Development Version) ==

Development Release found at [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2024z/ vhg.cmp.uea.ac.uk/tech/jas/vhg2024z].

This release is based on the Legacy Release [[#CWASA_2024b_(2024-05)| CWASA 2024b]].

In modern browsers the appearance of the Anna avatar with fully closed eyes is rather dark.
This may have been true for some time and will be investigated when time permits.

Users are encouraged to try the development release and report any issues encountered.

== CWASA 2024b (2024-05) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2024b/ vhg.cmp.uea.ac.uk/tech/jas/vhg2024b].

These are the main differences between this version and [[#CWASA_2024a_(2024-04)| CWASA 2024a]]:

* Offline transformation of h-SiGML to g-SiGML simplified using Node.js tool installed using npm
* Node.js software using Saxon for XSLT processing

== CWASA 2024a (2024-04) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2024a/ vhg.cmp.uea.ac.uk/tech/jas/vhg2024a].

The release should have the same features as the Legacy Release [[#CWASA_2023a_(2023-06)| CWASA 2023a]].

= CWASA 2023 =

== CWASA 2023 (Standard Version) ==

Open Release found at [//vhg.cmp.uea.ac.uk/tech/jas/vhg2023/ vhg.cmp.uea.ac.uk/tech/jas/vhg2023].

This release is based on the Legacy Release [[#CWASA_2022b_(2022-07)| CWASA 2022b]].

== CWASA 2023z (Development Version) ==

Development Release found at [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2023z/ vhg.cmp.uea.ac.uk/tech/jas/vhg2023z].

This release is based on the Legacy Release [[#CWASA_2023a_(2023-06)| CWASA 2023a]].

Users are encouraged to try the development release and report any issues encountered.

== CWASA 2023a (2023-06) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2023a/ vhg.cmp.uea.ac.uk/tech/jas/vhg2023a].

These are the main differences between this version and [[#CWASA_2022b_(2022-07)| CWASA 2022b]]:

* Electron apps now using better maintained framework using Electron and Vite
* Improved handling of Port 8052 for streamed SiGML data

= CWASA 2022 =

== CWASA 2022 (Standard Version) ==

Open Release found at [//vhg.cmp.uea.ac.uk/tech/jas/vhg2022/ vhg.cmp.uea.ac.uk/tech/jas/vhg2022].

This release is based on the Legacy Release [[#CWASA_2022a_(2022-01)| CWASA 2022a]].

== CWASA 2022z (Development Version) ==

Development Release found at [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2022z/ vhg.cmp.uea.ac.uk/tech/jas/vhg2022z].

This release is based on the Legacy Release [[#CWASA_2022b_(2022-07)| CWASA 2022b]].

Users are encouraged to try the development release and report any issues encountered.

== CWASA 2022b (2022-07) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2022b/ vhg.cmp.uea.ac.uk/tech/jas/vhg2022b].

These are the main differences between this version and [[#CWASA_2022a_(2022-01)| CWASA 2022a]]:

* C++ code for Animgen transpiled with a newer release of Emscripten
* Base directory for SiGML files for JWS apps now based on release installation
* Frame capture for video generation in JWS apps adapts to display resolution for Retina displays
* A new version of the video generation server is documented at [[JASigning Video Generator]]

== CWASA 2022a (2022-01) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2022a/ vhg.cmp.uea.ac.uk/tech/jas/vhg2022a].

This version is the same as [[#CWASA_2021f_(2021-12)| CWASA 2021f]].

= CWASA 2021 =

== CWASA 2021 (Standard Version) ==

Open Release found at [//vhg.cmp.uea.ac.uk/tech/jas/vhg2021/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021].

This release is based on the Legacy Release [[#CWASA_2021f_(2021-12)| CWASA 2021f]].

== CWASA 2021z (Development Version) ==

Development Release found at [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2021z/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021z].

This release is based on the Legacy Release [[#CWASA_2021f_(2021-12)| CWASA 2021f]].

Users are encouraged to try the development release and report any issues encountered.

== CWASA 2021f (2021-12) ==

Legacy Release found at [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2021f/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021f].

These are the main differences between this version and [[#CWASA_2021e_(2021-11)| CWASA 2021e]]:

* Recover from errors in URL specification for SiGML file URL
* Recover from errors in SiGML code from URL or text

== CWASA 2021e (2021-11) ==

Legacy Release found at [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2021e/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021e].

These are the main differences between this version and [[#CWASA_2021d_(2021-09)| CWASA 2021d]]:

* Using just https: URLs to support file: URLs for accessing the release
* Reports changes in camera settings that can later be used to change the initial camera setting
* Reports changes in signing speed that can later be used to change the initial speed setting
* See [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2021e/cwa/OneAvClientTest.html OneAvClientTest.html] for an example

== CWASA 2021d (2021-09) ==

Legacy Release found at [//vhg.cmp.uea.ac.uk/tech/jas/vhg2021d/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021d].

These are the main differences between this version and [[#CWASA_2021c_(2021-02)| CWASA 2021c]]:

* Employs protocol-relative URLs for HTTP and HTTPS support

The UEA server now supports just HTTPS. Older releases will mostly fail. We are, however, able to generate distributions using only HTTP or only HTTPS if required.

== CWASA 2021c (2021-02) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2021c/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021c].

These are the main differences between this version and [[#CWASA_2021b_(2021-01)| CWASA 2021b]]:

* New GUI element '''CWASAAmbBox''' to enable and disable ambient animation when an avatar is idle
* Configuration setting '''ambIdle''' providing default for ambient anumation

== CWASA 2021b (2021-01) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2021b/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021b].

These are the main differences between this version and [[#CWASA_2021a_(2021-01)| CWASA 2021a]]:

* Rearranged build process for Open, Legacy, and Development releases

== CWASA 2021a (2021-01) ==

Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2021a/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021a].

This version is the same as [[JASigning_Release_Notes#JASigning_2020c_(2020-11)|JASigning 2020c]].

= JASigning Release Notes =

See [[JASigning Release Notes]] for information on earlier legacy releases.

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

JASigning Platform Issues

2024-04-29T15:09:25Z

John.Glauert: More security notes. Changed http to https.

[[Main Page|Home]] >> [[JASigning]]
----

= Core Software : JavaScript =

== CWA Signing Avatars ==
The core [[CWA Signing Avatars]] software is implemented in JavaScript for HTML5 web pages using WebGL. It functions on most platforms. See [[CWASA Platform Issues]] for details.

= Legacy Software : Java =

A Java Runtime Environment (JRE) must be installed. In the Security settings of the Java Control Panel you may need to add https://vhg.cmp.uea.ac.uk to the Exception Site List.

== Java Web Start ==

JASigning applications and applets are launched using [https://en.wikipedia.org/wiki/Java_Web_Start Java Web Start] through Java Network Launching Protocol (JNLP) files, which have extension <code>.jnlp</code>. Web pages using the more recent JASigning implementation for HTML5 using JavaScript and WebGL is not dependent on JNLP.

The use of JNLP files for applets is deprecated in modern browsers. Where it is supported, it is fairly seamless, but changes to the Java security regime mean that some messages will be seen for the latest release of JASigning with older Java versions.

For applications, launching of Java Web Start is sometimes automatic, but sometimes requires further action. Apple makes it increasingly difficult to deploy components using JNLP so for recent versions of OS X it is necessary to override the default protection regime even though the components are correctly signed. See below for notes on using particular browsers.

== Code Signing ==

JASigning components are digitally signed using a Code Signing Certificate issues by [https://www.globalsign.com/code-signing/ GlobalSign] to [https://www.uea.ac.uk/business/consultancy UEA Consulting Ltd]. Before 2014, certificates were issued to [http://www.sys-consulting.co.uk/ SYS Consulting Limited]. When installing applications or applets, users will be asked to confirm that they trust the publisher. Users can choose to trust the publisher permanently to avoid future confirmation requests.

The certificates have a limited lifetime and have now expired. Unfortunately, it is therefore necessary to ignore security warnings to use the software. Components can still be used if https://vhg.cmp.uea.ac.uk is added to the Exception Site List via the Security tab on the Java control panel.

== Legacy Standalone Applications : Java ==
The security constraints on running Java-based applications mean that the [[CWA Signing Avatars]] applications are strongly preferred. At present, however, some functionality is only available in the Java software.

Java-based applications for the [https://vhg.cmp.uea.ac.uk/tech/jas/std/ current version of JASigning] are intended to run on Windows (XP, Vista, 7, 10) and on the latest releases of OS X 10.5 and later. Java-based JASigning apps are ''not'' supported on Linux. It is preferable to run JASigning with an up-to-date Java 8 run-time (JRE), although it should run with Java 7 and later versions of Java 6.

On the supported platforms, that is, Windows and OS X, JASigning supports both 32-bit and 64-bit operation. Which of this modes it actually runs in on any given occasion depends on several factors:

* Whether or not the processor supports 64-bit operation.
* Whether or not the operating system supports 64-bit operation.
* Whether the system has a 32-bit or a 64-bit Java installation (or both) -- and what options are set in the Java Control Panel (Windows) or Java Preferences app (OS X).
* For a JASigning applet: whether the browser is running in 32-bit or 64-bit mode.

==== Windows ====
[[JASigning|Home]] applications and applets
(apart from the SiGML Service Client) on Windows may require the appropriate
<em>Microsoft Visual Studio C++ 2010 Redistributable Package</em>
to be installed on the system.

On many Windows systems the required Redistributable package will already
have been installed.
But if not, each JASigning application and applet will display a message
at launch time giving the URLs from which the package can easily be
downloaded and installed.
These URLs can be copied from the Java console and pasted into
a web browser.

There is a 32-bit ([https://www.microsoft.com/en-us/download/details.aspx?id=5555 x86]) and a 64-bit ([https://www.microsoft.com/en-us/download/details.aspx?id=14632 x64])
version of the Redistributable package.
One or both of these should be installed, to match the system's
JRE (Java Runtime Environment) installation(s).

==== OS X ====

Before installing and running JASigning applications, the corresponding JNLP file must be downloaded. The application is then launched using Java Web Start. The user will be warned that the application (its JNLP file) has been downloaded from the Internet. The user will also be asked to confirm that they trust the publisher.

Under the default settings for GateKeeper on OS X 10.7.5 Lion and onwards, JASigning applications are blocked from running because they do not come from the App Store or an identified developer. To run blocked applications it is necessary to locate the JNLP file, typically in the Downloads folder, and open it by double-clicking with the control-key down or by right-clicking and choosing ''Open''. On some versions, GateKeeper can be disabled using the General tab of Security & Privacy in the System Preferences.

As documented in [[JASigning Release Notes]], on OS X 10.6 Snow Leopard and later some rendering artefacts can appear with the freestanding SiGML URL Player and SiGML Service Player.

== Legacy Web Applications : Java Applets ==
Support for Java Applets is now minimal and the HTML5 approach should be used wherever possible.

JASigning applets may work with browsers other than those mentioned below, but our testing in such cases is at best limited. Let us know!

==== Windows ====
JASigning web applets should work with '''Internet Explorer'''. The 32-bit (x86) release of Java should be installed.

==== OS X ====
JASigning web applets should work with '''Safari'''.

'''Safari''' will block applets by default but clicking on the avatar display area will allow the applet plug-in to be enabled. '''Safari 7''' and later impose a ''safe'' mode which blocks access to the local disk even though requested by the Java security settings. JASigning will operate in safe mode but will operate more slowly and will not work so well offline as a local cache will be disabled. The Safari Security preferences can be used to disable safe mode for JASigning applets, allowing the local cache to be used.

If GateKeeper is active, launching of applications will be blocked. See the Platforms section above. Even if GateKeeper is disabled: Safari does not consider Java Web Start to be safe so JNLP files may be downloaded to a temporary area and can only be launched by clicking on the icon for the downloaded file in the Downloads window; JNLP files for applications can be downloaded and launched from '''Chrome''' but a warning suggests that JNLP files can be harmful.

----
[[Main Page]] >> [[JASigning]]

JASigning Video Generator

2024-04-29T14:57:52Z

John.Glauert: Updated http to https

'''The software described on this page is © UEA and is for evaluation use only. Please contact the Virtual Humans Group at UEA [mailto:VirtualSigning@cmp.uea.ac.uk VirtualSigning@cmp.uea.ac.uk] if you wish to use this facility for other purposes.'''
 
----
[[Main Page|Home]] >> [[JASigning]]
----

 
== Video Generation using JASigning ==

JASigning is able to generate a video of an animation using a video video generation server application. The server needs to be installed on the same computer system as the main JASigning application being used. Video files are generated as '''.mp4''' files in '''H.264''' format.

This page gives information on installing the Video Generation Server and explains how to use the SiGML Player application to create videos.

An earlier system was based on the Xuggler package which is no longer supported. See [[Xuggler Video Generator]].

== Installing the Video Generation Server ==

* Download the [https://vhg.cmp.uea.ac.uk/tech/jas/vid/javacv-vg-server-1.0-assemble.zip Video Generator installation ZIP file]
* Unpack the ZIP file to a suitable location. It will be unpacked in a folder '''VideoGen'''
* Check (e.g. using the Java Preferences app) that you have a 64-bit Java installation
* If necessary configure the '''run-jas-video-gen-server''' script file for your platform to match the Java installation
* Use of Java has become very restricted. See [[JASigning Platform Issues]]

== Launching the Video Generation Server ==

* Use the '''run-jas-video-gen-server''' script file appropriate to the platform, Mac or Windows, to launch the server
* The server app should launch with a '''Test''' and '''Quit''' button
* '''Test''' runs a test client that uses the server to generate a video from frames held in the '''frames''' subfolder of the VideoGen folder
* '''Quit''' is used to terminate the server

== Using the SiGML Player to Generate Video Files ==

* Once the video generation server is running, a video of an animation can be generated using the Java Web Start SiGML Player app, accessible from https://vhg.cmp.uea.ac.uk/tech/jas/vhg2024a or a more recent Legacy Release found at [[CWASA Release Notes]]
* Use the SiGML Player's <code>File->Video Generation...</code> menu item to generate a video of the most recently played signing animation
* The SiGML Player accomplishes this by transmitting the animation's frame data to the video generation server, which produces the <code>.mp4</code> file
* The SiGML Player should refuse to attempt video generation if it is not feasible, e.g. when there is no current animation, or when the server is not running
* Some videos may be larger than expected due to high resolution displays such as Apple Retina displays

== Configuring the Video Server ==
* The <code>Log</code> checkbox can be used to provide more verbose logging of server operation
* The <code>Video</code> checkbox, selected by default, causes a movie to be generated in a specified location
* The <code>Frames</code> checkbox causes a folder to be created containing a set of <code>PNG</code> images for the frames sent to the server
* Frames are placed in a folder whose name is the same as the movie with ".frames" appended
* Files are created in XML and Java Properties formats recording settings sent to the server: movie name, width and height, frames per second, and frame count

== Adapting the Video Server ==
* The server uses JavaCV, a Java interface to FFmpeg, and has been built with Maven on NetBeans
* The VideoGen folder contains a NetBeans project containing sources and assembly information
* In order to support older MacOSX releases, such as High Sierra, older versions of JavaCV are used
* The Netbeans project should assemble a new installation ZIP file but may fail to run the server directly from NetBeans
 
----
[[Main Page|Home]] >> [[JASigning]]

CWASA Release Notes

2024-04-29T14:47:40Z

John.Glauert: Introduces vhg2024a

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

= CWA Signing Avatars Release Notes =

From 2021 the standard Open [[CWA Signing Avatars|CWASA]] release, found at
[http://vhg.cmp.uea.ac.uk/tech/jas/std/ http://vhg.cmp.uea.ac.uk/tech/jas/std/],
allows personal, public, and commercial use of the software when accessed, unmodified, from the UEA server. See [[CWASA Conditions of Use|Conditions of Use]].

These notes, and the notes for [[JASigning Release Notes|JASigning]], include Legacy releases with additional avatars and earlier deprecated [[JASigning]] resources. There is also a Development release containing components that cannot be guaranteed to be stable and should only be used for evaluation.

See [[CWA Signing Avatars|CWASA]] for other resources and documentation, including the [[CWASA Local Installation]], a version that can be installed on a localhost web server for evaluation.

Users are welcome to provide feedback via the [[JASigning Issue Reporting|Issue Reporting]] page. Documentation of the system is a work in progress so please send questions and comments to [mailto:cmp_virtualsigning@uea.ac.uk cmp_virtualsigning@uea.ac.uk] so that we can update these pages.

= Table of Contents =

__TOC__

= CWASA Release Notes =

All [[JASigning]] releases before 2021 are available only for evaluation and research, as for the current Legacy and Development releases. The Standard Version is an Open Release which will be based on a Legacy Release but omitting most deprecated software based on Java. The Development Version is a Development Release, potentially containing experimental features.

= CWASA 2024 =

== CWASA 2024 (Standard Version) ==

Open Release found at [//vhg.cmp.uea.ac.uk/tech/jas/vhg2024/ vhg.cmp.uea.ac.uk/tech/jas/vhg2024].

This release is based on the Legacy Release [[#CWASA_2023a_(2023-06)| CWASA 2023a]].

In modern browsers the appearance of the Anna avatar with fully closed eyes is rather dark.
This may have been true for some time and will be investigated when time permits.

== CWASA 2024z (Development Version) ==

Development Release found at [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2024z/ vhg.cmp.uea.ac.uk/tech/jas/vhg2024z].

This release is based on the Legacy Release [[#CWASA_2023a_(2023-06)| CWASA 2023a]].

In modern browsers the appearance of the Anna avatar with fully closed eyes is rather dark.
This may have been true for some time and will be investigated when time permits.

Users are encouraged to try the development release and report any issues encountered.

== CWASA 2024a (2024-04) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2024a/ vhg.cmp.uea.ac.uk/tech/jas/vhg2024a].

The release should have the same features as the Legacy Release [[#CWASA_2023a_(2023-06)| CWASA 2023a]].

= CWASA 2023 =

== CWASA 2023 (Standard Version) ==

Open Release found at [//vhg.cmp.uea.ac.uk/tech/jas/vhg2023/ vhg.cmp.uea.ac.uk/tech/jas/vhg2023].

This release is based on the Legacy Release [[#CWASA_2022b_(2022-07)| CWASA 2022b]].

== CWASA 2023z (Development Version) ==

Development Release found at [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2023z/ vhg.cmp.uea.ac.uk/tech/jas/vhg2023z].

This release is based on the Legacy Release [[#CWASA_2023a_(2023-06)| CWASA 2023a]].

Users are encouraged to try the development release and report any issues encountered.

== CWASA 2023a (2023-06) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2023a/ vhg.cmp.uea.ac.uk/tech/jas/vhg2023a].

These are the main differences between this version and [[#CWASA_2022b_(2022-07)| CWASA 2022b]]:

* Electron apps now using better maintained framework using Electron and Vite
* Improved handling of Port 8052 for streamed SiGML data

= CWASA 2022 =

== CWASA 2022 (Standard Version) ==

Open Release found at [//vhg.cmp.uea.ac.uk/tech/jas/vhg2022/ vhg.cmp.uea.ac.uk/tech/jas/vhg2022].

This release is based on the Legacy Release [[#CWASA_2022a_(2022-01)| CWASA 2022a]].

== CWASA 2022z (Development Version) ==

Development Release found at [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2022z/ vhg.cmp.uea.ac.uk/tech/jas/vhg2022z].

This release is based on the Legacy Release [[#CWASA_2022b_(2022-07)| CWASA 2022b]].

Users are encouraged to try the development release and report any issues encountered.

== CWASA 2022b (2022-07) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2022b/ vhg.cmp.uea.ac.uk/tech/jas/vhg2022b].

These are the main differences between this version and [[#CWASA_2022a_(2022-01)| CWASA 2022a]]:

* C++ code for Animgen transpiled with a newer release of Emscripten
* Base directory for SiGML files for JWS apps now based on release installation
* Frame capture for video generation in JWS apps adapts to display resolution for Retina displays
* A new version of the video generation server is documented at [[JASigning Video Generator]]

== CWASA 2022a (2022-01) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2022a/ vhg.cmp.uea.ac.uk/tech/jas/vhg2022a].

This version is the same as [[#CWASA_2021f_(2021-12)| CWASA 2021f]].

= CWASA 2021 =

== CWASA 2021 (Standard Version) ==

Open Release found at [//vhg.cmp.uea.ac.uk/tech/jas/vhg2021/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021].

This release is based on the Legacy Release [[#CWASA_2021f_(2021-12)| CWASA 2021f]].

== CWASA 2021z (Development Version) ==

Development Release found at [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2021z/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021z].

This release is based on the Legacy Release [[#CWASA_2021f_(2021-12)| CWASA 2021f]].

Users are encouraged to try the development release and report any issues encountered.

== CWASA 2021f (2021-12) ==

Legacy Release found at [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2021f/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021f].

These are the main differences between this version and [[#CWASA_2021e_(2021-11)| CWASA 2021e]]:

* Recover from errors in URL specification for SiGML file URL
* Recover from errors in SiGML code from URL or text

== CWASA 2021e (2021-11) ==

Legacy Release found at [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2021e/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021e].

These are the main differences between this version and [[#CWASA_2021d_(2021-09)| CWASA 2021d]]:

* Using just https: URLs to support file: URLs for accessing the release
* Reports changes in camera settings that can later be used to change the initial camera setting
* Reports changes in signing speed that can later be used to change the initial speed setting
* See [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2021e/cwa/OneAvClientTest.html OneAvClientTest.html] for an example

== CWASA 2021d (2021-09) ==

Legacy Release found at [//vhg.cmp.uea.ac.uk/tech/jas/vhg2021d/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021d].

These are the main differences between this version and [[#CWASA_2021c_(2021-02)| CWASA 2021c]]:

* Employs protocol-relative URLs for HTTP and HTTPS support

The UEA server now supports just HTTPS. Older releases will mostly fail. We are, however, able to generate distributions using only HTTP or only HTTPS if required.

== CWASA 2021c (2021-02) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2021c/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021c].

These are the main differences between this version and [[#CWASA_2021b_(2021-01)| CWASA 2021b]]:

* New GUI element '''CWASAAmbBox''' to enable and disable ambient animation when an avatar is idle
* Configuration setting '''ambIdle''' providing default for ambient anumation

== CWASA 2021b (2021-01) ==

Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2021b/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021b].

These are the main differences between this version and [[#CWASA_2021a_(2021-01)| CWASA 2021a]]:

* Rearranged build process for Open, Legacy, and Development releases

== CWASA 2021a (2021-01) ==

Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2021a/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021a].

This version is the same as [[JASigning_Release_Notes#JASigning_2020c_(2020-11)|JASigning 2020c]].

= JASigning Release Notes =

See [[JASigning Release Notes]] for information on earlier legacy releases.

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

Driving the SiGML Player App

2024-04-29T14:33:48Z

John.Glauert:

[[Main Page|Home]] >> [[CWA Signing Avatars|CWASA]]
----
This page describes the protocol a client app needs to follow in order to drive the SiGML Player app which is part of the [https://vhg.cmp.uea.ac.uk/tech/jas/std CWASA Standard Release]. The application is based on Electron and Node.js.

The page also provides a simple Java application that uses the protocol. The same protpcol is used for the [[JASigning]] SiGML Service Player app.

== Protocol ==

The SiGML Player accepts connection requests on standard TCP/IP port number 8052.

Each time the client wants to dispatch a SiGML text to the player it performs the following sequence:

* Make a new connection to that port (8052) on the server, i.e. the host system running the SiGML Player app, which may or may not be the "localhost".

* Send the SiGML text on the resulting output stream.
** If the SiGML text explicitly specifies an encoding in an initial XML declaration then the text should be sent as a byte stream with that encoding.
** If there's no explicit encoding it should be sent as a UTF-8 stream.

* Close the stream and the connection.

The protocol is extremely simple: so there's no feedback from the server to tell the client when the performance of a SiGML text is complete -- or indeed whether there are any errors in the SiGML text.

If a new text is dispatched before performance of the previous one is complete, then that previous performance is immediately abandoned in favour of the new one.
So, although in principle the client could be on the opposite side of the world from the server, in practice it does not make much sense if the client, i.e. its user, does not actually have line-of-sight contact with the server.

== Unix Commandline Scripting ==

On Unix systems, including OS X and Linux, or using Cygwin on Windows, the command:
nc localhost 8052 < mySigns.sigml
will send SiGML data to the application. The parameter -N may be needed to close the socket on EOF. Alternatively, the form
nc localhost 8052 -w 0 < mySigns.sigml
should work on all platforms

== Example Java Application ==

A NetBeans project for a simple Java application is available as a ZIP archive for the [http://vhg.cmp.uea.ac.uk/tech/tools/SignStreamer.zip SignStreamer Project].

* The '''src''' folder contains Java source files
* The '''dist''' folder contains '''SignStreamer.jar''' for the application
* The application can be run by the command <code>java -jar "SignStreamer.jar"</code>
* A SiGML file to be sent is selected by clicking the '''Select File''' button and sent using the '''Send File''' button

The code can be adapted or incorporated in your own code but please acknowledge the source.

== Other Applications ==

Various [[SiGML Tools]] send SiGML data to the SiGML Player.

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

Driving the SiGML Player App

2024-04-29T14:26:19Z

John.Glauert: Add link to other SiGML Tools

[[Main Page|Home]] >> [[CWA Signing Avatars|CWASA]]
----
This page describes the protocol a client app needs to follow in order to drive the SiGML Player app and provides a simple Java application that uses the protocol. The same protpcol is used for the [[JASigning]] SiGML Service Player app.

== Protocol ==

The SiGML Player accepts connection requests on standard TCP/IP port number 8052.

Each time the client wants to dispatch a SiGML text to the player it performs the following sequence:

* Make a new connection to that port (8052) on the server, i.e. the host system running the SiGML Player app, which may or may not be the "localhost".

* Send the SiGML text on the resulting output stream.
** If the SiGML text explicitly specifies an encoding in an initial XML declaration then the text should be sent as a byte stream with that encoding.
** If there's no explicit encoding it should be sent as a UTF-8 stream.

* Close the stream and the connection.

The protocol is extremely simple: so there's no feedback from the server to tell the client when the performance of a SiGML text is complete -- or indeed whether there are any errors in the SiGML text.

If a new text is dispatched before performance of the previous one is complete, then that previous performance is immediately abandoned in favour of the new one.
So, although in principle the client could be on the opposite side of the world from the server, in practice it does not make much sense if the client, i.e. its user, does not actually have line-of-sight contact with the server.

== Unix Commandline Scripting ==

On Unix systems, including OS X and Linux, or using Cygwin on Windows, the command:
nc localhost 8052 < mySigns.sigml
will send SiGML data to the application. The parameter -N may be needed to close the socket on EOF. Alternatively, the form
nc localhost 8052 -w 0 < mySigns.sigml
should work on all platforms

== Applications ==

Various [[SiGML Tools]] send SiGML data to the SiGML Player.

== Example Java Application ==

A NetBeans project for a simple Java application is available as a ZIP archive for the [http://vhg.cmp.uea.ac.uk/tech/tools/SignStreamer.zip SignStreamer Project].

* The '''src''' folder contains Java source files
* The '''dist''' folder contains '''SignStreamer.jar''' for the application
* The application can be run by the command <code>java -jar "SignStreamer.jar"</code>
* A SiGML file to be sent is selected by clicking the '''Select File''' button and sent using the '''Send File''' button

The code can be adapted or incorporated in your own code but please acknowledge the source.

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

CWA Signing Avatars

2024-04-29T14:22:05Z

John.Glauert:

[[Main Page|Home]]

----
CWA Signing Avatars, or CWASA, is our virtual signing system that sythesises natural sign language performance using virtual human characters. CWASA supersedes the earlier [[JASigning]] and SiGMLSigning system developed during the ViSiCAST and eSIGN projects.

Further development took place as part of our work on the Dicta-Sign project. CWASA is based on HTML5 using JavaScript and WebGL. The earlier [[JASigning]] system was largely based on using Java JNLP apps for freestanding use and in web pages.

To report issues with CWASA, please see [[JASigning Issue Reporting|Issue Reporting]].

== CWASA Topics ==

* [https://vhg.cmp.uea.ac.uk/tech/jas/std CWASA Standard Release]

* [[CWASA Conditions of Use|Conditions of Use]]

* [[CWASA Release Notes|Release Notes]]

* [[CWASA Platform Issues|Platform Issues]]

* [[CWASA Issue Reporting|Issue Reporting]]

== CWASA Facilities ==
* [[SiGML Extensions|CWASA SiGML Extensions]]

* [[Driving the SiGML Player App]]

* [[JASigning Local Installation|Local Installation]]

* [[Configuring CWASA for HTML5 web pages|Configuring HTML5 web pages]]

* [[Logging and Event Hooks]]

----

[[Main Page|Home]]

SiGML Tools

2024-04-29T11:47:45Z

John.Glauert: /* Ham2HPSG Tool */

[[Main Page|Home]]
----

A number of tools are available for creating and editing [[SiGML]] data to represent signing gestures. As [[SiGML]] is based on [[HamNoSys]], many of these allow entry using the
[https://vhg.cmp.uea.ac.uk/tech/hamnosys/HamNoSysUnicode.ttf HamNoSys Unicode font].

== [[CWA Signing Avatars|CWASA]] SiGML Player ==

The CWASA SiGML Player animates [[SiGML]] data sent to it over TCP sockets. See [[Driving the SiGML Player App]]. The application, or the legacy [[JASigning]] SiGML Service Player, can be used in conjunction with the [[JASigning]] SiGML Service Client
and other SiGML Tools mentioned below.

== [https://vhg.cmp.uea.ac.uk/tech/hamnosys/HamNoSysUnicode.ttf HamNoSysUnicode.ttf] ==

HamNoSys Unicode font as a TrueType font that should be installed in the usual way on systems using [[HamNoSys]].

== [[JASigning]] SiGML Service Client ==

Displays and allows Editing of [[SiGML]] files.
* Mac and PC tool
* Install the [https://vhg.cmp.uea.ac.uk/tech/hamnosys/HamNoSysUnicode.ttf HamNoSysUnicode.ttf]
* Sends [[SiGML]] data to a SiGML Player

== [https://vhg.cmp.uea.ac.uk/tech/ham2hpsg/Ham2HPSG22.zip Ham2HPSG Tool] ==

* Tool for entering [[HamNoSys]] on PC
* Mac Tool included for legacy (pre Mac OS X) Classic environment
* Sends [[SiGML]] data to a SiGML Player
* "..." button brings up [[HamNoSys]] entry panels
* Down Arrow button prepares [[HamNoSys]] for animation
* "V!" button sends data to player
* Limited documentation in Ham2HPSG ReadMe.txt file
* Download [https://vhg.cmp.uea.ac.uk/tech/ham2hpsg/Ham2HPSG22.zip Ham2HPSG Tool]

== [https://vhg.cmp.uea.ac.uk/tech/esigneditor/eSignEditor.zip eSIGN Editor] ==
The eSIGN Editor was developed for the [[eSIGN]] project at the IDGS, University of Hamburg.
See [https://www.sign-lang.uni-hamburg.de/dgs-korpus/index.php/welcome.html DGS Corpus] project for contacts with the authors of this tool.

* Mac and PC tool for creating [[SiGML]] signs
* Maintains a database of signs in [[HamNoSys]] notation
* Allows creation and modification of signing sequences
* Allows animation of signing sequences using a SiGML Player
* Limited documentation through [https://vhg.cmp.uea.ac.uk/tech/esigneditor/eSIGN-D23rev2.pdf Editor Manual]
* A [https://vhg.cmp.uea.ac.uk/tech/esigneditor/eSIGN%20Editor.exe Windows Installer] for an older version exists
** The installer creates Shortcuts and Start Menu items
** It appears safe to replace installed files with newer ones from [https://vhg.cmp.uea.ac.uk/tech/esigneditor/eSignEditor.zip eSIGN Editor Zip]
** The PC application must be renamed for the shortcuts to work
* Download [http://vhg.cmp.uea.ac.uk/tech/esigneditor/eSignEditor.zip eSIGN Editor]

== Manual HamNoSys/SiGML Conversion Tools ==

Ralph Elliott has produced some simple tools to convert different forms of manual HamNoSys, and to do a bit of related SiGML processing. They are limited in various ways, but they could be useful to others:

* [https://vhg.cmp.uea.ac.uk/tech/hamnosys/convert/hns-sigml-convert-2011-04-12.zip Executables, source code and Javadoc], Java classes plus shell and Python scripts.<br>Includes a README file explaining roughly what's on offer and how to use it.<br>'''Original 2010-11-05''', '''Updated 2010-12-07''', '''2011-01-19''' and '''2011-04-12'''

If you want to do some conversion not provided by these tools, you're welcome to modify them to suit your needs, but in some cases it may prove easier to augment them by writing a suitable bit of python or perl. We request that you share any tools developed from this package in the same way.

The HNS characters, their <tt>ham..</tt>names and the numeric encodings used for them can be seen using this
[http://vhg.cmp.uea.ac.uk/tech/hamnosys/convert/HNS-Table-App.jar HNS Table App].
To run it, double-click its jar file after downloading.

----
[[Main Page|Home]]

SiGML Tools

2024-04-29T11:45:50Z

John.Glauert: Change http URLs to https

[[Main Page|Home]]
----

A number of tools are available for creating and editing [[SiGML]] data to represent signing gestures. As [[SiGML]] is based on [[HamNoSys]], many of these allow entry using the
[https://vhg.cmp.uea.ac.uk/tech/hamnosys/HamNoSysUnicode.ttf HamNoSys Unicode font].

== [[CWA Signing Avatars|CWASA]] SiGML Player ==

The CWASA SiGML Player animates [[SiGML]] data sent to it over TCP sockets. See [[Driving the SiGML Player App]]. The application, or the legacy [[JASigning]] SiGML Service Player, can be used in conjunction with the [[JASigning]] SiGML Service Client
and other SiGML Tools mentioned below.

== [https://vhg.cmp.uea.ac.uk/tech/hamnosys/HamNoSysUnicode.ttf HamNoSysUnicode.ttf] ==

HamNoSys Unicode font as a TrueType font that should be installed in the usual way on systems using [[HamNoSys]].

== [[JASigning]] SiGML Service Client ==

Displays and allows Editing of [[SiGML]] files.
* Mac and PC tool
* Install the [https://vhg.cmp.uea.ac.uk/tech/hamnosys/HamNoSysUnicode.ttf HamNoSysUnicode.ttf]
* Sends [[SiGML]] data to a SiGML Player

== [http://vhg.cmp.uea.ac.uk/tech/ham2hpsg/Ham2HPSG22.zip Ham2HPSG Tool] ==

* Tool for entering [[HamNoSys]] on PC
* Mac Tool included for legacy (pre Mac OS X) Classic environment
* Sends [[SiGML]] data to a SiGML Player
* "..." button brings up [[HamNoSys]] entry panels
* Down Arrow button prepares [[HamNoSys]] for animation
* "V!" button sends data to player
* Limited documentation in Ham2HPSG ReadMe.txt file
* Download [https://vhg.cmp.uea.ac.uk/tech/ham2hpsg/Ham2HPSG22.zip Ham2HPSG Tool]

== [https://vhg.cmp.uea.ac.uk/tech/esigneditor/eSignEditor.zip eSIGN Editor] ==
The eSIGN Editor was developed for the [[eSIGN]] project at the IDGS, University of Hamburg.
See [https://www.sign-lang.uni-hamburg.de/dgs-korpus/index.php/welcome.html DGS Corpus] project for contacts with the authors of this tool.

* Mac and PC tool for creating [[SiGML]] signs
* Maintains a database of signs in [[HamNoSys]] notation
* Allows creation and modification of signing sequences
* Allows animation of signing sequences using a SiGML Player
* Limited documentation through [https://vhg.cmp.uea.ac.uk/tech/esigneditor/eSIGN-D23rev2.pdf Editor Manual]
* A [https://vhg.cmp.uea.ac.uk/tech/esigneditor/eSIGN%20Editor.exe Windows Installer] for an older version exists
** The installer creates Shortcuts and Start Menu items
** It appears safe to replace installed files with newer ones from [https://vhg.cmp.uea.ac.uk/tech/esigneditor/eSignEditor.zip eSIGN Editor Zip]
** The PC application must be renamed for the shortcuts to work
* Download [http://vhg.cmp.uea.ac.uk/tech/esigneditor/eSignEditor.zip eSIGN Editor]

== Manual HamNoSys/SiGML Conversion Tools ==

Ralph Elliott has produced some simple tools to convert different forms of manual HamNoSys, and to do a bit of related SiGML processing. They are limited in various ways, but they could be useful to others:

* [https://vhg.cmp.uea.ac.uk/tech/hamnosys/convert/hns-sigml-convert-2011-04-12.zip Executables, source code and Javadoc], Java classes plus shell and Python scripts.<br>Includes a README file explaining roughly what's on offer and how to use it.<br>'''Original 2010-11-05''', '''Updated 2010-12-07''', '''2011-01-19''' and '''2011-04-12'''

If you want to do some conversion not provided by these tools, you're welcome to modify them to suit your needs, but in some cases it may prove easier to augment them by writing a suitable bit of python or perl. We request that you share any tools developed from this package in the same way.

The HNS characters, their <tt>ham..</tt>names and the numeric encodings used for them can be seen using this
[http://vhg.cmp.uea.ac.uk/tech/hamnosys/convert/HNS-Table-App.jar HNS Table App].
To run it, double-click its jar file after downloading.

----
[[Main Page|Home]]

SiGML Tools

2024-04-26T18:47:07Z

John.Glauert: Additional detail

[[Main Page|Home]]
----

A number of tools are available for creating and editing [[SiGML]] data to represent signing gestures. As [[SiGML]] is based on [[HamNoSys]], many of these allow entry using the
[http://vhg.cmp.uea.ac.uk/tech/hamnosys/HamNoSysUnicode.ttf HamNoSys Unicode font].

== [[CWA Signing Avatars|CWASA]] SiGML Player ==

The CWASA SiGML Player animates [[SiGML]] data sent to it over TCP sockets. See [[Driving the SiGML Player App]]. The application, or the legacy [[JASigning]] SiGML Service Player, can be used in conjunction with the [[JASigning]] SiGML Service Client
and other SiGML Tools mentioned below.

== [http://vhg.cmp.uea.ac.uk/tech/hamnosys/HamNoSysUnicode.ttf HamNoSysUnicode.ttf] ==

HamNoSys Unicode font as a TrueType font that should be installed in the usual way on systems using [[HamNoSys]].

== [[JASigning]] SiGML Service Client ==

Displays and allows Editing of [[SiGML]] files.
* Mac and PC tool
* Install the [http://vhg.cmp.uea.ac.uk/tech/hamnosys/HamNoSysUnicode.ttf HamNoSysUnicode.ttf]
* Sends [[SiGML]] data to a SiGML Player.

== [http://vhg.cmp.uea.ac.uk/tech/ham2hpsg/Ham2HPSG22.zip Ham2HPSG Tool] ==

* Mac and PC tool for entering [[HamNoSys]].
* Sends [[SiGML]] data to a SiGML Player.
* "..." button brings up [[HamNoSys]] entry panels.
* Down Arrow button prepares [[HamNoSys]] for animation.
* "V!" button sends data to player.
* Limited documentation in Ham2HPSG ReadMe.txt file.
* Download [http://vhg.cmp.uea.ac.uk/tech/ham2hpsg/Ham2HPSG22.zip Ham2HPSG Tool].

== [http://vhg.cmp.uea.ac.uk/tech/esigneditor/eSignEditor.zip eSIGN Editor] ==
The eSIGN Editor was developed for the [[eSIGN]] project at the IDGS, University of Hamburg.
See [https://www.sign-lang.uni-hamburg.de/dgs-korpus/index.php/welcome.html DGS Corpus] project for contacts with the authors of this tool.

* Mac and PC tool for creating [[SiGML]] signs.
* Maintains a database of signs in [[HamNoSys]] notation.
* Allows creation and modification of signing sequences.
* Allows animation of signing sequences using a SiGML Player.
* Limited documentation through [http://vhg.cmp.uea.ac.uk/tech/esigneditor/eSIGN-D23rev2.pdf Editor Manual].
* A [http://vhg.cmp.uea.ac.uk/tech/esigneditor/eSIGN%20Editor.exe Windows Installer] for an older version exists.
** The installer creates Shortcuts and Start Menu items.
** It appears safe to replace installed files with newer ones from [http://vhg.cmp.uea.ac.uk/tech/esigneditor/eSignEditor.zip eSIGN Editor Zip].
** The PC application must be renamed for the shortcuts to work.
* Download [http://vhg.cmp.uea.ac.uk/tech/esigneditor/eSignEditor.zip eSIGN Editor].

== Manual HamNoSys/SiGML Conversion Tools ==

Ralph Elliott has produced some simple tools to convert different forms of manual HamNoSys, and to do a bit of related SiGML processing. They are limited in various ways, but they could be useful to others:

* [http://vhg.cmp.uea.ac.uk/tech/hamnosys/convert/hns-sigml-convert-2011-04-12.zip Executables, source code and Javadoc], Java classes plus shell and Python scripts.<br>Includes a README file explaining roughly what's on offer and how to use it.<br>'''Original 2010-11-05''', '''Updated 2010-12-07''', '''2011-01-19''' and '''2011-04-12'''.

If you want to do some conversion not provided by these tools, you're welcome to modify them to suit your needs, but in some cases it may prove easier to augment them by writing a suitable bit of python or perl. We request that you share any tools developed from this package in the same way.

The HNS characters, their <tt>ham..</tt>names and the numeric encodings used for them can be seen using this
[http://vhg.cmp.uea.ac.uk/tech/hamnosys/convert/HNS-Table-App.jar HNS Table App].
To run it, double-click its jar file after downloading.

----
[[Main Page|Home]]

SiGML Tools

2024-04-26T17:34:17Z

John.Glauert: /* CWASA SiGML Player */

[[Main Page|Home]]
----

A number of tools are available for creating and editing [[SiGML]] data to represent signing gestures. As [[SiGML]] is based on [[HamNoSys]], many of these allow entry using the
[http://vhg.cmp.uea.ac.uk/tech/hamnosys/HamNoSysUnicode.ttf HamNoSys Unicode font].

== [[CWA Signing Avatars|CWASA]] SiGML Player ==

The CWASA SiGML Player animates [[SiGML]] data sent to it over TCP sockets. See [[Driving the SiGML Player App]]. The application, or the legacy [[JASigning]] SiGML Service Player, can be used in conjunction with the [[JASigning]] SiGML Service Client
and other SiGML Tools mentioned below.

== [http://vhg.cmp.uea.ac.uk/tech/hamnosys/HamNoSysUnicode.ttf HamNoSysUnicode.ttf] ==

HamNoSys Unicode font as a TrueType font that should be installed in the usual way on systems using [[HamNoSys]].

== [[JASigning]] SiGML Service Client ==

Displays and allows Editing of [[SiGML]] files in conjunction with a SiGML Player.

== [http://vhg.cmp.uea.ac.uk/tech/ham2hpsg/Ham2HPSG22.zip Ham2HPSG Tool] ==

* Mac and PC tool for entering [[HamNoSys]].
* Sends [[SiGML]] data to a SiGML Player.
* "..." button brings up [[HamNoSys]] entry panels.
* Down Arrow button prepares [[HamNoSys]] for animation.
* "V!" button sends data to player.
* Limited documentation in Ham2HPSG ReadMe.txt file.
* Download [http://vhg.cmp.uea.ac.uk/tech/ham2hpsg/Ham2HPSG22.zip Ham2HPSG Tool].

== [http://vhg.cmp.uea.ac.uk/tech/esigneditor/eSignEditor.zip eSIGN Editor] ==
The eSIGN Editor was developed for the [[eSIGN]] project at the IDGS, University of Hamburg.
See [https://www.sign-lang.uni-hamburg.de/dgs-korpus/index.php/welcome.html DGS Corpus] project for contacts with the authors of this tool.

* Mac and PC tool for creating [[SiGML]] signs.
* Maintains a database of signs in [[HamNoSys]] notation.
* Allows creation and modification of signing sequences.
* Allows animation of signing sequences using a SiGML Player.
* Limited documentation through [http://vhg.cmp.uea.ac.uk/tech/esigneditor/eSIGN-D23rev2.pdf Editor Manual].
* A [http://vhg.cmp.uea.ac.uk/tech/esigneditor/eSIGN%20Editor.exe Windows Installer] for an older version exists.
** The installer creates Shortcuts and Start Menu items.
** It appears safe to replace installed files with newer ones from [http://vhg.cmp.uea.ac.uk/tech/esigneditor/eSignEditor.zip eSIGN Editor Zip].
** The PC application must be renamed for the shortcuts to work.
* Download [http://vhg.cmp.uea.ac.uk/tech/esigneditor/eSignEditor.zip eSIGN Editor].

== Manual HamNoSys/SiGML Conversion Tools ==

Ralph Elliott has produced some simple tools to convert different forms of manual HamNoSys, and to do a bit of related SiGML processing. They are limited in various ways, but they could be useful to others:

* [http://vhg.cmp.uea.ac.uk/tech/hamnosys/convert/hns-sigml-convert-2011-04-12.zip Executables, source code and Javadoc], Java classes plus shell and Python scripts.<br>Includes a README file explaining roughly what's on offer and how to use it.<br>'''Original 2010-11-05''', '''Updated 2010-12-07''', '''2011-01-19''' and '''2011-04-12'''.

If you want to do some conversion not provided by these tools, you're welcome to modify them to suit your needs, but in some cases it may prove easier to augment them by writing a suitable bit of python or perl. We request that you share any tools developed from this package in the same way.

The HNS characters, their <tt>ham..</tt>names and the numeric encodings used for them can be seen using this
[http://vhg.cmp.uea.ac.uk/tech/hamnosys/convert/HNS-Table-App.jar HNS Table App].
To run it, double-click its jar file after downloading.

----
[[Main Page|Home]]

CWASA Release Notes

2024-01-18T17:02:39Z

John.Glauert: Introduces vhg2024. Notes issues with dark closed eyes for Anna.

CWA Signing Avatars

2023-06-30T16:35:25Z

John.Glauert: Add SiGML Extensions

[[Main Page|Home]]

----
CWA Signing Avatars, or CWASA, is our virtual signing system that sythesises natural sign language performance using virtual human characters. CWASA supersedes the earlier [[JASigning]] and SiGMLSigning system developed during the ViSiCAST and eSIGN projects.

Further development took place as part of our work on the Dicta-Sign project. CWASA is based on HTML5 using JavaScript and WebGL. The earlier [[JASigning]] system was largely based on using Java JNLP apps for freestanding use and in web pages.

To report issues with CWASA, please use the [[JASigning Issue Reporting|Issue Reporting]] page.

== CWASA Topics ==

* [https://vhg.cmp.uea.ac.uk/tech/jas/std CWASA Standard Release]

* [[CWASA Conditions of Use|Conditions of Use]]

* [[CWASA Release Notes|Release Notes]]

* [[CWASA Platform Issues|Platform Issues]]

* [[CWASA Issue Reporting|Issue Reporting]]

== CWASA Facilities ==
* [[SiGML Extensions|CWASA SiGML Extensions]]

* [[Driving the SiGML Player App]]

* [[JASigning Local Installation|Local Installation]]

* [[Configuring CWASA for HTML5 web pages|Configuring HTML5 web pages]]

* [[Logging and Event Hooks]]

----

[[Main Page|Home]]

SiGML Extensions

2023-06-30T16:33:41Z

John.Glauert: To be edited for CWASA extensions.

[[Main Page]] >> [[CWASA]]

----
In progress: Revision for CWASA extensions.
= Player Settings =
A number of extensions to [[SiGML]] are available when using [[JASigning]] to animate SiGML data. These enable some actions of the player to be scripted with a SiGML file.
The current extensions are provided by adding a <code><player_settings\></code> element between signs in the SiGML file. The extensions act on the following sign so extensions at the end of a file will be ignored.

The <code><player_settings\></code> element encloses one or more settings elements. If several settings elements are provided before a sign, later settings override earlier ones.

== Camera Settings ==
The camera location is controlled by eight parameters that can be provided in a <code>.properties</code> file or an app <code><argument/></code> or applet <code><param/></code>. Changes to the settings caused by use of the mouse with modifier keys are reflected on the Java Console Log and can be copied to use as initial camera settings.

The first six camera settings can be changed during the course of playing a SiGML file with <code><player_settings/></code> as in the following example:
<player_settings>
<camera_location cx="0.00" cy="0.50" r="4.50" theta="30.0" phi="40.0" fov="30.0"/>
</player_settings>

== Sign Timing ==
The starting time for a sign can be set using a <code><time/></code> element with an attribute saying when the sign should begin, expressed in seconds since the start of the sequence. If the time specified has already passed, the following sign will play immediately.
<player_settings>
<time begin="3.5"/>
</player_settings>
It is possible to provide a <code>mode</code> attribute to say whether the avatar should got to <code>"rest"</code> until the given time is reached (the default), or whether to <code>"hold"</code> the final posture of the previous sign:
<player_settings>
<time begin="4.5" mode="hold"/>
</player_settings>

== Avatar Choice ==
[[JASigning]] accepts commands to switch between avatars through menu choices, through messages on a special socket for the SiGML Service Player app, and through
<code><player_settings/></code> in SiGML files.
<player_settings>
<avatar name="marc"/>
</player_settings>

== Ambient Motion Settings ==
The [[JASigning]] software accepts <code><player_settings/></code> to control the ambient motion behaviour. However, these settings refer to features of older player sofware and are ignored by JASigning at present.
<player_settings>
<ambient_motions body="ON" head="ON" blink="ON"/>
</player_settings>

----

[[Main Page]] >> [[CWASA]]

JASigning SiGML Extensions

2023-06-30T16:32:10Z

John.Glauert: New page for historical JASigning extensions.

[[Main Page]] >> [[SiGML]]

----
= JASigning Player Settings =
A number of extensions to [[SiGML]] are available when using [[JASigning]] to animate SiGML data. These enable some actions of the player to be scripted with a SiGML file.
The current extensions are provided by adding a <code><player_settings\></code> element between signs in the SiGML file. The extensions act on the following sign so extensions at the end of a file will be ignored.

The <code><player_settings\></code> element encloses one or more settings elements. If several settings elements are provided before a sign, later settings override earlier ones.

== Camera Settings ==
The camera location is controlled by eight parameters that can be provided in a <code>.properties</code> file or an app <code><argument/></code> or applet <code><param/></code>. Changes to the settings caused by use of the mouse with modifier keys are reflected on the Java Console Log and can be copied to use as initial camera settings.

The first six camera settings can be changed during the course of playing a SiGML file with <code><player_settings/></code> as in the following example:
<player_settings>
<camera_location cx="0.00" cy="0.50" r="4.50" theta="30.0" phi="40.0" fov="30.0"/>
</player_settings>

== Sign Timing ==
The starting time for a sign can be set using a <code><time/></code> element with an attribute saying when the sign should begin, expressed in seconds since the start of the sequence. If the time specified has already passed, the following sign will play immediately.
<player_settings>
<time begin="3.5"/>
</player_settings>
It is possible to provide a <code>mode</code> attribute to say whether the avatar should got to <code>"rest"</code> until the given time is reached (the default), or whether to <code>"hold"</code> the final posture of the previous sign:
<player_settings>
<time begin="4.5" mode="hold"/>
</player_settings>

== Avatar Choice ==
[[JASigning]] accepts commands to switch between avatars through menu choices, through messages on a special socket for the SiGML Service Player app, and through
<code><player_settings/></code> in SiGML files.
<player_settings>
<avatar name="marc"/>
</player_settings>

== Ambient Motion Settings ==
The [[JASigning]] software accepts <code><player_settings/></code> to control the ambient motion behaviour. However, these settings refer to features of older player sofware and are ignored by JASigning at present.
<player_settings>
<ambient_motions body="ON" head="ON" blink="ON"/>
</player_settings>

----

[[Main Page]] >> [[SiGML]]

SiGML

2023-06-30T16:30:38Z

John.Glauert: Allow for CWASA ands JASIgning extensions.

[[Main Page]]

----

SiGML (Signing Gesture Markup Language) is and XML application that enables transcription of sign language gestures. SiGML builds on [[HamNoSys]] and indeed one variant of
SiGML is essentially an encoding of [[HamNoSys]] manual features, accompanied by a representation of non-manual aspects.

SiGML is the input notation used by the [[JASigning]] applications and web applets. A number of [[SiGML Tools|Editing Tools]] for SiGML are available, mostly produced by the University of Hamburg.

[[CWASA]] supports some [[SiGML Extensions]] used to control the player during animation of SiGML data.

[[JASigning]] supports some [[JASigning SiGML Extensions|SiGML Extensions]] which overlap with the CWASA extensions.

----

[[Main Page]]

Main Page

2023-06-30T16:27:24Z

John.Glauert:

= Virtual Humans Research for Sign Language Animation =

This site is hosted by the [[Virtual Humans Group]] in the [http://www.uea.ac.uk/cmp/research School of Computing Sciences] at [http://www.uea.ac.uk UEA]. The aim is to provide access to research resources related to the use of Virtual Human avatars, especially for animation of Sign Language.

Visitors with an interest in avatars and other notations and techniques
for animating deaf sign language are encouraged to create a login on the site and contribute materials. For questions about the contents of this site please
contact [mailto:cmp_virtualsigning@uea.ac.uk cmp_virtualsigning@uea.ac.uk].

== Software ==

* [[CWA Signing Avatars|CWASA]]

* [[SiGML Tools]]

* [[JASigning]]

* [[Animgen]]

* [[ARP]]

== Demos ==

* [[CWA Signing Avatars Demos|CWASA Demos]]
* [[JASigning Demos]]

== Interfaces ==

* [[HamNoSys]]

* [[SiGML]]

== Projects ==

* [[Dicta-Sign]]

* [http://www.dictasign.eu/ Main Dicta-Sign Wiki]

* [[LinguaSign]]

* [[eSIGN]]

* [[ViSiCAST]]

== Links ==

* [http://linguasign.com LinguaSign] materials to support foreign language learning
* [http://www.sys-consulting.co.uk/web/Project_Performing_Hands.html Performing Hands] with Gamelab London
* [http://www.sys-consulting.co.uk/web/Project_SISI.html Say It Sign It] with IBM

Logging and Event Hooks

2023-06-30T15:36:58Z

John.Glauert: Add avatar ready event.

[[Main Page|Home]] >> [[CWA Signing Avatars|CWASA]]
----
== Logging System ==

A logging system is implemented in CWASA allowing independent logging of events for different components at a number of levels:

* '''error''': Error reporting using '''console.error'''. Always available.
* '''warn''': Warning messages using '''console.warn'''. Always available.
* '''log''': Sparing logging using '''console.log'''. Aways available.
* '''info''': Additional logging using '''console.info'''.
* '''debug''': Sign-level debugging information using '''console.info'''.
* '''trace''': Low-level debugging information using '''console.info'''.

Messages identify the time, component, and message. For '''debug''' and '''trace''' the level of reporting is also given.

Main releases of the software do not display logging at a more detailed level than '''log'''. Development releases also display '''info'''. Only unstable development versions use '''debug''' and '''trace'''. It may be possible to test these using versions ending in '''t''', '''u''', or '''v'''.
Unusually, the public method '''CWASA.getLogger()''' overrides this convention, allowing a logger to be configured to display messages at any level.

=== Using Loggers ===

* '''CWASA.getLogger(logger, loggerlevel)''': Configure and receive a CWASA logger.

This method takes a string for a class of logging and the lowest level to log (one of '''info''' to '''trace''' generally). The result is a logger which is an object whose fields have the names of the levels and hold logging functions. The fields will be null if no logger for the level exists so code must check that the level is supported first.

myLogger = CWASA.getLogger("myLog", "debug");
...
if (typeof (myLogger.trace) === "function") { myLogger.trace("My Message"); }

Further '''getLogger''' calls can be used to change the logging level dynamically.

== Event Hook System ==

The CWASA software uses a system of hook functions that are called when significant events occur. This system is used internally but can also be used via a public interface. As a result, external software can receive and generate events.

Hook functions can be added to process events of a particular type. Many events relate to avatar panels and if multiple panels are used on a page, events can be directed to one or all panels. Equally, a hook function can be designated to respond to messages for one or all panels.

=== Using Hooks ===

* '''CWASA.addHook(typ, fun, av)''': Install a hook function to be called on specific events for specific avatar instances.

The method takes a string for the type of event, a hook function, and an optional avatar panel index. If no index is given, '''*''' is used, indicating that the hook should receive events for all panels.

This example from '''OneAvClientTest.html''' links to existing '''status''' events to create a log of messages in a text field.

function addStatus(evt) {
var elt = document.getElementById("myStatusLog");
var msg = evt.msg;
if (evt.av != "*") { msg = "[av" + evt.av + "] " + msg; }
elt.value = elt.value + msg + "\n";
}

CWASA.addHook("status", addStatus);

To post an event use the function

* '''CWASA.callHookL(typ, msg, av)''': Post and event to be passed to appropriate hook functions.

As before, the avatar panel index is optional. When omitted, the event will be passed to all hook functions of the given type. The data will be presented in an event object with fields '''type''', for the type, and '''av''', for avatar index. The '''msg''' field has a structure depending on the type of event. See an example above and more examples on the '''OneAv*Test.html''' pages.

=== Supported Events ===

* '''status''': '''msg''' is a string. Used for reporting status changes to the console and to fields in the CWASA GUI.

* '''avatarloading''': '''msg''' is a string naming the avatar being loaded. Used for updating avatar menus in the CWASA GUI.

* '''avatarloaded''': '''msg''' is a string naming the avatar that has been loaded. Used for updating avatar menus in the CWASA GUI. If loading an avatar fails, the following '''avatarloaded''' event will indicate that the original avatar is reinstated.

* '''avatarready''': '''msg''' is null. Indicates that the avatar has been loaded and rendered.

* '''sigmlloading''': '''msg''' is null. Indicates that SiGML data is being processed. Used to update the CWASA GUI.

* '''sigmlsign''': '''msg''' is a JSON object containing the frames of a sign. Available for user scripts.

* '''sigmlloaded''': '''msg''' is an object with fields '''s''' for the number of signs and '''f''' for the number of frames. Used by the CWASA GUI.

* '''animactive''': '''msg''' is null. Indicates that animation is in progress. Used to update the CWASA GUI. Will normally be issued before '''sigmlloaded''' has been signalled.

* '''animidle''': '''msg''' is null. Indicates that animation has ceased. Used to update the CWASA GUI.

* '''avatarfps''': '''msg''' is a floating point number giving the frames per second at which the designated avatar is rendering. Used to update the CWASA GUI.

* '''avatarframe''': '''msg''' is an object with fields '''s''' for the sign index and '''f''' for frame index. Used to update the CWASA GUI. Called per frame. The indices are based at 0 so adding 1 will give a more natural presentation.

* '''avatarsign''': '''msg''' is an object with fields '''g''' for the sign gloss, '''s''' for the sign index and '''f''' for frame index. Used to update the CWASA GUI. Called per sign and at the end of animation. The indices are based at 0 so adding 1 will give a more natural presentation. The frame index will be in the range associated with the sign.

It is perfectly possible to define your own events, install hooks for them, and generate events for them. If the type of event is unknown to CWASA there will be no effect on the rest of the software.

== Public CWASA Interface ==

* '''CWASA.getLogger(logger, loggerlevel)''': Configure and receive a CWASA logger.
* '''CWASA.addHook(typ, fun, av)''': Install a hook function to be called on specific events for specific avatars.
* '''CWASA.callHook(typ, msg, av)''': Post an event to be passed to appropriate hook functions.

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

Configuring CWASA for HTML5 web pages

2023-06-30T15:31:11Z

John.Glauert: More on initialisation of CWASA.

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

== CWASA Development ==

The [[JASigning]] (Java Avatar Signing) software was a reimplementation of earlier work based on C++ and Visual Basic. [[JASigning]] uses Java to create freestanding applications and web applets that can be scripted through JavaScript on web pages. [[SiGML]] data is converted to motion data for animation using the [[Animgen]] software, written in C++. Animation data is rendered using an OpenGL renderer written in Java using the JOGL bindings.

With the advent of '''HTML5''' and '''WebGL''' it has become practical to create software for use in web pages that is not dependent on Java. This development has become essential as Java is now deprecated in browsers and unsupported on major browsers such as '''Chrome''' and '''Opera'''.

Development took place in a number of stages:

* Introduction of a WebGL renderer in place of OpenGL via Java. [[SiGML]] processing continued via a simplified Java applet.
* [[SiGML]] processing delegated to an [[Animgen]] server located at UEA using a CGI script.
* Preprocessing in JavaScript of the [[HamNoSys]] variant of [[SiGML]] to the Gestural variant.
* Fully client-side operation using a JavaScript implementation of [[Animgen]].

== CWASA Installation ==

An open installation of [[CWASA]] contains a number of index web pages, web pages with embedded signing avatars, and several directories containing resources.

* '''avatars''' contains JARs with avatar definition data.
* '''sigml''' contains example [[SiGML]] files.
* '''cwa''' contains scripts used by HTML5 pages and further example web pages.

The use of CORS allows an installation to be used from other servers and even, in some circumstances, from files on a local file system.
See [[JASigning Local Installation]].

== CWASA (CoffeeScript WebGL ARP Signing Avatars) ==

The CWASA software is largely written in CoffeeScript which generates JavaScript that is combined into a single script file in the '''cwa''' directory.
CWASA is configured using settings in JSON objects. Up to four sources of settings are consulted, with earlier settings overriding later ones:

* Initial settings provided as an optional argument when the CWASA software is initialised. This allows web pages to be self contained.
* Client settings held in an optional file '''clientcfg.json''' at the same level as the webpage. Normally bypassed if Initial settings are given.
* Installation settings held in a file '''cwacfg.json''' in the '''cwa''' folder of the installation.
* Installation-depended default settings applied by the CWASA initialisation code.

Parameters are in three classes:

* Settings determining which configuration files are consulted.
* Installation settings providing locations for installation directories.
* Settings for configuring a GUI for one or more avatar panels.

Full example configuration files are given below. Initial settings are provided using a similar JavaScript JSON object as in '''appletframe.html''' in BSLExamples ([[CWASA Local Installation]]).
Unrecognised settings (such as '''description''') are ignored without comment.

== Configuration Consultation Settings ==

Users can use these settings to change the normal pattern of consulting configuration files:

* '''useClientConfig''': Controls whether '''clientcfg.json''' is consulted. Default '''true''' but bypassed if Initial settings are given unless explicitly overridden.
* '''useCwaConfig''': Controls whether '''cwacfg.json''' is consulted. Default '''true'''.

Hence '''useClientConfig''' should be set to '''true''' by pages using Initial settings that also wish to consult a '''clientcfg.json''' file.

== CWASA Installation Settings ==

It is unlikely that users will need to change installation settings as these will be picked up from the installation when initialising CWASA. The settings are:

* '''jasBase''': Base installation directory.
* '''jasVersionTag''': Parameter used by deprecated Java applet.
* '''sigmlBase''': Directory for example [[SiGML]] files. Resolved relative to '''jasBase'''.
* '''avJARBase''': Directory for JAR files containing avatar definitions. Resolved relative to '''jasBase'''.
* '''avJSONBase''': Directory for JSON files containing avatar definitions. Resolved relative to '''jasBase'''.
* '''useAvatarJARs''': Flag choosing between JAR and JSON representation for avatars. Currently needs to be set '''true'''.
* '''animgenFPS''': Frames per Second of generated animation data. Defaults to '''50'''.
* '''animgenServer''': Path to CGI script for [[Animgen]] server if used.

The default is to specify no [[Animgen]] server and client-side JavaScript will implement [[Animgen]].
Some example web pages specify a server that will be used instead. The public server is
[http://vhg.cmp.uea.ac.uk/cgi-bin/animgen/animgenserver.pl http://vhg.cmp.uea.ac.uk/cgi-bin/animgen/animgenserver.pl].
The deprecated Java Applet implementing [[Animgen]] can be accessed using a pseudo-server '''stoca:'''.
Processing will fall back to the client-side implementation if Java is not supported in the chosen browser.

== CWASA GUI Settings ==

A CWASA web page can display several avatars identified as '''av0''', '''av1''', etc. Each avatar has an associated list of possible avatar characters to be displayed.
Named avatar lists can be included in the CWASA parameters. By default, '''avs''' names the list of standard avatars that can be used freely: '''anna''', '''marc''', and '''francoise'''.
The list '''avsfull''' contains all available avatars, but should only be used for evaluation.

Parameters for the avatars are given by entries in '''avSettings''', an array of JSON objects. The settings for an avatar are:

* '''width''': Width in pixels of avatar canvas. This is mainly used when a complete GUI is generated automatically.
* '''height''': Height in pixels of avatar canvas. This is mainly used when a complete GUI is generated automatically.
* '''avList''': Name of parameter holding avatar list. This will be '''avs''' by default.
* '''initAv''': Name of avatar that is loaded initially. Should normally be already present in the '''avList'''.
* '''ambIdle''': Flag controlling whether ambient motion accompanies an idle avatar.
* '''background''': By default the canvas will have a transparent background but valid text for a style background in HTML can be provided. Set to '''null''' to force a transparent background.
* '''initCamera''': Nine numbers that define the initial camera position when the avatar is loaded.
* '''initSpeed''': Initial speed setting. See below.
* '''rateSpeed''': Rate of change to speed in GUI. See below.

Note that an '''ambIdle''' setting may be given at installation level and will be inherited by each panel that does not provide its own setting.

The actual animation speed is given by '''2^(currSpeed/rateSpeed)''' where '''currSpeed''' is initially set to '''initSpeed''' and may be increased or decreased in the GUI. The rate determines how many steps are needed to change the speed by a factor of 2.

The remaining parameters are mostly needed when a GUI is generated automatically as a full panel:

* '''allowFrameSteps''': Includes buttons to suspend and resume playing, and to step forward and backwards, a frame at a time.
* '''initSiGMLURL''': Initial value for URL of [[SiGML]] file to display. No field or URL play button is displayed if the value is missing or '''null'''.
* '''allowSiGMLText''': Flag selecting whether a field for entry of [[SiGML]] text is displayed. No field or text play button is displayed if the value is '''false'''.

== CWASA Configuration Examples ==
=== Example: cwa/cwacfg.json ===
Example installation configuration:
{
"description" : "======== CWASA installation configuration data : Main release ========",
"jasBase" : "http://vhg.cmp.uea.ac.uk/tech/jas/vhg2021/",
"jasVersionTag" : "vhg2021",

"sigmlBase" : "sigml",
"avJARBase" : "avatars",
"avJSONBase" : "avjson",
"useAvatarJARs" : true,

"animgenFPS" : 30,

"avs" : [
"anna", "marc", "francoise"
],

"avsfull" : [
"anna", "marc", "francoise",
"luna", "siggi"
],

"avSettings" : [
{
"description": "Default if client configuration is missing or restricted",
"width": 384,
"height": 320,
"avList": "avs",
"initAv": "anna",
"initCamera": [ 0, 0.23, 3.24, 5, 18, 30, -1, -1 ],
"initSpeed": 0,
"rateSpeed": 5
"allowFrameSteps": true,
"initSiGMLURL": "iTakeMug.sigml",
"allowSiGMLText": true
}
]
}

=== Example: cwa/clientcfg.json ===
Configuration for Clients using client-side [[Animgen]] processing:
{
"description" : "======== CWASA client configuration data. No Animgen server ========",
"animgenServer": null,
"avSettings" : [
{
"width": 384,
"height": 320,
"avList": "avsfull",
"initAv": "luna",
"initSiGMLURL": "scotland-H.sigml"
},
{
"width": 228,
"height": 208,
"background": "Salmon",
"avList": "avs",
"initAv": "francoise",
"allowFrameSteps": false,
"allowSiGMLText": false,
"initSiGMLURL": "welkom-ngt.sigml"
}
]
}

== CWASA GUI Creation ==
There are four approaches to incorporating the CWASA software on a web page. The installation contains example web pages, built using the different approaches:

* Complete GUI: '''WebGLAvTwo.html'''. A single '''div''' is populated with a panel containing an avatar canvas and GUI elements.
* GUI Panels: '''CWASA-plus-gui-panel.html'''. A '''div''' for the avatar canvas and a separate '''div''' for the GUI.
* GUI Elements: '''CWASA-plus-gui-elements.html'''. A number of '''div'''s and '''span'''s arranging different sections of the GUI.
* Bespoke GUI: '''CWASA-plus-bespoke-gui.html'''. Individual HTML elements defining an equivalent GUI.

The first example displays two avatars on a page.
The first two approaches select elements according to layout parameters in the configuration, while the final approaches choose elements directly.
The final three examples have very similar appearance, illustrating the alternative approaches.

A CSS stylesheet controls appearance in all cases. The '''class''' attribute is also used by the CWASA script to identify elements of the GUI
for attaching handlers and to change enabled state during animation. For a page that might use the Java applet it is necessary to include one instance of:
<pre><div class="SToCA"></div></pre>
This will be ignored if an [[Animgen]] server is used or the browser does not support Java.

A '''div''' or '''span''' that forms part of the CWASA GUI will have a class which identifies the GUI component and the avatar concerned. For example, a complete GUI panel for the first avatar would be specified by:
<pre><div class="CWASAPanel av0"></div></pre>

=== Complete GUI ===
* '''CWASAPanel''': A GUI, '''CWASAGUI''', to the left of an avatar canvas, '''CWASAAvatar'''.
=== GUI Panels ===
* '''CWASAGUI''': A combination of GUI elements, some omitted according to the avatar settings in the configuration.
* '''CWASAAvatar''': A canvas for a WebGL avatar. The canvas fills the size of the enclosing element.
=== GUI Elements ===
* '''CWASAAvMenu''': A menu listing avatars in the expanded '''avList''' for the avatar.
* '''CWASAAmbBox''': A checkbox controlling whether ambient motion is seen for an idle avatar.
* '''CWASASpeed''': Controls for decreasing, increasing, and resetting the speed of animation.
* '''CWASASiGMLURL''': Input to hold a SiGML URL. Omitted by '''CWASAGUI''' if no initial URL is given.
* '''CWASASiGMLText''': Text area for entry of SiGML. Omitted by '''CWASAGUI''' if SiGML text is not allowed.
* '''CWASAPlay''': Play and Stop buttons. Only included if corresponding SiGML URL or Text fields are present.
* '''CWASAPlayExtra''': Suspend and Resume buttons. Only included if Play buttons are present. Omitted by '''CWASAGUI''' if frame steps are not allowed.
* '''CWASAFrames''': Frame single step buttons. Only included if Play buttons are present. Omitted by '''CWASAGUI''' if frame steps are not allowed.
* '''CWASAProgress''': Display of current sign and frame number, sign gloss, and actual FPS.
* '''CWASAStatus''': Display of status information.
=== Bespoke GUI ===
Users are encouraged to use the defined GUI elements as these are not expected to change significantly. Localisation does not require the use of a bespoke GUI.
For details on creating a bespoke GUI, if desired, examine the HTML file '''CWASA-plus-bespoke-gui.html'''.
Essentially, the example shows the HTML generated for GUI elements by CWASA. In order that the CWASA code will link to the GUI HTML elements it is necessary to use the appropriate classes where an avatar code is also given.

Regrettably, some of the low-level GUI elements use classes with names that might clash with those already in use in an existing application.

Some examples illustrate that certain GUI elements, such as buttons, menus, and output fields, can be duplicated. CWASA will copy information to all fields and enable and disable all duplicated buttons.

== CWASA Web Pages ==

To use CWASA, include the following CSS file and JavaScript code, relative to the JASigning installation:
<pre><link rel="stylesheet" href="http://vhg.cmp.uea.ac.uk/tech/jas/vhg2021/cwa/cwasa.css" />
<script type="text/javascript" src="http://vhg.cmp.uea.ac.uk/tech/jas/vhg2021/cwa/allcsa.js"></script></pre>
The method '''CWASA.init();''' should be called on loading the body of the page:
<pre><body onload="CWASA.init();"></pre>
Initial configuration parameters can be specified using a JSON object passed as a parameter to '''CWASA.init''', such
as for example pages using a server or Java applets. To disable ambient animation by default, but use other '''clientcfg.json''' settings:
<pre><body onload="CWASA.init({ambIdle:false,useClientConfig:true});"></pre>
To change the initial camera position and make signing slightly slower:
<pre><body onload="CWASA.init({useClientConfig:true,
avSettings:{initCamera:[0.00,0.53,2.06,-12.50,18.00,30.00,-1.00,-1.00],initSpeed:-1}});"></pre>

All methods to be used are found in the '''CWASA''' object. Examples of direct calls to CWASA are illustrated in the BSLExamples demo mentioned above,
which also illustrates use of a JSON object for initial settings. The methods supported are:
* '''CWASA.init(cfg)''': Initialise CWASA with optional configuration parameters as a JSON object.
* '''CWASA.playSiGMLText(sigtext, av)''': Play SiGML given as text. The avatar panel index is given by the second parameter, defaulting to zero.
* '''CWASA.playSiGMLURL(sigurl, av)''': Play SiGML at given URL. The avatar panel index is given by the second parameter, defaulting to zero.
* '''CWASA.stopSiGML(av)''': Stop playing SiGML. The avatar panel index is given by the parameter, defaulting to zero.
* '''CWASA.getLogger(logger, loggerlevel)''': Configure and receive a CWASA logger.
* '''CWASA.addHook(typ fun, av)''': Install a hook function to be called on specific events for specific avatars.
* '''CWASA.callHook(typ, msg, av)''': Post an event to be passed to appropriate hook functions.

==== Testing for Initialisation ====
A call to '''CWASA.init''' sets up a promise at '''CWASA.ready''' that will be resolved when all the configuration data has been loaded.

To test when an avatar is loaded and rendered, it is possible to add a hook for the '''avatarready''' event. This will be called for each avatar panel and on switching avatars on a panel.

==== Examples ====
Examples of use of these methods will be found on the '''OneAvTest.html''' example web page. The logging and event hook facilities are described under [[Logging and Event Hooks]].

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

Configuring CWASA for HTML5 web pages

2023-06-30T15:14:10Z

John.Glauert: Fix typos for CWASA.callHook

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

== CWASA Development ==

The [[JASigning]] (Java Avatar Signing) software was a reimplementation of earlier work based on C++ and Visual Basic. [[JASigning]] uses Java to create freestanding applications and web applets that can be scripted through JavaScript on web pages. [[SiGML]] data is converted to motion data for animation using the [[Animgen]] software, written in C++. Animation data is rendered using an OpenGL renderer written in Java using the JOGL bindings.

With the advent of '''HTML5''' and '''WebGL''' it has become practical to create software for use in web pages that is not dependent on Java. This development has become essential as Java is now deprecated in browsers and unsupported on major browsers such as '''Chrome''' and '''Opera'''.

Development took place in a number of stages:

* Introduction of a WebGL renderer in place of OpenGL via Java. [[SiGML]] processing continued via a simplified Java applet.
* [[SiGML]] processing delegated to an [[Animgen]] server located at UEA using a CGI script.
* Preprocessing in JavaScript of the [[HamNoSys]] variant of [[SiGML]] to the Gestural variant.
* Fully client-side operation using a JavaScript implementation of [[Animgen]].

== CWASA Installation ==

An open installation of [[CWASA]] contains a number of index web pages, web pages with embedded signing avatars, and several directories containing resources.

* '''avatars''' contains JARs with avatar definition data.
* '''sigml''' contains example [[SiGML]] files.
* '''cwa''' contains scripts used by HTML5 pages and further example web pages.

The use of CORS allows an installation to be used from other servers and even, in some circumstances, from files on a local file system.
See [[JASigning Local Installation]].

== CWASA (CoffeeScript WebGL ARP Signing Avatars) ==

The CWASA software is largely written in CoffeeScript which generates JavaScript that is combined into a single script file in the '''cwa''' directory.
CWASA is configured using settings in JSON objects. Up to four sources of settings are consulted, with earlier settings overriding later ones:

* Initial settings provided as an optional argument when the CWASA software is initialised. This allows web pages to be self contained.
* Client settings held in an optional file '''clientcfg.json''' at the same level as the webpage. Normally bypassed if Initial settings are given.
* Installation settings held in a file '''cwacfg.json''' in the '''cwa''' folder of the installation.
* Installation-depended default settings applied by the CWASA initialisation code.

Parameters are in three classes:

* Settings determining which configuration files are consulted.
* Installation settings providing locations for installation directories.
* Settings for configuring a GUI for one or more avatar panels.

Full example configuration files are given below. Initial settings are provided using a similar JavaScript JSON object as in '''appletframe.html''' in BSLExamples ([[CWASA Local Installation]]).
Unrecognised settings (such as '''description''') are ignored without comment.

== Configuration Consultation Settings ==

Users can use these settings to change the normal pattern of consulting configuration files:

* '''useClientConfig''': Controls whether '''clientcfg.json''' is consulted. Default '''true''' but bypassed if Initial settings are given unless explicitly overridden.
* '''useCwaConfig''': Controls whether '''cwacfg.json''' is consulted. Default '''true'''.

Hence '''useClientConfig''' should be set to '''true''' by pages using Initial settings that also wish to consult a '''clientcfg.json''' file.

== CWASA Installation Settings ==

It is unlikely that users will need to change installation settings as these will be picked up from the installation when initialising CWASA. The settings are:

* '''jasBase''': Base installation directory.
* '''jasVersionTag''': Parameter used by deprecated Java applet.
* '''sigmlBase''': Directory for example [[SiGML]] files. Resolved relative to '''jasBase'''.
* '''avJARBase''': Directory for JAR files containing avatar definitions. Resolved relative to '''jasBase'''.
* '''avJSONBase''': Directory for JSON files containing avatar definitions. Resolved relative to '''jasBase'''.
* '''useAvatarJARs''': Flag choosing between JAR and JSON representation for avatars. Currently needs to be set '''true'''.
* '''animgenFPS''': Frames per Second of generated animation data. Defaults to '''50'''.
* '''animgenServer''': Path to CGI script for [[Animgen]] server if used.

The default is to specify no [[Animgen]] server and client-side JavaScript will implement [[Animgen]].
Some example web pages specify a server that will be used instead. The public server is
[http://vhg.cmp.uea.ac.uk/cgi-bin/animgen/animgenserver.pl http://vhg.cmp.uea.ac.uk/cgi-bin/animgen/animgenserver.pl].
The deprecated Java Applet implementing [[Animgen]] can be accessed using a pseudo-server '''stoca:'''.
Processing will fall back to the client-side implementation if Java is not supported in the chosen browser.

== CWASA GUI Settings ==

A CWASA web page can display several avatars identified as '''av0''', '''av1''', etc. Each avatar has an associated list of possible avatar characters to be displayed.
Named avatar lists can be included in the CWASA parameters. By default, '''avs''' names the list of standard avatars that can be used freely: '''anna''', '''marc''', and '''francoise'''.
The list '''avsfull''' contains all available avatars, but should only be used for evaluation.

Parameters for the avatars are given by entries in '''avSettings''', an array of JSON objects. The settings for an avatar are:

* '''width''': Width in pixels of avatar canvas. This is mainly used when a complete GUI is generated automatically.
* '''height''': Height in pixels of avatar canvas. This is mainly used when a complete GUI is generated automatically.
* '''avList''': Name of parameter holding avatar list. This will be '''avs''' by default.
* '''initAv''': Name of avatar that is loaded initially. Should normally be already present in the '''avList'''.
* '''ambIdle''': Flag controlling whether ambient motion accompanies an idle avatar.
* '''background''': By default the canvas will have a transparent background but valid text for a style background in HTML can be provided. Set to '''null''' to force a transparent background.
* '''initCamera''': Nine numbers that define the initial camera position when the avatar is loaded.
* '''initSpeed''': Initial speed setting. See below.
* '''rateSpeed''': Rate of change to speed in GUI. See below.

Note that an '''ambIdle''' setting may be given at installation level and will be inherited by each panel that does not provide its own setting.

The actual animation speed is given by '''2^(currSpeed/rateSpeed)''' where '''currSpeed''' is initially set to '''initSpeed''' and may be increased or decreased in the GUI. The rate determines how many steps are needed to change the speed by a factor of 2.

The remaining parameters are mostly needed when a GUI is generated automatically as a full panel:

* '''allowFrameSteps''': Includes buttons to suspend and resume playing, and to step forward and backwards, a frame at a time.
* '''initSiGMLURL''': Initial value for URL of [[SiGML]] file to display. No field or URL play button is displayed if the value is missing or '''null'''.
* '''allowSiGMLText''': Flag selecting whether a field for entry of [[SiGML]] text is displayed. No field or text play button is displayed if the value is '''false'''.

== CWASA Configuration Examples ==
=== Example: cwa/cwacfg.json ===
Example installation configuration:
{
"description" : "======== CWASA installation configuration data : Main release ========",
"jasBase" : "http://vhg.cmp.uea.ac.uk/tech/jas/vhg2021/",
"jasVersionTag" : "vhg2021",

"sigmlBase" : "sigml",
"avJARBase" : "avatars",
"avJSONBase" : "avjson",
"useAvatarJARs" : true,

"animgenFPS" : 30,

"avs" : [
"anna", "marc", "francoise"
],

"avsfull" : [
"anna", "marc", "francoise",
"luna", "siggi"
],

"avSettings" : [
{
"description": "Default if client configuration is missing or restricted",
"width": 384,
"height": 320,
"avList": "avs",
"initAv": "anna",
"initCamera": [ 0, 0.23, 3.24, 5, 18, 30, -1, -1 ],
"initSpeed": 0,
"rateSpeed": 5
"allowFrameSteps": true,
"initSiGMLURL": "iTakeMug.sigml",
"allowSiGMLText": true
}
]
}

=== Example: cwa/clientcfg.json ===
Configuration for Clients using client-side [[Animgen]] processing:
{
"description" : "======== CWASA client configuration data. No Animgen server ========",
"animgenServer": null,
"avSettings" : [
{
"width": 384,
"height": 320,
"avList": "avsfull",
"initAv": "luna",
"initSiGMLURL": "scotland-H.sigml"
},
{
"width": 228,
"height": 208,
"background": "Salmon",
"avList": "avs",
"initAv": "francoise",
"allowFrameSteps": false,
"allowSiGMLText": false,
"initSiGMLURL": "welkom-ngt.sigml"
}
]
}

== CWASA GUI Creation ==
There are four approaches to incorporating the CWASA software on a web page. The installation contains example web pages, built using the different approaches:

* Complete GUI: '''WebGLAvTwo.html'''. A single '''div''' is populated with a panel containing an avatar canvas and GUI elements.
* GUI Panels: '''CWASA-plus-gui-panel.html'''. A '''div''' for the avatar canvas and a separate '''div''' for the GUI.
* GUI Elements: '''CWASA-plus-gui-elements.html'''. A number of '''div'''s and '''span'''s arranging different sections of the GUI.
* Bespoke GUI: '''CWASA-plus-bespoke-gui.html'''. Individual HTML elements defining an equivalent GUI.

The first example displays two avatars on a page.
The first two approaches select elements according to layout parameters in the configuration, while the final approaches choose elements directly.
The final three examples have very similar appearance, illustrating the alternative approaches.

A CSS stylesheet controls appearance in all cases. The '''class''' attribute is also used by the CWASA script to identify elements of the GUI
for attaching handlers and to change enabled state during animation. For a page that might use the Java applet it is necessary to include one instance of:
<pre><div class="SToCA"></div></pre>
This will be ignored if an [[Animgen]] server is used or the browser does not support Java.

A '''div''' or '''span''' that forms part of the CWASA GUI will have a class which identifies the GUI component and the avatar concerned. For example, a complete GUI panel for the first avatar would be specified by:
<pre><div class="CWASAPanel av0"></div></pre>

=== Complete GUI ===
* '''CWASAPanel''': A GUI, '''CWASAGUI''', to the left of an avatar canvas, '''CWASAAvatar'''.
=== GUI Panels ===
* '''CWASAGUI''': A combination of GUI elements, some omitted according to the avatar settings in the configuration.
* '''CWASAAvatar''': A canvas for a WebGL avatar. The canvas fills the size of the enclosing element.
=== GUI Elements ===
* '''CWASAAvMenu''': A menu listing avatars in the expanded '''avList''' for the avatar.
* '''CWASAAmbBox''': A checkbox controlling whether ambient motion is seen for an idle avatar.
* '''CWASASpeed''': Controls for decreasing, increasing, and resetting the speed of animation.
* '''CWASASiGMLURL''': Input to hold a SiGML URL. Omitted by '''CWASAGUI''' if no initial URL is given.
* '''CWASASiGMLText''': Text area for entry of SiGML. Omitted by '''CWASAGUI''' if SiGML text is not allowed.
* '''CWASAPlay''': Play and Stop buttons. Only included if corresponding SiGML URL or Text fields are present.
* '''CWASAPlayExtra''': Suspend and Resume buttons. Only included if Play buttons are present. Omitted by '''CWASAGUI''' if frame steps are not allowed.
* '''CWASAFrames''': Frame single step buttons. Only included if Play buttons are present. Omitted by '''CWASAGUI''' if frame steps are not allowed.
* '''CWASAProgress''': Display of current sign and frame number, sign gloss, and actual FPS.
* '''CWASAStatus''': Display of status information.
=== Bespoke GUI ===
Users are encouraged to use the defined GUI elements as these are not expected to change significantly. Localisation does not require the use of a bespoke GUI.
For details on creating a bespoke GUI, if desired, examine the HTML file '''CWASA-plus-bespoke-gui.html'''.
Essentially, the example shows the HTML generated for GUI elements by CWASA. In order that the CWASA code will link to the GUI HTML elements it is necessary to use the appropriate classes where an avatar code is also given.

Regrettably, some of the low-level GUI elements use classes with names that might clash with those already in use in an existing application.

Some examples illustrate that certain GUI elements, such as buttons, menus, and output fields, can be duplicated. CWASA will copy information to all fields and enable and disable all duplicated buttons.

== CWASA Web Pages ==

To use CWASA, include the following CSS file and JavaScript code, relative to the JASigning installation:
<pre><link rel="stylesheet" href="http://vhg.cmp.uea.ac.uk/tech/jas/vhg2021/cwa/cwasa.css" />
<script type="text/javascript" src="http://vhg.cmp.uea.ac.uk/tech/jas/vhg2021/cwa/allcsa.js"></script></pre>
The method '''CWASA.init();''' should be called on loading the body of the page:
<pre><body onload="CWASA.init();"></pre>
Initial configuration parameters can be specified using a JSON object passed as a parameter to '''CWASA.init''', such
as for example pages using a server or Java applets. To disable ambient animation by default, but use other '''clientcfg.json''' settings:
<pre><body onload="CWASA.init({ambIdle:false,useClientConfig:true});"></pre>
To change the initial camera position and make signing slightly slower:
<pre><body onload="CWASA.init({useClientConfig:true,
avSettings:{initCamera:[0.00,0.53,2.06,-12.50,18.00,30.00,-1.00,-1.00],initSpeed:-1}});"></pre>

All methods to be used are found in the '''CWASA''' object. Examples of direct calls to CWASA are illustrated in the BSLExamples demo mentioned above,
which also illustrates use of a JSON object for initial settings. The methods supported are:
* '''CWASA.init(cfg)''': Initialise CWASA with optional configuration parameters as a JSON object.
* '''CWASA.playSiGMLText(sigtext, av)''': Play SiGML given as text. The avatar panel index is given by the second parameter, defaulting to zero.
* '''CWASA.playSiGMLURL(sigurl, av)''': Play SiGML at given URL. The avatar panel index is given by the second parameter, defaulting to zero.
* '''CWASA.stopSiGML(av)''': Stop playing SiGML. The avatar panel index is given by the parameter, defaulting to zero.
* '''CWASA.getLogger(logger, loggerlevel)''': Configure and receive a CWASA logger.
* '''CWASA.addHook(typ fun, av)''': Install a hook function to be called on specific events for specific avatars.
* '''CWASA.callHook(typ, msg, av)''': Post an event to be passed to appropriate hook functions.

Examples of use of these methods will be found on the '''OneAvTest.html''' example web page. The logging and event hook facilities are described under [[Logging and Event Hooks]].

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

Logging and Event Hooks

2023-06-30T15:11:53Z

John.Glauert: Fix typos on CWASA.callHook

[[Main Page|Home]] >> [[CWA Signing Avatars|CWASA]]
----
== Logging System ==

A logging system is implemented in CWASA allowing independent logging of events for different components at a number of levels:

* '''error''': Error reporting using '''console.error'''. Always available.
* '''warn''': Warning messages using '''console.warn'''. Always available.
* '''log''': Sparing logging using '''console.log'''. Aways available.
* '''info''': Additional logging using '''console.info'''.
* '''debug''': Sign-level debugging information using '''console.info'''.
* '''trace''': Low-level debugging information using '''console.info'''.

Messages identify the time, component, and message. For '''debug''' and '''trace''' the level of reporting is also given.

Main releases of the software do not display logging at a more detailed level than '''log'''. Development releases also display '''info'''. Only unstable development versions use '''debug''' and '''trace'''. It may be possible to test these using versions ending in '''t''', '''u''', or '''v'''.
Unusually, the public method '''CWASA.getLogger()''' overrides this convention, allowing a logger to be configured to display messages at any level.

=== Using Loggers ===

* '''CWASA.getLogger(logger, loggerlevel)''': Configure and receive a CWASA logger.

This method takes a string for a class of logging and the lowest level to log (one of '''info''' to '''trace''' generally). The result is a logger which is an object whose fields have the names of the levels and hold logging functions. The fields will be null if no logger for the level exists so code must check that the level is supported first.

myLogger = CWASA.getLogger("myLog", "debug");
...
if (typeof (myLogger.trace) === "function") { myLogger.trace("My Message"); }

Further '''getLogger''' calls can be used to change the logging level dynamically.

== Event Hook System ==

The CWASA software uses a system of hook functions that are called when significant events occur. This system is used internally but can also be used via a public interface. As a result, external software can receive and generate events.

Hook functions can be added to process events of a particular type. Many events relate to avatar panels and if multiple panels are used on a page, events can be directed to one or all panels. Equally, a hook function can be designated to respond to messages for one or all panels.

=== Using Hooks ===

* '''CWASA.addHook(typ, fun, av)''': Install a hook function to be called on specific events for specific avatar instances.

The method takes a string for the type of event, a hook function, and an optional avatar panel index. If no index is given, '''*''' is used, indicating that the hook should receive events for all panels.

This example from '''OneAvClientTest.html''' links to existing '''status''' events to create a log of messages in a text field.

function addStatus(evt) {
var elt = document.getElementById("myStatusLog");
var msg = evt.msg;
if (evt.av != "*") { msg = "[av" + evt.av + "] " + msg; }
elt.value = elt.value + msg + "\n";
}

CWASA.addHook("status", addStatus);

To post an event use the function

* '''CWASA.callHookL(typ, msg, av)''': Post and event to be passed to appropriate hook functions.

As before, the avatar panel index is optional. When omitted, the event will be passed to all hook functions of the given type. The data will be presented in an event object with fields '''type''', for the type, and '''av''', for avatar index. The '''msg''' field has a structure depending on the type of event. See an example above and more examples on the '''OneAv*Test.html''' pages.

=== Supported Events ===

* '''status''': '''msg''' is a string. Used for reporting status changes to the console and to fields in the CWASA GUI.

* '''avatarloading''': '''msg''' is a string naming the avatar being loaded. Used for updating avatar menus in the CWASA GUI.

* '''avatarloaded''': '''msg''' is a string naming the avatar that has been loaded. Used for updating avatar menus in the CWASA GUI. If loading an avatar fails, the following '''avatarloaded''' event will indicate that the original avatar is reinstated.

* '''sigmlloading''': '''msg''' is null. Indicates that SiGML data is being processed. Used to update the CWASA GUI.

* '''sigmlsign''': '''msg''' is a JSON object containing the frames of a sign. Available for user scripts.

* '''sigmlloaded''': '''msg''' is an object with fields '''s''' for the number of signs and '''f''' for the number of frames. Used by the CWASA GUI.

* '''animactive''': '''msg''' is null. Indicates that animation is in progress. Used to update the CWASA GUI. Will normally be issued before '''sigmlloaded''' has been signalled.

* '''animidle''': '''msg''' is null. Indicates that animation has ceased. Used to update the CWASA GUI.

* '''avatarfps''': '''msg''' is a floating point number giving the frames per second at which the designated avatar is rendering. Used to update the CWASA GUI.

* '''avatarframe''': '''msg''' is an object with fields '''s''' for the sign index and '''f''' for frame index. Used to update the CWASA GUI. Called per frame. The indices are based at 0 so adding 1 will give a more natural presentation.

* '''avatarsign''': '''msg''' is an object with fields '''g''' for the sign gloss, '''s''' for the sign index and '''f''' for frame index. Used to update the CWASA GUI. Called per sign and at the end of animation. The indices are based at 0 so adding 1 will give a more natural presentation. The frame index will be in the range associated with the sign.

It is perfectly possible to define your own events, install hooks for them, and generate events for them. If the type of event is unknown to CWASA there will be no effect on the rest of the software.

== Public CWASA Interface ==

* '''CWASA.getLogger(logger, loggerlevel)''': Configure and receive a CWASA logger.
* '''CWASA.addHook(typ, fun, av)''': Install a hook function to be called on specific events for specific avatars.
* '''CWASA.callHook(typ, msg, av)''': Post an event to be passed to appropriate hook functions.

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

Driving the SiGML Player App

2023-06-20T11:29:44Z

John.Glauert: More on nc command

[[Main Page|Home]] >> [[CWA Signing Avatars|CWASA]]
----
This page describes the protocol a client app needs to follow in order to drive the SiGML Player app and provides a simple Java application that uses the protocol. The same protpcol is used for the [[JASigning]] SiGML Service Player app.

== Protocol ==

The SiGML Player accepts connection requests on standard TCP/IP port number 8052.

Each time the client wants to dispatch a SiGML text to the player it performs the following sequence:

* Make a new connection to that port (8052) on the server, i.e. the host system running the SiGML Player app, which may or may not be the "localhost".

* Send the SiGML text on the resulting output stream.
** If the SiGML text explicitly specifies an encoding in an initial XML declaration then the text should be sent as a byte stream with that encoding.
** If there's no explicit encoding it should be sent as a UTF-8 stream.

* Close the stream and the connection.

The protocol is extremely simple: so there's no feedback from the server to tell the client when the performance of a SiGML text is complete -- or indeed whether there are any errors in the SiGML text.

If a new text is dispatched before performance of the previous one is complete, then that previous performance is immediately abandoned in favour of the new one.
So, although in principle the client could be on the opposite side of the world from the server, in practice it does not make much sense if the client, i.e. its user, does not actually have line-of-sight contact with the server.

== Unix Commandline Scripting ==

On Unix systems, including OS X and Linux, or using Cygwin on Windows, the command:
nc localhost 8052 < mySigns.sigml
will send SiGML data to the application. The parameter -N may be needed to close the socket on EOF. Alternatively, the form
nc localhost 8052 -w 0 < mySigns.sigml
should work on all platforms

== Example Java Application ==

A NetBeans project for a simple Java application is available as a ZIP archive for the [http://vhg.cmp.uea.ac.uk/tech/tools/SignStreamer.zip SignStreamer Project].

* The '''src''' folder contains Java source files
* The '''dist''' folder contains '''SignStreamer.jar''' for the application
* The application can be run by the command <code>java -jar "SignStreamer.jar"</code>
* A SiGML file to be sent is selected by clicking the '''Select File''' button and sent using the '''Send File''' button

The code can be adapted or incorporated in your own code but please acknowledge the source.

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

CWASA Release Notes

2023-06-20T11:26:06Z

John.Glauert: Introduces vhg2023a

CWASA Release Notes

2023-01-10T16:26:37Z

John.Glauert: Versions for 2023

CWASA Release Notes

2022-07-22T16:37:46Z

John.Glauert: Update 2022b

CWASA Release Notes

2022-07-04T11:26:34Z

John.Glauert: Introduces vhg2022b