rubyredrick-ri_cal 0.0.2 → 0.0.3

data/History.txt

@@ -1,3 +1,20 @@
-== 0.0.1 / 2009-4/26
+=== 0.0.3
+ * Added tzid method to Ruby Time and DateTime instances, and to ActiveRecord::TimeWithZone if it is defined this method is used to determine the desired
+timezone when an instance of one of these classes is given as the value of a datetime property.  If the tzid is nil then the default tzid is used,
+if it is set to :floating then the property will be a floating time.
+ * Removed the ability to pass an array with a tzid string and a date-time since the above made it unnecessary
+ * The ruby datetime property returned from the ruby_value method on the DateTime property will return an instance of ::DateTime with:
+   ** The proper utc offset
+   ** The tzid set to the right tzid
+ * Made exdate/rdate building possible
+ * Added a default_tzid attribute to the Calendar component, if this attribute is not set for a particular calendar it will delegate to the default set 
+for the DateTime property class.
+ * Added fix patches from
+   ** http://github.com/kjwierenga/ri_cal
+   ** http://github.com/wesmaldonado/ri_cal
 
-* Initial public release
+=== 0.0.2
+ * Fixed gemspec
+== 0.0.1
+
+ * Initial public release

data/Manifest.txt

@@ -36,7 +36,6 @@ lib/ri_cal/core_extensions/array/conversions.rb
 lib/ri_cal/core_extensions/date.rb
 lib/ri_cal/core_extensions/date/conversions.rb
 lib/ri_cal/core_extensions/date_time.rb
-lib/ri_cal/core_extensions/date_time/conversions.rb
 lib/ri_cal/core_extensions/object.rb
 lib/ri_cal/core_extensions/object/conversions.rb
 lib/ri_cal/core_extensions/string.rb
@@ -44,7 +43,10 @@ lib/ri_cal/core_extensions/string/conversions.rb
 lib/ri_cal/core_extensions/time.rb
 lib/ri_cal/core_extensions/time/calculations.rb
 lib/ri_cal/core_extensions/time/conversions.rb
+lib/ri_cal/core_extensions/time/tzid_access.rb
 lib/ri_cal/core_extensions/time/week_day_predicates.rb
+lib/ri_cal/floating_timezone.rb
+lib/ri_cal/invalid_property_value.rb
 lib/ri_cal/invalid_timezone_identifer.rb
 lib/ri_cal/occurrence_enumerator.rb
 lib/ri_cal/parser.rb
@@ -85,7 +87,6 @@ lib/ri_cal/property_value/text.rb
 lib/ri_cal/property_value/uri.rb
 lib/ri_cal/property_value/utc_offset.rb
 lib/ri_cal/required_timezones.rb
-lib/ri_cal/time_with_floating_timezone.rb
 ri_cal.gemspec
 sample_ical_files/from_ical_dot_app/test1.ics
 script/console
@@ -101,6 +102,7 @@ spec/ri_cal/component/t_z_info_timezone_spec.rb
 spec/ri_cal/component/timezone_spec.rb
 spec/ri_cal/component/todo_spec.rb
 spec/ri_cal/component_spec.rb
+spec/ri_cal/core_extensions/string/conversions_spec.rb
 spec/ri_cal/core_extensions/time/calculations_spec.rb
 spec/ri_cal/core_extensions/time/week_day_predicates_spec.rb
 spec/ri_cal/occurrence_enumerator_spec.rb
@@ -108,6 +110,7 @@ spec/ri_cal/parser_spec.rb
 spec/ri_cal/property_value/date_spec.rb
 spec/ri_cal/property_value/date_time_spec.rb
 spec/ri_cal/property_value/duration_spec.rb
+spec/ri_cal/property_value/occurrence_list_spec.rb
 spec/ri_cal/property_value/period_spec.rb
 spec/ri_cal/property_value/recurrence_rule/recurring_year_day_spec.rb
 spec/ri_cal/property_value/recurrence_rule_spec.rb
@@ -119,4 +122,4 @@ spec/ri_cal_spec.rb
 spec/spec.opts
 spec/spec_helper.rb
 tasks/ri_cal.rake
-tasks/spec.rake
+tasks/spec.rake

data/README.txt

@@ -14,6 +14,8 @@ but do not support important things like enumerating occurrences of repeating ev
 
 This is a clean-slate implementation of RFC2445.
 
+A Google group for discussion of this library has been set up http://groups.google.com/group/rical_gem
+
 == FEATURES/PROBLEMS:
 
 * All examples of recurring events in RFC 2445 are handled. RSpec examples are provided for them. 
@@ -22,17 +24,18 @@ This is a clean-slate implementation of RFC2445.
 
 === Components and properties
 
-An iCalendar calendar comprises subcomponents like Events, Timezones and Todos.  Each component may have
-properties, for example an event has a dtstart property which defines the time (and date) on which the event
-starts.
+An iCalendar calendar comprises subcomponents like Events, Timezones and Todos. Each component may
+have properties, for example an event has a dtstart property which defines the time (and date) on
+which the event starts.
 
-RiCal components will provide reasonable ruby objects as the values of these properties, and allow the properties
-to be set to ruby objects which are reasonable for the particular property.  For example time properties like dtstart
-can be set to a ruby Time, DateTime or Date object, and will return a DateTime or Date object when queried.
+RiCal components will provide reasonable ruby objects as the values of these properties, and allow
+the properties to be set to ruby objects which are reasonable for the particular property. For
+example time properties like dtstart can be set to a ruby Time, DateTime or Date object, and will
+return a DateTime or Date object when queried.
 
-The methods for accessing the properties of each type of component are defined in a module with the same name
-as the component class in the RiCal::properties module.  For example the property accessing methods for 
-RiCal::Component::Event are defined in RiCal::Properties::Event
+The methods for accessing the properties of each type of component are defined in a module with the
+same name as the component class in the RiCal::properties module. For example the property
+accessing methods for RiCal::Component::Event are defined in RiCal::Properties::Event
 
 === Creating Calendars and Calendar Components
 
@@ -51,12 +54,14 @@ RiCal provides a builder DSL for creating calendars and calendar components. An
     end
   end
   
-This style is for compatibility with the iCalendar and vpim to ease migration.  The downside is that the block is evaluated
-in the context of a different object which cause surprising if the block contains direct instance variable references or
-implicit references to self.  Note that, in this style, one must use 'declarative' method calls like dtstart to set values
-rather than more natural attribute writer methods, like dtstart=
+This style is for compatibility with the iCalendar and vpim to ease migration. The downside is that
+the block is evaluated in the context of a different object which can cause surprises if the block
+contains direct instance variable references or implicit references to self. Note that, in this
+style, one must use 'declarative' method calls like dtstart to set values rather than more natural
+attribute writer methods, like dtstart=
   
-Alternatively you can pass a block with a single argument, in this case the component being built will be passed as that argument
+Alternatively you can pass a block with a single argument, in this case the component being built
+will be passed as that argument
 
   RiCal.Calendar do |cal|
     cal.event do |event|
@@ -71,64 +76,145 @@ Alternatively you can pass a block with a single argument, in this case the comp
     end
   end
 
-As the example shows, the two styles can be mixed, the inner block which builds the alarm uses the first style.
+As the example shows, the two styles can be mixed, the inner block which builds the alarm uses the
+first style.
   
-The blocks are evaluated in the context of an object which builds the calendar or calendar component. method names
-starting with add_ or remove_ are sent to the component, method names which correspond to a property value setter of
-the object being built will cause that setter to be sent to the component with the provided value.
+The blocks are evaluated in the context of an object which builds the calendar or calendar
+component. method names starting with add_ or remove_ are sent to the component, method names which
+correspond to a property value setter of the object being built will cause that setter to be sent
+to the component with the provided value.
+
+A method corresponding to the name of one of the components sub component will create the sub
+component and evaluate a block if given in the context of the new subcomponent.
+
+==== Multiply occurring properties
 
-A method corresponding to the name of one of the components sub component will create the sub component and 
-evaluate the block in the context of the new subcomponent.
+Certain RFC Components have properties which may be specified multiple times, for example, an Event
+may have zero or more comment properties, A component will have a family of methods for
+building/manipulating such a property, e.g.
 
-=== Times, Time zones, and Floating Times
+Event#comment::         will return an array of comment strings.
+Event#comment=::        takes a single comment string and gives the event a single comment property, 
+                        replacing any existing comment property collection.
+Event#comments=::       takes multiple comment string arguments and gives the event a comment property for each,
+                        replacing any existing comment property collection.
+Event#add_comment::     takes a single comment string argument and adds a comment property.
+Event#add_comments::    takes multiple comment string arguments and adds a comment property for each.
+Event#remove_comment::  takes a single comment string argument and removes an existing comment property with that value.
+Event#remove_comments:: takes multiple comment string argument and removes an existing comment property with that value.
+
+
+==== Times, Time zones, and Floating Times
 
 RFC2445 describes three different kinds of DATE-TIME values with respect to time zones:
 
-  1. date-times with a local time. These have no actual time zone, instead they are to be interpreted in the local time zone of the viewer.  These floating times are used for things like the New Years celebration which is observed at local midnight whether you happen to be in Paris, London, or New York.
+  1. date-times with a local time. These have no actual time zone, instead they are to be 
+     interpreted in the local time zone of the viewer.  These floating times are used for things 
+     like the New Years celebration which is observed at local midnight whether you happen to be
+     in Paris, London, or New York.
 
-  2. date-times with UTC time.  An application would either display these with an indication of the time zone, or convert them to the viewer's time zone, perhaps depending on user settings.
+  2. date-times with UTC time.  An application would either display these with an indication of 
+     the time zone, or convert them to the viewer's time zone, perhaps depending on user settings.
 
   3. date-times with a specified time zone.
 
 RiCal can be given ruby Time, DateTime, or Date objects for the value of properties requiring an 
-iCalendar DATE-TIME value. It can also be given a two element array where the first element is a Time or DateTime,
-and the second is a string representation of the time zone identifier.
+iCalendar DATE-TIME value.  It can also be given a string
+
+Note that a date only DATE-TIME value has no time zone by definition, effectively such values float
+and describe a date as viewed by the user in his/her local time zone.
 
-Note that a date only DATE-TIME value has no time zone by definition, effectively such values float and describe
-a date as viewed by the user in his/her local time zone.
+When a Ruby Time or DateTime instance is used to set properties with with a DATE-TIME value, it
+needs to determine which of the three types it represents. RiCal is designed to make use of the
+TimeWithZone support which has been part of the ActiveSupport component of Ruby on Rails since
+Rails 2.2. However it's been carefully designed not to require Rails or ActiveSupport, but to
+dynamically detect the presence of the TimeWithZone support.
 
-When a Ruby Time or DateTime instance is used to set properties with with a DATE-TIME value, it needs to determine
-which of the three types it represents.  RiCal is designed to make use of the TimeWithZone support which has been
-part of the ActiveSupport component of Ruby on Rails since Rails 2.2. However it's been carefully designed not
-to require Rails or ActiveSupport, but to dynamically detect the presence of the TimeWithZone support.
+RiCal adds accessor methods for a tzid attribute to the Ruby Time, and DateTime classes as well as
+a set_tzid method which sets the tzid attribute and returns the receiver for convenience in
+building calendars. If ActiveSupport::TimeWithZone is defined, a tzid instance method is defined
+which returns the identifier of the time zone.
 
 When the value of a DATE-TIME property is set to a value, the following processing occurs:
 
-* If the object responds to both the :acts_as_time, and :timezone methods then the result of the timezone method (assumed to be an instance of TZInfoTimezone) is used as a specific local time zone.
+  * If the value is a string, then it must be a valid rfc 2445 date or datetime string optionally
+    preceded by a parameter specification e.g
+  
+    "20010911"  will be interpreted as a date
+  
+    "20090530T123000Z"  will be interpreted as the time May 30, 2009 at 12:30:00 UTC
+  
+    "20090530T123000"  will be interpreted as the time May 30, 2009 with a floating time zone
+  
+    "TZID=America/New_York:20090530T123000"  will be interpreted as the time May 30, 2009 in the time zone identified by "America/New_York"
+  
+  * If the value is a Date it will be interpreted as that date
+  * If the value is a Time, DateTime, or TimeWithZone then the tzid attribute will determine the
+    time zone. If tzid returns nil then the default tzid will be used.
+  
+==== Default TZID
+
+The PropertyValue::DateTime class has a default_tzid attribute which is initialized to "UTC".
 
-* If not then the default time zone id is used.  The normal default timezone id is "UTC". You can set the default by calling ::RiCal::PropertyValue::DateTime.default_tzid = timezone_identifier, where timezone_identifier isa string, or nil.  If you set the default tzid to 'none' or :none, then Times or DateTimes without timezones will be treated as floating times.
+The Component::Calendar class also has a default_tzid attribute, which may be set, but if it is not
+set the default_tzid of the PropertyValue::DateTime class will be used.
 
-Note it is likely that in a future version of RiCal that the default timezone will be set on a Calendar by Calendar
-basis rather than on the DateTime property class.
+To set the interpreting of Times and DateTimes which have no tzid as floating times, set the
+default_tzid for Component::Calendar and/or PropertyValue::DateTime to :floating.
 
-Also note that time zone identifiers are not standardized by RFC 2445. For an RiCal originated calendar
-time zone identifiers recognized by the TZInfo gem, or the TZInfo implementation provided by ActiveSupport as the case
-may be may be used.  The valid time zone identifiers for a non-RiCal generated calendar imported into RiCalendar
-are determined by the VTIMEZONE compoents within the imported calendar.
+Also note that time zone identifiers are not standardized by RFC 2445. For an RiCal originated
+calendar time zone identifiers recognized by the TZInfo gem, or the TZInfo implementation provided
+by ActiveSupport as the case may be may be used. The valid time zone identifiers for a non-RiCal
+generated calendar imported into RiCalendar are determined by the VTIMEZONE compoents within the
+imported calendar.
 
-If you use a timezone identifer within a calendar which is not defined within the calendar it will detected at the time
-you try to convert a timezone. In this case an InvalidTimezoneIdentifier error will be raised by the conversion method.
+If you use a timezone identifer within a calendar which is not defined within the calendar it will
+detected at the time you try to convert a timezone. In this case an InvalidTimezoneIdentifier error
+will be raised by the conversion method.
 
-To explicitly set a floating time you can use the method #with_floating_timezone on Time or DateTime instances as in
+To explicitly set a floating time you can use the method #with_floating_timezone on Time or
+DateTime instances as in
 
    event.dtstart = Time.parse("1/1/2010 00:00:00").with_floating_timezone
+   
+or the equivalent
+
+event.dtstart = Time.parse("1/1/2010 00:00:00").set_tzid(:floating)
+
+==== RDATE, and EXDATE properties (Occurrence Lists)
+
+A calendar component which supports recurrence properties (e.g. Event) may have zero or more RDATE
+and or EXDATE properties. Each RDATE/EXDATE property in turn specifies one or more occurrences to
+be either added to or removed from the component's recurrence list. Each element of the list may be
+either a DATE, a DATETIME, or a PERIOD, or the RFC 2445 string representation of one of these:
+
+  event.rdate = "20090305"
+  event.rdate = "20090305T120000"
+  event.rdate = "20090305T120000/P1H30M"
+  
+It can also have multiple occurrences, specified as multiple parameters:
+
+  event.rdate = "20090305T120000", "20090405T120000"
+  event.rdate = DateTime.parse("12 December, 2005 3:00 pm"), DateTime.civil(2001, 3, 4, 15, 30, 0)
+  
+
+Multiple string values can be combined separated by commas:
+
+   event.rdate = "20090305T120000,20090405T120000"
+
 
+An occurrence list has one set of parameters, so only one timezone can be used, the timezone may
+be set explicitly via the first argument.  If the first argument is a string, it is first split on
+commas. Then if the first segment (up to the first comma if any) is not a valid RFC 2445
+representation of a DATE, DATETIME, or PERIOD, then it will be used as the timezone for the
+occurrence list. Otherwise the arguments must have the same time zone or an InvalidPropertyValue
+error will be raised.
 === Parsing
 
 RiCal can parse icalendar data from either a string or a Ruby io object.
 
-The data may consist of one or more icalendar calendars, or one or more icalendar components (e.g. one or more 
-VEVENT, or VTODO objects.)
+The data may consist of one or more icalendar calendars, or one or more icalendar components (e.g.
+one or more VEVENT, or VTODO objects.)
 
 In either case the result will be an array of components.
 ==== From a string

data/Rakefile

@@ -1,7 +1,7 @@
 #- ©2009 Rick DeNatale
 #- All rights reserved. Refer to the file README.txt for the license
 #
-%w[rubygems rake rake/clean fileutils newgem rubigen].each { |f| require f }
+%w[rubygems rake rake/clean fileutils newgem].each { |f| require f }
 require File.dirname(__FILE__) + '/lib/ri_cal'
 
 # Generate all the Rake tasks

data/copyrights.txt

@@ -1,2 +1 @@
-©2009 Rick DeNatale
-All rights reserved. Refer to the file README.txt for the license
+©2009 Rick DeNatale, All rights reserved. Refer to the file README.txt for the license

data/lib/ri_cal/component/alarm.rb

@@ -3,8 +3,7 @@ require File.join(File.dirname(__FILE__), %w[.. properties alarm.rb])
 module RiCal
 
   class Component
-    #- ©2009 Rick DeNatale
-    #- All rights reserved. Refer to the file README.txt for the license
+    #- ©2009 Rick DeNatale, All rights reserved. Refer to the file README.txt for the license
     #
     # An Alarm component groups properties defining a reminder or alarm associated with an event or to-do
     # TODO: The Alarm component has complex cardinality restrictions depending on the value of the action property

data/lib/ri_cal/component/calendar.rb

@@ -2,8 +2,7 @@ require File.join(File.dirname(__FILE__), %w[.. properties calendar.rb])
 
 module RiCal
   class Component
-    #- ©2009 Rick DeNatale
-    #- All rights reserved. Refer to the file README.txt for the license
+    #- ©2009 Rick DeNatale, All rights reserved. Refer to the file README.txt for the license
     #
     # to see the property accessing methods for this class see the RiCal::Properties::Calendar module
     class Calendar < Component
@@ -51,6 +50,17 @@ module RiCal
         result
       end
 
+      # Return the default time zone identifier for this calendar
+      def default_tzid
+        @default_tzid || PropertyValue::DateTime.default_tzid
+      end
+
+      # Set the default time zone identifier for this calendar
+      # To set the default to floating times use a value of :floating
+      def default_tzid=(value)
+        @default_tzid=value
+      end
+
       # return an array of event components contained within this Calendar
       def events
         subcomponents["VEVENT"]
@@ -77,7 +87,7 @@ module RiCal
         subcomponents["VFREEBUSY"]
       end
 
-      class TimezoneID
+      class TimezoneID #:nodoc:
         attr_reader :identifier, :calendar
         def initialize(identifier, calendar)
           self.identifier, self.calendar = identifier, calendar
@@ -100,29 +110,35 @@ module RiCal
       def timezones
         subcomponents["VTIMEZONE"]
       end
-      
+
       class TZInfoWrapper #:nodoc:
         attr_reader :tzinfo, :calendar #:nodoc:
         def initialize(tzinfo, calendar) #:nodoc:
           @tzinfo = tzinfo
           @calendar = calendar
         end
-        
+
         def identifier #:nodoc:
           tzinfo.identifier
         end
-        
+
         def date_time(ruby_time, tzid) #:nodoc:
           RiCal::PropertyValue::DateTime.new(calendar, :value => ruby_time, :params => {'TZID' => tzid})
         end
-        
+
         def local_to_utc(utc) #:nodoc:
           date_time(tzinfo.local_to_utc(utc.to_ri_cal_ruby_value), 'UTC')
         end
-        
+
         def utc_to_local(local) #:nodoc:
           date_time(tzinfo.utc_to_local(local.to_ri_cal_ruby_value), tzinfo.identifier)
         end
+
+
+        def rational_utc_offset(local)
+          Rational(tzinfo.period_for_local(local, true).utc_offset, 3600) / 24
+        end
+
       end
 
       def find_timezone(identifier)  #:nodoc:
@@ -135,7 +151,7 @@ module RiCal
         else
           result = timezones.find {|tz| tz.tzid == identifier}
           raise RiCal::InvalidTimezoneIdentifier.not_found_in_calendar(identifier) unless result
-          result  
+          result
         end
       end
 

data/lib/ri_cal/component/event.rb

@@ -2,8 +2,7 @@ require File.join(File.dirname(__FILE__), %w[.. properties event.rb])
 
 module RiCal
   class Component
-    #- ©2009 Rick DeNatale
-    #- All rights reserved. Refer to the file README.txt for the license
+    #- ©2009 Rick DeNatale, All rights reserved. Refer to the file README.txt for the license
     #
     # An Event (VEVENT) calendar component groups properties describing a scheduled event.
     # Events may have multiple occurrences

data/lib/ri_cal/component/freebusy.rb

@@ -2,8 +2,7 @@ require File.join(File.dirname(__FILE__), %w[.. properties freebusy.rb])
 
 module RiCal
   class Component
-    #- ©2009 Rick DeNatale
-    #- All rights reserved. Refer to the file README.txt for the license
+    #- ©2009 Rick DeNatale, All rights reserved. Refer to the file README.txt for the license
     #
     #  A Freebusy (VFREEBUSY) calendar component groups properties describing either a request for free/busy time,
     #  a response to a request for free/busy time, or a published set of busy time.

data/lib/ri_cal/component/journal.rb

@@ -3,8 +3,7 @@ require File.join(File.dirname(__FILE__), %w[.. properties journal.rb])
 
 module RiCal
   class Component
-    #- ©2009 Rick DeNatale
-    #- All rights reserved. Refer to the file README.txt for the license
+    #- ©2009 Rick DeNatale, All rights reserved. Refer to the file README.txt for the license
     #
     #  A Journal (VJOURNAL) calendar component groups properties describing a journal entry.
     #  Journals may have multiple occurrences

data/lib/ri_cal/component/t_z_info_timezone.rb

@@ -1,5 +1,4 @@
-#- ©2009 Rick DeNatale
-#- All rights reserved. Refer to the file README.txt for the license
+#- ©2009 Rick DeNatale, All rights reserved. Refer to the file README.txt for the license
 #
 # A wrapper class for a Timezone implemented by the TZInfo Gem
 # (or by Rails)

data/lib/ri_cal/component/timezone/daylight_period.rb

@@ -1,8 +1,7 @@
 module RiCal
   class Component
     class Timezone
-      #- ©2009 Rick DeNatale
-      #- All rights reserved. Refer to the file README.txt for the license
+      #- ©2009 Rick DeNatale, All rights reserved. Refer to the file README.txt for the license
       #
       # A DaylightPeriod is a TimezonePeriod during which daylight saving time *is* in effect
       class DaylightPeriod < TimezonePeriod #:nodoc: all

data/lib/ri_cal/component/timezone/standard_period.rb

@@ -1,8 +1,7 @@
 module RiCal
   class Component
     class Timezone
-      #- ©2009 Rick DeNatale
-      #- All rights reserved. Refer to the file README.txt for the license
+      #- ©2009 Rick DeNatale, All rights reserved. Refer to the file README.txt for the license
       #
       # A StandardPeriod is a TimezonePeriod during which daylight saving time is *not* in effect
       class StandardPeriod < TimezonePeriod #:nodoc: all

data/lib/ri_cal/component/timezone/timezone_period.rb

@@ -3,8 +3,7 @@ require File.join(File.dirname(__FILE__), %w[.. .. properties timezone_period.rb
 module RiCal
   class Component
     class Timezone
-      #- ©2009 Rick DeNatale
-      #- All rights reserved. Refer to the file README.txt for the license
+      #- ©2009 Rick DeNatale, All rights reserved. Refer to the file README.txt for the license
       #
       # A TimezonePeriod is a component of a timezone representing a period during which a particular offset from UTC is
       # in effect.

data/lib/ri_cal/component/timezone.rb

@@ -2,8 +2,7 @@ require File.join(File.dirname(__FILE__), %w[.. properties timezone.rb])
 
 module RiCal
   class Component
-    #- ©2009 Rick DeNatale
-    #- All rights reserved. Refer to the file README.txt for the license
+    #- ©2009 Rick DeNatale, All rights reserved. Refer to the file README.txt for the license
     #
     # An Timezone (VTIMEZONE) calendar component describes a timezone used within the calendar.
     # A Timezone has two or more TimezonePeriod subcomponents which describe the transitions between
@@ -23,6 +22,10 @@ module RiCal
           # Don't use alias, as identifier gets overridden.
           identifier
         end
+        
+        def rational_utc_offset(local) #:nodoc:
+          Rational(period_for_local(local, true).utc_offset, 3600) / 24
+        end
 
         # Returns the TimezonePeriod for the given UTC time. utc can either be a DateTime,
         # Time or integer timestamp (Time.to_i). Any timezone information in utc is ignored (it is treated as a UTC time).

data/lib/ri_cal/component.rb

@@ -1,8 +1,7 @@
 module RiCal
-  #- ©2009 Rick DeNatale
-  #- All rights reserved. Refer to the file README.txt for the license
+  #- ©2009 Rick DeNatale, All rights reserved. Refer to the file README.txt for the license
   #
-  class Component    
+  class Component #:nodoc:
     class ComponentBuilder #:nodoc:
       def initialize(component)
         @component = component
@@ -46,11 +45,27 @@ module RiCal
       end
     end
     
-    def find_timezone(identifier) #:nodoc:
-      @parent.find_timezone(identifier)
+    def default_tzid #:nodoc:
+      if @parent
+        @parent.default_tzid
+      else
+        PropertyValue::DateTime.default_tzid
+      end
     end
     
-    def time_zone_for(ruby_object)
+    def find_timezone(identifier) #:nodoc:
+      if @parent
+        @parent.find_timezone(identifier)
+      else
+        begin
+          Calendar::TZInfoWrapper.new(TZInfo::Timezone.get(identifier), self)
+        rescue ::TZInfo::InvalidTimezoneIdentifier => ex
+          raise RiCal::InvalidTimezoneIdentifier.invalid_tzinfo_identifier(identifier)
+        end
+      end
+    end
+
+    def time_zone_for(ruby_object) #:nodoc:
       @parent.time_zone_for(ruby_object) #:nodoc:
     end
     
@@ -127,7 +142,7 @@ module RiCal
       x_properties[name] = prop
     end
     
-    def method_missing(selector, *args, &b)
+    def method_missing(selector, *args, &b) #:nodoc:
       xprop_candidate = selector.to_s
       if (match = /^x_(.+)(=?)$/.match(xprop_candidate))
         if match[2] == "="

data/lib/ri_cal/core_extensions/date/conversions.rb

@@ -4,22 +4,23 @@ module RiCal
       #- ©2009 Rick DeNatale
       #- All rights reserved. Refer to the file README.txt for the license
       #
-      module Conversions
+      module Conversions #:nodoc:
         # Return an RiCal::PropertyValue::DateTime representing the receiver
-        def to_ri_cal_date_time_value
-          RiCal::PropertyValue::DateTime.new(nil, :value => self)
+        def to_ri_cal_date_time_value(timezone_finder = nil)
+          RiCal::PropertyValue::DateTime.new(timezone_finder, :value => self)
         end
         
         # Return an RiCal::PropertyValue::Date representing the receiver
-        def to_ri_cal_date_value
-          RiCal::PropertyValue::Date.new(nil, :value => self)
+        def to_ri_cal_date_value(timezone_finder = nil)
+          RiCal::PropertyValue::Date.new(timezone_finder, :value => self)
         end
 
         alias_method :to_ri_cal_date_or_date_time_value, :to_ri_cal_date_value
+        alias_method :to_ri_cal_occurrence_list_value, :to_ri_cal_date_value
         
         # Return the natural ri_cal_property for this object
-        def to_ri_cal_property_value
-          to_ri_cal_date_value
+        def to_ri_cal_property_value(timezone_finder = nil)
+          to_ri_cal_date_value(timezone_finder)
         end
       end
     end

data/lib/ri_cal/core_extensions/date_time.rb

@@ -1,4 +1,5 @@
-require "#{File.dirname(__FILE__)}/date_time/conversions.rb"
+require "#{File.dirname(__FILE__)}/time/conversions.rb"
+require "#{File.dirname(__FILE__)}/time/tzid_access.rb"
 require "#{File.dirname(__FILE__)}/time/week_day_predicates.rb"
 require "#{File.dirname(__FILE__)}/time/calculations.rb"
 require 'date'
@@ -9,5 +10,6 @@ class DateTime #:nodoc:
   #
   include RiCal::CoreExtensions::Time::WeekDayPredicates
   include RiCal::CoreExtensions::Time::Calculations
-  include RiCal::CoreExtensions::DateTime::Conversions
+  include RiCal::CoreExtensions::Time::TzidAccess
+  include RiCal::CoreExtensions::Time::Conversions
 end

data/lib/ri_cal/core_extensions/object/conversions.rb

@@ -4,7 +4,7 @@ module RiCal
       #- ©2009 Rick DeNatale
       #- All rights reserved. Refer to the file README.txt for the license
       #
-      module Conversions
+      module Conversions #:nodoc:
         # Used to format rfc2445 output for RiCal
         def to_rfc2445_string
           to_s