Bug 152608 - Tray and taskbar icon should show cpu usage
Summary: Tray and taskbar icon should show cpu usage
Status: RESOLVED UNMAINTAINED
Alias: None
Product: ksysguard
Classification: Unmaintained
Component: ksysguard (show other bugs)
Version: unspecified
Platform: unspecified All
: NOR wishlist
Target Milestone: ---
Assignee: KSysGuard Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-11-20 20:43 UTC by Yuri
Modified: 2024-09-23 21:01 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
screenshot of a button in the tray (14.71 KB, image/png)
2007-11-21 11:43 UTC, Yuri
Details
Menu in main application to select which tray icons should be shown (43.65 KB, image/jpeg)
2018-08-07 16:48 UTC, Gregor Mi
Details
Example of system tray where 3 icons are enabled (1.63 KB, image/png)
2018-08-07 16:49 UTC, Gregor Mi
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Yuri 2007-11-20 20:43:49 UTC
Version:           1.2.0 (using KDE 3.5.8, compiled sources)
Compiler:          gcc version 3.4.6 [FreeBSD] 20060305
OS:                FreeBSD (i386) release 7.0-BETA2

At least this should be optional.
Also the window that pops up when the mouse is over the button should also show load information in more details.
Comment 1 Greg Martyn 2007-11-21 00:10:36 UTC
I'm sorry, I don't understand. A mockup might help make your wish clearer.
Comment 2 Yuri 2007-11-21 01:00:27 UTC
Sorry I didn't express myself clear.

Right now when I run ksysguard I get a static button showing some knobs. But this is just a picture.

I would like to see the CPU utilization, memory utilization, load average shown in this button. Show it roughly since it's not enough space in the button.

Also the window that comes up when I move my mouse over the button could show some more relevant into as well, not just the work KSysGuard. But this isn't as important as showing system load in the button itself.

My rationale is that this button takes space on the screen. And this space can be utilized much better than just showing the picture.

This will make ksysguard much more usable.
Comment 3 John Tapsell 2007-11-21 01:17:35 UTC
Yuri,

 Could you take a screenshot and indicate what static button thing you
are referring to please?
Comment 4 Yuri 2007-11-21 11:36:19 UTC
John Tapsell wrote:
[bugs.kde.org quoted mail]
John,

Please find screenshot attached.

Yuri
Comment 5 Yuri 2007-11-21 11:43:54 UTC
Created attachment 22142 [details]
screenshot of a button in the tray
Comment 6 Yuri 2008-01-18 21:26:58 UTC
I believe making tray icon show most important information about system load would be major improvement of usability.
Windows shows CPU load in the tray.

Yuri
Comment 7 Gregor Mi 2018-08-07 16:48:39 UTC
Created attachment 114359 [details]
Menu in main application to select which tray icons should be shown

I have attached an example of how this is done in Process Hacker (Free software process monitor and debugging tool for Windows: https://processhacker.sourceforge.io/):

1) "Menu in main application to select which tray icons should be shown"

2) "Example of system tray where 3 icons are enabled". The tray icons have black background by default an show a log graph of recent activity (e.g. CPU usage, Disk IO, network activity)
Comment 8 Gregor Mi 2018-08-07 16:49:46 UTC
Created attachment 114360 [details]
Example of system tray where 3 icons are enabled
Comment 9 Richard Llom 2019-03-12 21:25:23 UTC
System Tray is sooo early 2000s .. ;-)

We have CPU and System load widget available, just saying...
Comment 10 Gregor Mi 2019-03-16 11:05:41 UTC
> We have CPU and System load widget available, just saying...

I am still spoiled from the experience that is is possible to neatly integrate these things into the main application like Process Hacker. :-)
Comment 11 Christoph Cullmann 2024-09-23 21:01:06 UTC
ksysguard is no longer maintained, in Plasma 6 there is the Plasma system monitor for this task.

If your wish is still valid for the Plasma 6 replacement, please re-open and we can move this bug to the new product, thanks!