Ticket #196 (new enhancement)

Opened 3 years ago

Last modified 3 years ago

External Integration, not Synchronization

Reported by: kukkurovaca@gmail.com Assigned to: developer
Priority: normal Milestone:
Component: Instiki Version: 0.10.0
Severity: normal Keywords: email RSS iCal iCalendar Atom
Cc:

Description

I use textile in Instiki and love it, and I've noticed that there are a number of great things that also use textile lately, like backpack and 43things. Is there any way to get information into or out of in Instiki in a way that would work with these? I'm thinking particularly of backpack, which allows emails in and out....

Change History

08/07/05 14:55:13 changed by quidire@gmaildotcom

  • keywords set to email RSS iCal iCalendar Atom .
  • priority changed from lowest to normal.
  • version changed from 0.9.2 to 0.10.0.
  • summary changed from Synchronization to External Integration, not Synchronization.

I would really rather that Instiki worked on less vendor-specific solutions. For example, how about some way to "import" and markup iCalendar feeds.

* A URI would be specified, as well as a view {{iCal|URI|viewspec}} or somesuch, in the editing window of a page

* That page, when rendered, would render the iCalendar data and allow the subsequent material of the page to mark it up

Some mechanism needed to indicate if subsequent content is to be rendered below or added to the rendered iCal view.

perhaps {{2005.08.07} content} (recognising the date format) and {{2005.08.07.14.26} content} for time specific content...

* Any markup to specific dates could be propogated back to the original server if it supports two-way subscription

* Wiki references to a specific date might merge all (or a user definable subset) subscribed iCalendar data for that day, and display that as well as any subsequent markup

Further possibilities in the realm of interfacing with other data stores:

* Embedded RSS subscriptions (works much like above)

* Email Gateway/importer isn't a bad idea (hell, even IM could work ;-) )

* Support for Atom's new publishing protocol?