emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Adam Spiers <orgmode@adamspiers.org>
To: Baptiste Fouques <bateast@bat.fr.eu.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: Sync Org with Google Calendar using google API (rather than caldav)
Date: Mon, 8 Apr 2013 18:25:20 +0100	[thread overview]
Message-ID: <CAOkDyE9o17gqqBnuky0+_RvK4MMGNJxZ3pE-sTLiWVu5H+aTTA@mail.gmail.com> (raw)
In-Reply-To: <loom.20130402T090240-590@post.gmane.org>

Thanks a lot for the info!  I agree that natively talking to the JSON API
is a nice feature :)

On 2 April 2013 08:17, Baptiste Fouques <bateast@bat.fr.eu.org> wrote:
> Adam Spiers <orgmode <at> adamspiers.org> writes:
>> Sounds interesting.  It would be very helpful if you could explain how it is
>> different from the other synchronization possibilities out there, e.g.
>> http://orgmode.org/worg/org-tutorials/org-google-sync.html
>> https://code.google.com/p/emacs-google/
>> https://github.com/travisbhartwell/Emacs-Google-Calendar-Sync
>> http://www.emacswiki.org/emacs/GoogleClient
> two  main things  make  my sync  different  (also  this does  not  make it  more
> interesting ;)
> - it does not rely on external command
> - it does not rely on ics
> I always found that relying on  external commands makes thing more complex : you
> have to  configure that command, in  its configuration file or  through scripted
> call by passing right arguments, and then you have to integrate it in your Emacs
> workflow.
> Using command in Emacs, configured  through convenient customization group is so
> natural …
> Then, my sync. uses Google json API (and authentification using oauth, stored in
> crypted file, for no secret in your  config file or anywhere else). This make it
> by far less  portable. But, with Google dropping standards,  or juts maintaining
> it at  there minimal  level, it makes  it more  close to what  you can  get from
> Google calendar and events.
> Also using  elisp Json library is  so easy and  robust in regard to  parsing ics
> files that it sounds very natural to use it.
> I don't  mean it is  better than caldav  sync tools, but  that I could  not find
> myself satisfied  with those  tools, worried  about Google  call to  drop caldav
> compatibility,  that  I  feel  I  need   something  more  close  to  Google  API
> possibilities. Then I  started it, and just  offer to share (that  how it works,
> right ? ;)
> Thanks for the work of the community,
> Bat.

  reply	other threads:[~2013-04-08 17:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-29 15:05 Sync Org with Google Calendar using google API (rather than caldav) Adam Spiers
2013-04-02  7:17 ` Baptiste Fouques
2013-04-08 17:25   ` Adam Spiers [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-03-29 11:03 Baptiste
2013-04-03 17:09 ` Bastien

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAOkDyE9o17gqqBnuky0+_RvK4MMGNJxZ3pE-sTLiWVu5H+aTTA@mail.gmail.com \
    --to=orgmode@adamspiers.org \
    --cc=bateast@bat.fr.eu.org \
    --cc=emacs-orgmode@gnu.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).