-
 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:  10534
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  ... 4  5  6  7  8  9  10  11  12  13  14  15 

-

 mtr script

 
 by marcotangaro on: Nov 18 2010
 
Score 38%

the Script by mtr does not work on my archlinux 64, with kde 4.5.3.
it stop to : "Waiting for: DataFree"


Reply to this

-

 Re: mtr script

 
 by cialdo99 on: Nov 18 2010
 
Score 50%

doesn't work with any distro if you don't specify the mountpoint of the hardrive you want to monitor.

See the comment:RE:Problem at page 11 to solve.


Reply to this

-

 Re: Re: mtr script

 
 by marcotangaro on: Nov 18 2010
 
Score 50%

I solved thank you
ps. sorry for multiple post... by browser is going crazy


Reply to this

-

 systemmonitor:disk/ dataengine

 
 by hamelg on: Jan 30 2011
 
Score 50%

Hello,

I want to use disk metrics from systemmonitor dataengines but none works.
ie :
sensor name="IOsda" type="engine" cmd="systemmonitor:disk/sda_(8:0)/Rate/totalio:value"
yasp-script is stuck on "Waiting for: IOsda" message.
The source:key dataengine is correct : I get values with the Plasma Engine Explorer tool.
Any ideas ?


Reply to this

-

 Re: systemmonitor:disk/ dataengine

 
 by hamelg on: Jan 31 2011
 
Score 50%

The issue comes from the field separator colon.

cmd="systemmonitor:disk/sda_(8:0)/Rate/totalio:value"
__________________________________^

the parser ignore that because it counts 4 fields, not 3.
So, all dataengine keys which contains a colon can't be used :(
Could you fix that ?


Reply to this

-

 Re: Re: systemmonitor:disk/ dataengine

 
 by finkandreas on: Jan 31 2011
 
Score 50%

fixed in version 1.0.7. Thx for reporting the issue ;)


Reply to this

-

 Resizing

 
 by phiga2 on: Feb 10 2011
 
Score 50%

HI,
How to resize it? it's too wide and no way to shrink it!


Reply to this

-

 Re: Resizing

 
 by finkandreas on: Feb 10 2011
 
Score 50%

Short answer: You cannot make it smaller than the widest element.
What exactly gives you trouble? Cut the value which is too long with the awesome command "cut".


Reply to this

-

 Re: Resizing

 
 by DuncanKDE on: Feb 10 2011
 
Score 50%

To resize it, you must resize the longest element (usually a text element) inside. It will only shrink down until that element is displayed at its natural size.

That is in fact how I control the sizes on all of mine. I use monospace fonts, and strictly control the number of chars on each line. (I hadn't fully gotten the hang of it when I posted the sample scripts that now appear in the duncan subdir. I've refined my technique a bit since then.)

Hint: If you're using value lines with both key and (possibly formatted) use values, the longest key value will apply to all of them, as will the longest (formatted) use value, assuming the same font for all of them, anyway. So to calculate the length required for the value lines, add the longest key length to the longest use length.

Basically, what that means is that you need to trim/abbreviate more. If you have text results that are too long, feed them to grep or cut to trim them some. For integer results, divide by factors of 10 to reduce the number of digits. For floats, use format to control the number of decimal places. And of course abbreviate your keys/labels if necessary.

Or use narrower/smaller fonts...

Note that I don't use meter/bar graphs here, preferring plotters as I like to see the trends that bars hide. Thus, I don't have much experience with or advice on them, but the same idea would apply. If commenting everything but the sensor and meter lines results in the same minimum width, they're forcing the width, so you gotta figure out how to make them narrower.


Duncan
Reply to this

-

 Re: Re: Resizing

 
 by phiga2 on: Feb 11 2011
 
Score 50%

Thanks,
I understand the principle but out of my reach!


Reply to this

-

 Not showing CPU temp

 
 by 2handband on: Feb 13 2011
 
Score 50%

Hi, I just installed yast-scripted and it looks great! I'm using the systemmonitor_by_patkoscsaba.script script with a few slight modifications. Only problem I have is that my CPU temps are not showing up; there's no error messages, but no values appear in the appropriate places, either. I'm running an AMD Athalon II X2 245 processor. Is there something I can do to the script that'll make my CPU temps display?


Reply to this

-

 Re: Not showing CPU temp

 
 by DuncanKDE on: Feb 13 2011
 
Score 50%

The command he uses for CPU temps is "sensors", piped to grep, etc, to filter it to just the desired coretemp data.

"sensors" is part of the lm_sensors package. Do you have it installed and configured, so that running it from a command prompt produces a bunch of output including the coretemps? If not, you won't get anything for that and might as well comment those lines (or install and configure the package). You'll also need the appropriate kernel modules available. They may be available by default or installed as dependencies of lm_sensors for many distribution kernels, but if you build your own kernel, you may well need to go into the kernel config and turn on the appropriate drivers, either as built-in or as modules (which would then normally be loaded by the lm_sensors initscript, once it's configured).

HOWEVER: Many modern laptops (and presumably more modern desktops than mine, as well) don't actually need or use lm_sensors, instead using acpi based information, directly. My netbook doesn't have lm_sensors installed, tho it does have specific kernel drivers for that model of netbook, but cpu speed, temps, battery, etc, are all available, using other commands.

Bottom line. That's system-specific configuration. You'll need it configured for your system before it'll work.


Duncan
Reply to this

-

 Re: Not showing CPU temp

 
 by finkandreas on: Feb 13 2011
 
Score 50%

As duncan already mentioned it, you first need to find out, how you can get the temperature information on your computer. Yasp-scripted is in no way a magic box, which does work for you. It is a program which prints information on the desktop, but how the information is obtained has to be regulated by the user.

That said, you can try if you have lm_sensors installed, and execute the binary "sensors" and watch its output.
On modern kernel (and I think you as arch user, are on a modern kernel), you can look in /sys/class/hwmon, if you finde something that has temperature information.
For example this command-line will get the core temperatures on my laptop:
'cat /sys/class/hwmon/hwmon[01]/device/temp1_input'
The commandline can be very different for your computer, just checkout what directories you have in /sys/class/hwmon.


Reply to this

-

 Re: Re: Not showing CPU temp

 
 by 2handband on: Feb 13 2011
 
Score 50%

Okay, I got it working. The problem had more to do with my very mediocre scripting skills than anything else. I really like this widget; great job!


Reply to this

-

 plasma crashes when re-parsing

 
 by 2handband on: Feb 13 2011
 
Score 50%

Okay, another problem, one that's a showstopper unless you've got a solution. Reparsing the script, or logging into a session, causes plasma crashes. The screen goes completely black. i'm running KDE 4.6 on Arch.


Reply to this

-

 Re: plasma crashes when re-parsing

 
 by DuncanKDE on: Feb 13 2011
 
Score 50%

Two points:

1) I don't understand why, when everyone else (well, at least the browsers) are going separate processes in ordered to keep one applet/plugin from crashing the entire thing, plasma was /still/ designed with everything in the same process, even the same thread, so if one plasmoid crashes, it crashes the ENTIRE thing... if one stalls, it stalls the entire thing! It /does/ save memory, but come on, we're not running MS WormOS 3.1 with shared memory in 4 megabytes of RAM any more, and there's a /reason/ the browsers are spending all that work separating things from each other! </rant>

But at least in theory if it's actually crashing, there's another component of kde that's supposed to notice it and restart plasma automatically. I started noticing that with 4.5 and while I'm not sure 4.6 has crashed on me, it should be the same. So what I think is happening is that plasma is stalling, NOT crashing, stalling, waiting for something.

Which is where #2 comes in...

2) I've had yasp-scripted (and therefore all of plasma, due to the design I was ranting about above) stall out on me when I made a mistake, in my case a typo in a plotter use= phrase, so it pointed at a sensor name that didn't exist. When it tries to use a sensor that doesn't exist, it apparently locks up, thereby locking up all of plasma.

Try this to troubleshoot (it's what I did to find the problem line): First, start a konsole so you have somewhere to type commands when plasma goes haywire on you. Then, edit the script, commenting (leading #) each line. You should be able to then start plasma-desktop with the (now all comments) script running. You can then quit the desktop again. (I like the traditional killall plasma-desktop, the kde-specific method is kquitapp plasma-desktop, you can type it in the konsole window you opened.) Then edit the script, uncommenting /just/ the sensors (nothing using them, so no plotters, meters, values, or text lines using a sensor), and try running plasma-desktop again. My experience has been that sensors lines (at least as long as they don't use other sensors) shouldn't cause a stall, even if the command fails for whatever reason, because yasp-scripted is designed so it /should/ work around unresponsive sensors (if there's a typo in the line, causing bad format, say a missing set of quotes, that might still cause it). If that does NOT work, go back and try each individual sensors line until you find the bad one. If it DOES work, start uncommenting the plotters, values, etc, one or a group at a time, until you find the bad one.

As I said, it happened to me. I'll bet you find a bad line, and upon examining that line, you find a typo or something, possibly a use= pointing at a non-existent sensor (abbc instead of abc, or abcd instead of ab.cd, or the like, that was the problem I had, simple, stupid typo). Correct that and you should be in business. =:^)


Duncan
Reply to this

-

 Re: plasma crashes when re-parsing

 
 by finkandreas on: Feb 13 2011
 
Score 50%

Some additional information to what duncan has already said:

- Try compiling it in debug mode, and get a backtrace. This is some information, I can work with. Telling me that it crashes on reparsing, is not really helpful, since I don't even know, if it always fails, or just from time to time.

- I think that starting with KDE-4.5 all plasmoids work in their own thread, so a stalling yasp, shouldn't stall your desktop (maybe you can configure it somewhere, I don't know exactly)


Reply to this

-

 Re: Re: plasma crashes when re-parsing

 
 by 2handband on: Feb 13 2011
 
Score 50%

Okay, fixed this one; it stemmed from an imperfect understanding of the script syntax.


Reply to this

-

 Change size?

 
 by 2handband on: Feb 13 2011
 
Score 50%

One other small thing; I can't figure out the syntax to cahnge the size of the display. I want to make it wider and a little bit taller.


Reply to this

-

 Re: Change size?

 
 by finkandreas on: Feb 13 2011
 
Score 50%

How about just resizing it? hover over the plasmoid, then the kde-plasmoid-bar should appear next to the plasmoid. Resize it. Finished.

I just realized, that there seems to be a bug in my plasmoid. After reparsing the script the kde-plasmoide-bar does not appear again. So you maybe need to restart your kde (or remove the plasmoid, and add it again, or restart plasma-desktop, or ...)


Reply to this

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

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.