On Wed, Oct 19, 2016 at 4:54 AM, Elvis Angelaccio <elvis.angelac...@kde.org> wrote:
> > Hi Martin, > I'm planning to integrate KAccounts with kio-gdrive, so your email is > very much appreciated. > What exactly is "Kaccounts" in the first place? Are we talking about > the kaccounts-integration repo? > KAccounts is basically just the KDE UI for the Accounts-SSO system. It's a collection of KCM, which allows you to manage those accounts and also KDED daemon which allows to load custom plugins that react on those account changes and/or service changes (each account has a set of services). So for example, in the KCM you add a Google account and then the KDED module is notified of this and it will pass this info to all its loaded plugins. The plugins would then check if the account is of interest and if yes, then do something, like set up the calendar integration, for example. The KDED module also watches for services change, so eg. if in the KCM you disable the calendar service, the Google plugin would disable the calendar (but not remove). At least that's the idea. In the case of the kio-gdrive, I'm not sure if you'd need such plugin at all. I mean, if you don't need to configure anything, then you won't. You can just query the credentials data from KAccounts directly from the kio. > A tutorial would be great, but maybe is enough to look at the KDE > Telepathy usage. Could you share more details about this? > KDE Telepathy is a bit special case. It builds a lot on the existing upstream code, which is basically a Mission Control plugin that does exactly what the KDED is doing. Ie. there is no KTp KDED plugin, this is all handled by Telepathy itself. I'd recommend looking at the kaccounts-mobile repo, which has some code for ownCloud stuff, like importing CardDAV contacts iirc. Cheers -- Martin Klapetek