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

-

 hard drive temps

 
 by DuncanKDE on: May 27 2010
 
Score 50%

Several comments have mentioned hard drive temps, but the two at least appear to be at the max-reply-depth for kde-look, so it doesn't have a reply button for them. So I'm starting a new thread.

One single purpose and thus reasonably simple app that can report and monitor hard disk drive temps is the unsurprisingly named "hddtemp". It works for SATA, PATA, and SCSI drives. In simplest form, you can run it as follows, tho you probably have to run it as root (thus using sudo or the like) if it's not installed setUID on your system.

hddtemp <device>

Here's the the command and output for my four drives, as run (from my admin account, configured for unrestricted and passwordless sudo access) here:

sudo hddtemp /dev/sd[abcd]
/dev/sda: ST3300831AS: 47°C
/dev/sdb: ST3300831AS: 48°C
/dev/sdc: ST3300831AS: 47°C
/dev/sdd: ST3300831AS: 46°C

So assuming that sort of output and that appropriate sudo privs are configured for the user running yasp-scripted, a the command to get the temp for /dev/sda, as used in a yasp-script sensor command, might look like this:

sudo hddtemp /dev/sda | sed -n 's/.* \([0-9]\+\)°C/\1/p'


Reply to this

-

 Problem if wlan0 not connected

 
 by ondrokm on: May 28 2010
 
Score 50%

Hi,
I have problem with displaying wlan ESSID when I'm not connected to any network. Instead of "nothing" or empty field it shows long string like

\x05\xEF\xF7\XA1:\x ..... (more than 50 characters)

Because of it, the widget resize itself and it's not possible to make it smaller.
If I try "$ /sbin/iwconfig 2>/dev/null ", it shows that string instead in the ESSID place.

How can I fix this? Is there a possibility to use conditions in the script?


Reply to this

-

 Problem if wlan0 not connected

 
 by ondrokm on: May 28 2010
 
Score 50%

Hi,
I have problem with displaying wlan ESSID when I'm not connected to any network. Instead of "nothing" or empty field it shows long string like

\x05\xEF\xF7\XA1:\x ..... (more than 50 characters)

Because of it, the widget resize itself and it's not possible to make it smaller.
If I try "$ /sbin/iwconfig 2>/dev/null ", it shows that string instead in the ESSID place.

How can I fix this? Is there a possibility to use conditions in the script?


Reply to this

-

 Re: Problem if wlan0 not connected

 
 by DuncanKDE on: May 28 2010
 
Score 50%

yasp-scripted doesn't provide conditions AFAIK, but it doesn't need to, as bash does.

bash actually has the generally rich conditional branching choices available in many programming languages, including if/then/else/elif/fi (fi is the reverse of if, closing the conditional), case/esac, with shell style wildcards, while/until loops, etc. Take a look at a bash tutorial (or the bash manpage or info pages) and/or issue the command "help <builtin>" (where <builtin is the if/case/while/until or other bash builtin of interest) at the command line, for a briefer description. It's also possible to use the test builtin (commonly seen as a [ -x "$var" ] or [[ -x $var ]] style test) and simple exit code results, along with boolean logic operators like &&, ||, and !.

Scripts with conditionals are, however, generally complex enough that they don't fit well directly within a yasp-scripted sensor command itself, so the usual solution in that case would be a separately created bash script, with the yasp-scripted script simply invoking it as its command.

There is in fact one invoked bash script of "intermediate" complexity, shipped in my scripts pack as yasps.diskstats, with examples of functions, if/then/else branching (even nested), [] and &&/|| logic, etc (I don't see any case or while/until logic, tho). You can see how a yasp-script invokes it in the disks script.

Or, you can take a much simpler path and simply truncate the output to the maximum desired length, so it doesn't unreasonably widen the plasmoid. An easy way to do that is to simply pipe the existing output to the cut command, telling it at what character you want to truncate. Unfortunately, all the shipped script usage examples seem to use cut's -d delimiter and -f fieldnumber options, instead of the -c character-range option, but it takes a simple list or range, so:

<existing command> | cut -c -20

... gives you the first 20 characters, and...

<existing command> | cut -c 2-10

... would skip the first character and give you the next 9.

You can even do this:

<existing command> | cut -c 3-5,10,23-

... to get chars 3-5, 10, and 23 to the end of the line (altho if the line's of unknown length, that obviously wouldn't limit the output length, just shorten it a bit).

Simple, eh? =:^)

FWIW, the cut manpage has the details. As demonstrated by all the shipped examples, often, using the delimiter and field number options works better than using the character option. Head and tail are similarly useful "small and simple" commands, which together with sed, grep, pipes/redirection, and conditionals, help give Unix shell scripting the power it's rightly famous for.

FWIW, you could probably optimize things a bit from that cut, by tweaking the grep or sed appropriately, cutting the cut out of the pipeline while still getting the same effect, but as should be obvious by now, that gets pretty complex, with a simple pipe to cut being much easier to figure out if you're not extremely well versed in regex syntax as well as grep/sed options and commands themselves. That's where even the experts started! =:^)


Reply to this

-

 Re: Re: Problem if wlan0 not connected

 
 by ondrokm on: May 29 2010
 
Score 50%

Thanks very much. I'd prefer empty field but this also works :-)


Reply to this

-

 Panel Popup Applet?

 
 by jwm on: May 29 2010
 
Score 50%

Hey there,

Thanks for writing this applet -- it's very useful!

There is one thing I was wondering about: a typical yasp theme is not really suitable for display in a panel. So would it be a good idea to use a PopupApplet instance? This way, the plasmoid would be displayed with an icon in the panel that pops up the widget when clicked.

I suppose there is also a use case for in-line display of small yasp widgets directly in the panel, but I would think the majority of users would prefer the popup behaviour.


Reply to this

-

 Re: Panel Popup Applet?

 
 by finkandreas on: May 29 2010
 
Score 50%

Sounds like a nice idea, but unfortunately I neither have much time nor I have an installed KDE for testing it ;)

Maybe I'll implement it in approx half a year when I have finished my studies but before that I cannot promise you anything...


Reply to this

-

 Re: Panel Popup Applet?

 
 by DuncanKDE on: May 29 2010
 
Score 50%

Note that the whole set of yasp-scripts I submitted are designed to run in a panel configuration, as they are doing in the third screenshot. That's using most of a horizontal full-width max-height (1/3 screen) panel across the top of my top monitor (of two, stacked), 1920x1200 monitor so 1920x400 panel, set to always-on-top, so I have system performance always visible. (BTW, I've modified the layout a bit since the screenshot, narrowing the views a bit and eliminating the diskstats one, in ordered to fit a syslog tail of 20-some lines, cut to 108 char width.)

But of course while that panel's only a sixth of the screen-space (a third of one monitor, of two) on my main machine, it's more panel than some netbooks have screenspace! So obviously, that's not going to work for everyone.

The solution I came up with on my netbook was to configure the dashboard as a separate activity (option available from kde 4.4, I believe), and put all my yasp-scripts and other general system status plasmoids (including the system-tray and the sys-log-tailer yasp-script I mentioned above) on the dashboard activity. That allows me a full-screen system-monitor "popup", by simply triggering the dashboard.

But popup implementation would be nice...

Of course, it can be done now, sort-of. In addition to the dashboard solution, there's another, if you want to take the time to configure it.

What you'd do is use the plasmoidviewer applet (ships as part of plasma-workspace, on gentoo anyway), to run your yasp-scripted plasmoid in a window instead of as part of the desktop activity, panel, or whatever.

You'd then setup a popup launcher for it as you would for a normal application. If the command line is complex, simply create a bash scriptlet that launches plasmoidviewer with the appropriate command line, thus giving you a simple one-word command-line bash script to invoke.

Then, for hotkey or gesture triggering, create an "input action" (in kcontrol/personalsettings/systemsettings) with the appropriate hotkey or gesture triggers. OR...

For icon-click triggering, use kmenuedit to create a menu entry, complete with desired icon, then (with widgets unlocked) drag it from the menu to your preferred containment (panel, folderview, activity, launcher) to create an icon launcher.

If desired, you could then use existing kwin "special window settings" functionality, to configure where the window pops up, make it borderless (you'd then use the keyboard close-window shortcut to close it), set the correct size, always-on-top, whatever.

So the functionality is already there in kde and yasp-scripted itself. It's just that as with yasp-scripted in general, it's a flexibility-first, configure-it-for-your-own-needs, thing, not something that ships pre-configured out-of-the-box for every anticipated usage, but at the same time limiting the flexibility for other-than-anticipated usage. True, people who don't want to bother with learning how to configure it on their own will have problems with this, but then again, yasp-scripted was never targeted at the "run-it-as-it-comes" crowd in the first place. There's other, more appropriate plasmoids (and I might add, more appropriate desktop environments), for the "I don't want to configure it, I just want it to work" non-power-user.


Reply to this

-

 Re: Re: Panel Popup Applet?

 
 by jwm on: May 30 2010
 
Score 50%

Thanks for the detailed reply :-).

The problem with using plasmoidviewer is that the window is not shown with transparency, so it will look like a bit of a hack.

The problem with using the dashboard activity is that i use separate activities for each workspace (so I can have different wallpapers), which means that you also get separate dashboards for each workspace -- and keeping them all looking the same then becomes a bit of a pain.

Anyway -- I had a quick look at the source. Hacking this should not be too difficult. Pretty much all that is required is the implementation of the graphicsWidget() handle. May get around to it in a few weeks.


Reply to this

-

 Re: Re: Re: Panel Popup Applet?

 
 by finkandreas on: May 30 2010
 
Score 50%

you could start a fork because that would make the merging easier...
http://bitbucket.org/jocker16/yasp-scripted


Reply to this

-
.

 tput: No value for $TERM ...

 
 by ondrokm on: May 30 2010
 
Score 50%

Hi, I like this plasmoid very much so I did several modifications to display some other data.
I have a simple command to retrieve a value from Internet - usually one-digit number. It works fine in terminal, but when I try to display it in the plasmoid, I get this:

tput: No value for $TERM and no -T specified
0

("0" is the number I want to display; other number gives the same error)

I've found it has something to do with ssh connection ... I just want to display the number retrieved by a command than "out of plasmoid" work fine ... Why this error appears? How can I get rid of it?


Reply to this

-

 Re: tput: No value for $TERM ...

 
 by finkandreas on: May 30 2010
 
Score 50%

What happens if you write a bashscript with exactly the command you need, and invoke the bash script as the yasp command?

Another chance is to add to your bash script something like:

#!/bin/bash
export TERM=xterm
HERE_COMES_YOUR_COMMAND


Maybe this will help


Reply to this

-

 Re: Re: tput: No value for $TERM ...

 
 by ondrokm on: May 30 2010
 
Score 50%

Works! Thank you very much!


Reply to this

-
.

 tput: No value for $TERM ...

 
 by ondrokm on: May 30 2010
 
Score 50%

Hi, I like this plasmoid very much so I did several modifications to display some other data.
I have a simple command to retrieve a value from Internet - usually one-digit number. It works fine in terminal, but when I try to display it in the plasmoid, I get this:

tput: No value for $TERM and no -T specified
0

("0" is the number I want to display; other number gives the same error)

I've found it has something to do with ssh connection ... I just want to display the number retrieved by a command than "out of plasmoid" work fine ... Why this error appears? How can I get rid of it?


Reply to this

goto page: prev  ... 2  3  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.