[Kde-pim] Using Akonadi localdir and remote resource bridges

[David Jarvie]

The Akonadi version of KAlarm needs to provide either compatibility with the old ResourceLocalDir and ResourceRemote resources (in their modified KAlarm incarnations), or a migration facility for these resources.

I hope to write an Akonadi based localdir resource, but this isn't likely to be feasible for KDE 4.6, both because of the time needed to code and test it, and because it will presumably need new translatable strings. In the meantime, I'm trying to work out the feasibility of using the resource bridges. Can somebody (e.g. Kevin?) please give guidance on what is necessary to implement them for an application? The possible snag is that KAlarm would probably have to use a modified version of these resource bridges. I notice that plugins are used - would it be a problem having the implementing code outside the kdepim/runtime directory, or would any new code have to be located in kdepim/runtime?

-- 
David Jarvie.
KDE developer.
KAlarm author -- http://www.astrojar.org.uk/kalarm
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-pim/attachments/20101212/e476694f/attachment.sig>
-------------- next part --------------
_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/