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.

titan

17 years ago

Hi there. From all the screenshots I have seen this program looks awesome, but I still haven't got it running on my own system.

I am using RH8 and superkaramba-0.32-1mdk.i586.rpm. Everything installed perfectly, and I have an entry in /usr/share/applnk-mdk/Amusement/Toys/, however there is nothing on the menu. Also, when I run superkaramba from the terminal I get the following error:

superkaramba: relocation error: superkaramba: undefined symbol: static_QUType_varptr

Any ideas? Thanks.

Report

C

ageitgey

17 years ago

Yes, don't install the mandrake RPM as you did. Install a Redhat RPM.

Report

yagami

17 years ago

also , dont know if this is the right place to say this but
systray is having a problem with gaim systray icon.dunno why,that icon only goes to the kicker systray and never to the karamba systray ( this is the only systray icon that i find this behaviour )

Report

yagami

17 years ago

could you make a feature so that instead of being in 1 or all , could be like 3 , or 4 desktops ?!
i work like this :
desktop 1,2,3 and four is for working
desktop 5-8 is for internet
and desktops 9-12 is for multimedia

so in desktop 1,2,3,4 would have a theme like top ,

have a karamba internet info (like internet news themes) on 5,6,7,8

and have an multimedia script on 9,10,11,12.

congratulations on the great work

Report

C

ageitgey

17 years ago

hah yeah i think you are the only person who uses 12 desktops :)

Anyway, I will fix the more than 10 desktop bug and also add the ability to put a theme on some, but not all desktops.

Thanks.

Report

yagami

17 years ago

guess being the only one who uses 12 desktops :)

in the send to desktop 10 , instead of a 10 , there is a :
i think desktop 11 is a ;
and desktop 12 is a ... well , another weird character

Report

Claire

17 years ago

Upgrading to Superkaramba 0.32 did the job for me. I'm using SuSE 8.2 Pro and had the cycling-bug with the Polish News Module. Thanx a lot for the fix...

Report

C

ageitgey

17 years ago

thanks, i'm glad the fix was successful :)

Report

WinterWolf

17 years ago

http://kde-look.org/content/show.php
http://apps.kde.com/fr/2/info/vid/9606?br=true

It is a lot like SK except completely C++ and including a THEME EDITOR!!!

I really hope taht these two projects are merged, becasue there isn't a need to have two, but there is defintely a need to have a theme editor and many of the other goodies KR has.

Please consider switching to XML too.

Report

C

ageitgey

17 years ago

By the way, what do you mean it is "completely in C++?"

SuperKaramba is completely in C++. It's not written in python at all. All of the karamba methods you can call from python are implemented directly in C++. SuperKaramba embeds a python interpreter so you can control your widget, but SK is definately completely written in C++.

Just clarifying.

Report

WinterWolf

17 years ago

Both scripting and program is in C++, jsut try it to see what features I'm talking about.

That theme editor is not complete, but i think it's a great start and that's defitnely my favorite thing about it.

It also says" and more with all specs based only on QT and KDE" I don't know if SK doesen't also do this, but if it doesen't this sounds like a good thing.

Also, will someone tell me, what are the disadvantages fo using the XML format to make the GUI instead of the current way?

And finally, and most importantly THANK YOU, I like and use your program daily, I ams orry if I appeared ungrateful, I just want Linux and KDE to succeed as much as possible. With Konfabulator on mac, Objects Desktop from Stardock and Samurize on Windows, and gDesklets on GNOME it's a tough competitive world for these kinds fo apps and having no clear application for this on KDE makes it a bigger challenge for developers and users and in total there will be fewer themes for each. This is why I want KDE to have only one program that is the best on any platform.

I also hope that maybe if SK isn't included in 3.2 due to it's novelty, i defintely hope tos ee it in 4.0, if it's officially endorsed it will have an even larger userbase.

Report

C

ageitgey

17 years ago

Just to clarify again:

KarambaR doesn't have any scripting at all as far as I know. It's much simpler right now than SuperKaramba (i'm not implying that is a bad thing). For example, there is no way you could do an exact copy of most of the popular SuperKaramba themes in KarambaR (Liquid Weather ++, any of the task bars, etc) because KarambaR just doesn't support all the needed features.

And what do you mean by "with all specs based only on QT and KDE"? SuperKaramba is based only on Qt and KDE. In fact, SuperKaramba uses much more of the KDE api (task management, systray, etc) than KarambaR does. The only extra requirement that SuperKaramba has is that you have python installed when you compile it. If you compile SK a certain way, you wouldn't even need python installed on users' computers (who install from an RPM or deb or whatever).

Report

WinterWolf

17 years ago

I don't realy know anything about XML, I just know that gDesklets and Konfabulator both sue it and Qt Designer uses it for the GUI files, so I thought it was the best format to sue if therre is a theme creator.

I don't really know if that makes it eaier on the developer or user in any way.

It seems pretty simple as is, even I can make a small applet like:

karamba W=140 H=20 #I am commenting! :p w = width and h = height these define the size of the theme
text value="SK is super easy!! " #just tells karamba to put "SK is super easy!!" in the space just created

I love commenting, it helps me read what I write even if I really write nothing :)

Anyway, this is even easier than in gDesklets, but I don't know if that's true for long programs too.

I don't think that the mroe SK like programs the better they will be. I think that if isntead of developers making SK like programs tehy would jsut improve SK, than SK would be better than what other SK like programs could be. But, anyway my biggest arguement is that if there are alot of SK like programs themes would be incomatible and there wil be only a few for each program instead of a lot for one. But, I don't really know, that's probably wrong ;(



Report

C

ageitgey

17 years ago

I certainly wouldn't complain if everyone else dropped their projects and wanted to help me out :) I was just saying that you shouldn't expect that to happen :)

Report

C

ageitgey

17 years ago

Thanks for the comments. Don't worrry, I know you are just commenting and aren't trying to tell us how to do things :)

KarambaR's theme editor is cool, but it's not exactly how I want SuperKaramba's theme editor to work. There will be a SuperKaramba theme editor. I just haven't had time to write it yet. But at the same time, you can't just take the KarambaR editor and slap it into SuperKaramba if it doesn't really do what you want (wasn't designed with python scripts in mind).

So basically, SuperKaramba and KarambaR both began life as Karamba. But merging them isn't neccesarily productive from a programming point of view. It would be way more work than just adding whatever features KarambaR might have to SuperKaramba by hand. I've written (and others contributed) far more code to SuperKaramba than there was original Karamba code. Just because SK and KarambaR came from the same original source doesn't mean they are still compatible in source code terms. You can't just drag and drop functions from one to the other.

I totally understand why you think that there should be one clear leader. But what do you want, one of us to just stop working and delete all existance of our creation? :) I think that users will pick the one they like the best and that will probably be the "leader". And if 30 more "karamba clones" pop up, that isn't a Bad Thing. It just means there is more competition and the "winner(s)" will be better programs for it.

In the world of free software, you can't kill a project because it is not "popular", because sales don't equal further development. You kill a project when the developer(s) give up or lose interest.

As for the other question, there is nothing wrong with using XML for the file format (like Konfabulator and gDesklets do). If I was involved in the first month or two of Karamba development, I might have used XML (because I would be too lazy to write my own parser). But what is the compelling reason to switch right now and thus break every single existing theme? And I think XML is a lot more cumbersome to edit by hand than what we have now. What is the reason you want XML so bad?

Maybe when the theme creator is finished (so you won't edit by hand anymore), I will switch to XML. It isn't a huge change to the code to do so.

XML is a buzz word. It does help in certain areas (program interoperability), but that doesn't mean having XML in SK makes SK a better program at this stage of development. Don't believe the hype :)

Report

ViRgiLiO

17 years ago

Talking about python. Will SK support python 2.3 in a nearly future?

Report

C

ageitgey

17 years ago

Yes, if one of the following two things happens:

Mandrake releases 9.2. I upgrade and thus have a python 2.3 box to test on.

or

Someone else submits a patch :)

I don't have python 2.3 to test with right now. But I would love to add python 2.3 support.

Report

C

ageitgey

17 years ago

What does replica do that you can't do in SK? SK can do a whole lot more than KarambaR. I'm sure KarambaR is a great program. It's just got a different focus than SK.

The theme creator is kind of neat, but it's not really WYSIWYG. I definately plan to do a real SK theme editor at some point, but I want to do it more like the way Qt Designer works.

Please don't everyone yell at us to merge. We are giving you cool toys for free and asking nothing in return. I've worked many, many hours on SuperKaramba. The KarambaR guy is designing what he thinks is cool and I'm designing what I think is cool. Suggestions are welcome, but patches are much better :)

Report

hughnicks

17 years ago

this is getting more and more frustrating.
how can this not work on a new install of fbsd 5.1 and kde 3.1.3? is it not supposed to? does it only work with gnome?
how can i not have python installed correctly when pkg_info tells me it is?

why does the config file complain about stuff that i don't have installed? what extra stuff do i need to install after a new fbsd installation???

once again;

# cd superkaramba-0.31/
# ./configure
checking build system type... i386-unknown-freebsd5.1
checking host system type... i386-unknown-freebsd5.1
checking target system type... i386-unknown-freebsd5.1
checking for a BSD-compatible install... /usr/bin/install -c
checking for -p flag to install... yes
checking whether build environment is sane... yes
checking for gawk... no
checking for mawk... no
checking for nawk... nawk
checking whether make sets $(MAKE)... yes
checking for style of include used by make... GNU
checking for gcc... gcc
checking for C compiler default output... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking dependency style of gcc... gcc3
checking how to run the C preprocessor... gcc -E
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking whether g++ supports -Wundef... yes
checking whether g++ supports -Wno-long-long... yes
checking whether g++ supports -Wnon-virtual-dtor... yes
checking whether g++ supports -fno-exceptions... yes
checking whether g++ supports -fno-check-new... yes
checking whether g++ supports -fexceptions... yes
checking how to run the C++ preprocessor... g++ -E
checking whether g++ supports -frepo... yes
not using lib directory suffix
checking for ld used by GCC... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for /usr/bin/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/nm -B
checking for a sed that does not truncate output...
checking whether ln -s works... yes
checking how to recognise dependant libraries... pass_all
checking for egrep... grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking the maximum length of command line arguments... 16384
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for objdir... .libs
checking for ranlib... ranlib
checking for strip... strip
checking if gcc static flag works... yes
checking if gcc supports -fno-rtti -fno-exceptions... yes
checking for gcc option to produce PIC... -fPIC
checking if gcc PIC flag -fPIC works... yes
checking if gcc supports -c -o file.o... yes
checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... yes
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking dynamic linker characteristics... freebsd5.1 ld.so
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
configure: creating libtool
appending configuration tag "CXX" to libtool
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking for g++ option to produce PIC... -fPIC
checking if g++ PIC flag -fPIC works... yes
checking if g++ supports -c -o file.o... yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... yes
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking dynamic linker characteristics... freebsd5.1 ld.so
appending configuration tag "GCJ" to libtool
checking if gcj supports -fno-rtti -fno-exceptions... (cached) yes
checking for gcj option to produce PIC... -fPIC
checking if gcj PIC flag -fPIC works... no
checking if gcj supports -c -o file.o... no
checking whether the gcj linker (/usr/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... yes
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking dynamic linker characteristics... freebsd5.1 ld.so
checking for msgfmt... /usr/local/bin/msgfmt
checking for gmsgfmt... /usr/local/bin/msgfmt
checking for xgettext... /usr/local/bin/xgettext
checking for main in -lutil... yes
checking for main in -lcompat... yes
checking for crypt in -lcrypt... yes
checking for socklen_t... socklen_t
checking for dnet_ntoa in -ldnet... no
checking for dnet_ntoa in -ldnet_stub... no
checking for inet_ntoa... yes
checking for connect... yes
checking for remove... yes
checking for shmat... yes
checking crt_externs.h usability... no
checking crt_externs.h presence... no
checking for crt_externs.h... no
checking for _NSGetEnviron... no
checking for sys/types.h... (cached) yes
checking for stdint.h... (cached) yes
checking for poll in -lpoll... no
checking CoreAudio/CoreAudio.h usability... no
checking CoreAudio/CoreAudio.h presence... no
checking for CoreAudio/CoreAudio.h... no
checking for res_init... no
checking if res_init needs custom prototype... res_init unavailable
checking for killpg in -lucb... no
checking for int... yes
checking size of int... 4
checking for long... yes
checking size of long... 4
checking for char *... yes
checking size of char *... 4
checking for char... yes
checking size of char... 1
checking for dlopen in -ldl... no
checking for shl_unload in -ldld... no
checking for vsnprintf... yes
checking for snprintf... yes
checking for X... libraries /usr/X11R6/lib, headers /usr/X11R6/include
checking for IceConnectionNumber in -lICE... yes
checking for libXext... yes
checking for Xinerama... no
checking for pthread_create in -lpthread... no
checking whether g++ supports -pthread... yes
checking for extra includes... no
checking for extra libs... no
checking for libz... -lz
checking for libpng... no
checking for libjpeg6b... no
checking for libjpeg... no
configure: WARNING:
There is an installation error in jpeg support. You seem to have only one
of either the headers _or_ the libraries installed. You may need to either
provide correct --with-extra-... options, or the development package of
libjpeg6b. You can get a source package of libjpeg from http://www.ijg.org/
Disabling JPEG support.

checking for Qt... libraries /usr/X11R6/lib, headers /usr/X11R6/include using -mt
checking if Qt compiles without flags... yes
checking for moc... /usr/X11R6/bin/moc
checking for uic... /usr/X11R6/bin/uic
checking whether uic supports -L ... yes
checking whether uic supports -nounload ... yes
checking if Qt needs ... sed: first RE may not be empty
yes
checking for rpath... yes
checking for KDE... libraries /usr/local/lib, headers /usr/local/include
checking for KDE paths... defaults
checking for dcopidl... /usr/local/bin/dcopidl
checking for dcopidl2cpp... /usr/local/bin/dcopidl2cpp
checking for mcopidl... /usr/local/bin/mcopidl
checking for artsc-config... /usr/local/bin/artsc-config
checking for kde-config... /usr/local/bin/kde-config
checking for meinproc... /usr/local/bin/meinproc
checking whether byte ordering is bigendian... no
checking for MAXPATHLEN... 1024
checking for Python directory... /usr/local
checking for Python2.2... header no library no modules no
checking for Python2.1... header no library no modules no
checking for Python2.0... header no library no modules no
checking for Python1.5... header no library no modules no
checking for libxmms... xmms-config: not found
xmms-config: not found
no
checking if doc should be compiled... yes
checking if po should be compiled... yes
checking if src should be compiled... yes
configure: creating ./config.status
fast creating Makefile
fast creating doc/Makefile
fast creating doc/en/Makefile
fast creating po/Makefile
fast creating src/Makefile
config.status: creating config.h
config.status: config.h is unchanged
config.status: executing depfiles commands

Good - your configure finished. Start make now

why doesn't it say somewhere (anywhere), about other files you might need to install this? why wouldn't i have jpeg support built in. what do i need?

thank you.

Report

svnt

17 years ago

checking for Python2.2... header no library no modules no
checking for Python2.1... header no library no modules no
checking for Python2.0... header no library no modules no
checking for Python1.5... header no library no modules no

This is your problem, or at least your first one. You need to have Python headers/modules installed for this installation to work, even though the configuration script will chug along just fine if you don't. If you do have Python installed, check the paths that the config script is looking in in config.log and make a symbolic link so that it finds it.

Report

C

ageitgey

17 years ago

Only linux is supported right now. That's simply because I don't have any freebsd boxes here to test SK right now. I wish I could help. Maybe try asking on some other freebsd-focused help forums.

Report

DecayingOmega

17 years ago

jesus hates you for posting that

Report

JasonX

17 years ago

The GNOME team is working hard to mkae a karamba equivalent lol :)

http://gdesklets.gnomedesktop.org

I do like that they're using XML and its more flexible though, but SK is way more powerful and has a lot more features. but, maybe SK could use XMl too, it doesen't sound like a bad idea, it would defintely be easier to make a GUI SK applet contrustor if we used XML.

There are a few cool ideas in gdeskelt sthat we could use, just check out the source.

Anyway, I'm happy with 0.31, jsut wish the GUI was more like I said above.

Report

hughnicks

17 years ago

i'm running kde 3.1.3 on freebsd 5.1, and evertime i try to install sk, the configuration file works ok, but then during the compile, i get this:

-c -o main.o `test -f 'main.cpp' || echo './'`main.cpp; \
then mv ".deps/main.Tpo" ".deps/main.Po"; \
else rm -f ".deps/main.Tpo"; exit 1; \
fi
In file included from main.cpp:19:
karamba.h:12:20: Python.h: No such file or directory
In file included from main.cpp:19:
karamba.h:185: syntax error before `*' token
main.cpp:35: syntax error before `*' token
main.cpp: In function `int main(int, char**)':
main.cpp:77: `Py_Initialize' undeclared (first use this function)
main.cpp:77: (Each undeclared identifier is reported only once for each
function it appears in.)
main.cpp:80: `PyEval_InitThreads' undeclared (first use this function)
main.cpp:82: `mainThreadState' undeclared (first use this function)
main.cpp:85: `PyThreadState_Get' undeclared (first use this function)
main.cpp:88: `PyEval_ReleaseLock' undeclared (first use this function)
main.cpp:118: `PyInterpreterState' undeclared (first use this function)
main.cpp:118: `mainInterpreterState' undeclared (first use this function)
main.cpp:120: `PyThreadState' undeclared (first use this function)
main.cpp:120: `myThreadState' undeclared (first use this function)
main.cpp:120: `PyThreadState_New' undeclared (first use this function)
main.cpp:121: `PyThreadState_Swap' undeclared (first use this function)
main.cpp:122: `PyEval_AcquireLock' undeclared (first use this function)
main.cpp:123: `Py_Finalize' undeclared (first use this function)
gmake[2]: *** [main.o] Error 1
gmake[2]: Leaving directory `/usr/local/superkaramba-0.31/src'
gmake[1]: *** [install-recursive] Error 1
gmake[1]: Leaving directory `/usr/local/superkaramba-0.31/src'
gmake: *** [install-recursive] Error 1

does anyone have an idea of what could be wrong?

thanks.

Report

ltcmdrdata

17 years ago

its because of python2.3

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 7