From: Sriram Karra <karra.etc@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Org Mode TOOD two way sync tool
Date: Fri, 22 Jun 2012 18:03:45 +0530 [thread overview]
Message-ID: <CAFkt3UNhoQBMk3bqJx6dycN7QkxdQpx4BN9iQHpyGs-vHWRd3g@mail.gmail.com> (raw)
In-Reply-To: <4FE45EF9.8040307@grierwhite.com>
[-- Attachment #1: Type: text/plain, Size: 3022 bytes --]
Chris, thanks for the pointer to org-toodledo. Does org-toodledo's handle
all the options and formats of possible TODOs supported by org mode? Are
you yet to implement support for anything that is parsed by the Emacs
org-mode?
On Fri, Jun 22, 2012 at 5:33 PM, Christopher J. White <
orgmode@grierwhite.com> wrote:
> Hi Karra,
>
> I've been working on org-toodledo.el to perform bi-directional sync of
> TODO items with the Toodledo server, and faced many of the same issues you
> raise about figuring out the exact format and grammar of a TODO item.
>
> You may find looking at my source useful, either as inspiration,
> integration, or just understanding what fields are what.
>
> The general approach was to build an object that represents a parsed TODO
> item, and fill that in from either the org-buffer TODO items, or from items
> retrieved from the server. That object can then be compared to others (one
> from the server and one from the local buffer), converted to a new org
> TODO, sent to the server as a new TODO, etc. The components of the TODO
> item are obviously targeted to what makes sense for Toodledo, but I think
> they are fairly generic.
>
> You might also look at org-element.el which I recently learned about which
> may also help. I have it on my TODO list to learn more about it to see if
> I can't refactor org-toodledo to leverage it. It is more geared toward
> generic org items as opposed to specifically TODO items.
>
> ...cj
>
>
> On 6/22/12 2:40 AM, Sriram Karra wrote:
>
>> I am the author of ASynK (http://karra-asynk.appspot.**com<http://karra-asynk.appspot.com>),
>> a PIM sync
>> tool and framework written in python that works across a variety of PIM
>> providers such as Outlook, Google and BBDB. I am considering extending
>> ASynK to do a bi-directional sync of Outlook tasks to Org Mode tasks. To
>> be able to do this I need a working read/write API for reading and
>> creating TODOs in org mode.
>>
>> *"Offline parsers"*
>>
>>
>> My first preference is to be able to parser org files without required
>> Emacs - this is the approach that I have implemented for BBDB sync. I
>> considered PyOrgMode (https://github.com/bjonnh/**PyOrgMode/network<https://github.com/bjonnh/PyOrgMode/network>),
>> but
>> it appears unable to process TODOs, or even recurring events. To be able
>> to extend PyOrgMode so I can read and write TODOs, I needed a full
>> description of the format of TODO entries in all its forms. The Org
>> manual itself has this information, I'm sure but scattered all over the
>> place, given its real audience. Can someone point me to some sort of a
>> concise representation, if any, of the org file format grammar?
>>
>> *org-protocol*
>> *
>>
>> *
>> By quickly reading the documentation I figured that org-protocol can be
>> used to create entries, but is there a way to use it to do generic
>> queries like "list all TODOs in a specified file, with a particular
>> property value" and such?
>>
>> Any help is much appreciated.
>>
>> -Karra
>>
>
>
>
[-- Attachment #2: Type: text/html, Size: 3679 bytes --]
next prev parent reply other threads:[~2012-06-22 12:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-22 6:40 Org Mode TOOD two way sync tool Sriram Karra
2012-06-22 12:03 ` Christopher J. White
2012-06-22 12:33 ` Sriram Karra [this message]
2012-06-22 14:05 ` Christopher J. White
2012-06-24 13:15 ` Aurélien Aptel
2012-06-24 13:17 ` Aurélien Aptel
2012-06-24 17:07 ` Christopher Allan Webber
2012-06-25 12:32 ` Aurélien Aptel
2012-06-25 13:51 ` Sriram Karra
2012-06-25 14:41 ` Christopher Allan Webber
2012-06-25 15:29 ` Christopher Allan Webber
2012-10-07 19:48 ` Jonathan BISSON
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
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=CAFkt3UNhoQBMk3bqJx6dycN7QkxdQpx4BN9iQHpyGs-vHWRd3g@mail.gmail.com \
--to=karra.etc@gmail.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).