similar to: ri_cal 0.7.0 Released

Hello all, I am currently evaluating the vpim libraries and like them very much. However there''s one thing I can''t get done: How can I set the TZID parameter for DTSTART/END dates so my encoded ICS file looks something like this: BEGIN:VEVENT ... DTSTART;TZID=Eastern Time:20071201T080000 DTEND;TZID=Eastern Time:20071207T110000 ... END:VEVENT I managed

I can not tell from the docs or from the mailing list what is the state of timezone support in the iCalendar package? If I want to parse an iCalendar file that has non utc dstarts and dends will it convert those times to UTC or otherwise allow me to do that? When I tried to parse an iCalendar input file started off with something like this: BEGIN:VCALENDAR METHOD:REQUEST

This is a follow-up to the thread ending with: http://rubyforge.org/pipermail/vpim-talk/2008/000120.html I too am in search of some ruby parser for icalendar which properly handles timezones on the datetimes in the icalendar RFC. As I understand it there are actually three types of times. 1) UTC times with a string form of yyyymmddThhmmssZ note the trailing Z indicates zulu time aka utc. 2)

I''ve discovered a strange behavior regarding ActiveRecord and TimeWithZone I''ve seen the error when using SQL Server, I have not yet tried with any other database. Here''s output from the console - "User" is a simple model made with a migration. ----------------------------------------- >> d1 = User.find(:first).created_at => Thu, 21 Jun 2001

Hello all, I''m trying to use the new ActiveSupport::TimeWithZone from Edge. The problem seems to be that I have a several-action process to create a Booking. This Booking is stored in the session (session[:booking] = @booking) throughout the actions until the last action is reached and the record is saved to the DB. Using TimeWithZone seems to be producing errors when trying to

Hey, I''ve noticed that I seem unable to get a _before_type_cast value for dates in 2.1. Specifically, if I assign a date string to a date attribute, and then call attribute_before_type_cast I get a TimeWithZone instead of a String: model.start_date = "2001/01/02" model.start_date.class = ActiveSupport::TimeWithZone model.start_date_before_type_cast.class =

My environment.rb contains config.time_zone = ''UTC'' If my understanding is correct, rails should assume time values coming from the database are UTC, and since config.time_zone is set to ''UTC'', it should not try to convert the times. Instead, rails is assuming that the db values are Eastern (my local zone) and is incorrectly adding four hours to convert to

Some code in my current project validates date time format using _before_type_cast method. But after adding "config.time_zone = "UTC" in environment.rb, we can''t get string raw values of some date time columns using _before_type_cast. for example, >> p = Person.new(:name => ''sean'', :birthday => ''1989-01-23'') >>

I''m looking at the docs for 1.0.2 and saw this example... # Now, you can make timezones like this cal = Calendar.new cal.timezone do timezone_id "America/Chicago" daylight do timezone_offset_from "-0600" timezone_offset_to "-0500" timezone_name "CDT" dtstart

R Developers, I cannot seem to find an R package that can read/write iCalendar (RFC2445) files. I have found the libical library at sourceforge. I've used it briefly so it may be what I need, but again no R interface. I may have to connect the dots myself. I'm guessing this might be useful for someone other than myself (scrubbing files, performing temporal analysis on events, etc).

Hello fellow Rail-builders, Is it possible to declare one class that includes two polymorphic fields as such: class Mark < ActiveRecord::Base # attribute: value, :string belongs_to :markable, polymorphic => true end class Property < ActiveRecord::Base has_one :name, :as => :markable has_one :value, :as => :markable end ? Based on what I know of the underlying

Hi All, Let say > df Session_Setup DCT FwdDataVols_bin counts 761 0 1 1 87162 762 0 1 2 11495 763 0 1 3 3986 764 0 1 4 1583 765 0 1 5 920 766 0 1 6 920 767 0 1

We''re using Vpim to parse iCal and vCard files, and so far it''s been great. However, when we were parsing some iCal files we noticed that all the endlines in the description section were disappearing. I start peering through the source code and find (in the Field#to_text method that is being called): # The value as text. Text can have escaped newlines, commas, and escape #

I have Time fields in my PostgreSQL tables, which I force to display as time only with this entry in config/locales/en.yml: time: formats: default: "%H:%M:%S" Problem is, that format is now applied to Timestamp fields, including the default created_at and updated_at fields. Why is it applying the Time (time only) format to a Timestamp (date + time) field, and how do I

Hello How can I test equality with two objects when they include some attribute that is BigDecimal? if I make something like this: it "should ...whatever" do obj = Factory.create(:my_object) ... MyObject.first.should == obj end. FAILS This fails because the object expected is different from the object gotten, and the only difference are the BigDecimal attributes, that are

There''s got to be an easier way... I am building an event manager and as part of it, the user selects the time zone of the event from a drop-down list using the time_zone_select helper. This is stored in the events table as a string. Because of legacy data which is stored in UTC, I want to keep the dates and times in the table as UTC but when I display it, I want to show the abbreviated

I''m running into the need (on at least one project now) to implement end-user-customizable "metadata" or properties on model objects. The standard example would be a Person class that had first_name, last_name, etc. but would need to be extended real-time (through the web admin interface) with properties such as phone_number : varchar (30). I''ve done some basic

Hello All, I''m happy to announce the next stable release of Foreman, main new features include: - Integration of Puppet Reports, once enabled you would see a real time overview of all of yours hosts status. - Improved support for multiple Puppet Masters (e.g. import facts and reports from remote serves over http) - Simplified migration from existing external nodes setup,

I have isolated what appears to be a bug in the Rails extensions to DateTime, but I don''t know where to report it. I have a standalone file to demonstrate the bug, but the punch line is that this code: TestRecord.create!(:f_datetime => (expected = DateTime.jd(2000000))) found = TestRecord.first.f_datetime puts("expected == found => #{expected == found}")