Quick Fixes
Problem: If there is no "plots" directory in appdata, the sysinfo graphing tool fails (ristretto waits forever).
Solution: If there is no "plots" directory, sysinfo should create one if needed.
How did this happen: I just renamed one "plots" dir I wanted to keep as "plots-yyyymmdd", as I thought sysinfo will autogenerate a new one if needed.
Logging-info shall be shown until timeout regardless of panel switching
If you change the logging interval or state (start, pause, resume, stop), the logging-info-area is shown for $timeout seconds, in the current layout at the left bottom.
Current behavior: If you switch to another panel, it is hidden during the transition effect, and then shown again, and after the remaining $timeout hidden again. This is a confusing user experience. "Did the state change?", "Why, I only changed the view", etc.
Desired behavior: It should stay at the same position, and fade away after the $timeout, and show up again only if the interval gets altered or the logging state changes. Independent from the panel views and their transition effects. And the readability must be ensured also while the panel transition animation. Either as it does not collide with any panel content, or by placing a black background rectangle, beyond the text, but still above the panel content.
Plot file chose dialog: Shall start in descending order
This shows the newest log files on top, which is the most probable use case, as mosts users likely want to plot one of their newer logs.
One must just change the variable SortOrder in appdata/sysinfo/gtk-2.0/gtkfilechooser.ini to descending.
I think that would be a good default for PND delivery.
Plot templates: Create one which shows correlation between battery-capacity-drainage and usage
AFAIK the drain factors of the battery are:
- to the largest extent: CPU, WiFi — which are logged by sysinfo
- and to some extent: USB, Bluetooth, screen-brightness, loudspeakers — which are not logged (some of them could be tracked, some not at all because of their technical nature (i.e. loudspeaker drainage), AFAIK)
- with little extent: RAM — is logged, but it is not a large power factor, or is it?
I am not familiar with gnuplot, thus I kindly ask you to supply one more well thought built-in plot template, which shows all that necessary correlations in a combined plot, which helps with performance troubleshooting and/or optimization.
It should clearly depict power consumption AND charging power, maybe calculate the difference value between them, so that power consumption is adjusted as an absolute value. Then we would have:
- Power consumption absolute (adjusted from charging, sum of all power consuming Pandora parts)
- Charging (what gets through the charging cable and circuitry into the battery)
- Power consumption relative (battery current + charging current coming in - power consumption)
Then all the energy-draining factors can be clearly seen in correlation to Power-consumption-absolute.
And separately from this one can analyze mere charging issues itself.
Layout of panel "Network": Text block "Download" and "Upload" not aligned
I would prefer them aligned at the same height, meaning, that the Download text block moves closer to the bottom as well.
If you conceptually wanted them at a different height alignment (which I doubt), I would propose to put Upload higher than Download, as the word "up" is immanent in "Upload", the same with "down" in "Download".
Long Term
Panels "Network" and "Storage" seem to consume quite much CPU
If you jump from the panel "Help" to the panel "CPU", you can read in the young past of the graph that "Help" used very little CPU resources.
But if you jump from "Network" or "Storage" to "CPU" you can read, that they both use quite an amount of CPU. I can understand that for the "Network" panel, as it contains a frequently updated graph, but "Storage" just consists from pie charts and rectangular shapes, why does this use so much resources?
Maybe you could use some more resource-friendly drawing techniques? Btw, which ones do you use?
Possibility for comments
- A new CSV column "Comment" is added to our logging format.
- If the user presses the key command for commenting, i.e. "C" :
the program remembers the current timestamp
- a textfield overlay opens, user types i.e. "WiFi enabled. Running Chromium web apps".
- ENTER closes the textfield.
- the program retro-effectively writes the comment into the lcomment cell of the line with the closest timestamp to when the comment writing was started as this was the correlating moment.
Alternative idea: Insert a new line with the real comment-start-timestamp, but then, this would break the regular intervals. Possibly a choice for the config file.