cfigura

I love CWP!

I'm wondering if anyone who's used this has put together a xml format page to take data from Weather Underground (wunderground.com).

I'm looking at playing around with the xml to do it myself, but I thought I'd check first. Thanks! - Jun 16 2010

I just installed the latest version, and when I tried adding it to the desktop/dashboard, I get an error message:
Could not locate the sk_cm901x package required for the CrystalMonitor

I'm currently running KDE4.3, is this the problem, or is there something else wrong? - Aug 20 2009

I dug around and found the answer!
The Crystal.theme has the following for the CPU temperature sensor:

text x=260 y=48 sensor=program program="sensors | grep Core0| cut -f2 -d+ | cut -c -6" interval=50000 color=220,220,220 align=right

Sensors reports my two cores as 'Core 0' and 'Core 1' - so by replacing the 'Core0' by 'Core 0', it works just fine.

- Oct 16 2008

With the update - the processor name is now accurately shown, but I still do NOT get a CPU *temperature* shown. I know that there are two cpu temperatures to report, I would think that that's probably the issue. Is there a way around that?
- Oct 15 2008

The September exhange between Miha and Polydeukes seems to suggest that there is currently no support for dual-core systems. Is that correct? I've got crystalmonitor running on my laptop, and everything works perfectly EXCEPT core temperature - which doesn't show up at all. The "cpuinfo=..." command above yields:
Genuine Intel(R) CPU T2500 @ 2.
...

It's a great plasmoid - I'd just love to get the CPU temperature fixed!

Thanks! - Oct 12 2008

Thanks - that path did the trick. I suspect the other errors resulted from a separate change I made, renaming the image directory to 'NixieDir' (change made for other reasons).

I've uploaded an updated version, and that should work. Let me know -

-C - Mar 14 2009

bizzl -

Thanks for the comments. Unfortunately, you've found the one problem that I was aware of - difficulty with specifying path.

When I originally wrote the clock (as a non-plasmoid), I used sys.path[0] to specify the location of the images and the configuration file. I've found that that doesn't work under plasma, and haven't been able to find a solution. I was hoping that the .kde directory structure was universal enough that I could specify from there, and it seemed to work on several different machines here.

If anyone has any recommendations on that front, that would be appreciated.

Otherwise, the path is specified in the second line of main.py - I'd edit it after installation (rather than unzipping, editing, rezipping and installing). If you do a 'locate NixieClock' after installing the script, you should be able to find out where it was installed, and modify main.py appropriately.

Let me know if you have further problems! - Mar 14 2009

Thanks for posting this for intrepid! Sadly, the plasmoid seems to suffer the same problem that knetworkmanager does - it connects to a WEP network just fine, but fails when trying to connect to PEAP.
- Feb 16 2009

I concur- it's a great plasmoid, but not quite as useful on the vertical panel. Specifying # of columns would be ideal. - Oct 06 2008

Thanks! That and the kdebase-workspace-dev. So it's successfully built, and says that it installed to
Quote:

Now I can't get it to add to my widget list! I go to 'add widget -> install new widgets -> install from file -> plasmoid: Native plasma widget'. I've tried looking in the install directories, nothing comes up. Any thoughts on this? - Oct 06 2008

I've just upgraded from hardy to intrepid beta, and am really working with KDE4 for the first time. I'd like to try out the quicklauncher - that's a big missing piece from the KDE4 panel, but I'm having problems. The hardy package installed, but doesn't show up on the 'add widget'. And I can't build from source. I get the following feedback on running the installer:

Quote:

Does anyone have any ideas? Help? - Oct 05 2008