[Kde-imaging] [Bug 199848] turn facebook import/export plugin into a virtual folder ressource

[Colin Guthrie]

https://bugs.kde.org/show_bug.cgi?id=199848





--- Comment #11 from Colin Guthrie <kde colin guthr ie>  2009-10-01 15:35:13 ---
If I understand Gilles comment correct Johannes, then most of what you suggest
is already handled by the abstraction layer in Akonadi.

I believe Gilles is suggesting a generic client to the Akonadi being added to
libkipi such that host applications can implement this external linkage very
easily and that makes a lot of sense.

In Akonadi you'd write the relevant code to setup and configure each individual
external link and it would then expose a standard API for querying and updating
the external stuff. As far as the implementation in Kipi is concerned, all it
deals with is generic code for searching and listing the objects.

Essentially libkipi (or something - doesn't matter where) will provide a class
that represents an "image" complete with tags and extra attributes etc. This
will be common class that is specifically serialised to/from the Akonadi
system.

Once this common class is written, it is simply a matter of writing an akonadi
resource for each external system. Once all this is in place, it would be
trivial to write a standard widget to be included in libkipi and also to expose
it in other areas of KDE (e.g. for screen savers or virtualised kio style
browsing).

I'm a bit out of date with my terminology, but please do read up on Akonadi if
you are interested in helping out here.

I'd be happy to arrange a time for an interactive chat on IRC so that I can
explain things better and hopefully find people to take the idea forward!

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.