Quoting Sebastian Kügler <se...@kde.org>:
everything the C++ widget does, I'd in fact like to replace that widget
(recycling its plugin name for the QML Plasmoid).
+1 :)
that you won't get the dataengine if QOAuth is not there). The app or engine
does not save the password anymore, it rather saves the oauth accesstoken and
-secret to a koauthrc config file. This could also go into kwallet, not 100%
sure about that ... thoughts?
It's a *huge* improvement to not store the password anymore but just
the access token :)
We can store the access token either in kwallet (better) or in
koauthrc config file. IIRC we store the password in a config file
today right? So, both solutions are already better than current
scenario :)
As to (3), this brings another additional dependency in. The reason
to use the
JSON format instead of XML are:
- the XML feeds do not contain all information, so we end up needing a
lot
of extra requests
- the files are a lot smaller, I've measured about 40% smaller files for
JSON feeds than for XML feeds
- Code is smaller, JSON is a bit easier to parse (it basically puts
everything into a map for you to pick from)
- Twitter recommends JSON above XML
JSON++ even if it adds a new dependency. We can take a look into Qt5's
json parser as it may be even better and we can backport just it to
use right now.
Cheers :)
--
-------------------------------------------------------
http://claimid.com/morpheuz
Blog: http://blog.morpheuz.cc
PGP: 0xDBEEAAC3 @ wwwkeys.pgp.net
-------------------------------------------
_______________________________________________
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel
