[Kde-pim] configuration in akonadi-next

[Aaron J. Seigo]

On Wednesday, December 17, 2014 09.56:14 Martin Klapetek wrote:
> That is moreless how KAccounts works these days.

Questions:

How well does KAccounts work on Windows / Mac / Android?
What dependencies does it bring?
Is the SSO daemon a requirement, or can we pull that in-process on platforms 
where we will need to?

A reasonable (good, even) goal is to centralize configuration of accounts, 
however this only really makes sense in environments where this is integrated 
(so.. Plasma and Unity, currently). On Windows/Mac this probably makes less 
sense .. how difficult is it to embed the configuration in the application 
(e.g. Kontact) when necessary?

I can see us using the "full environment integration" approach on Linux, but 
for Win/Mac/Android we probably need something a bit less integrated with the 
environment as a whole and a bit more with the application itself.

-- 
Aaron J. Seigo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-pim/attachments/20141218/5ad47dd2/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/