export iCalendar format for pages with an RSS feed

iCalExporterPlugin

Description

read trac feeds in your calendar

For out of the box trac, only the roadmap module has an iCal feed. the IcalExporterPlugin exposes an iCal format in the "Download in other formats" section. The calendar is created by parsing the RSS feed for the page and transforming it to iCal format. The calendar can then be read by (e.g.) google calendar by using the Add by URL feature.

Installation

The homepage for this plugin is at http://trac-hacks.org/wiki/IcalExporterPlugin with links to the subversion repository and zipped eggs. The plugin is installed in the standard way. For more information, see http://trac.edgewall.org/wiki/TracPlugins

How it Works

The IcalExporterPlugin examines if a page has an RSS feed. If it does, it adds a iCalendar download option as well. The brunt of the work is done by ical.py, which writes the iCalendar format (most of the hard work was stolen from the roadmap module). ical.py is independent of trac and should probably be moved upstream of the plugin or of trac entirely.

Example

Click on the Timeline navigation item in a trac instance where this plugin is enabled. Scroll to the bottom of the page. The ability to download as iCalendar should be evident:

sample screenshot of the iCalExporter plugin in action

see the bottom of http://trac.openplans.org/openplans/timeline

Bugs/Feature Requests

Existing bugs and feature requests for IcalExporterPlugin are here.

If you have any issues, create a new ticket.

Download

Download the zipped source from here.

Source

You can check out the source using Subversion, or browse with Trac.

Recent Changes

[5054] by k0s on 12/23/08 07:49:41

match query; this is useless without preserving the arguments; refs #4104

[5053] by k0s on 12/23/08 07:44:05

adding helpful comment

[5051] by k0s on 12/23/08 06:04:31

fix capitalization for FeedParser?

[5050] by k0s on 12/23/08 05:42:44

minor documentation improvements, fixes #4105

Author/Contributors

Originally developed at The Open Planning Project

Author: k0s
Contributors:

Attachments