With the great intro provided about Plasma Packages to get Apple's Dashboard Widgets running, it follows a screenshot that shows SuperKaramba - yes, it works with legacy *.skz files.
btw, SuperKaramba example that uses KHTML to display content :)
I guess this has been asked before, but what's the reason you keep developing superkaramba as separate API instead of porting good widgets over to plasma dataengines/visualisations?
Does superkaramba extend beyond the features plasma provides, or it just another widget engine?
A bunch of good reasons come to mind:
* There are loads of good SuperKaramba widgets already in existence that can keep working this way.
* There's existing SuperKaramba know-how in the community that doesn't go down the drain this way.
* Some might prefer the SuperKaramba API to Plasma or the other widget engine APIs Plasma supports (Apple Dashboard, maybe more in the future).
* It makes the move to KDE 4 less disruptive for KDE 3 users because they can keep using the widgets they've grown dependent on. Backwards compatibility is a nice thing to be able to afford, and given that Plasma is architected to make it easy to plug in support for other widget engines, the cost is low.
* I assume it's fun for Sebastian.
Nothing to add there, thanks eike :)
p.s. yes, it's "just another widget engine" and it also shows how well Plasma is designed to be able to extend it. So, we are ready for Opera, Yahoo or google widgets and you can be sure Apple's Dashboard Widgets and SuperKaramba Themes are just the first both script engines and more will follow over the time.
Incredibly sweet! I use AIO to keep track of processes and network usage, and am thrilled at that SuperKaramba not only exists for KDE4.x, but is integrated into the Power of Plasma!
This place is a blogging platform for KDE contributors. It only hosts a fraction of KDE contributor's blogs. If you are interested in all of them please visit the agregator at Planet KDE.