Bug 172312

try to move System Monitor plasma widget to panel

I'm sorry but I don't understand. I already have that widget in my panel; but what does that have to do with this request?

Just a note that I for one still have this wish under 4.2.

(FYI, the most important reason I have for this wish is that there's no way to monitor remote systems with the current plasmoids, which means that I have to keep a 3.5.x system available for the purpose of gathering and displaying remote statistics.)

*** This bug has been confirmed by popular vote. ***

I need this too.  See my screenshots page for why. (A 1500x300 ksysguard kicker applet, 16 plotters each 93x300.)

http://members.cox.net/pu61ic.1inux.dunc4n/pix/screenshots/

In KDE 3, the user could define monitors in ksysguard with all relevant
parameters, i.e. defined range, color, sensor, vertical and horizontal lines
and then drag&drop them into the panel. This is not possible in KDE 4. Please
return this functionality. Thanks.

Definitely needed, I wish to drag the sensors from ksysguard to my panel applet, and to choose the display style: bar, plot, digital, etc. I still need ksensors (very old kde3 app) to display my cpu temperature in systray!!

Instead of having multiple plasmoids (system monitor - ram, system monitor - cpu, system monitor - network, system monitor - disk, etc..) we need a SINGLE plasmoid that accepts elements dragged from ksysguard, and deeply configurable: colors, style, ranges, etc.

Agreed with commend #6. I do miss it too. Exactly, I need what you can see in the bottom-right corner of this screenshot: http://dimgel.ru/rsdn/firefox3-linux.png

*** Bug 191377 has been marked as a duplicate of this bug. ***

I'd like to see plasmoid embedding ksysguard as well, especially since those "new" plasma system monitor plasmods aren't very configurable and they have some scaling glitches.

I absolutely second this wishlist... I need to keep an eye on some remote system, and the old KDE3 applet was just perfect. Nothing similar in KDE4... very bad.

+10 votes

For those still looking for ksysguard-kicker applet replacements:

Either super-karamba or the yasp-scripted plasmoid from kdelook are able to replace at least the local functionality (I think they can replace remote as well, but I only do local so don't know for sure).  However, these tools depend very much on a reasonable knowledge of the command line for scripting, etc, since their functionality basically takes STDOUT and plots/bargraphs/text-displays it, however they're configured, making them at the same time *EXTREMELY* flexible and not really appropriate for those who aren't particularly comfortable on the command line and who can't work with at least shell scripting and sed/grep/awk/cut/head/tail, etc.

Yasp-scripted and super-karamba are reasonably similar to each other and anyone knowing one will immediately feel reasonably at home with the other, with two differences of note.

1) Yasp-scripted lacks the element positioning language of super-karamba, depending instead on line ordering for vertical layout, and not supporting horizontal layout.  (If you want multiple horizontal elements, you run multiple yasp-scripted plasmoids.)  It also lacks the direct python support and bindings of super-karamba.  As such, yasp-scripted is simpler and easier to learn initially, with the possibility of graduating to super-karamba once you understand how the general idea works.

2) Yasp-scripted is a (single) plasmoid on kdelook, while super-karamba themes are directly supported by plasma itself, as yet another choice of plasmoid implementation language.

FWIW, I originally chose yasp-scripted here, as I wasn't yet familiar with either when I was trying to do my own kde4 migration, and I didn't want to hassle the extra complexity of super-karamba when I had a bunch of other upgrade issues on my plate to deal with at the same time.  In addition to yasp-scripted now shipping with a number of my own scripts for it, I'm subscribed to its comment feed on kdelook, and try to help people out with questions where I can (tho I'm not the author or a programmer, so I leave feature requests and the real complex stuff for him to deal with).

I'll probably graduate to super-karamba at some point, learning in detail the differences and how to port yasp-scripted scripts into super-karamba themes when I do, but there's no real hurry, now, as yasp-scripted meets my needs quite well as it is.

So there's alternatives for those who know the command line, etc, but a rather less flexible and thus less complex alternative that never-the-less implements a reasonably simple way for users to create plasmoids out of ksysguard sensors is still sorely missed, and the individual sensor sysmon plasmoids that presently exist are simply not a satisfactory substitute. =:^(

But I do hope that at least points a few of the advanced folks coming across this bug at something that'll work, anyway.  I wish this pointer had been around for me when I was dealing with the issue.

Hello!

This feature request was filed for KDE Plasma 4, which reached end-of-support status in August 2015. KDE Plasma 5's desktop shell has been almost completely rewritten for better performance and usability, so it is likely that this feature request is already implemented in Plasma 5, or is no longer applicable.

Accordingly, we hope you understand why we must close this feature request. If the requested feature is still desired but not implemented in KDE Plasma 5.12 or later, please feel free to open a new ticket in the "plasmashell" product after reading https://community.kde.org/Get_Involved/Bug_Reporting

If you would like to get involved in KDE's bug triaging effort so that future mass bug closes like this are less likely, please read https://community.kde.org/Get_Involved#Bug_Triaging

Thanks for your understanding!

Nate Graham