Open kodeaben opened 2 years ago
Yes, this is very a nice post to have and I have a few comments.
Chart.register(zoomPlugin);
is executed, only the ChartJS register the plugin however Kirby Chart does not. To fix this we made a hack where we get the ChartJS object from the Kirby Chart and from this we can use functions like ChartJS.zoomScale to adjust the view with a new date range. This "hack" also solved another problem we had which was the Kirby Chart does have a function called update(); to force an update to the Chart.
We still have one problem and that is making the graph wait with first draw until data is ready. The initialize function is so that we can wait to create the Chart when our data is ready to be shown and our Chart.Option has been set up the right data.
Describe the research request
It is difficult for the users of the Kirby charts to make changes/additions to the charts.
This results in either requests to the Kirby team to fix bugs or add functionality, or the teams implementing their own charts, thus not using Kirbys.
This issue investigates how Kirby can offer a chart which gives the implementer more freedom to modify and add functionality to the table.
This will include talking to developers who are using charts.
Whats the outcome?
The outcome of this investigation is a plan on how to improve the usage of Kirbys charts for its users.
Have you considered any alternatives?
This issue is considering ALL possibilities.
Are there any additional context?
No