CWASA Platform Issues
CWASA software should work with Firefox, Chrome, Opera, and Safari.
CWASA software should work with Firefox, Chrome, Opera, and Edge.
CWASA software should work with Firefox, Chrome, Opera, Chromium, and Vivaldi.
CWASA software should work with Safari.
Standalone Applications : Node.js and Electron
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.
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 may prevent the application being opened immediately because they do not come from the App Store or an identified developer. To run blocked applications it is necessary to open them by double-clicking with the control-key down or by right-clicking and choosing Open. On future occasions the software should launch normally.
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.
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
chmod +x SiGML-Player.AppImage can be entered in a shell.
Legacy Software : Java
Java Web Start
Legacy JASigning applications and applets are launched using 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.