-
Looking at it, the changes to the previous standard (at the end of the RFC) seem to be mainly or even fully about changing constraints (MUST vs. SHOULD) and deprecating certain "features" (like multiple RRULEs). Also, a lot of icalendar support in an application deals with whatever other tools' output you are forced to handle, hence the ical4j lib acts more as a framework anyway, that should...
2009-12-14 22:24:52 UTC in iCal4j
-
I think this is right - it will return a new list with both lists combined. Maybe the javadoc could be a bit more clearer.
Alex.
2009-11-04 16:29:09 UTC in iCal4j
-
Actually the workaround must use the current default timezone, **but the offset applied should be the one for the given, floating datetime**, as the current time could be in DST and the given time not (or vice versa).
Hence it should be:
a) reading from ical4j:
`date.getTime() + TimeZone.getDefault().getOffset(date.getTime())`
b) creating ical4j objects:
`date.setTime(time -...
2009-11-02 16:56:59 UTC in iCal4j
-
Hi fran!
Period.before() means: "whether this period is completed before the given period starts" (see javadoc). Hence B is not before() the target.
Same for Period.after(): "Decides whether this period starts after the given period ends." Applies to G and H.
If the start and end date of a period fall together, it has no length and thus will never intersect another...
2009-10-15 11:02:26 UTC in iCal4j
-
Have you tried to set the validation to relaxed?
See [http://wiki.modularity.net.au/ical4j/index.php?title=Compatibility][1]
*I couldn't find the definition of a valid date-time in the docs*
http://tools.ietf.org/html/rfc2445#section-4.3.5
Which points to ISO 8601, complete representation, hence a 0000 is the year 0, which would be -1 BC in "common" notation. ([from...
2009-10-12 07:51:44 UTC in iCal4j
-
Ups, just noted that the maxCount argument is only for limiting the actual number of matching events returned. So only the system property net.fortuna.ical4j.recur.maxincrementcount is actually useful in that case ;-) AFAIK this isn't in a released version yet (1.0-rc2 was released before this was committed), so you need to build ical4j from cvs.
Regards,
Alex.
2009-08-24 11:24:36 UTC in iCal4j
-
There is another getDates method that allows you to specify a maximum number of events to try, in order to prevent an infinite loop if nothing ever matches [1]:
getDates(final Date seed, final Date periodStart, final Date periodEnd, final Value value, final int maxCount)
You would call
rrule.getRecur().getDates(new Date(startCal.getTime()), new Date(startCal.getTime()), new...
2009-08-24 11:19:42 UTC in iCal4j
-
There are two quite useful parts in iCal4j apart from reading/writing icalendar (RFC-2445) files: recurrence calculation (based on the icalendar model). That one is tricky to get right, so I'd recommend to not write it yourself.
Also, the flexible timezone handling with net.fortuna.ical4j.model.TimeZone which extends the standard java.util.TimeZone class and is backed by an icalendar...
2009-07-31 11:58:10 UTC in iCal4j
-
I created a workaround and noticed that one has to take care of this problem also when creating an ical4j DateTime object, since it will add the default timezone for floating times when formatting the value in Iso8601.toString().
Thus the workaround is:
a) reading from ical4j: date.getTime() + current default offset
b) creating ical4j objects: date.setTime(time - current default offset)
2009-07-10 14:22:54 UTC in iCal4j
-
Hi Ben,
if you import a floating time (ie. no UTC and no timezone given in the date property), ical4j will apply the JVM's default timezone for the DateTime object returned in eg. DateProperty.getDate(). This is correct if the "user" is represented by the application code accessing it and if the default timezone represents that user's current timezone (in which the floating time...
2009-07-10 12:37:11 UTC in iCal4j
