Line Diagram Widget

[noyannus]

Checklist

• [X] I made sure that there are no similar feature requests - open or closed.
• [X] I have taken the time to fill in all the required details in an appropriate descriptive way. I understand that the feature request will be dismissed otherwise.
• [X] This issue contains only one feature request.

Describe the Feature you'd like

A line diagram widget would be very informative.

• This line diagram shows cumulative used data from a given time period.
• Abscissa can be set to various times: from \<date> to \<date>; period of current data plan; this day; this week; this month; this quarter; this year.
• Ordinate to show the cumulative data amount.
• If a data plan with data limit is active, a horizontal line to indicate its total. This will allow the user to estimate whether (and when) a given plan will be exhausted. Alternatively, let the user manually set the data amount to be indicated by this line.
• Different cumulative lines and limit lines with different color schemes for different data plans; at the minimum separate for Mobile and Wifi.
• The widget should come in different sizes from 1x1 thru 1x5, 2x1..2x5, 3x1..3x5, etc., so the user can chose what is legible for them and adapt to various time scales and resolutions of data usage.

Why do you want this feature?

To have an information at a glance what the data use and its relation to data plans is. Line Diagram is much easier to grasp than written figures.

Additional context

No response

[itsdrnoob]

I believe that displaying the amount of data used in a straightforward text format can be more user-friendly and less overwhelming compared to a graphical representation. It allows users to quickly check their data usage without having to interpret a chart. There's also an element of battery usage to consider when using more complex graphical elements.

[noyannus]

I believe that displaying the amount of data used in a straightforward text format can be more user-friendly and less overwhelming compared to a graphical representation

Different cognition types parse info differently. For the more visual types, a single glance tells whether the line of used data is going to cross the set data plan line soon or much later. Far easier to visually extrapolate than from numbers.

There's also an element of battery usage to consider when using more complex graphical elements.

True, but it doesn't need to be updated frequently. 1/300th of the abscissa time scale should be enough (this a rough guess for "once per pixel on the time axis", more frequent is just wasted cpu cycles.

Can probably even be updated once per 10 pixels time equivalent. On a widget the diagram is so small as to make small changes not discernible, and in the app it is not continuously on display anyway.