Latest revision as of 13:51, 23 November 2024

CWA Signing Avatars Release Notes

From 2021 the standard Open CWASA release, found at 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 Conditions of Use.

These notes, and the notes for 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 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 Issue Reporting page. Documentation of the system is a work in progress so please send questions and comments to cmp_virtualsigning@uea.ac.uk so that we can update these pages.

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.

This release is based on the Legacy Release 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 vhg.cmp.uea.ac.uk/tech/jas/vhg2024z.

This release is based on the Legacy Release 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 vhg.cmp.uea.ac.uk/tech/jas/vhg2024d.

These are the main differences between this version and CWASA 2024c:

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

CWASA 2024c (2024-08)

Legacy Release found at vhg.cmp.uea.ac.uk/tech/jas/vhg2024c.

These are the main differences between this version and 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 vhg.cmp.uea.ac.uk/tech/jas/vhg2024b.

These are the main differences between this version and 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 vhg.cmp.uea.ac.uk/tech/jas/vhg2024a.

The release should have the same features as the Legacy Release CWASA 2023a.

CWASA 2023

CWASA 2023 (Standard Version)

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

This release is based on the Legacy Release CWASA 2022b.

CWASA 2023z (Development Version)

Development Release found at vhg.cmp.uea.ac.uk/tech/jas/vhg2023z.

This release is based on the Legacy Release CWASA 2023a.

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

CWASA 2023a (2023-06)

Legacy Release found at vhg.cmp.uea.ac.uk/tech/jas/vhg2023a.

These are the main differences between this version and 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.

This release is based on the Legacy Release CWASA 2022a.

CWASA 2022z (Development Version)

Development Release found at vhg.cmp.uea.ac.uk/tech/jas/vhg2022z.

This release is based on the Legacy Release CWASA 2022b.

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

CWASA 2022b (2022-07)

Legacy Release found at vhg.cmp.uea.ac.uk/tech/jas/vhg2022b.

These are the main differences between this version and 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 vhg.cmp.uea.ac.uk/tech/jas/vhg2022a.

This version is the same as CWASA 2021f.

CWASA 2021

CWASA 2021 (Standard Version)

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

This release is based on the Legacy Release CWASA 2021f.

CWASA 2021z (Development Version)

Development Release found at vhg.cmp.uea.ac.uk/tech/jas/vhg2021z.

This release is based on the Legacy Release CWASA 2021f.

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

CWASA 2021f (2021-12)

Legacy Release found at vhg.cmp.uea.ac.uk/tech/jas/vhg2021f.

These are the main differences between this version and 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 vhg.cmp.uea.ac.uk/tech/jas/vhg2021e.

These are the main differences between this version and 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 OneAvClientTest.html for an example

CWASA 2021d (2021-09)

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

These are the main differences between this version and 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 vhg.cmp.uea.ac.uk/tech/jas/vhg2021c.

These are the main differences between this version and 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 vhg.cmp.uea.ac.uk/tech/jas/vhg2021b.

These are the main differences between this version and CWASA 2021a:

Rearranged build process for Open, Legacy, and Development releases

CWASA 2021a (2021-01)

Release found at vhg.cmp.uea.ac.uk/tech/jas/vhg2021a.

This version is the same as JASigning 2020c.

JASigning Release Notes

See JASigning Release Notes for information on earlier legacy releases.

Home >> CWASA

Difference between revisions of "CWASA Release Notes"

Latest revision as of 13:51, 23 November 2024

CWA Signing Avatars Release Notes

Table of Contents

Contents

CWASA Release Notes

CWASA 2024

CWASA 2024 (Standard Version)

CWASA 2024z (Development Version)

CWASA 2024d (2024-11)

CWASA 2024c (2024-08)

CWASA 2024b (2024-05)

CWASA 2024a (2024-04)

CWASA 2023

CWASA 2023 (Standard Version)

CWASA 2023z (Development Version)

CWASA 2023a (2023-06)

CWASA 2022

CWASA 2022 (Standard Version)

CWASA 2022z (Development Version)

CWASA 2022b (2022-07)

CWASA 2022a (2022-01)

CWASA 2021

CWASA 2021 (Standard Version)

CWASA 2021z (Development Version)

CWASA 2021f (2021-12)

CWASA 2021e (2021-11)

CWASA 2021d (2021-09)

CWASA 2021c (2021-02)

CWASA 2021b (2021-01)

CWASA 2021a (2021-01)

JASigning Release Notes

Navigation menu

Search

@@ Line 1: / Line 1: @@
-[[Main Page|Home]] >> [[JASigning]]
+[[Main Page|Home]] >> [[CWA Signing Avatars|CWASA]]
 ----
-= JASigning Release Notes =
-The current release of [[JASigning]] can be found at [http://vhg.cmp.uea.ac.uk/tech/jas/std/ http://vhg.cmp.uea.ac.uk/tech/jas/std/] which provides links for downloading applications and viewing web pages using the virtual signing technology. The standard release is [[#JASigning_2015_(Standard_Version)|vhg2015]].
+= CWA Signing Avatars Release Notes =
-The development version of [[JASigning]] can be found at [http://vhg.cmp.uea.ac.uk/tech/jas/dev/ http://vhg.cmp.uea.ac.uk/tech/jas/dev/] which provides links for development versions of applications and web pages. The development version is [[#JASigning_2015z_(Development_Version)|vhg2015z]].
+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]].
-Notes for the current and previous releases are found below. There are also notes on development versions that are not currently guaranteed to be stable. Users are welcome to try these and provide feedback via the [[JASigning Issue Reporting]] page. It is helpful to consult the [[JASigning Platform Issues]] notes.
+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.
-== JASigning 2015z (Development Version) ==
+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.
-Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2015z/ vhg.cmp.uea.ac.uk/tech/jas/vhg2015z].
+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.
-This release is currently the same as [[#JASigning_2015a_(2015-04)|JASigning 2015a]].
+= Table of Contents =
-== JASigning 2015 (Standard Version) ==
+__TOC__
-Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2015/ vhg.cmp.uea.ac.uk/tech/jas/vhg2015].
+= CWASA Release Notes =
-This release is currently the same as [[#JASigning_2015a_(2015-04)|JASigning 2015a]].
+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.
-== JASigning 2015a (2015-04) ==
-Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2015a/ vhg.cmp.uea.ac.uk/tech/jas/vhg2015a].
+= CWASA 2024 =
-These are the main differences between this version and
+== CWASA 2024 (Standard Version) ==
-[[#JASigning_0.9.5t_(2015-03)|JASigning 0.9.5t]]:
-* Provides a new SiGML Player application which combines functionality of the SiGML URL Player and SiGML Service Player. The GUI is as for the URL Player, but data can be sent to the player on the same sockets as for the Service Player.
+Open Release found at [//vhg.cmp.uea.ac.uk/tech/jas/vhg2024/ vhg.cmp.uea.ac.uk/tech/jas/vhg2024].
-* Playing of CAS files now reflects camera changes from the original SiGML file in addition to avatar changes.
-== JASigning 0.9.5t (2015-03) ==
+This release is based on the Legacy Release [[#CWASA_2024b_(2024-05)| CWASA 2024b]].
-Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/095t/ http://vhg.cmp.uea.ac.uk/tech/jas/095t/].
+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.
-These are the main differences between this version and
+== CWASA 2024z (Development Version) ==
-[[#JASigning_0.9.5p_(2014-07)|JASigning 0.9.5p]]:
-* Allows JAS parameters and settings to be provided as arguments to  a javaws command when starting JASigning Apps.
+Development Release found at [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2024z/ vhg.cmp.uea.ac.uk/tech/jas/vhg2024z].
-* Handles a new <player_settings/> element which sets the time at which the following sign will start.
-== JASigning 0.9.5r (2015-02) ==
+This release is based on the Legacy Release [[#CWASA_2024d_(2024-11)| CWASA 2024d]].
-Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/095r/ http://vhg.cmp.uea.ac.uk/tech/jas/095r/].
+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.
-This release adds no significant functionality to [[#JASigning_0.9.5p_(2014-07)|JASigning 0.9.5p]] but was built on a recent version of OS X using JDK 1.8.
+Users are encouraged to try the development release and report any issues encountered.
-== JASigning 0.9.5q (2015-02) ==
-Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/095q/ http://vhg.cmp.uea.ac.uk/tech/jas/095q/].
+== CWASA 2024d (2024-11) ==
-This release adds no significant functionality to [[#JASigning_0.9.5p_(2014-07)|JASigning 0.9.5p]] but was built on a recent version of OS X using JDK 1.7.
+Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2024d/ vhg.cmp.uea.ac.uk/tech/jas/vhg2024d].
-== JASigning 0.9.5p (2014-07) ==
+These are the main differences between this version and [[#CWASA_2024c_(2024-08)| CWASA 2024c]]:
-Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/095p/ http://vhg.cmp.uea.ac.uk/tech/jas/095p/].
+* Animgen transpiled using current version of Emscripten
+* Functionality should be unchanged.
-These are the main differences between this version and
+== CWASA 2024c (2024-08) ==
-[[#JASigning_0.9.5o_(2014-05)|JASigning 0.9.5o]]:
-* Signed with a GlobalSign certificate valid from 2014.
+Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2024c/ vhg.cmp.uea.ac.uk/tech/jas/vhg2024c].
-* Uses a more recent version of JOGL 2 to bypass problems in Java 7u60 on OS X.
-* Operates without local cache if security regime does not allow access to local disk. See [[JASigning Platform Issues]] notes.
-* Fixes incorrect handling of some repeated movements where the base position moves between repetitions.
-== JASigning 0.9.5o (2014-05) ==
+These are the main differences between this version and [[#CWASA_2024b_(2024-05)| CWASA 2024b]]:
-Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/095o/ http://vhg.cmp.uea.ac.uk/tech/jas/095o/].
+* 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
-These are the main differences between this version and
+== CWASA 2024b (2024-05) ==
-[[#JASigning_0.9.5n_(2013-11)|JASigning 0.9.5n]]:
-* Fixes a bug that cause some eye-related non-manual features to be omitted when using the HamNoSys form of SiGML.
+Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2024b/ vhg.cmp.uea.ac.uk/tech/jas/vhg2024b].
-* Corrects the handling of parameter settings for JASigning applications via JNlP files. These now use <argument/> elements rather than <property/> elements.
+These are the main differences between this version and [[#CWASA_2024a_(2024-04)| CWASA 2024a]]:
-* Playing of CAS files now reflects avatar changes from the original SiGML file, as introduced in [[#JASigning_0.9.5l_(2013-06)|JASigning 0.9.5l]].
+* Offline transformation of h-SiGML to g-SiGML simplified using Node.js tool installed using npm
+* Node.js software using Saxon for XSLT processing
-== JASigning 0.9.5n (2013-11) ==
+== CWASA 2024a (2024-04) ==
-Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/095n/ http://vhg.cmp.uea.ac.uk/tech/jas/095n/].
+Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2024a/ vhg.cmp.uea.ac.uk/tech/jas/vhg2024a].
-These are the main differences between this version and
+The release should have the same features as the Legacy Release [[#CWASA_2023a_(2023-06)| CWASA 2023a]].
-[[#JASigning_0.9.5m_(2013-10)|JASigning 0.9.5m]]:
-* Uses a locally signed version of the JOGL libraries with compatible JAR manifest entries.
-* All Characters currently use separate texture files.
-== JASigning 0.9.5m (2013-10) ==
+= CWASA 2023 =
-Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/095m/ http://vhg.cmp.uea.ac.uk/tech/jas/095m/].
+== CWASA 2023 (Standard Version) ==
-These are the main differences between this version and
+Open Release found at [//vhg.cmp.uea.ac.uk/tech/jas/vhg2023/ vhg.cmp.uea.ac.uk/tech/jas/vhg2023].
-[[#JASigning_0.9.5l_(2013-06)|JASigning 0.9.5l]]:
-* The '''Platform Issues''' reported for [[#JASigning_0.9.5j_(2012-08)|JASigning 0.9.5j]] are largely overcome, though rendering artefacts remain for Mac OS 10.6 Snow Leopard.
+This release is based on the Legacy Release [[#CWASA_2022b_(2022-07)| CWASA 2022b]].
-* Adds <code>Application-Name</code>, <code>Permissions</code>, and <code>Codebase</code> attributes to JAR file manifests for Java 6u65 and Java 7u45.
+== CWASA 2023z (Development Version) ==
-* Replaces <code>Trusted-Library</code> attribute by <code>Caller-Allowable-Codebase</code>.
-== JASigning 0.9.5l (2013-06) ==
+Development Release found at [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2023z/ vhg.cmp.uea.ac.uk/tech/jas/vhg2023z].
-Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/095l/ http://vhg.cmp.uea.ac.uk/tech/jas/095l/].
+This release is based on the Legacy Release [[#CWASA_2023a_(2023-06)| CWASA 2023a]].
-These are the main differences between this version and
+Users are encouraged to try the development release and report any issues encountered.
-[[#JASigning_0.9.5k_(2013-06)|JASigning 0.9.5k]]:
-* '''Open GL handling uses JOGL2''': Uses Version 2 of [http://jogamp.org/jogl/www/ JOGL], the Java binding for Open GL.
+== CWASA 2023a (2023-06) ==
-* '''Avatar Switching''' is supported via a <player_settings/> element. See [[SiGML Extensions]]. Avatar changes are reflected in CAS files exported by the SiGML URL Player, but playback does not handle changes until version [[#JASigning_0.9.5o_(2014-05)|JASigning 0.9.5o]]. Camera changes are not reflected in CAS files.
-* The '''Platform Issues''' reported for [[#JASigning_0.9.5j_(2012-08)|JASigning 0.9.5j]] continue to apply.
-* The properties/preferences setting <code>ja.force.remote.ja.home</code> now defaults to <code>true</code> when not provided.
+Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2023a/ vhg.cmp.uea.ac.uk/tech/jas/vhg2023a].
-* Adds <code>Trusted-Library</code> attribute to JAR file manifests for Java 6u45 and Java 7u21.
-* Correctly signs JNLP files for trusted launching via current browsers.
-== JASigning 0.9.5k (2013-06) ==
+These are the main differences between this version and [[#CWASA_2022b_(2022-07)| CWASA 2022b]]:
-Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/095k/ http://vhg.cmp.uea.ac.uk/tech/jas/095k/].
+* Electron apps now using better maintained framework using Electron and Vite
+* Improved handling of Port 8052 for streamed SiGML data
-These are the main differences between this version and
-[[#JASigning_0.9.5j_(2012-08)|JASigning 0.9.5j]]:
-* '''Open GL handling uses JOGL1''': Reverts to using Version 1 of [http://jogamp.org/jogl/www/ JOGL], the Java binding for Open GL.
+= CWASA 2022 =
-* The '''Platform Issues''' reported for [[#JASigning_0.9.5i_(2012-08)|JASigning 0.9.5i]] continue to apply.
-== JASigning 0.9.5j (2012-08) ==
+== CWASA 2022 (Standard Version) ==
-Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/095j/ http://vhg.cmp.uea.ac.uk/tech/jas/095j/].
+Open Release found at [//vhg.cmp.uea.ac.uk/tech/jas/vhg2022/ vhg.cmp.uea.ac.uk/tech/jas/vhg2022].
-These are the main differences between this version and
+This release is based on the Legacy Release [[#CWASA_2022a_(2022-01)| CWASA 2022a]].
-[[#JASigning_0.9.5i_(2012-08)|JASigning 0.9.5i]]:
-* '''Open GL handling uses JOGL2''': Now uses Version 2 of [http://jogamp.org/jogl/www/ JOGL], the Java binding for Open GL, which is required for the SiGML Player Applet (SPA) on Mac OS X.
+== CWASA 2022z (Development Version) ==
-* '''Platform Issues''': Unfortunately there are problems on recent Mac OS X systems:
+Development Release found at [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2022z/ vhg.cmp.uea.ac.uk/tech/jas/vhg2022z].
-** '''Mac OS 10.6 Snow Leopard''': Web pages using SPA function correctly. JNLP Player Applications show some unacceptable rendering artefacts, so consider [[#JASigning_0.9.5i_(2012-08)|JASigning 0.9.5.i]] instead.
-** '''Mac OS 10.7 Lion and 10.8 Mountain Lion''': Web pages using SPA function correctly. JNLP Player Applications fail to run when using Java 7 but function correctly on a system that uses the initial Apple release of Java 6.
-** '''Windows''': Windows users should observe correct functionality.
-== JASigning 0.9.5i (2012-08) ==
+This release is based on the Legacy Release [[#CWASA_2022b_(2022-07)| CWASA 2022b]].
-Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/095i/ http://vhg.cmp.uea.ac.uk/tech/jas/095i/].
+Users are encouraged to try the development release and report any issues encountered.
-These are the main differences between this version and
+== CWASA 2022b (2022-07) ==
-[[#JASigning_0.9.5h_(2012-02)|JASigning 0.9.5h]]:
-* '''Improved Avatar Loading''': Fixed a bug which caused loading of new avatars to fail for locales using European number representation due to incorrect setting of camera properties.
+Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2022b/ vhg.cmp.uea.ac.uk/tech/jas/vhg2022b].
-* '''Updated Security Certificate''': Uses a re-issued Code Signing Certificate to replace the one used since [[#JASigning_0.9.5f_(2010-07)|JASigning 0.9.5.f]] which has expired.
+These are the main differences between this version and [[#CWASA_2022a_(2022-01)| CWASA 2022a]]:
-* '''Platform Issues''': Unfortunately there are problems on recent Mac OS X systems:
+* C++ code for Animgen transpiled with a newer release of Emscripten
-** '''Mac OS X : HTML Applets''': Most browsers on Mac OS X now create a new process to run Java applets on web pages. This means that nothing is displayed when the SiGML Player Applet (SPA) is loaded, although the Java Console reports normal processing of signing events. Consider SPA in [[#JASigning_0.9.5j_(2012-08)|JASigning 0.9.5.j]] instead.
+* Base directory for SiGML files for JWS apps now based on release installation
-** '''Mac OS 10.6 Snow Leopard : JNLP Player Applications''':  Should function correctly.
+* Frame capture for video generation in JWS apps adapts to display resolution for Retina displays
-** '''Mac OS 10.7 Lion and 10.8 Mountain Lion : JNLP Player Applications''': Fail to run when using Java 7 but function correctly on a system that uses the initial Apple release of Java 6.
+* A new version of the video generation server is documented at [[JASigning Video Generator]]
-** '''Windows''': Windows users should observe correct functionality.
-== JASigning 0.9.5h (2012-02) ==
+== CWASA 2022a (2022-01) ==
-Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/095h/ http://vhg.cmp.uea.ac.uk/tech/jas/095h/].
+Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2022a/ vhg.cmp.uea.ac.uk/tech/jas/vhg2022a].
-These are the main differences between this version and
+This version is the same as [[#CWASA_2021f_(2021-12)| CWASA 2021f]].
-[[#JASigning_0.9.5g_(2011-02)|JASigning 0.9.5g]]:
-* '''Françoise Avatar''': In addition to the standard avatars '''anna''', and '''marc''', a new avatar '''francoise''' is included. This avatar was developed by UEA and LIMSI within the [[Dicta-Sign]] project for use with project outcomes.
-* '''Enhanced Flexibility and Precision in SiGML''': The HamNoSys notation allows for changes in hand posture that might involve simultaneous movement and changes to hand shape and hand orientation. Implementation in [[Animgen]] assumes all changes are synchronised. Detailed examination of natural signing suggests that changes to orientation and shape are often established early in a movement. Additional attributes <code>orientation_lead</code> and <code>shape_lead</code> have been added to <code>handconfig</code> elements in [[SiGML]] to enable more precision in signing. If linguistic research identifies the normal pattern of sign language performance, [[Animgen]] could be modified to provide a different default behaviour.
+= CWASA 2021 =
-This release was supported by the [[Dicta-Sign]] project and is documented in [http://www.dictasign.eu/Main/PubliclyAvailableProjectDeliverables Deliverable D3.3] of the project.
+== CWASA 2021 (Standard Version) ==
-== JASigning 0.9.5g (2011-02) ==
+Open Release found at [//vhg.cmp.uea.ac.uk/tech/jas/vhg2021/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021].
-Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/095g/ http://vhg.cmp.uea.ac.uk/tech/jas/095g/].
+This release is based on the Legacy Release [[#CWASA_2021f_(2021-12)| CWASA 2021f]].
-These are the main differences between this version and
+== CWASA 2021z (Development Version) ==
-[[#JASigning_0.9.5f_(2010-07)|JASigning 0.9.5f]]:
-* '''Improved Handling of Initial Options for Apps''': The initial option settings for a JASigning app are now handled more flexibly.  In particular, different JNLP variants of the same underlying JASigning app can now use distinct initial options settings without confusion.  Initial options properties files are cached on the client to support offline operation.
+Development Release found at [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2021z/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021z].
-* '''Improved CAS Input and Output''': CAS is the system's animation data format, which is amenable to conversion for use with other animation systems. CAS input and output are consistent, so re-exporting a previously imported CAS file generally produces a result whose format matches that of the original.
+This release is based on the Legacy Release [[#CWASA_2021f_(2021-12)| CWASA 2021f]].
-* '''Improvements to SiGML Processing''': SiGMLInLib, the component which performs conversions from H-SiGML (HNS SiGML) to G-SiGML (Gestural SiGML), and also from G-SiGML back to H-SiGML or HamNoSys, performs these conversions consistently with one another, and some errors in the conversion from H- to G-SiGML have been fixed.
+Users are encouraged to try the development release and report any issues encountered.
-*'''Fine-grain Control of Avatar Posture and Motion''': HamNoSys uses discrete ranges of values for features of the signer's posture and motion such as the orientation of hands and fingers and the direction and size of a movement. The HamNoSys “between” operator (\) can be used to specify a value halfway between two adjacent values in any of these discrete ranges. For example, specifying an extended finger direction between “up” and “left” produces a hand pointing diagonally (upwards and to the left).
+== CWASA 2021f (2021-12) ==
-** The G-SiGML format used as direct input to the animation generation generalises this notion by allowing the specification of an additional “ratio” value, which may be an arbitrary real number between zero and one. This specifies a relative weighting between the two base values, thus effectively replacing HamNoSys's discrete range by a continuous one, giving arbitrarily fine-grain control over such features. Intermediate weighting values of this kind are currently supported for extended finger directions, palm orientations, and locations.
-** G-SiGML provides an alternative form of fine-grain control of direction – for features such as hand orientation and motions – by allowing a direction to be expressed as a vector of integer values specifying relative weightings in Cartesian space. For example, the HamNoSys direction “upwards and leftwards” (positive y and x, respectively) can be represented in G-SiGML as a direction value of “1 1 0”. Thus, greater relative degrees of upward-ness in the direction can be achieved by specifying direction values of “1 2 0”, “1 3 0”, etc.
-This release was supported by the [[Dicta-Sign]] project and is documented in [http://www.dictasign.eu/Main/PubliclyAvailableProjectDeliverables Deliverable D3.2] of the project.
+Legacy Release found at [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2021f/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021f].
-== JASigning 0.9.5f (2010-07) ==
+These are the main differences between this version and [[#CWASA_2021e_(2021-11)| CWASA 2021e]]:
-Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/095f/ http://vhg.cmp.uea.ac.uk/tech/jas/095f/].
+* Recover from errors in URL specification for SiGML file URL
+* Recover from errors in SiGML code from URL or text
-These are the main differences between this version and
+== CWASA 2021e (2021-11) ==
-[[#JASigning_0.9.5e_(2009-12)|JASigning 0.9.5e]]:
-* '''Ambient Motion''': Some of the avatars, including the standard avatar, Anna, are now capable of ambient motion, both when idle and when signing. Versions of the applications and applets supporting this feature have been provided. An application menu allows this feature to be enabled/disabled both during signing and during idle periods, as required by the user. Finer grain control is provided through the system's standard options setting mechanism. Adding this feature to the other avatars is technically as simple matter, but this awaits more detailed evaluation and user feedback on the feature.
+Legacy Release found at [https://vhg.cmp.uea.ac.uk/tech/jas/vhg2021e/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021e].
-* '''Video Generation''': JASigning now has an experimental video generation facility. Because it depends on an externally provided video processing software library, this facility depends on a supporting video generation service application (running on the client system), which must be downloaded separately. For details on the download and use of the video generation service application, see the [[JASigning Video Generator]] page.
+These are the main differences between this version and [[#CWASA_2021d_(2021-09)| CWASA 2021d]]:
-*'''Security Certificate''': The JASigning software components are now signed with a certificate issued by [http://www.globalsign.com/ GlobalSign] (to our School's consulting company, SYS Consulting Ltd.). While this gives stronger assurances about the software's authenticity than previously, it has one possible drawback for those running the software on Mac OS X: there is a bug/issue in the Mac OS X Java implementation which requires the system to be online when a JASigning application is launched, in order that the OCSP security checks can be made (even though the application is marked as suitable for offline execution). This means that on Mac OS X the JASigning applications can not be launched while completely offline.  (Although going offline once the application is successfully launched is not a problem.) The only way we can see of circumventing this problem is for us to provide an alternative, self-signed, copy of the software, which is not subject to this limitation (but which is correspondingly less secure). This self-signed version can be found at the URL obtained by inserting an extra step "ss/" into the path just before the version tag: [http://vhg.cmp.uea.ac.uk/tech/jas/ss/std/ http://vhg.cmp.uea.ac.uk/tech/jas/ss/std/]
+* 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
-* '''Java Security Checks''': JASigning has been adjusted to take account of the fussier security régime introduced into the Java releases of recent months. In particular, the JASigning applications and applets should no longer give rise to Java security messages about "mixtures of signed and unsigned components".
+== CWASA 2021d (2021-09) ==
-* '''Platform Independent Applet''': The main [http://vhg.cmp.uea.ac.uk/tech/jas/095f/SPA.html SiGML Player Applet] and its variants are now launched as JNLP Applets on platforms that support this mechanism, falling back to the use of the JNLP Applet Launcher on those that don't.
+Legacy Release found at [//vhg.cmp.uea.ac.uk/tech/jas/vhg2021d/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021d].
-* '''Support for Windows 7''': Although our testing is relatively limited, JASigning apparently runs successfully on Windows 7. But users of Windows XP should note that on that platform JASigning applications and applets (apart from the SiGML Service Client) now (since 2010-03) require prior installation of the freely available [http://www.microsoft.com/downloads/details.aspx?familyid=A5C84275-3B97-4AB7-A40D-3802B2AF5FC2 Microsoft Visual Studio C++ 2008 Redistributable Package] - which may well be present already on many Windows XP systems.
+These are the main differences between this version and [[#CWASA_2021c_(2021-02)| CWASA 2021c]]:
-* '''64-bit Support''': All JASigning applications and applets now support 64-bit operation whenever this feature is provided by the underlying Windows, Mac OS X and Java runtime systems.
+* Employs protocol-relative URLs for HTTP and HTTPS support
-* '''Improved HamNoSys/XML Input Error Handling''': Recovery from HamNoSys and XML errors in SiGML input texts is now robust - i.e. it should no longer be necessary to re-launch a JASigning application or applet after feeding erroneous SiGML input to it.
+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.
-This release was supported by the [[Dicta-Sign]] project and is documented in [http://www.dictasign.eu/Main/PubliclyAvailableProjectDeliverables Deliverable D3.2] of the project.
+== CWASA 2021c (2021-02) ==
-== JASigning 0.9.5e (2009-12) ==
+Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2021c/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021c].
-Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/095e/ http://vhg.cmp.uea.ac.uk/tech/jas/095e/].
+These are the main differences between this version and [[#CWASA_2021b_(2021-01)| CWASA 2021b]]:
-These are the main differences between this version and
+* New GUI element '''CWASAAmbBox''' to enable and disable ambient animation when an avatar is idle
-[[#JASigning_0.9.5d_(2008-12)|JASigning 0.9.5d]]:
+* Configuration setting '''ambIdle''' providing default for ambient anumation
-* Support for Windows Vista.
+== CWASA 2021b (2021-01) ==
-* Support for genuine offline running of a JASigning JNLP application once it has been run and cached from the server for the first time.
+Legacy Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2021b/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021b].
-* Improved quality and range of HamNoSys 4 non-manuals for all avatars.
+These are the main differences between this version and [[#CWASA_2021a_(2021-01)| CWASA 2021a]]:
-* Improvements in the [http://vhg.cmp.uea.ac.uk/tech/jas/095e/jnlp/SiGMLServiceClientApp.jnlp SiGML Client/Editor] application's UI: the editor supports UNDO/REDO (Ctl-Z/Ctl-Shift-Z), and handles unsaved edits in a more forgiving way.
+* Rearranged build process for Open, Legacy, and Development releases
-* Support in the [http://vhg.cmp.uea.ac.uk/tech/jas/095e/index.html#html-applets SiGML Player Applet (SPA)] for "piped" SiGML input, that is, for SiGML input that is supplied one sign at a time over an extended period, for example, in response to input from the user.
+== CWASA 2021a (2021-01) ==
-* Support in the [http://vhg.cmp.uea.ac.uk/tech/jas/095e/jnlp/SiGMLURLApp.jnlp SiGML URL Player] application for the saving of CAS animation data to a file on the client system, and support for the incorporation of CAS data into a SiGML stream using the <tt>&lt;signing_ref&gt;</tt> SiGML element.
+Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/vhg2021a/ vhg.cmp.uea.ac.uk/tech/jas/vhg2021a].
-* Support for explicit user control of the frame-dropping policy, intended for use in the case where the frame rate is too high for the graphics hardware.
+This version is the same as [[JASigning_Release_Notes#JASigning_2020c_(2020-11)|JASigning 2020c]].
-* Definition of standard HTML frames, with associated scripts, to run the [http://vhg.cmp.uea.ac.uk/tech/jas/095e/index.html#html-applets SiGML Player Applet (SPA)] either with a standard GUI or with a customised one.
-Note, however, that the usual [http://en.wikipedia.org/wiki/Same_origin_policy same origin policy] means that unfortunately it is not possible to deploy a JASigning applet on some other host simply by linking to the standard SPA frame definition on this one.
+= JASigning Release Notes =
-This release was supported by the [[Dicta-Sign]] project and is documented in [http://www.dictasign.eu/Main/PubliclyAvailableProjectDeliverables Deliverable D3.1] of the project.
-== JASigning 0.9.5d (2008-12) ==
-Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/095d/ http://vhg.cmp.uea.ac.uk/tech/jas/095d/].
-These are the main differences between this version and
-[[#JASigning_0.9.5c_(2008-07)|JASigning 0.9.5c]]:
-* The two LiveConnect applets have been replaced by a single [http://vhg.cmp.uea.ac.uk/tech/jas/095d/SiGML-Player-Applet.html SiGML Player Applet], which accepts either form of SiGML sequence specification recognised by its two predecessors, that is, a SiGML URL or an explicit SiGML text.  It provides feedback to the HTML GUI via Javascript calls. <br> The applet controls its signing avatar panel via its own event dispatch thread (EDT), which responds to two classes of event: GUI events coming from the user via the HTML/Javascript [https://developer.mozilla.org/en-US/docs/JavaScript/Guide/LiveConnect_Overview LiveConnect] interface, and call-back events generated by the avatar panel itself.  The EDT generates an acknowledgement for each event it receives and at present it processes events serially, that is, it will not accept a new event until it has generated the acknowledgement for its predecessor. <br> The EDT is thus a potential bottleneck, but the JASigning avatar panel component is intended to operate with enough asynchronous concurrency for this not to be a problem in practice. <br> This event-based architecture should make it a relatively straightforward matter to enhance the applet while maintaining its robustness: a new operation can be introduced by making appropriate exensions to the applet's Event enumeration, and adding code to the EDT specifying how each new event is to be processed. <br> The applet has a boolean option controlling the generation of event logging output on the Java console. <br> (The LC-SiGML-Player and LC-SiGML-URL-Player applet classes are still included in the <code>use-jarp</code> library, but this release does not provide any HTML demos for them.)
-* JASigning now allocates a local workspace for itself in a directory called <code>.jasigning</code> in the user's home directory.
-* If the user wishes to define a default JA options set, that is, one common to all JASigning applications, then the file defining these options (<code>jadefaults.properties</code>) should be placed in the user's <code>.jasigning</code> directory. In the absence of this file, a standard JA default options file (which typically is empty) is read from the JASigning installation server instead.
-* For an avatar with Cacheable access, the locally cached copy is now held in the user's JASigning workspace (<code>.jasigning</code> directory) rather than in the JNLP Persistence Service cache, as before. This means that avatars with Cacheable access can now be used by JASigning HTML applets (which do not have access to the JNLP cache). As a result, Cacheable access is probably now the most satisfactory avatar access mode in most contexts.
-* JASigning now supports a standard installation-wide set of avatar configuration options.
-** The properties that may be defined in this set are:
-*** <code>avatar.id</code>
-*** <code>avatar.id.list</code>
-*** <code>direct.files.avatar.list</code>
-*** <code>cacheable.avatars.list</code>
-*** <code>avatar.config.base.uri</code>
-*** <code>avatar.jar.base.uri</code>
-** together possibly with appropriate entries, each for an individual avatar, AV, in one of the forms:
-*** <code>avatar.direct.base.uri.AV</code> (if AV has Direct Files access)
-*** <code>avatar.jar.uri.AV</code> (if AV has Cacheable access)
-** (See the previous release's [[#JASigning_0.9.5c_(2008-07)|change list]] for descriptions of these options.)
-** The built-in JA options set does not now include settings for any of these options, but the standard JA options set may still include definitions for them through the JA default options and/or the application/applet-specific options.
-** Definitions of avatar options in the JA options set supplement and override the installation's standard avatar configurataion options. Thus, for example, the installation may define a basic set of avatars and standard locations for their definition files, while a particular application may define additions to the installation's standard avatar set, together with locations for these extra avatars, and possibly also non-standard locations for avatars in the installation's original set.
-* The SiGML Editor/Client application now uses the Preferences mechanism to remember the location of its SiGML folder from one invocation to the next. When first used the application prompts the user to choose the required folder via a standard file dialog.
-* The behavour of the Frame Number spinner component used in the JASigning applications has been reworked and should now be more robust - for example, in the case where SiGML animation generation is streamed (i.e. asynchronous).
-* The [http://vhg.cmp.uea.ac.uk/tech/jas/095d/jnlp/SiGMLServicePlayer.jnlp SiGML Service Player] application now supports streamed animation generation, that is, it should be possible (with the appropriate option setting) for that application to play the animation for earlier signs in a SiGML sequence while animation data is still being generated for later signs in the sequence, or even while waiting for later signs to be delivered from the remote source.
-== JASigning 0.9.5c (2008-07) ==
-Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/095c/ http://vhg.cmp.uea.ac.uk/tech/jas/095c/].
-These are the main differences between this version and
-[[#JASigning_0.9.5b_(2008-02)|JASigning 0.9.5b]]:
-* Support for the [https://jogamp.org/applet-launcher/www/ JNLP Applet Launcher] (JAL), which allows an applet in a web browser to be launched without any prior download of supporting native libraries and avatar definitions.<br> (And which despite its name appears not to use the JNLP APIs, but just the JNLP XML file format.)<br> All the remaining changes are consequences of this one.
-* No "JASigning Applet Support" installation on the client system, nor explicit offers to install local avatar definitions, if appropriate, when a JASigning JNLP application is launched. Instead all cacheing of native libraries on the client depends on the Java Web Start cacheing mechanisms, or, in the case of an HTML applet, on the JAL's own cacheing mechanisms (whose activities are recorded on the Java console log, for those who are interested). The treatment of avatar data files is described below.
-* Hence this version has no need of the system-wide JA_HOME preferences setting. In previous versions JA_HOME usually identified the installation directory on the client system.  In this version JA_HOME is effectively a fixed internal setting, forced to point to the remote JASigning base directory on the server.
-* Applet-specific properties may now be set via <code>&lt;param&gt;</code> entries in the HTML <code>&lt;applet&gt;</code> element (or in a JNLP <code>&lt;applet-desc&gt;</code> element), the parameter name in each case being simply the the name of the preference setting it represents.<br> One consequence of this is that applet-specific properties files are no longer necessary, although they are still supported, for the time being, anyway. Another consequence is that the special <code>avatar</code> parameter of previous versions must now for consistency be named <code>avatar.id</code>
-* There are now three possible access methods for an avatar's data files:
-** '''ClassPath''' Access: the folder of data files for the given avatar is packaged in a JAR file together with a Java access class (details below) whose sole purpose is to provide a resource base against which the avatar files can be accessed by a Java class loader. <br> Provided this avatar access JAR is placed on the classpath of a JASigning application or applet the avatar is automatically accessible - and will benefit from Java's standard client-side caching mechanisms.<br> The drawback of this method is that on first use, the user is forced to wait while every JAR of this kind is downloaded into the Java client-side cache before the application or applet can start. This is the default access method. (And it is also used to access the <code>COMMON/config.xml</code> file.)
-** '''Direct Files''' Access: this is essentially the access method used in previous versions, that is, the avatar data files are obtained via a base URL for the folder containing these files - but in previous versions that was typically a <code>file:</code> URL on the client, whereas now it will typically be a remote <code>http:</code> URL.
-** '''Cacheable''' Access: this is similar to the first access method in that the avatar data files are packaged with an access class in a JAR file.  But in this case the JAR is not put on the Java classpath; instead JASigning downloads it only on demand and places it in the client's JNLP cache, from whence a temporary copy is taken and dynamically loaded. (Using the JNLP cache for this purpose seems to be a mistake since JNLP is not available to HTML applets, so at present this access method is available <em>only</em> to JNLP applications and applets. But using a custom-built cache instead of the JNLP cache - as JAL does -- would not be difficult to implement and JASigning may well change to do this in the near future.) <br>The access class for a given avatar, <code>marc</code> say, is a miniscule Java class called <code>marc.Access</code> whose compiled class file <code>Access.class</code> is placed in the <code>marc</code> avatar data folder. The Java code for this class is simply:
- package marc; public final class Access{}
-* There are a number of new properties/preferences settings to control the avatar access mechanisms, and several of the old setttings take on a more prominent role.  As noted above, an HTML applet can now control these settings by means of <code>&lt;param&gt;</code> entries in the relevant HTML <code>&lt;applet&gt;</code> element.
-** <code>avatar.id</code>:&nbsp;&nbsp; The name of the avatar to be loaded initially.
-** <code>avatar.id.list</code>:&nbsp;&nbsp; Colon-separated list of avatars available to the application/applet, e.g. <code>anna:marc</code>.<br> (Since there is no longer an installation folder in the file system, JASigning is no longer able to determine this list for itself by inspecting its <code>agconfig</code> subfolder.)
-** <code>direct.files.avatar.list</code>:&nbsp;&nbsp; Colon-separated list of avatars using the Direct Files access method.<br> May be omitted (or explicitly <code>null</code>, or explicitly empty) if the list is empty.
-** <code>cacheable.avatar.list</code>:&nbsp;&nbsp; Colon-separated list of avatars using the Cacheable access method.<br> May be omitted (or explicitly <code>null</code>, or explicitly empty) if the list is empty.
-** <code>avatar.config.base.uri</code>:&nbsp;&nbsp; The default base location for the data folders of avatars in the Direct Files list.
-** <code>direct.files.base.uri.AVATAR</code>:&nbsp;&nbsp; Assuming <code>AVATAR</code> appears in the Direct Files avatar list, an entry of this form explicitly specifies the URL of its avatar data folder, overriding the default location implicit in the <code>avatar.config.base.uri</code> setting.
-** <code>avatar.jar.uri.AVATAR</code>:&nbsp;&nbsp; Assuming <code>AVATAR</code> appears in the Cacheable avatar list, an entry of this form specifies the URL of its access JAR file.
-: Clearly, the <code>avatar.id.list</code> should include the <code>avatar.id</code> value, and should contain as sublists both the <code>direct.files.avatar.list</code> and <code>cacheable.avatar.list</code> values.
-* As well as the various client-side cacheing mechanisms, this version of JASigning currently caches all avatar data in memory for the remainder of the session once loaded.  This could amount to a good few Mb if many avatars are used, but probably not enough to be a problem in most environments.
-* At present this version of JASigning makes no attempt to set the Java Applet runtime parameters for the user, since the separate installer which used to do this is is no longer used.
-== JASigning 0.9.5b (2008-02) ==
-Release found at [http://vhg.cmp.uea.ac.uk/tech/jas/095b/ http://vhg.cmp.uea.ac.uk/tech/jas/095b/].
-[[JASigning]] is a software system for scripted performance of sign language
-animations by a virtual human, or avatar.  The scripting language used to define
-these animations is SiGML (Signing Gesture Markup Language).
-SiGML is an XML application language, derived from
-[http://www.sign-lang.uni-hamburg.de/Projects/HamNoSys.html HamNoSys],
-the sign language notation system developed at the University of Hamburg.
-[[JASigning]] is based on work undertaken at UEA in conjunction with our
-partners in the
-[[ViSiCAST]] and
-[[eSIGN]] projects.
-It is an alternative to the
-[http://www.sign-lang.uni-hamburg.de/eSIGN/Software.html Avatar Plugin]
-software released at the end of the eSIGN project.  One important difference
-is that [[JASigning]] runs on Mac OS X as well as Windows.
-[[JASigning]] is a combination of
+See [[JASigning Release Notes]] for information on earlier legacy releases.
-[http://java.sun.com/ Java] software with supporting native libraries.
-So, use of [[JASigning]] requires that the
-[http://www.java.com/en/download/index.jsp Java runtime]
-software, version 5 or later, is installed on the client system.
-Java is pre-installed on all Mac OS X systems, and on many Windows systems.
-The standard method of accessing a [[JASigning]] application or
-applet is via
-[http://java.sun.com/products/javawebstart/ Java Web Start]
-using JNLP, the Java Network Launch Protocol.
 ----
-[[Main Page|Home]] >> [[JASigning]]
+[[Main Page|Home]] >> [[CWA Signing Avatars|CWASA]]