Closed nilshoerrmann closed 3 years ago
Maybe using a bar chart instead of a graph would be more true to the given data?
I'll have to think about this for a while. Doesn't convince me immediately to not show data from the ongoing timeframe. And I think many are used to this visualization as it is used by Google Analytics and others... but I might change my mind when I think about this more.
Doesn't convince me immediately to not show data from the ongoing timeframe.
That might be a misunderstanding from my quick mockup. My point was that it's a bit confusing to see the graph fall to zero for the next month (or day, or year – depending on the set context). This makes it look as if there was a peek but everything has been resolved by now (it's down to zero again) which is not correct because the peek is happening right now.
And I think many are used to this visualization as it is used by Google Analytics and others...
I'm not a Google Analytics user so you might have a point here.
Ok, I understood you now. This is hard since the chart library doesn't seem to support something like "draw (smooth) lines up until this data point, after that just drop to the next value (0)"
Maybe this library might be interesting: https://chartscss.org/
That looks great at a first look. Will give it a spin!
Oh never mind it's 72kb - that's quite big
Uh, I hadn't checked that!
But it gave me ideas to try something else
I think I am getting closer to a solution where it just cuts off the graph at today (this month/this year...)
That's a great direction because it emphasises the current stats. Thanks for working on the visualisation 👍
✅ in 4.0.0-beta.1
What aspect in Retour bothers you and why?
Looking at the timeline makes me think that all issues have been resolved because the graph goes down to zero on the x axis:
How would you improve it?
Cutting of at the current point in time would make the actual stats clearer:
How would this make Retour better?
The stats would be more accurate :)