hi, very quickly… just like I wrote on the plasma mailing list, my recent flood of commit on workspace was due to several small (offline) changes to base applets, on which I implemented the slot configChanged().

This is a slot that is called every time an applet’s configuration is changed behind its back. This is usually because there’s a configuration script running (at startup?) or anyways, the user is modifying the settings from a different place than the configuration dialog.

I finished today with the kdebase applets, now I think that I will start with the ones in kdeplasma-addons (much more fun ;-) ).

So, if you’re an applet developer you may want to do a similar change in your code (and backport it to the 4.4 branch too), or if you’re looking for a junior job to get started with development I think this is a perfect task for you. If you plan on working on such things, please drop me a line though (you can get my mail on my blog… it’s there on the left, yeah, there! black and shiny), so we don’t step on each other’s toes.

You can get a better idea of what you have to do by looking at the commit diff on this cumbersome websvn page:
http://websvn.kde.org/?view=revision&revision=1088785

As you see you simply have to move the configuration reading and setup from init() to configChanged(), and eventually use it from init() too.

Oh and by the way… I’m going to Tokamak 4! :-)