We've had rather nice Python and Ruby support for some time, thanks to Simon Edwards on Python, Richard Dale on Ruby and Carter Beauford on the drums .. wait, no, Carter is part of some other cool group, but Simon and Richard do indeed rock out with us. ;) While I think that these are great languages for writing full applications with, I also feel that there are possibly better choices for little plugins like Plasmoids. I won't get into all those reasons here (I probably have already done so in a past blog entry, though), but there you have it.
The entries case insensitive, and if security says "yes" then the extensions are activated and the API available to that instance of the widget grows accordingly. This also allows us to quite easily know which Plasmoids will be doing things like, well, opening files or launching applications. You can read about these extensions in the aptly named Extensions section of the API documentation or by looking at the http and fileOperations examples in the kdeexamples module.
WebKit Plasmoids Improve
This resulted in people actually writing WebKit based Plasmoids which led to a feature request for Web Inspector support. QtWebKit made that insanely simple: a one line patch and the results are:
There is more to do with the WebKit ScriptEngine, but it's already pretty nice for the 4.4 release of the KDE Software Compilation. One of the biggest things lacking is documentation. We have two examples in kdeexamples now (the above screenshot is from one of them) and there is an introductory article on Techbase, but it's really embryonic still.