Sad Liskov

Many small changes for this release.

For the receiver:

• Don't run a benchmark on start, animate less by default. Three new receivers can be used: /receiver-slow, /receiver-medium, /receiver-fast, depending on how fast your device is. Default is /receiver-medium.
• Rework viewport logic. Setting a viewport for a device should now work on Chromecast and Android devices. Better interaction between device viewport and dashboard viewport.
• Credential storage in URL is only used if local storage has failed. May be a regression for some people. Open an issue if this is the case.
• Iframes are not sandboxed anymore. This should make stuff work better.

For the server:

• Migrate the demo app to Heroku.
• Use Mustache and runtime templating.
• Support for more recent versions of Node. Node 0.10 is not supported anymore.
• Documentation update.
• Various fixes.

For the Android application:

• Webview update (equivalent to Chromium 52).
• Client certificate support (either in a file or embedded).
• Android 4.0 support is dropped.
• Android TV compatibility.

Distracted Morse

From this version, Dashkiosk will keep the current dashboard displayed in spite of communication problems with the server part. This should reduce pressure on less powerful device and a dashboard that doesn't update is still more useful than no dashboard at all.

Nostalgic McLean

This update makes Dashkiosk compatible with Node 4.1.

Other changes:

• The delay between heartbeats is reduced to enable low-end devices to cope better under load (e.g Chromecast devices).
• The build system has been updated to provide source map files.

No change for the Android app.

High Payne

This is a small release:

• Drag'n'drop of dashboard now moves by default. Use Ctrl to do a copy (or a duplicate)
• Branding is done through a runtime option/environment variable now

Also, most dependencies have been updated. This is the more invasive change. File an issue in case of a problem and stick to the previous option.

Furious Fermi

Most important changes are:

• The most visible change of this release is the ability to copy a dashboard from one group to another or to duplicate a dashboard with drag'n'drop.
• A receiver is now benchmarked to check if it is too slow. In this case, animations are disabled. This is mostly useful on slow devices with non-accelerated browsers, like a Raspberry Pi.
• The Zepto dependency has been dropped from all mini-apps (Chromecast receiver, generic receiver, unassigned displays) in favor of vanilla Javascript. Hopefully, no new bugs has been introduced.

In an attempt to support the previously future but now cancelled Matchstick.tv, a Firefox OS receiver is now also present. Not really tested. No DRM have unfortunately been implemented in this receiver.

There is also a Dockerfile in case you want to run Dashkiosk in Docker. In this case, you won't be able to drive any Chromecast:

$ docker run -d -p 8080:8080 \
             -v /var/lib/dashkiosk/database:/database \
             vincentbernat/dashkiosk:2.6.1

Important changes in Android receiver:

• Compatibility with Android 4.0.
• Engine upgrade (Crosswalk 14, Chromium 43).
• Some stability fixes.

Trusting Archimedes

This version doesn't introduce any code change in Dashkiosk.

The Android application has been split up into its own repository and the documentation has been updated to reflect this fact. The Android application is now built with Crosswalk 11 which is using Chromium 39 as a base (the previous version was using Crosswalk 7 with Chromium 35 as a base). Moreover, it is now possible to skip SSL errors in preferences.

Clever Wright

This release adds ability to schedule dashboard display. A dashboard can be displayed during work hours only for example.

Stoic Yonath

Include a demo mode. The demo is running on http://dashkiosk.app.exo.io/admin.

Sleepy Galileo

Small fixes for the receiver and the administration panel. Additional documentation to deploy Dashkiosk to a PaaS.

Determined Morse

This release only fixes Chromecast support broken in the previous release due to a bug in a new feature.