First we embed a screenshot as an img
so that a static version exists if interactivity fails. Next we create a TimeSeries
Javascript object with some Vega JSON
and then initialise it with the container of the img
element. The TimeSeries
then replaces the contents of the container with an interactive version.
The same as Example 1 but we load the data from external CSV files.
This example behaves in a similar way to the one above except that we load the Vega JSON
from a separate file. The fit:true
attribute tells TimeSeries
to use the existing size of the element in the HTML; over-riding the size specified in the JSON
file.
This example is identical to the one above except that the container has a size specified in CSS and we inherit that using the fit:true
option rather than use the width and height set in the JSON
.
This example shows the same timeseries as the previous example but it is non-interactive by default. We add a CSS class to it and a Javascript event so that the end-user can choose to initialize it. This can help reduce the amount of processing done on page load if there are multiple timeseries on the page.
A more complicated example with multiple series all in different CSV
files.
This example uses a different dataset. Once again we delay loading so start with a static image. This time we use the mouseover
event to prompt interaction. In this example we style the tooltips using a CSS class (aas-theme
) provided in the Javascript set-up.