emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Anupam Sengupta <anupamsg@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: The most important project for org developers?
Date: Thu, 19 Mar 2009 21:01:22 +0530	[thread overview]
Message-ID: <m2ocvxleb9.fsf@gmail.com> (raw)
In-Reply-To: 49C227F2.8050009@manor-farm.org

>>>>> "Ian" == Ian Barton <lists@manor-farm.org> writes:

    >>
    >> I currently export my schedule to google calendar with org's
    >> icalendar export. But I have to manually upload the ics file, so

[...]


    Ian> If you have access to a server that supports WebDav you can
    Ian> create a Google Calendar that reads your org ics file directly.

    Ian> I publish my todo items to a web server, where I can browse
    Ian> them on my phone. It's also possible to copy the html fine to
    Ian> my phone's memory, where I could browse it without Internet
    Ian> access. The only downside is that it's read only, but that's
    Ian> not a problem for me.

I also export the agenda as an ics file and then pre-process using Ruby
to make some changes on the ics file (mainly to remove some of the TODO
entries that I normally do not need on my Blackberry). There is a good
Ruby module for handling the iCalendar format
(http://icalendar.rubyforge.org/).

I then use a automator workflow to load the processed ics file into iCal
(I am using OS X) and sync normally to iCal using the synchronization
program that came with the Blackberry (PocketMac Sync Manager).

As a bonus, I get to sync the iCal entries automatically with Google
calendar as well.

I.e, the flow is:

+--------+ ics  +-------------+ ics   +--------------+
| Org    +------> Ruby        +-------> Automator    |
+--------+      +-------------+       +-------+------+
                                              | load
                +-------------+ sync  +-------v------+
                | PDA /Google <-------+    iCal      |
                +-------------+       +--------------+

This works pretty well - though the problem is that it is a one-way
street: from org files to the BB - and round trip changes are not yet
possible.

Also, this is a OS X oriented solution, but the automation can probably
be done on other platforms as well using equivalent scripting.

HTH,

-- 
Anupam

  reply	other threads:[~2009-03-19 15:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-18 22:43 The most important project for org developers? Sven Bretfeld
2009-03-18 23:56 ` Michael Ekstrand
2009-03-19  8:43 ` Detlef Steuer
2009-03-19  9:05   ` Detlef Steuer
2009-03-19 10:42 ` Friedrich Delgado Friedrichs
2009-03-19 11:09   ` Ian Barton
2009-03-19 15:31     ` Anupam Sengupta [this message]
2009-03-19 16:03     ` Friedrich Delgado Friedrichs
2009-03-19 16:45     ` Rasmus Pank Roulund
     [not found]       ` <87bprqtzl1.fsf@gmx.ch>
2009-03-24 21:18         ` sven.bretfeld

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=m2ocvxleb9.fsf@gmail.com \
    --to=anupamsg@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).