Description: This is the script required by WiFi plasma applet. You must install it first, otherwise the wireless applet won't work Installation instructions - README This script is required by WiFi applet (http://bit.ly/wifi-plasmoid) To install, issue the following command plasmapkg -t dataengine -i wifi-engine-1.0.plasmoid
Known Bugs -On some systems (Arch, SuSE, possibily others) you have to manually change the path to the iwconfig executable at line 40 in ~.kde/share/apps/plasma/plasmoids/pywifi-engine/contents/code/main.py -If you note high CPU usage, edit line 19 in the above main.py, setting setMinimumPollingInterval to 333 or higher Both these bugs will be fixed soon. Thanks for reporting them
PiWiFi Dataengine This dataengine is needed by Wifi plasmoid
Please report bug to raffaeleSgarro@gmail.comLast changelog:
1.0.1: Absolute path for /sbin commands that by default are not in $PATH on Debian
There's an issue with this dataengine, cause the iwconfig executable has different paths on different systems. I have been suggested to implement a "degradation strategy" looping among known locations. Unfortunately I am unable to run my plasmoid because of python scriptengine failure on my ubuntu
The CPU issue can only be related to the update frequency. Edit line 19 of ~.kde/share/apps/plasma/plasmoids/pywifi-engine/contents/code/main.py
Change from
self.setMinimumPollingInterval(33)
to
self.setMinimumPollingInterval(333)
This should go, but I have not tested it myself
have you got an idea, why the plasmoid needs so much cpu power ?
unfortunately too much, the fan of my laptop seems always busy when i run the plasmoid, that's why i can't use it.
maybe it belongs to python or qt librarys..
hi, i installed your plasmoid and dataengine, but it didn't work right from the start. for opensuse (11.3) systems people have to fix the path to iwconfig. here, the correct is /usr/sbin/iwconfig. so i edited the following file:
~/.kde4/share/apps/plasma/dataengines/pywifi-engine/contents/code/main.py
the code now looks like this:
blob = commands.getoutput("/usr/sbin/iwconfig " + interface)
Ratings & Comments
6 Comments
There's an issue with this dataengine, cause the iwconfig executable has different paths on different systems. I have been suggested to implement a "degradation strategy" looping among known locations. Unfortunately I am unable to run my plasmoid because of python scriptengine failure on my ubuntu The CPU issue can only be related to the update frequency. Edit line 19 of ~.kde/share/apps/plasma/plasmoids/pywifi-engine/contents/code/main.py Change from self.setMinimumPollingInterval(33) to self.setMinimumPollingInterval(333) This should go, but I have not tested it myself
thanks, but i have to set it to 2000 in order to get a strong effect in less CPU load.
have you got an idea, why the plasmoid needs so much cpu power ? unfortunately too much, the fan of my laptop seems always busy when i run the plasmoid, that's why i can't use it. maybe it belongs to python or qt librarys..
hi, i installed your plasmoid and dataengine, but it didn't work right from the start. for opensuse (11.3) systems people have to fix the path to iwconfig. here, the correct is /usr/sbin/iwconfig. so i edited the following file: ~/.kde4/share/apps/plasma/dataengines/pywifi-engine/contents/code/main.py the code now looks like this: blob = commands.getoutput("/usr/sbin/iwconfig " + interface)
In Debian normal users have to run /sbin/iwconfig in order to use it, not only iwconfig. Anyway thanks for the script.
Thank you for pointing this out