On Friday, 2014-02-07, 15:59:52, Sebastian Kügler wrote: > Hi Heena, > > On Thursday, February 06, 2014 21:59:48 Heena Mahour wrote: > > Greetings , > > I was recently discussing about the integration of plasma workspace for > > akonadi with Kevin , as also suggested in [1] but is not yet done . > > Further > > , Since is Plasma is moving toward Qt 5.2 and QML 2.0 while akonadi is not > > .It could be achieved by using the control d-bus of akonadi directly > > ,without the use of kdepimlibs .It would be nice to get some suggestions > > over this idea from plasma-devel :) > > You want to implement an akonadi client API over DBus? Isn't that what > kdepimlibs does, so the right thing to do seems porting kdepimlibs to me.
No, sorry, that is a misunderstanding based on missing context :) The GSOC idea referenced below is not about data at all, it is about state. Akonadi state information and control works via D-Bus, so it would be possible to do a client for that without linking to libakonadi-kde. This was just brought up as an option, since Plasma/workspace development and KDEPIM libs development are currently not using the same Qt version and potentially will not during the GSOC period. Cheers, Kevin > > On a second note , it would be nice to have a mentor for it from plasma as > > well apart from Kevin since it is more inclined towards plasma > > [1] > > http://community.kde.org/GSoC/2012/Ideas#Project:_Plasma_Workspace_Integra > > ti on_for_Akonadi Regards ! -- Kevin Krammer, KDE developer, xdg-utils developer KDE user support, developer mentoring
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
