DDC-14 Chart/Sparkline UX Web Widget

Current Status:
In Development GitLab Last Commit GitLab Contributors

Suggested By: @Rosenthaler
You Track: DDC-14
Gitlab Branch: DDC-14

Description:
A chart widget using Apex Charts. The widget should be highly configurable, allow multiple series and data types. There should be export options and the ability to display the widget as a sparkline.

1 Like

Update on the chart widget, more configurations to be added, but its starting to come together.

Currently done:

  • Multiple series from Wb View Bindings
  • Different chart types
  • Data Labels
  • Sparkline/Full Chart
  • Time Range Selection
  • Display in card
  • Set card properties like border and radius
  • Show/hide toolbar

3 Likes

Small update, still working on getting the API correct for history rollup and aggregation so we can do some more advanced charting. I decided to move away from ApexCharts as it has some performance issues with large data sets.

Instead we are using Plotly which is built on D3 and has a lot of built in features that will save us time.

If there are any particular history chart types that you think are beneficial and should be included please let us know!

1 Like

Uuuh very nice :smiley:

A few I would like to see is something like this for meters (without the animation)
Bar Chart Race / D3 | Observable (observablehq.com)

This would be awesome for a single meter (one can dream right :wink: )
Electricity Usage, 2019 / Mike Bostock | Observable (observablehq.com)

And if you can make a pie chart, I’ll rename you The Pie Master

1 Like

I recon those are already built into plotly. Might be as simple as setting the chart type.

I’ll add these to the list :ok_hand:

Plotly has an extensive collection of available chart types including heat map and pie chart options. I’m sure using the plotly framework all of what you’re looking for should be possible.

I’ve been after something like their simple indicator chart for dashboard usage.

@Giantsbane are you still using the n:history tag to gather the datasets or moving over to specifying the history data?

This is on the todo list once the core charting widget is completed

Still using the n:history tag to retrieve the history ord/id. Then we are making an API call to the history api with the history ids to retrieve the data. DDC-14 remote repo branch is a many commits behind the local version on my PC. I will be pushing it as soon as I work out the best way to achieve sampling and rollup.

1 Like

Nice one. Looking forward to checking it out.

1 Like

whats been happening with updates on this? keen to try it out.

Been bogged down unfortunately at the moment mate. My real job has to take priority, however the module is still I. The pipeline. As any hobby, it’s something we tend to when we have time :slight_smile: slow and steady

Yup, same here. Between work and home life I’ve had little or no spare time and unfortunately it’s going to be like it until after the new year :grimacing: