See: Description
Package | Description |
---|---|
basic.diagnostics.javascript |
Javascript-to-Player interface for sending messages from Javascript to the
SignStix diagnostics.
|
basic.javascript |
Javascript-to-Player interface for sending messages from Javascript to the
SignStix reboot, restart, screenshots and other device level actions.
|
basic.networks.javascript |
Javascript-to-Player interface for accessing content over the internet and discovering
other Players on the local network.
|
basic.serial.javascript |
Javascript-to-Player interface for providing access to serial devices
connected via USB.
|
basic.serial.javascript.rfid |
Javascript-to-Player interface for providing access to SignStix RFID pads
connected via USB.
|
basic.serial.javascript.rfid.lift |
Javascript-to-Player interface for setting up lift-and-learn experiences using
SignStix RFID pads connected via USB.
|
config.javascript |
Javascript-to-Player interface for accessing configuration settings.
|
data.tags.javascript |
Javascript-to-Player interface for providing access to the Player's persistent tag database.
|
downloading.javascript |
Javascript-to-Player interface for accessing files living in a folder that has been associated
with a Web View and downloaded to the Player as part of its content.
|
player.engine.javascript |
Javascript-to-Player interface for controlling the play engine.
|
player.stats.javascript |
Javascript-to-Player interface for querying playback statistics.
|
signactivity.panels.javascript |
Javascript-to-Player interface for storing key/value pairs across multiple
Web Views.
|
signage.elements.javascript |
Javascript-to-Player interface for modifying layers dynamically.
|
The functions in this API can be called from Javascript code running inside a Web View layer within a SignStix sign.
The API provides access to various SignStix Player functionality, such as:
This API is supported on all SignStix devices that run the Android operating system. This includes models M12S (box), Philips D-Line (panel), APC380 (box), EKD08 (wedge), MK809III (dongle).
This version of the API is supported on SignStix Player 3.2 and above.
The API includes several top-level interfaces, all beginning with 'SignStix'.
Assuming the API has been enabled on a given Web View, all the interfaces are automatically available.
Use the relevant top-level interface name directly to call an API function from Javascript, for example:
<p>
Hello, this device is in zone: <br/>
<script type="text/javascript">document.write(<b>SignStixConfig.getZoneName()</b>)</script>
<br/>
</p>
To test your web application:
When developing, use the SignStixDebug interface to record information, warnings and error messages in the SignStix logging system.
The resulting messages can be viewed in 3 ways:
To run a Javascript Extension on its own without a web page, set the URL of the Web View to:
about:blank
This note is only relevant if you are deploying a non-interactive Web View within an interactive sequence (i.e. a sequence of signs where one of more of the signs includes an interactive event).
All the signs in an interactive sequence get loaded by the Player as a single operation. (This is an efficiency measure to allow for subsequent fast switching between signs in response to user activity.) However, a consequence of this behaviour is that any Javascript intended to be triggered on page load may first execute when the sequence is loaded, not necessarily when the sign containing the Web View is displayed. Essentially, your Javascript may run sooner than you expect.
This does not apply to interactive Web Views because their content is loaded dynamically when the Web View is displayed.
For further support, please visit www.signstix.com/support.