SuperKaramba

Karamba & Superkaramba

Source (link to git-repo or to original if based on someone elses unmodified work): Add the source-code for this project on opencode.net

0
5.0
Description:

You can check out the SuperKaramba web site at:

http://netdragon.sourceforge.net

You can download SuperKaramba themes at:

http://www.superkaramba.com (new!)

What is SuperKaramba?

SuperKaramba is, in simple terms, a tool that allows you to easily create interactive eye-candy on your KDE desktop. Currently, only linux is officially supported.


How does it work?

Theme writers create themes, or text files that define their widget. Then, they can optionally add python scripting to make their widget interactive. The possibilities are endless!


Here are just some examples of the things that can be done:

Display system information such as CPU Usage, MP3 playing, etc.

Create cool custom toolbars that work any way imaginable

Create little games or virtual pets that live on your desktop

Display information from the internet, such as weather and headlines


The possibilities really are endless!
Last changelog:

16 years ago

Changes in 0.35

- Ryan (p0z3r), Petri, Ivica, and Sarah have done all the work on this release! Thanks!

- many new APIs

- new callbacks

- DCOP interface for superkaramba

- multiple superkarambas / one systray support

- added Fahrenheit support

- fixed the "moving themes" problem

- fixed the "always on top" problem

- fixed bug in setMenuConfigOption(). Please see api.html for the new syntax.

- asyncronous image loading. setImagePath() should now work with networked/remote files.

- fixed bug in meterClicked()

- fixed bug in setRichTextWidth() and getRichTextSize()

- much more code cleanup, bug fixes, and internal documentation


Changes in 0.34

- Ryan (p0z3r) and Petri have joined the team! They have helped a lot with this release.

- Added a tray icon that lets you lauch additional themes, quit SuperKaramba, or open the theme list dialog.

- Added a theme list dialog that lets you see all the themes currently running, close any of them, or open a new theme.

- The start-up dialog now integrates with the new SuperKaramba.com theme archive. When you start up SuperKaramba, it lets you see all the new themes automatically! Everyone post your themes on SuperKaramba.com so they will appear here for all to see.

- Fixed tons of bugs including, but not limited to, themes always on top in KDE 3.2, themes saving negative co-ordinates, themes not saving session info the first time they run, etc, etc. (Thanks alot to Petri and Ryan, and epecially Ryan for testing everything before the release).

- Lots of code cleanup (lots of thanks to Petri for his help in this area).

- Probably a lot of stuff I am forgetting. Have fun!

Changes in 0.33

- Fixed many bugs. These include: moveImage combined with attachClickArea now works, moveText now works, SuperKaramba properly handles different backgrounds on each desktop again, and who knows how many more little things.

- Fleshed out Systray API. In addition to createSystray() to create the System tray, there is now a hideSystray(), showSystray(), and moveSystray(). See the API for more details.

- Changed fonts to use fixed sizes. This means a few existing themes might look slightly different than intended, but once all themes are updated, no one should have problems with fonts not matching what the theme designer intended (unless they don't have the specific font installed that the theme uses).

- Added a new callback: widgetClosed() - This allows you to run cleanup code when your widget closes. See examples/template.py for full details.

trash_double

17 years ago

oops..i fixed the error,it looks like i can`t trust my mdk 9.1 standard ed. cds anymore but when i did ./configure i did got this error:

checking for X... configure: error: Can't find X includes. Please check your installation and add the correct paths!

what should i do?and what does that mean?

Report

spoon

17 years ago

create a hot area, like some screensavers have to activate or halt. When the mouse enters that area, it shades the entire screen and brings all the karamaba themes to the front ( non-shaded).

I know I can click on the 'show desktop' button, however something to bring all the themes to the front without removing all the windows would be pretty cool.

Report

doomchild

17 years ago

I'm having trouble getting the Python scripts I write to run. When I run them in the console, I get the error that it can't find the module named "karamba". Does anyone know what the problem here is?

Report

C

ageitgey

17 years ago

The module karamba only exists inside SuperKaramba's python interpreter. It doesn't exist in your system's regular python interpreter.

Don't run your python script by hand. Create a file called mytheme.theme and define the basic theme stuff (size, location, etc) then create mytheme.py and write your python code there. Then to test it, run "superkaramba mytheme.theme" and your python code will automatically be run.

I hope that makes sense.

Report

kopkid

17 years ago

I'm getting these errors:

karamba.cpp: In function `QString PyString2QString(PyObject*)':
karamba.cpp:26: no matching function for call to `QString::setAscii(char*&)'
karamba.cpp: In function `PyObject* py_attach_clickArea(PyObject*, PyObject*,
PyObject*)':
karamba.cpp:249: no matching function for call to `QString::setAscii(char*&)'
karamba.cpp:253: no matching function for call to `QString::setAscii(const
char[1])'
karamba.cpp:257: no matching function for call to `QString::setAscii(char*&)'
karamba.cpp:261: no matching function for call to `QString::setAscii(const
char[1])'
karamba.cpp:265: no matching function for call to `QString::setAscii(char*&)'
karamba.cpp:269: no matching function for call to `QString::setAscii(const
char[1])'
karamba.cpp: In function `PyObject* py_add_menu_item(PyObject*, PyObject*)':
karamba.cpp:353: no matching function for call to `QString::setAscii(char*&)'
karamba.cpp: In function `PyObject* py_add_menu_config_option(PyObject*,
PyObject*)':
karamba.cpp:469: no matching function for call to `QString::setAscii(char*&)'
karamba.cpp: In function `PyObject* py_set_menu_config_option(PyObject*,
PyObject*)':
karamba.cpp:492: no matching function for call to `QString::setAscii(char*&)'
karamba.cpp: In function `PyObject* py_read_menu_config_option(PyObject*,
PyObject*)':
karamba.cpp:513: no matching function for call to `QString::setAscii(char*&)'
karamba.cpp: In function `PyObject* py_write_config_entry(PyObject*,
PyObject*)':
karamba.cpp:539: no matching function for call to `QString::setAscii(char*&)'
karamba.cpp:540: no matching function for call to `QString::setAscii(char*&)'
karamba.cpp: In function `PyObject* py_read_config_entry(PyObject*,
PyObject*)':
karamba.cpp:589: no matching function for call to `QString::setAscii(char*&)'
karamba.cpp:593: no matching function for call to `QString::setAscii(const
char*)'
karamba.cpp: In function `long int createWidgetMask(long int, char*)':
karamba.cpp:922: no matching function for call to `QString::setAscii(char*&)'
karamba.cpp: In function `long int createClickArea(long int, long int, long
int, long int, long int, char*)':
karamba.cpp:987: no matching function for call to `QString::setAscii(char*&)'
karamba.cpp: In function `long int changeImageChannelIntensity(long int, long
int, float, char*, int)':
karamba.cpp:1049: no matching function for call to `QString::setAscii(char*&)'
karamba.cpp: In function `long int addImageTooltip(long int, long int,
QString)':
karamba.cpp:1255: no matching function for call to `QString::setAscii(QString&)
'
karamba.cpp: In function `long int createBackgroundImage(long int, long int,
long int, char*)':
karamba.cpp:1307: no matching function for call to `QString::setAscii(char*&)'
karamba.cpp: In function `long int createImage(long int, long int, long int,
char*)':
karamba.cpp:1340: no matching function for call to `QString::setAscii(char*&)'
karamba.cpp: In function `long int changeTextFont(long int, long int, char*)':
karamba.cpp:1493: no matching function for call to `QString::setAscii(char*&)'
karamba.cpp: In member function `void karamba::passMenuItemClicked(int)':
karamba.cpp:3814: no matching function for call to `KPopupMenu::isItemVisible(
int&)'
make[3]: *** [karamba.o] Error 1

Report

C

ageitgey

17 years ago

Upgrade to KDE 3.1.

Report

ramone

17 years ago

this comes out trying to compile superkaramba-0.27 on a red hat 9.0 box:

karamba.cpp: In function `QString PyString2QString(PyObject*)':
karamba.cpp:33: no matching function for call to `QString::setUnicodeCodes(
Py_UNICODE*&, int&)'
/usr/local/qt/include/qstring.h:618: candidates are: QString&
QString::setUnicodeCodes(const ushort*, unsigned int)
make[3]: *** [karamba.o] Error 1
make[3]: Leaving directory `/home/ramone/inst/superkaramba-0.27/src'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/ramone/inst/superkaramba-0.27/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/ramone/inst/superkaramba-0.27'
make: *** [all] Error 2

anyone any hints ?

thanx

Report

C

ageitgey

17 years ago

This should be fixed in 0.28.

Thanks.

Report

Rjx

17 years ago

I get the same thing and I'm running RedHat 9.0, I don't know if you get this part though:

karamba.moc:17:2: #error "This file was generated using the moc from 3.0.5. It"
karamba.moc:18:2: #error "cannot be used with the include files from this version of Qt."

Report

Matti

17 years ago

When will the new API documentation be ready?

Some of the themes I've written haven't reacted that well to the new superkaramba, and there are a couple of the new features that I'd like to implement on them.

And thanks for the great new features.

Report

C

ageitgey

17 years ago

They are ready. Sorry for the delay.

Report

maciunio

17 years ago

Yeah, API's docs are quite usefull, you know :)

Report

takashi123

17 years ago

I have a problem. When i'm opening them with python extension, then it crash.
Backtrace:

[New Thread 16384 (LWP 2922)]
0x4105d7f6 in waitpid () from /lib/libpthread.so.0
#0 0x4105d7f6 in waitpid () from /lib/libpthread.so.0
#1 0x405ea5bd in KCrash::defaultCrashHandler(int) ()
from /usr/lib/libkdecore.so.4
#2 0x4105c549 in __pthread_sighandler () from /lib/libpthread.so.0
#3
#4 0x40bdc698 in QGList::append(void*) ()
from /usr/lib/qt-3.1/lib/libqt-mt.so.3
#5 0x08061c20 in createImage(long, long, long, char*) ()
#6 0x08061ceb in py_create_image(_object*, _object*) ()


When i'am running Slickbar, everything is okey, but in karamba_scheduler, or Polish News Module it is crashing.

Report

karamazov

17 years ago

After a bit of research, it appears that the majority of (super)karamba scripts assume a dpi of 75... Why anyone is runnig this, I do not know but here is a bit of python I hacked out to deal with higher dpi.

import os


havexdpy = os.system("which xdpyinfo")

if (havexdpy == 0):
pass
else:
print "\nCan't find xwininfo in your path."

fp = os.popen("xdpyinfo")
output = fp.read()
output = output.splitlines()
i = 0
for x in output:
param = x.split()
if (len(param) > 1):
if param[0].find("resolution:") != -1:
resolution = param[1].split("x")
fontbaseX = resolution[0]
fontbaseY = resolution[1]


The first thing I have to do with most any superkaramba script is change the font (my dpi is 112)... this bit of code should probably be dealt with the same a the resolution bits everyone is in (the start of) use.

Report

karamazov

17 years ago

sorry about double post - refresh is a bad thing :)

Report

karamazov

17 years ago

After a bit of research, it appears that the majority of (super)karamba scripts assume a dpi of 75... Why anyone is runnig this, I do not know but here is a bit of python I hacked out to deal with higher dpi.

import os


havexdpy = os.system("which xdpyinfo")

if (havexdpy == 0):
pass
else:
print "\nCan't find xwininfo in your path."

fp = os.popen("xdpyinfo")
output = fp.read()
output = output.splitlines()
i = 0
for x in output:
param = x.split()
if (len(param) > 1):
if param[0].find("resolution:") != -1:
resolution = param[1].split("x")
fontbaseX = resolution[0]
fontbaseY = resolution[1]


The first thing I have to do with most any superkaramba script is change the font (my dpi is 112)... this bit of code should probably be dealt with the same a the resolution bits everyone is in (the start of) use.

Report

jmaloy

17 years ago

I used the Superkaramba RPM for Mandrake 9.1 to install, and it said it was already installed. But when I do a search for it even in "SUPER" mode its nowhere to be found. I tried to to untar it but I got an error message. Im a NOOB.....
I did finally got Karamba to install, but with out super karamba I cant use superkaramba stuff.......Thanks

Report

bobo

17 years ago

i have in many python scripts import errors!

only themes without python files work fine.

can anyone help me ?

i use suse 8.2 and i'm a linux newbie :)

Report

ntesa

17 years ago

One feature I'd really like to see in SuperKaramba is session management, so I don't have to always load all my themes when I start KDE. I'm not a KDE programmer, but I wish someone would implement this and if it's not the original author please send him the patches :)

Report

spo0ner

17 years ago

For some reason I can't seem to get kde-devel installed. Apt is saying that it is uninstallable due to bug errors or broken packages. Has anyone had this problem and is there a work around. I almost have SuperKaramba installed but its missing the KDE headers. Any help would be greatly appreciated.

Report

wurz25

17 years ago

the perf. is very bad, i will use the old one

nico

Report

ViRgiLiO

17 years ago

I can't find superkaramba 0.26 file (gz or rpm) on any mirror from sourceforge.

Report

p0z3r

17 years ago

Is there going to be an implementation to minimize applications into a superkaramba bar with animation, similar to how OS X Docker works?
I'm using kroller, and it functions exactly like the Docker, except the minimizing functions with animations.

Nice work regardless.
-p0z3r-

Report

caspian

17 years ago

FYI I think I found a bug in SK last night while coding on kroller.

Steps to re-produce bug:
1. createImage
2. resizeImageSmooth
3. applyImageEffect (highlight is what I was using)
4. Notice that image has now been resized to original size :(

This does not happen if you use the non-smooth resizeImage function.

Anyway, it wasn't a show stopper, but thought I should let you know.

Report

caspian

17 years ago

Is there a way for SK to know if the mouse is currently over our widget or not? I am famialiar with mouseMoved callback, but when widgetUpdated gets called I have no way of knowing wether the mouse is currently in our widget or not. This problem usually happens when the user is tricky and escapes from the SK widget directly to another application without leaving the borders of the SK widget. Does that make sense? It would be nice to have a callback like int moseInWidget(). If that's not possible how about just getting the absolute x/y coords of the mouses current position on the screen?

Report

16 years ago

Changes in 0.35

- Ryan (p0z3r), Petri, Ivica, and Sarah have done all the work on this release! Thanks!

- many new APIs

- new callbacks

- DCOP interface for superkaramba

- multiple superkarambas / one systray support

- added Fahrenheit support

- fixed the "moving themes" problem

- fixed the "always on top" problem

- fixed bug in setMenuConfigOption(). Please see api.html for the new syntax.

- asyncronous image loading. setImagePath() should now work with networked/remote files.

- fixed bug in meterClicked()

- fixed bug in setRichTextWidth() and getRichTextSize()

- much more code cleanup, bug fixes, and internal documentation


Changes in 0.34

- Ryan (p0z3r) and Petri have joined the team! They have helped a lot with this release.

- Added a tray icon that lets you lauch additional themes, quit SuperKaramba, or open the theme list dialog.

- Added a theme list dialog that lets you see all the themes currently running, close any of them, or open a new theme.

- The start-up dialog now integrates with the new SuperKaramba.com theme archive. When you start up SuperKaramba, it lets you see all the new themes automatically! Everyone post your themes on SuperKaramba.com so they will appear here for all to see.

- Fixed tons of bugs including, but not limited to, themes always on top in KDE 3.2, themes saving negative co-ordinates, themes not saving session info the first time they run, etc, etc. (Thanks alot to Petri and Ryan, and epecially Ryan for testing everything before the release).

- Lots of code cleanup (lots of thanks to Petri for his help in this area).

- Probably a lot of stuff I am forgetting. Have fun!

Changes in 0.33

- Fixed many bugs. These include: moveImage combined with attachClickArea now works, moveText now works, SuperKaramba properly handles different backgrounds on each desktop again, and who knows how many more little things.

- Fleshed out Systray API. In addition to createSystray() to create the System tray, there is now a hideSystray(), showSystray(), and moveSystray(). See the API for more details.

- Changed fonts to use fixed sizes. This means a few existing themes might look slightly different than intended, but once all themes are updated, no one should have problems with fonts not matching what the theme designer intended (unless they don't have the specific font installed that the theme uses).

- Added a new callback: widgetClosed() - This allows you to run cleanup code when your widget closes. See examples/template.py for full details.

12345678910
Be the first to comment
File (click to download) Version Description Downloads Date Filesize DL OCS-Install MD5SUM
*Needs pling-store or ocs-url to install things
Pling
0 Affiliates
Details
license
version
0.35
updated Nov 16 2004
added Apr 19 2003
downloads 24h
0
mediaviews 24h 0
pageviews 24h 4