Hi folks,

I've been reading your thread on "AnyDateTime" and stumbled upon this
quote from Markus:

For most purposes, we would like 
to implement an idea of a totally ordered, "physical" time, i.e. every two 
input times should be comparable and correspond to real time points of the 
world. This excludes inputs like "May 1" which would describe an infinite 
number of recurring intervals that we are not prepared to handle. 

I was actually reading through the list because I'm quite interested in
a result format that could present recurring events on a weekly or
monthly basis.

When you say, you're not prepared to handle that, what are the issues
involved? Are there no efforts being put into a recurring events feature?
 I don't know whether I can find the time to work on it, but if you
could give me a few hints as to the problems, I might give it a try.

The background is that we're currently using semediawiki to handle our
events calendar (https://www.hackerspace.lu/wiki/Calendar and
Trouble is with recurring (weekly or monthly) classes or workshops. It'd
be very convenient to have such a feature.


Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
Semediawiki-devel mailing list

Reply via email to