Just a quick note for packagers and people building kdelibs:
I released libattica 0.1.3 yesterday. Now kdelibs trunk (4.5) doesn’t depend on an unrelease attica version from kdesupport trunk any more.
Get it while it’s hot: ftp://ftp.kde.org/pub/kde/stable/attica/.
No big changes, but a few bug fixes and one or two new calls. And a lesson learned.
When you use QPluginLoader you should not delete the root components of the loaded plugins… just like it says in the docs… of course it will only bite you once you have more than one application using the plugin at once.
That’s why I wrote Grantlee::PluginPointer.
http://gitorious.org/grantlee/grantlee/blobs/master/corelib/pluginpointer_p.h
It allows different objects to access the plugin, and makes sure it gets deleted when nothing is using it anymore.
http://steveire.wordpress.com/2010/03/05/the-mother-goose-plugin-loader-pattern/
In this case using unload upon deletion works OK since the plugin should only be used by libattica internally, so it’s all in one place. Still I agree with you that the docs could be clearer as I obviously missed the unload issues the first time. I’ll remember the ” The Mother Goose Plugin Loader Pattern” the next time I touch plugins though
And you already bumped the version requirement in trunk to 0.1.4?
Hi,
is this version for kde 4.4 ?
Will kde 4.4 build against attica 0.1.4 ?
Attica will stay compatible, so for KDE 4.4 any version since 0.1.2 will work. In 0.1.3 you have some additional bug fixes. 0.1.4 which will be required for KDE 4.5 brings a few new features, such as allowing to see which provider provides what parts of the ui. That is needed for the ownCloud integration for example.