Re: [Evolution-hackers] Google Tasks in EDS
Hey, On Thu, 2011-09-01 at 07:58 +0100, Ross Burton wrote: Hi, Is anyone working on a Google Tasks backend for EDS? Annoyingly Google doesn't expose Tasks over CalDAV but they do have a custom HTTP/OAuth/REST API that shouldn't be that hard to access from librest. I don't know if anyone's working on one, but there's a bug report about it here: https://bugzilla.gnome.org/show_bug.cgi?id=652132 Any such backend would be best using libgdata to do the protocol-level work, since as you say, Tasks aren't exposed over CalDAV. This will require a new service to be added in libgdata: https://bugzilla.gnome.org/show_bug.cgi?id=657539 I hope to be able to fix that bug in libgdata next cycle. (Version 0.12 is targeted at GNOME 3.4.) Philip Ross ___ evolution-hackers mailing list evolution-hackers@gnome.org To change your list options or unsubscribe, visit ... http://mail.gnome.org/mailman/listinfo/evolution-hackers signature.asc Description: This is a digitally signed message part ___ evolution-hackers mailing list evolution-hackers@gnome.org To change your list options or unsubscribe, visit ... http://mail.gnome.org/mailman/listinfo/evolution-hackers
Re: [Evolution-hackers] Google Tasks in EDS
On 1 September 2011 08:15, Philip Withnall phi...@tecnocode.co.uk wrote: Any such backend would be best using libgdata to do the protocol-level work, since as you say, Tasks aren't exposed over CalDAV. This will require a new service to be added in libgdata: As far as I am aware the Tasks API uses a custom JSON protocol[1], whereas libgdata implements their GData extensions to Atom, which is why I was suggesting json-glib+librest. Ross [1] http://code.google.com/apis/tasks/v1/reference.html#resource_tasks ___ evolution-hackers mailing list evolution-hackers@gnome.org To change your list options or unsubscribe, visit ... http://mail.gnome.org/mailman/listinfo/evolution-hackers
Re: [Evolution-hackers] Google Tasks in EDS
On Thu, 2011-09-01 at 08:26 +0100, Ross Burton wrote: On 1 September 2011 08:15, Philip Withnall phi...@tecnocode.co.uk wrote: Any such backend would be best using libgdata to do the protocol-level work, since as you say, Tasks aren't exposed over CalDAV. This will require a new service to be added in libgdata: As far as I am aware the Tasks API uses a custom JSON protocol[1], whereas libgdata implements their GData extensions to Atom, which is why I was suggesting json-glib+librest. That's entirely correct. However, I've been thinking about extending libgdata to support JSON-based services in addition to the ‘normal’ Atom-based services for a little while now; since Google seem to be moving in that direction. I think it should be possible, and would be a better approach than writing things from scratch using json-glib. (An approach which, for example, would end up duplicating the non-trivial load of authentication code already present in libgdata.) The code in libgdata should definitely make use of json-glib, though. Philip Ross [1] http://code.google.com/apis/tasks/v1/reference.html#resource_tasks signature.asc Description: This is a digitally signed message part ___ evolution-hackers mailing list evolution-hackers@gnome.org To change your list options or unsubscribe, visit ... http://mail.gnome.org/mailman/listinfo/evolution-hackers
