activity aware plasmoids

[Martin Klapetek]

On Fri, Mar 9, 2012 at 11:30, Sebastian Kügler <sebas at kde.org> wrote:

> On Friday, March 09, 2012 10:30:40 Marco Martin wrote:
> > On Monday 05 March 2012, Sebastian Kügler wrote:
> > > On Saturday, February 25, 2012 16:01:15 Marco Martin wrote:
> > > > not storing the entries of the various social media i think, since is
> > > > too
> > > > volatile data that loses meaning pretty quickly, but having the
> "twitter
> > > > source" facebook source and so on as resources, that gets associated
> to
> > > > the activitiy resources (funny fact, association of any nepomuk
> resource
> > > > to an activity is something already supported, is just the desktop
> that
> > > > lacks an ui for it.. yet
> > >
> > > This could (probably should) be unified through Akonadi, which would
> make
> > > give us most of the complicated things for free. THere's already a
> > > (unmaintained) microblogging resource, we support all kinds of emails
> > > (social networking for geeks ;)), Thomas McGuire has been working on a
> > > Facebook Akonadi resource, etc.
> > >
> > > So what's needed is a mechanism to combine and display this data, and
> > > probably a bit more streamlined configuration. Ow, and more resources
> for
> > > social networks.
> >
> > btw, do we have note on the breakout session at the active sprint on
> > exactly  this topic? should be published and used as starting point
>
> *pokes Marty*
>


Sorry for the delay, I was mostly away the whole weekend, but here it goes.

So the idea is to have one central auth handling component, which will
shield the apps themselves from account credentials, ie. the apps will work
only with an auth token provided by the auth library. This library is
almost done btw. For getting the feeds from social networks, we'll use
akonadi resources/agents, which will cache that stuff in there. We don't
really want that stuff in Nepomuk as we want to only cache it, not store
it. We can still make some use of those data in Nepomuk though. Contacts
will be feeded there for free by the akonadi feeders. The frontend, (the
social apps themselves), will then be built on top of Akonadi. We also need
a KCM to have one place to configure it all, this is currently in the works
by Alex Fiestas. A prerequisite is working metacontacts.

I plan to work on this as a GSoC project and I plan to write it in details
and well structured in the proposal, which can later be published for
reference/starting point.

--
Martin Klapetek | KDE Developer
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/plasma-devel/attachments/20120312/a5c9c2aa/attachment.html>