-
 KDE-Apps.org Applications for the KDE-Desktop 
 GTK-Apps.org Applications using the GTK Toolkit 
 GnomeFiles.org Applications for GNOME 
 MeeGo-Central.org Applications for MeeGo 
 CLI-Apps.org Command Line Applications 
 Qt-Apps.org Free Qt Applications 
 Qt-Prop.org Proprietary Qt Applications 
 Maemo-Apps.org Applications for the Maemo Plattform 
 Java-Apps.org Free Java Applications 
 eyeOS-Apps.org Free eyeOS Applications 
 Wine-Apps.org Wine Applications 
 Server-Apps.org Server Applications 
 apps.ownCloud.com ownCloud Applications 
--
-
 KDE-Look.org Artwork for the KDE-Desktop 
 GNOME-Look.org Artwork for the GNOME-Desktop 
 Xfce-Look.org Artwork for the Xfce-Desktop 
 Box-Look.org Artwork for your Windowmanager 
 E17-Stuff.org Artwork for Enlightenment 
 Beryl-Themes.org Artwork for the Beryl Windowmanager 
 Compiz-Themes.org Artwork for the Compiz Windowmanager 
 EDE-Look.org Themes for your EDE Desktop 
--
-
 Debian-Art.org Stuff for Debian 
 Gentoo-Art.org Artwork for Gentoo Linux 
 SUSE-Art.org Artwork for openSUSE 
 Ubuntu-Art.org Artwork for Ubuntu 
 Kubuntu-Art.org Artwork for Kubuntu 
 LinuxMint-Art.org Artwork for Linux Mint 
 Arch-Stuff.org Art And Stuff for Arch Linux 
 Frugalware-Art.org Themes for Frugalware 
 Fedora-Art.org Artwork for Fedora Linux 
 Mandriva-Art.org Artwork for Mandriva Linux 
--
-
 KDE-Files.org Files for KDE Applications 
 OpenTemplate.org Documents for OpenOffice.org
 GIMPStuff.org Files for GIMP
 InkscapeStuff.org Files for Inkscape
 ScribusStuff.org Files for Scribus
 BlenderStuff.org Textures and Objects for Blender
 VLC-Addons.org Themes and Extensions for VLC
--
-
 KDE-Help.org Support for your KDE Desktop 
 GNOME-Help.org Support for your GNOME Desktop 
 Xfce-Help.org Support for your Xfce Desktop 
--
openDesktop.orgopenDesktop.org:   Applications   Artwork   Linux Distributions   Documents    LinuxDaily.com    Linux42.org    OpenSkillz.com   
 
Artwork
News
Groups
Knowledge
Events
Forum
People
Jobs
Register
Login



Sponsoring


-
- Content .- Fans (26) .- Knowledge Base (1) . 

Yasp-Scripted (Systemmonitor) v1.0.8a

   1.0.8a  

Plasmoid Binary

Score 86%
Yasp-Scripted (Systemmonitor) v1.0.8a
zoom


Yasp-Scripted (Systemmonitor) v1.0.8a
zoom


Yasp-Scripted (Systemmonitor) v1.0.8a
zoom


Minimum required   KDE 4.x
Downloads:  10586
Submitted:  Jul 31 2009
Updated:  Feb 25 2011

Description:

Yes, Yet another systemmonitor plasmoid.
But still different from the others.
The only useful plasmoid systemmonitor i have found was Yasp. The problem with it was that it was not configurable enough.
So I came up with the idea, that everyone has its own imaginations of what belongs into a systemmonitor and what not. The birth of Yasp-scripted.
The name is similar to Yasp, because I use some modified code from that project.
The biggest advantage is that you can add things to the monitor or remove some, by just changing the script file and reparse it again...) No recompilation or something like that needed...
The scriptfile which comes with this applet is a scriptfile which fits exactly my system. You probably need to change it to fit your system (e.g. if you do not have a wireless lan card, you need to remove the wlan stuff from the script file).

You can send me your script, such that I can upload a whole bunch of scripts, the user could choose of later (maybe with a screenshot to see directly what the script does)

The scripts can be found in the directory yasp_scripts.
The 1st screenshot is systemmonitor_by_mtr.script, the 2nd screenshot is systemmonitor_by_patkoscsaba.script
and the 3rd screenshot is the script collection by duncan
(thx for the scripts).

If you want to align things, you should either use a monospace font, or use a \t in the value.

If you are familiar with svg you maybe will create your own svg's for the bar-meter. Send them please to me to have a wider range of look and feel for the system monitor ;)




Changelog:

1.0.8a - wrong folder prefix ;)

1.0.8 - bug fixed when reparsing (the kde-plasma-handle was deleted, but we should not delete it)

1.0.7 - bug fixed if engine-sensors contains a colon
- Added script by joseph (thx for the script)
- New script by aldo (thx for the script)

1.0.6 - stack keyword added to plotter (thx Chris99 for the patch)
- Script by mtr added (thx for the script)

1.0.5 - fix crash on reparsing in kde-4.5.2 (with 4.5.2 reparsing works again, but 4.5.1 and 4.5.0 have a bug)

1.0.4
- Label preferredSize setting correctly + sizePolicy changed

1.0.3
- meter sizePolicy changed (works now better in KDE-4.5)
- bugfix for KDE-4.5 such that it does not crash on removal

1.0.2
- workaround for problems with KDE-4.5 and meters (min_height parameter added)
- added script by aldo to the package (italian labels)
(- known issue: yasp-scripted crashes on reparsing in kde-4.5. This will be fixed in a later release)

1.0.1 - bug fixed if yasp is closed while parsing the script

1.0: - Reparsing should be more stable




LicenseGPL
Source(Yasp-Scripted v1.0.8a)
Arch(Arch Linux PKGBUILD)
Send to a friend
Subscribe
Other  Artwork  from finkandreas
Report inappropriate content



goto page: prev   1  2  3  4  5  6  7  8  9  10  11  12 ...

-

 Problem in KDE initialization

 
 by ronanjardim on: Oct 4 2009
 
Score 50%

Hi,

I have started to see a little problem in your plasmoid.
When I start KDE (logout / login), for some reason, the plasmoid says that it couldn't find the sensors of plasma (type="engine").
It starts to work very well when I re-parse the script. So I think it is something related to initialization.

Thanks,
Ronan.


Reply to this

-

 Re: Problem in KDE initialization

 
 by finkandreas on: Oct 5 2009
 
Score 50%

Does this only happen when you logout and login again, or does this also happen on the first startup?


Reply to this

-

 Re: Re: Problem in KDE initialization

 
 by ronanjardim on: Oct 5 2009
 
Score 50%

It also happens on start-up.
But it isn't deterministic. It happens just a few times and not every initialization of KDE. I'm trying to find some behavior to characterize better this problem.

Thanks,
Ronan.


Reply to this

-

 Re: Re: Re: Problem in KDE initialization

 
 by finkandreas on: Oct 5 2009
 
Score 50%

Ok, then I guess I know what the problem is:
The plasmoid tries to first setup all sensors, and if one sensor could not be setup it stops the processing and gives a message like: This sensor could not be...
The problem is, that the plasma-sensors (type="engine") are asynchronious, i.e. the do not give directly a response but more or less when they have the data.
Yasp-scripted is waiting some time until it gets all data, but sometimes your pc is just too busy to get the data in the period yasp is waiting for and then you get this message.
You could try to replace this line:
scriptparser.cpp:489 while ( m_pYasp->DependenciesFulfilled(Dependencies) == false && nCount++ < 200 )
by the line
while ( m_pYasp->DependenciesFulfilled(Dependencies) == false && nCount++ < 500 )

this lets yasp waiting even longer for the sensors to be registered. I hope this fixes the problem (it fails on startup because kde is loading a lot of stuff then, and it takes some time to settle down, but for me 200 was always enough)


Reply to this

-

 Re: Re: Re: Re: Problem in KDE initialization

 
 by Droopy159 on: Nov 5 2009
 
Score 50%

I've the same problem but I don't see where I've to modify that. There's no such a line in .yasp.script (I just use systemmonitor.script to create my own .yasp.script)


Reply to this

-

 Re: Problem in

 
 by DuncanKDE on: Nov 6 2009
 
Score 50%

He's talking about modifying the yasp-scripted plasmoid source code itself, then recompiling it, as can be seen by the reference to the *.cpp file.

FWIW I've not tried it, but may, as I have the same issues here.

I have an idea that might work in a script, however, but haven't tried it yet. If the script is parsed in order as I suspect, it's possible a single-shot sensor at the top, type program, that simply called sleep, for a user-configurable number of seconds, might just do it. This "delay" sensor wouldn't have to be hooked up to an output, simply fired one-shot. If it works, that would be enough to give plasma and the rest of the system time to settle down, before the script started running normally.

I'll have to try it and post back...


Duncan
Reply to this

-
.

 Re: Problem in

 
 by DuncanKDE on: Nov 6 2009
 
Score 50%

Well... /THAT/ didn't work! Sleep behaved as it should, but with all of plasma apparently being single-threaded, the delay for the one script not only caused it to fail, but all the others to fail as well! Plus, the entire plasma desktop (both desktop and panels) was frozen for the length of the sleep, or until yasp-scripted timed it out and returned the usual sensor can't be registered error after about 10 seconds, if the sleep was 10s or longer.

Which reveals the other side of the coin. Yasp-scripted must be careful with its timeouts, because they freeze the entire plasma desktop during the wait! The same is true for users creating scripts. Anything they call that takes time to process... will apparently freeze the entire desktop until the processing is done, or until the timeout, whichever is first.

The ultimate fix would therefore be a new version of yasp-scripted, that (1) either shortens the timeout again or makes it a script or sensor configurable setting, and (2) introduces a new optional sensor parameter, at least for type engine and probably for type program as well, that sets the value to return on timeout. If this value isn't set, it'd return the current warning, "breaking" the script as it currently does, as that's useful for troubleshooting purposes in case of typos and the like.

(The one change I'd make to the warning, however, would be to wrap it at some arbitrary width, say 25 characters, as doubling or more the expected width of the plasmoid isn't particularly practical, especially when you have multiple yasp-scripted plasmoids lined up side-by-side on a panel, already filling the available width.)


Duncan

-

 Re: Re: Problem in

 
 by finkandreas on: Nov 6 2009
 
Score 50%

Sorry, I do not have much time for fixing the problem, but actually a sleep sensor should work, since the sensor parsing is done in another thread, i.e. it shouldn't freeze the main thread. Unfortunately I changed from KDE to openbox, such that testing is not possible atm... So I really do not know, why a sleep sensor is blocking plasma completely. And why plasma is single threaded I do not understand either, since this would mean that any plasmoid can block your whole desktop, which would be quite stupid.



-

 Re: Re: Problem in

 
 by finkandreas on: Nov 10 2009
 
Score 50%

Ok, I've looked once again in my source code and voila, I've seen that the parsing itself happens in a seperate thread, whereas the execution happens in the main thread (which of course is a stupid idea, and will probably be changed)
And finally I understood why plasma needs to be single threaded, since paintings can only happen in the main thread in qt, and thus all plasmoids need to run in the main thread...

But unlike duncan has mentioned that the waiting should be very careful, the waiting can be very long since it happens in a second thread and doesn't bother the main thread... So increasing the number as mentioned in the workaround above should work...



-

 Re: Re: Problem in

 
 by Droopy159 on: Nov 18 2009
 
Score 50%

Thanks for the update and both contributions. It works perfectly. It's now for me the perfect system monitor I'm looking for a while.



-

 clickable icons?

 
 by rangerGR on: Oct 6 2009
 
Score 50%

Is it possible to use clickable icons like SuperKaramba?


Reply to this

-

 Re: clickable icons?

 
 by finkandreas on: Oct 7 2009
 
Score 50%

There is nothing impossible, but the question is what you want to do with that...
D'you want to start some program, or do you want get more information when clicking on the icon (like a small box appearing with some information)


Reply to this

-

 Re: Re: clickable icons?

 
 by rangerGR on: Oct 7 2009
 
Score 50%

To start a program but mainly it will make possible to execute some qdbus commands.
For example, control amarok, ktorrent and every KDE program ;)


Reply to this

-

 Re: Re: Re: clickable icons?

 
 by finkandreas on: Nov 19 2009
 
Score 50%

Ok, finally I found some time to implement this. So have a look at version 0.99, there are some new features.
Shortly said for the keyword value you can add "icon_click", "key_click" and "value_click"
For the keyword "text" you can add "click"
And a completely new keyword was introduced, namely "icons". The icons keyword adds a horizontal stack of icons where each icon can have it's own click event (look in README.syntax)


Reply to this

-
.

 Re: Re: Re: Re: clickable icons?

 
 by rangerGR on: Nov 21 2009
 
Score 50%

Excellent!
Works like a charm

Thanks!


Reply to this

-

 Scripts plus... contribution

 
 by DuncanKDE on: Oct 22 2009
 
Score 50%

I'm using yasp-scripted as a more-flexible substitute for the missing "application formerly known as ksysguard" kicker applet in kde4. In kde3 I had a LOT of stuff graphed, so I missed that applet quite a bit until I found yasp-scripted and got my sets of scripts setup.

So now I have about eight scripts, designed to be lined up across a 400 px high (max height, here) panel, graphing and current numbers for CPU activity (four cores, separate user/system/nice/wait/total, %), memory (separate app, buffer, cache, total-used, swap-used, MB), load&fans (1/5/15 load average, 4 fans, RPM), temps (four core temps, five system temps, C), disk activity (read and write graphed separately for four separate disks, MB), Eth0 net activity (separate Rx/Tx, four graphs 8X factor, no wifi but it'd not be hard to adapt), and time&top (time locally and UTC, date, last repository sync, last boot date, day and week of year, Unix time in seconds updated 1/min, CPU% top five, Mem% top five).

I run them eight-across, lined up on a horizontal panel. It'd make a great screenshot for this kde-look page.

Additionally I created a gentoo ebuild, which could be posted.

The question is, what's the best way to get it to you? I suppose I could send the scripts and ebuild via the contact thing, or here, but I'm not sure whether they'd get line-wrap mangled. And the screen-shot...

I think you can click my name on the message and send me a private mail with your email address if you like. Either that, or if you have someplace I could upload them. Or I could imagebin/pastebin them, I suppose, if you'd get around to fetching them soon enough. Your call.


Duncan
Reply to this

-

 Re: Scripts plus... contribution

 
 by finkandreas on: Oct 29 2009
 
Score 50%

Thanks for the scripts. I've packaged them now with the main tarball...


Reply to this

-

 Thanks

 
 by vazoline on: Nov 2 2009
 
Score 50%

I've been looking for something like this for a while. Very nice job!


Reply to this

-

 Conditionnal display

 
 by Temet on: Nov 19 2009
 
Score 50%

Hello!
Thanks for your plasmoid, I use it as my system monitor since I installed KDE 4 (2 weeks ago).
It just works fine!

I didn't see this feature, so I emit the idea and you can implement it if you like it :D
I would like to be able to display some parts only under a certain condition.

For example, see the occupation on my external HD, only if it's power on. Something like:

if $(mount | grep /mnt/HDEXT)
blablabla to display partition stats
endif

Anyway, thanks for this plasmoid ;)


Reply to this

-

 Re: Conditionnal display

 
 by finkandreas on: Nov 21 2009
 
Score 50%

sounds interesting, but I won't implement it, since the system behind yasp-scripted was not thought for that, and therefore it requires a bit more work to do sth like that...
If you or anyone else needs this feature feel free to implement it.


Reply to this

-

 problem with the display of me

 
 by nicollivier on: Dec 2 2009
 
Score 50%

Hi, :)

I use it on Mandriva 2010 x86-64.

With the command htop, I see " mem: 805/3878MB", but with plasmoid "05/3878MB". So I don't have the first digit. I'm alone with this pb?!

Nico


Reply to this

-

 Re: problem with the display of me

 
 by finkandreas on: Dec 2 2009
 
Score 50%

That's strange. Could you post the sensors and values you're using for getting this line?


Reply to this

-

 Re: Re: problem with display of me

 
 by nicollivier on: Dec 3 2009
 
Score 50%

Yes that's strange.

On my laptop:
sensor name="RamApplicationMb" type="engine" cmd="systemmonitor:mem/physical/application:value" math="int $0 1024 /"
sensor name="RamTotalMb" type="program" cmd=$cat /proc/meminfo | grep MemTotal | sed -e "s/MemTotal: *\([0-9]*\).*/\1/"$ math="int $0 1024 /" interval="single"
meter use="RamApplicationMb" use="RamTotalMb" label:0="Ram" label:1="$1 sur $2 Mb" alignment:1="right" min="0" max="$2" value="$1"

And on my desktop I have same code, and it's ok.

But my laptop is Acer 1810TZ with 4Go Ram, Mdv 64b
And my desktop Acer M3640 with 2Go Ram, Mdv 32b


Reply to this

-

 Re: problem with display of me

 
 by DuncanKDE on: Dec 3 2009
 
Score 50%

Hmm... I don't use meters here, as I like to see the trends and thus use plotters instead. The plotters don't display a number, however, just the plot, so I use a value line as well, thus getting a text readout of the current number as well as a plot over time.

What happens if you add a value line? Does it show the whole thing, or is it truncated as well? Does the meter have enough room to display the whole thing?

Here's a value line to try:

value key="RamApp" use="RamApplicationMb" format="$1 MB"

If that shows up correctly, then the sensor is correct, the number is just being truncated in the meter display. As I don't do meters I can't help much there. If the number is coming up 05 instead of 805 there as well, then perhaps it's a sensor issue, and since the sensor is using the systemmonitor engine, it's likely a bug in it, that is, in kde itself, since that's where the engine is.

FWIW, I'm running Gentoo/amd64 here, so 64-bit, without issues, but as I said I don't do meters only plotters and values, so I'd not have seen any meter issues, and of course if it's a distribution bug, I'd have missed that too since I'm on a different distribution.


Reply to this

-

 Re: Re: Re: problem with display of me

 
 by finkandreas on: Dec 3 2009
 
Score 50%

Another thing you could try: make the plasmoid wider, than the '8' should appear...
If you see the 805 then completely the problem is that svg for the meter defines a too small field, so you can change the svg itself and define a bigger field.
But the simplest is to resize the plasmoid that it becomes wider.


Reply to this

-

 Re: problem with display of me

 
 by DuncanKDE on: Dec 3 2009
 
Score 50%

... Or try using a smaller or at least narrower font...


Reply to this

-

 Re: Re: problem with display of me

 
 by nicollivier on: Dec 4 2009
 
Score 50%

I enlarged the size of the window and it's good.

Tks :)


Reply to this

goto page: prev   1  2  3  4  5  6  7  8  9  10  11  12 ...

Add commentBack






-

-
How do you like Plasma 5?
 The best KDE Desktop ever.
 Definitely a nice improvement.
 Not decided yet. Haven't tried it yet.
 I do not like some of the changes.
 KDE is taking the wrong way.
 I am still sticking with KDE 3.5.
 I have no opinion, but wanted to vote anyway.

resultmore




 
 
 Who we are
Contact
More about us
Frequently Asked Questions
Register
Twitter
Blog
Explore
Artwork
Jobs
Knowledge
Events
People
Updates on identi.ca
Updates on Twitter
Facebook App
Content RSS   
News RSS   
Discussion RSS   
Events RSS   

Participate
Groups
Forum
Add Artwork
Public API
About KDE-Look.org
Legal Notice
Spreadshirt Shop
CafePress Shop
Advertising
Sponsor us
Report Abuse
 

Copyright 2001-2014 KDE-Look.org Team  
All rights reserved. KDE-Look.org is not liable for any content or goods on this site.
All contributors are responsible for the lawfulness of their uploads.
KDE and K Desktop Environment are trademarks of KDE e.V.