Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

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'

0_7_2

=== 0.7.2 - 6 July 2007
  updated to use newest versions of newgem and hoe, in order to make run-code-run work again

0_7_1

=== 0.7.1 - 6 July 2007
  * fixed http://rick_denatale.lighthouseapp.com/projects/30941/tickets/15
      duration validation issues
  * fixed http://rick_denatale.lighthouseapp.com/projects/30941/tickets/16
      event finish_time loses timezone info when event has a dtstart and duration

0_7_0

* fixed http://rick_denatale.lighthouseapp.com/projects/30941/tickets/14
    component without recurrence properties should enumerate just itself only if it is within the period between starting and before
* added the :overlapping option to OccurrenceEnumerator#occurrences - Allows the enumeration of occurrences which are either partiall or completely within a timespan given by a pair of Dates/Times/DateTimes
* Fixed some Ruby 1.9 incompatibilities
* Added some new rake tasks to run specs under multi-ruby

0_6_3

0.6.3 - 14 June 2009
 * Fixed http://rick_denatale.lighthouseapp.com/projects/30941-ri_cal/tickets/13
      tzinfotimezones-with-no-transitions-fail-on-export

0_6_2

0.6.2 - 11 June 2009
 * Fixed http://rick_denatale.lighthouseapp.com/projects/30941-ri_cal/tickets/12
      export-failure-for-unbounded-tzinfo-timezone

0_6_1

0.6.1 - 6 June 2009
 * Fixed problem with file which loads activesupport for the rake spec:with_activesupport task, it now
   requires >=2.2 instead of <=2.2 - Thanks to Paul Scott-Murphy for finding this.

0_6_0

=== 0.6.0 - 5 June 2009
 Time for a minor version bump.
 * Improved overall enumeration performance bypassing most of the effects of the poor performance of Ruby's DateTime class.
 * Added a framework for performance monitoring during development.
   - New performance directory with subdirs for code to be monitored for performance (subjects)
   - New script files:
        script/benchmark_subject runs a ruby benchmark on one performance subject
        script/profile_subject runs ruby-prof for a subject and puts a kcachegrind compatible calltree in the performance_data directory.
   - New rake tasks:
        performance:benchmark runs benchmarks against all subjects in the performance directory and produces a consolidated output file in performance_data/benchmarks.out
        performance:profile runs script/profile_subject against all subjects in the performance directory.

0_5_1

0.5.1 fix README to acknowledge release on RubyForge

0_5_0

version 0.5.0 rubyforge release candidate
Something went wrong with that request. Please try again.