From mboxrd@z Thu Jan 1 00:00:00 1970 From: Meng Weng Wong Subject: roundtrip integration with Asana? Date: Thu, 31 Jan 2013 19:46:07 +0800 Message-ID: <394BD125-8D2D-4305-BE41-98C902FC7DAD@gmail.com> References: <877gmt3dzq@ch.ristopher.com> <871ud13dkp@ch.ristopher.com> <6C559BF7-BACF-48AF-AB06-383D6AC14BDE@gmail.com> <87622dlhqm.fsf@bzg.ath.cx> Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([208.118.235.92]:51127) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U0sav-0001iV-RJ for emacs-orgmode@gnu.org; Thu, 31 Jan 2013 06:46:20 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1U0sas-0002wc-Te for emacs-orgmode@gnu.org; Thu, 31 Jan 2013 06:46:17 -0500 Received: from mail-pb0-f50.google.com ([209.85.160.50]:39234) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U0sas-0002vp-Mp for emacs-orgmode@gnu.org; Thu, 31 Jan 2013 06:46:14 -0500 Received: by mail-pb0-f50.google.com with SMTP id ro8so1583492pbb.23 for ; Thu, 31 Jan 2013 03:46:12 -0800 (PST) In-Reply-To: <87622dlhqm.fsf@bzg.ath.cx> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: "emacs-orgmode@gnu.org Mailing List" I use org for personal task management, but I use asana.com with my = workgroup. I just learned that Asana offers an API that exposes all the usual = interfaces. http://developers.asana.com/documentation/ Roundtrip integration between org and Asana is therefore possible. I'm sure I'm not the first person to have thought about this... which = approach would be the preferred architecture for achieving such = integration? I can imagine writing, say, a bunch of Perl scripts using WWW::Asana, to = act as a gateway between text file and web API. As far as org and emacs = are concerned, the text files magically update themselves, and no = additional elisp need be written. I can also imagine native org-mode extensions that talk directly to = asana, in the same way that org2blog/wp talks directly to Wordpress. = Until emacs gets threading support, though, blocking HTTP IO operations = might seriously inconvenience one's editing. Which approach do you think is preferable?