| Expand | ||
|---|---|---|
| ||
|
...
| Expand | ||
|---|---|---|
| ||
|
This page covers the content requirements, abilities, and restrictions of the HTML rendering engine on BrightSign players.
...
For performance reasons, we recommend against downscaling images. This consumes considerably more resources than either displaying images at their native size or upscaling them.
Memory and Performance
The amount of memory available for HTML applications varies by model:
...
If a font file is not included and referenced by the HTML page, text will be rendered using a default system font. While functional, the default font has little aesthetic appeal, so we recommend including font files for most digital-signage applications. Supported font types include TrueType Font files (.ttf), OpenType Font (.otf), and Web Open Font files (.woff, .woff2).
Creating HTML Pages
Follow these steps when creating HTML pages:
...
GPU rasterization is enabled by default in firmware versions 6.2.x and later.
Optimized Image Rendering
The image-rendering CSS property can be assigned the optimizeSpeedBS value. Using this value ensures that Chromium uses lower-quality but faster bilinear filtering when scaling images to 50% or less. We recommend using this value with pages that scale a lot of images at runtime.
...
BrightSign players are compatible with touchscreens that use standard HID drivers. Note that some manufacturers claim support for HID but still use custom drivers. See this FAQ for further discussion and a list of touchscreen models that have been tested with BrightSign players.
Debugging Webpages
Web Inspector
...
Inspector
You can use the Web Inspector to debug webpages over the local network.
The JavaScript console should only be used in non-production presentations and it should be disabled before you publish in a production environment because it uses more memory, which can lead to frequent reboots, and it compromises security.
Enabling the Web Inspector
The Web Inspector can be enabled using BrightAuthor:connected, BrightAuthor, or BrightScript:
BrightAuthor:connected: Select Allow JavaScript console in theChromium Debuggingsection of the DWS andEnable Javascript consolein Presentation tab > State Properties > Options. To disable Chromium debugging, uncheck either of these boxes.
BrightAuthor: In your BrightAuthor presentation, navigate to File > Presentation Properties > HTML and check the Enable Javascript console box. Note that as of BOS 8.5.31 you will need to also set the enable_web_inspector registry key (in the "html" section) to enable the JavaScript console. See the "inspector_server" in roHtmlWidget for more information.
BrightScript: When creating the roHtmlWidget instance, include the inspector_server initialization parameter and specify a port number. Note that as of BOS 8.5.31, you must set the
enable_web_inspectorregistry key to “1” to enable the web inspector for Chromium on the player (if it is set to “0” or nothing, the web inspector is disabled). For example:
...