What charting should we use?

[modersohn]

I'm slowly making progress with the PairsDetail page from #49 and was excited to try the MudBlazor Chart, but so far it is underwhelming:

I can't seem to find a way to influence y axis scaling - and it is useless like it is. If I don't scale down the values (millions in volume of course) the page rendering becomes extremely slow so much it is unusable.

The question is - should we stick with the MudBlazor chart and just accept its shortcomings - or should we get on the lookout and try to find a better alternative? I mean if the long term plan is to have some fancy price charts one day, we'd need to search for something else anyway. And there's lot's of interesting data available via the graph!

Edit: Here's the shortcut to their doc and holy moly, if I run the code of the first chart in try.mudblazor (click Run this code on the top right), it comes up quite quickly, but if I move the splitter around it's starts to react very slowly!

What's your opinion?

[modersohn]

This quote form their github is quite telling:

MudBlazor still lacks in charts. We already started working on new charts. But decided to focus on more important issues at the moment.
I suggest that you use something like https://github.com/apexcharts/Blazor-ApexCharts for now

So indeed maybe we should have a look at ApexCharts?

[fudgebucket27]

That looks like a great library! I've used chart.js in the past but not sure how difficult it would be to integrate that with Blazor.

[modersohn]

I wouldn't even know where to start with chart.js and ApexCharts do look powerful and easy to integrate, so I'll go with that one!

[modersohn]

I only now realise that this is actually a Blazor wrapper around a JavaScript library as well. OTOH I found no convincing Blazor wrappers for chart.js, so still willing to try to go with this one.

Got it working in general, but still some obstacles:

1. formatting of Y values doesn't seem to work like in the demo (see UseDotNet at the end)
2. X values are off - like shown only for every 5/6th bar but misplaced
3. Does obviously not adjust to our own dark mode, nor to the system settings