-
 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:  10460
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  13  14 ...

-

 autoscale

 
 by locke87 on: Jan 12 2010
 
Score 50%

Hey,

I really like that systemmonitor. For me it replaced my good old conky.
But there is one feature, I really miss. Is there a possible way to autoscale units and graphs like conky does.
E.g. if I want to monitor my network, which has a data rate of about 10 MiB/sec at home, the graph is quite useless, if I am at any other place, where I have not such a fast internet connection.

keep on coding :)
locke


Reply to this

-

 Re: autoscale

 
 by finkandreas on: Jan 13 2010
 
Score 50%

if you do not specify min and max the range is calculated automatically by KDE...


Reply to this

-
.

 Re: Re: autoscale

 
 by DuncanKDE on: Jan 13 2010
 
Score 50%

... which would be fine, if there was some way to see what the scale then was. Knowing it's maxing out the graph doesn't help much if, to use the OP's example, I'm supposed to be getting 10 MiByte/s, but for all I know it's maxing at a MiByte/sec.


Reply to this

-

 Re: Re: Re: autoscale

 
 by patkoscsaba on: Jan 13 2010
 
Score 50%

That's why you can display the exact UP/Down values (see second screenshot).

I will try auto-scale as soon as I get home, I was thinking about this, too.


Reply to this

-

 Re: Re: Re: autoscale

 
 by finkandreas on: Jan 13 2010
 
Score 50%

or, you can edit the source code ;)
hint: line 428 in scriptparser.cpp should be changed to:
p->setShowLabels( true );


Reply to this

-

 Re: Re: Re: Re: autoscale

 
 by locke87 on: Jan 13 2010
 
Score 50%

thank you, man!
That's exactly the functionality I was missing :)


Reply to this

-

 Partition monitor?

 
 by Ireyon on: Jan 15 2010
 
Score 50%

Nice system monitor. But one thing does not work - the partition monitors do not do anything on KDE 4.4.


Reply to this

-

 Re: Partition monitor?

 
 by finkandreas on: Jan 15 2010
 
Score 50%

Open plasmaengineexplorer and check how the sensors are named in kde-4.4 or check if the sensors give correct values. If the values there are wrong go to bugs.kde.org and tell them


Reply to this

-
.

 Again a bug

 
 by nicollivier on: Jan 21 2010
 
Score 50%

Hi,

First: thanks a lot for this great job :)
Second: But I've again a bug...
Some informations:
I use Mandriva 2010, kde.4.3.4 i586 on a desktop and a X64 on a laptop.
When I start it, I've a black box with this message :" Waiting for: Eth0Down", something it's with Wlan.
I've must close this box, and open a new.
But when I close it, I've a crash to plasma :(...

Tks Nico


Reply to this

-

 Re: Again a bug

 
 by finkandreas on: Jan 21 2010
 
Score 50%

fixed in 1.0.1...
Did you ever try to reparse the script, instead of restarting the whole plasmoid?

But why are you guys having such problems on mandriva??? Is something broken with your KDE?
If I for example disable my Wlan card (with rmmod rt61pci) I get the same message as you get (Waiting for: ...), but as soon as I do modprobe rt61pci, yasp-scripted automatically continues to parse the script and everything just works fine...
I can't understand why it does not work for you that way???


Reply to this

-

 Re: Re: Again a bug

 
 by nicollivier on: Jan 21 2010
 
Score 50%

Thanks.... Now I've not bug with plasma :)
But I've again the black box :(

I've any problem with kde. I'm not use «cooker».
My wlan connection takes a few seconds to connect, but it's not a problem?!


Reply to this

-

 Re: Re: Re: Again a bug

 
 by finkandreas on: Jan 21 2010
 
Score 50%

very strange... As I said, yasp-scripted waited infinitely long for a sensor to appear, and if it does not appear, it is very likely to not appear on a yasp restart...
So the most likely thing is, that your sensor itself is broken (i.e. it is a sensor which never will be registered).

Could you post the line with sensor name="Eth0Down" and all lines with use="Eth0Down"


Reply to this

-

 Re: Re: Re: Re: Again a bug

 
 by patkoscsaba on: Jan 24 2010
 
Score 50%

No, we don't have any problem with Mandriva or KDE. Mandriva uses a technology to start your DE (ex. KDE) as soon as possible. So, in many cases, the graphical interface comes up before the network or other services. Those services come up in few seconds after KDE is already loaded. This usually happens on newer computers, which are fast enough to start the graphics faster than the rest of the services.

So, YaSP is loaded before network is up, and it waits indefinitely on eth0. The sensor for Eth0Down is:
sensor name="Eth0Down" type="engine" cmd="systemmonitor:network/interfaces/eth0/receiver/data:value"
The sensor becomes available as soon as there is a network connection, but YaSP can't sense it. If the sensor would not come available, YaSP would fail on a restart of the plasmoid, too. But it doesn't, on second run, it gets the sensor correctly.


Reply to this

-

 Re: Re: Re: Re: Re: Again a bug

 
 by finkandreas on: Jan 24 2010
 
Score 50%

And that should not happen at all because the KDE systemmonitor engine (I guess this is what you are using for your sensors), is smart enough to register the sensors as soon as your Network connection appears, and Yasp is smart enough to continue as soon as the systemmonitor engine registers the sensor...
That is what wonders me. Why does it not work on Mandriva because it works perfectly fine on my laptop (there is written for 2 secons Waiting for WLan0 and then at some point it continues because the WLan connection was established)
I'm using gentoo and here the WM is also started as soon as possible, so network connections are established after the window manager was started.


Reply to this

-

 Re: Re: Re: Re: Again a bug

 
 by nicollivier on: Apr 12 2010
 
Score 50%

Hi I come back

I solved my bugs :),
I changed my grub, before I've had this option: «.... splash=silent», and now I've this: «.... elevator=deadline ».

And now it's ok,
May be you understand something, me nothing :)

Nico


Reply to this

-
.

 Can we add gkrellm functions?

 
 by Franksuse64 on: Jan 21 2010
 
Score 50%

Hi!

Hey this one is quite close to what I need! I'll give it a try...

Do you know gkrellm? It's not a plasmoid, but that's the one I am forced to use, it is EXTREMELY configurable and shows more than you could imagine. I use things no plasmoid monitor offers, so I hope I can do it with yours.

But if I can't do you have an idea on how we could import gkrellm functions into your monitor? We could talk outside the site so that I can explain what I am looking for.

But I swear, if you can come up with a solution on how to make it as customizable as gkrellm, you will dominate the plasmoid monitor market! lolll


gkrellm uses gtk or gtk2 and has not changed grafx look for years! It doesn't fit at all KDE4, but I still use it, cuz no other can offer as much as gkrellm.

tnx! :)
Frank


openSUSE 64-Bits
Reply to this

-

 Re: Can we add gkrellm functions?

 
 by finkandreas on: Jan 21 2010
 
Score 50%

I am not aware of a information you cannot get by a simple shell command?

However if you want to have it in a reasonable performance then the KDE way is to write a dataEngine (the systemmonitor is such an dataEngine).
If you are interested in writing such an engine, you can contact me by mail (mail adress should be somewhere in the README I think)


Reply to this

-
.

 Re: Re: Can we add gkrellm functions?

 
 by Franksuse64 on: Jan 21 2010
 
Score 50%

Actually, it's also how things are displayed that is very customizable. For example the Network graphic monitor, you can show the U/D k/s, you can show the total U/D of the day, the total of the month, reset month any day you want, you can split view to show download on top and upload at bottom and you can place the numbers (totals, speed, etc.) anywhere on the network graph section. I don't know if yours can do these details. The network graphic customization is important to me for quick reference and monitoring and also cuz I have limited d/l amount per month that I can watch live.

For CPU graphic monitors, it can show User processes usage vs System processes usage or the total of both, here too you can split view, etc... you can choose to display % and Core Temp besides each core graphic monitor (I have 4 cores, it's useful to have the % and temp of each just besides) and many other things. Of course it can show both CoreTemps and CPUTemp.

I'll play around with your script and see what I can get. :) Maybe it's not too complicated to do a few adjustments.

tnx


openSUSE 64-Bits
Reply to this

-
.

 Re: Re: Re: Can we add gkrellm functions?

 
 by Franksuse64 on: Jan 22 2010
 
Score 50%

And there is also the disk monitor which displays grafx of the I/O with the read Kb/s and write kb/s. This is also very useful, so if there is a command for that your monitor could do it if we pass it on the command, right?


openSUSE 64-Bits
Reply to this

-

 Re: Re: Re: Re: Can we add gkrellm functions?

 
 by finkandreas on: Jan 22 2010
 
Score 50%

check out the scripts by duncan as a good starting point because it seems that he did most of the stuff you need...

for the disk I/O there is in the systemmonitor dataEngine something. Check out with plasmaengineexplorer what there is at all in the systemmonitor dataEngine.


Reply to this

-
.

 Re: Can we add

 
 by DuncanKDE on: Jan 22 2010
 
Score 50%

Just what I was going to say, check my scripts.

On the disk I/O, the kde system monitor data engine wasn't able to track md/raid last I checked (it had dummy values that were always zero), and I have md/raid, so I had to make my own script to handle that. The kernel makes the raw totals available in a file (in /proc or /sys IDR which, see the script), but I had to figure out how to track the last value, so I could do a comparison and get the difference between current and last. I used a tmpfile for that. Once I had the mechanism working for that, I was just simpler to use it for all my disk i/o, including the ones the engine supported, so I did.

On the network bandwidth, you could use similar techniques to track running totals, if desired. Also note that if you have iptables/netfilter installed, it can track the running totals over reboots, etc (but of course loses any from the time of the last iptables-save, in the event of a system crash). You could use that mechanism to save the numbers over reboots, and just do the iptables-save without a redirect to file, to grab the numbers for a script, if desired. (My Internet has no monthly/daily bandwidth cap, so I don't need to worry about that.)

For temps and stuff, the sensors command (package lm_sensors, probably a dep of what you're already running tho so likely already installed) gives you text output, which can be scripted. Or, the numbers are normally available in /sys, as well. Again, see my scripts.

I just got my netbook up and running. The acpi command gives me battery info, and again, there's /sys interface data I can use, as well. That's not in the tarball as I didn't have the netbook setup when I sent my scripts and screenshot in. What I sent in was off my main machine.


Duncan
Reply to this

-

 more than one command per line

 
 by vi3dr0 on: Jan 24 2010
 
Score 50%

Hi,

First of all - absolutely excellent work! Really, it's awesome ;)

However is it possible to show more than one command per line? I'd like to adjust it to show data horizontally in the panel, like:
"download: xx | upload: xx | cpu: xx | ram: xx |".

I hope you know what I mean.


Reply to this

-

 Re: more than one command per line

 
 by DuncanKDE on: Jan 24 2010
 
Score 50%

Quote:
More than than one command per line? [L]ike:
"download: xx | upload: xx | cpu: xx | ram: xx |"


Yes. See the README.syntax file, value section.

Basically, you define your separate sensors, then in your value line, you use multiple use= parms, and a format= parm listing them all with $1, $2, etc, at the spot where the values for the respective positioned use parms would go. There's even a multi-sensor example. =:^)

As documented, the default format is only "$1", so don't forget to add a format= parm, or it'll only show the first sensor value. As the example demonstrates, you can fill in text between the substituted values, so yes, your given line with four sensor values on the same line, complete with labels (which would be part of the format string), is quite possible.

There are a couple caveats, unfortunately. It seems the whole line takes the same color, so you can't multi-color the line. That's actually what prevented me from using it, as in most cases, my value lines corresponded to an element in a plotter as well, with the value lines serving the dual purpose of plotter color key and text readout. That was the big issue here, but a lessor one is that while I used a monospace font to maintain alignment, being very careful to allow spacing for the variable number of digits so the alignment wouldn't get screwed up, that's pretty much impossible with multiple value readouts per value line, because in most cases, each one can be variable digits wide, and multiple variable digits just doesn't allow for the possibility of proper alignment.

So yes, you /can/ have multiple output values per line; but the caveats may or may not be something you're willing to live with. If you have one long line of readout and thus don't need vertical alignment, it's possible, but you'll still lack the ability to color-code the individual outputs, and that was a deal-breaker for me.


Duncan
Reply to this

-

 Re: Re: more than one command per line

 
 by finkandreas on: Jan 24 2010
 
Score 50%

Duncan said basically everything. However I would recommend you to use the "text" keyword instead of the "value" keyword (because it uses the full width of the plasmoid), i.e. add a line like this:

text use="CPU" use="RAM" use="NetworkUp" use="NetworkDown" format="CPU: $1 RAM: $2 Up: $3 Down: $4"

of course you first need to define the sensors CPU, RAM, NetworkUp and NetworkDown


Reply to this

-

 Can't find yasp_scripted

 
 by Franksuse64 on: Jan 24 2010
 
Score 50%

Ok well I am compiling it, after installing dependencies and doing symlinks from my lib64 to lib folder, when I load the widget it says:

Could not find requested component: yasp_scripted.

I have copied systemmonitor.script to .yasp.script as a FILE and I also tried as .yasp_scripted and also without the dot (.). No success. What is that error?

tnx


openSUSE 64-Bits
Reply to this

-

 Re: Can't find yasp_scripted

 
 by finkandreas on: Jan 24 2010
 
Score 50%

did you really follow the install instructions in the file INSTALL?

these files have to be installed:
yasp-scripted.desktop --> $KDE_PREFIX/share/kde4/services/yasp-scripted.desktop
yasp_scripted.so --> $KDE_PREFIX/lib/kde4/yasp_scripted.so

KDE_PREFIX you can find out with 'kde4-config --prefix'
However the install routine should do all the work for you, if you follow the instructions in INSTALL...
Afterwards either restart your KDE or execute 'kbuildsycoca4' (otherwise KDE will not be aware of the new installed package).


Reply to this

-

 Re: Re: Can't find yasp_scripted

 
 by Franksuse64 on: Jan 24 2010
 
Score 50%

The INSTALL file says the following:

===
IMPORTANT:
Copy the file yasp_scripts/systemmonitor.script to $HOME/.yasp.script (if not available yet)
Otherwise, nothing will happen with this applet...
Or choose while running this applet a scriptfile of interest.

Install instructions:
#Release
mkdir build
cd build
cmake -DCMAKE_INSTALL_PREFIX=`kde4-config --prefix` -DCMAKE_BUILD_TYPE=release ../
sudo make install
kbuildsycoca4
===

I did that. No mention of:

yasp-scripted.desktop -->
$KDE_PREFIX/share/kde4/services/yasp-scripted.desktop
yasp_scripted.so -->
$KDE_PREFIX/lib/kde4/yasp_scripted.so

So I will try what you said. :)

tnx


openSUSE 64-Bits
Reply to this

-

 Re: Re: Re: Can't find yasp_scripted

 
 by finkandreas on: Jan 24 2010
 
Score 50%

because 'make install' installs this two files automatically for you... So if you followed the install instructions you do not need to copy them manually... I just wanted to point out which files need to be where (so you can check if they are where they should be)


Reply to this

-

 Re: Re: Re: Re: Can't find yasp_scripted

 
 by Franksuse64 on: Jan 29 2010
 
Score 50%

Well, both files are located exactly where you told me. Except that since I have a 64-bits OS, the .so needs to be in /usr/lib64 and not /usr/lib. Now it loads.

I get "Waiting for Wlan0Down" and it shuts down one of my case fan. Weird.

So now that nothing shows, I have to play with the scripts to get something? It's blank plasmoid only with what I wrote above inside.

tnx


openSUSE 64-Bits
Reply to this

-

 Re: Re: Re: Re: Re: Can't find yasp_scripted

 
 by finkandreas on: Jan 29 2010
 
Score 50%

default title:color="white" title:font="Dejavu Sans, 13" title:shadow="Sunken" title:alignment="Center"
default value:color="white" value:font="Dejavu Sans, 8" value:alignment="Left"

title text="System"
default interval="single"
sensor name="KernelVersion" type="program" cmd="uname -r"
sensor name="KernelMachine" type="program" cmd="uname -m"
sensor name="KdeVersion" type="program" cmd=$kde4-config --version | grep KDE | sed -e "s/KDE: \([0-9.]*\).*/\1/"$
sensor name="QtVersion" type="program" cmd=$kde4-config --version | grep Qt | cut -d" " -f2$
value key="Kernel" use="KernelVersion"
value key="Machine" use="KernelMachine"
value key="KDE / Qt" use="KdeVersion" use="QtVersion" format="$1 / $2"
default interval="60000"
sensor name="UptimeSecs" type="engine" cmd="systemmonitor:system/uptime:value"
sensor name="UptimeDays" type="math" use="UptimeSecs" math="int $1 86400 /"
sensor name="UptimeHours" type="math" use="UptimeSecs" use="UptimeDays" math="int $1 86400 $2 * - 3600 /"
sensor name="UptimeMinutes" type="math" use="UptimeSecs" use="UptimeDays" use="UptimeHours" math="int $1 86400 $2 * - 3600 $3 * - 60 /"
sensor name="LoggedUsers" type="program" cmd="users | sed -e 's/ /\n/g' | sort | uniq | xargs"
value key="Uptime" use="UptimeDays" use="UptimeHours" use="UptimeMinutes" format="$1 day(s) $2 h $3 m"
value key="Users" use="LoggedUsers" interval="10000"



That is a very basic script file which should work on every PC. Otherwise you can comment all lines in your scriptfile which contain something with WLan0 (because you probably do not have a network with wlan0).

I do not know why it was installed in /usr/lib, instead of /usr/lib64. It is a KDE bug, because I ask KDE where the plugins should be installed...


Reply to this

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

Add commentBack






-

-
Do you like or dislike Ubuntu Unity?
 Yes, unity is alien technology!
 It is less confusing than Gnome 3 default, shell.
 Granny thinks it is much more usable than Gnome 2
 Canonical is embarrasing itself with this split project
 Gnome 3 default shell is much better
 I dislike Unity, Gnome 3 default shell is alien technology!
 None of the above, I like the 2Gb for free and Apple alike behavior. Will post a comment instead

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.