Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP

v0.8.8

Regenerate gemspec for version 0.8.8

v0.8.7

Regenerated gemspec for version 0.8.7

v0.8.6

Regenerated gemspec for version 0.8.6

v0.8.2

another attempt to trigger github to rebuild

v0.8.1

0.8.1 - 18 August 2009
  Fixes http://rick_denatale.lighthouseapp.com/projects/30941/tickets/21
        exception-when-count-option-used-to-enumerate-non-recurring-event

v0.8.0

0.8.0 - 11 August 2009 Minor Version Bump - There is a small potentia…
…lly breaking change see section on treatment of X-properties below

  * Unknown Components

  Starting with version 0.8.0 RiCal will parse calendars and components which contain nonstandard components.

  For example, there was a short-lived proposal to extend RFC2445 with a new VVENUE component which would hold structured information about the location of an event.  This proposal was never accepted and was withdrawn, but there is icalendar data in the wild which contains VVENUE components.

  Prior to version 0.8.0, RiCal would raise an exception if unknown component types were encountered.  Starting with version 0.8.0 RiCal will 'parse' such components and create instances of NonStandard component to represent them.  Since the actual format of unknown components is not known by RiCal, the NonStandard component will simply save the data lines between the BEGIN:xxx and END:xxx lines, (where xxx is the non-standard component name, e.g. VVENUE).  If the calendar is re-exported the original lines will be replayed.

  * Change to treatment of X-properties

  RFC2445 allows 'non-standard' or experimental properties which property-names beginning with X.  RiCal always supported parsing these.

  The standard properties are specified as to how many times they can occur within a particular component.  For singly occurring properties RiCal returns a single property object, while for properties which can occur multiple times RiCal returns an array of property objects.

  While implementing NonStandard properties, I realized that X-properties were being assumed to be singly occurring. But this isn't necessarily true.  So starting with 0.8.0 the X-properties are represented by an array of property objects.

  THIS MAY BREAK SOME APPLICATIONS, but the adaptation should be easy.

v0.7.6

Version 0.7.6
  - Fixes http://rick_denatale.lighthouseapp.com/projects/30941/tickets/20
    RiCal::PropertyValue::Period was returning a nil ruby value.

v0.7.5

Merge commit 'origin/master'
Something went wrong with that request. Please try again.