Free ical software for linux

Date::ICal is a Perl extension for ICalendar date objects.

SYNOPSIS

use Date::ICal;

$ical = Date::ICal->new( ical => 19971024T120000 );
$ical = Date::ICal->new( epoch => time );
$ical = Date::ICal->new( year => 1964,
month => 10, day => 16, hour => 16,
min => 12, sec => 47 );

$hour = $ical->hour;
$year = $ical->year;

$ical_string = $ical->ical;
$epoch_time = $ical->epoch;

$ical2 = $ical + $duration;
(Where $duration is either a duration string, like P2W3DT7H9M, or a Date::ICal::Duration (qv) object.
$ical += P6DT12H;

$duration = $ical1 - $ical2;
$ical3 = $ical1 - $duration;

iCal::Parser is a Perl module to parse iCalendar files into a data structure.

SYNOPSIS

use iCal::Parser

my $parser=iCal::Parser->new();
my $hash=$parser->parse($file);

$parser->parse($another_file);
my $combined=$parser->calendar;

my $combined=iCal::Parser->new->parse(@files);
my $combined=iCal::Parser->new->parse_files(@files);
my $combined=iCal::Parser->new->parse_strings(@strings);

This module processes iCalendar (vCalendar 2.0) files as specified in RFC 2445 into a data structure. It handles recurrences (RRULEs), exclusions (EXDATEs), event updates (events with a RECURRENCE-ID), and nested data structures (ATTENDEES and VALARMs). It currently ignores the VTIMEZONE, VJOURNAL and VFREEBUSY entry types.

The data structure returned is a hash like the following:

{
calendars=>[%cal, ...],
events=>{yyyy=>{mm=>{dd}=>{UID=>%event}}
todos=>[%todo, ...]
}

That is, it contains an array of calendar hashes, a hash of events key by year=>month=>day=>eventUID, and an array of todos.

Calendars, events and todos are "rolled up" version os the hashes returned from Text::vFile::asData, with dates replaced by DateTime objects.

During parsing, events in the input calendar are expanded out into multiple events, one per day covered by the event, as follows:
If the event is a one day "all day" event (in ical, the event is 24hrs long, starts at midnight on the day and ends a midnight of the next day), it contains no hour field and the allday field is set to 1.

If the event is a recurrence (RRULE), one event per day is created as per the RRULE specification.

If the event spans more than one day (the start and end dates are on different days, but does not contain an RRULE), it is expanded into multiple events, the first events end time is set to midnight, subsequent events are set to start at midnight and end at midnight the following day (same as an "allday" event, but the allday field is not set), and the last days event is set to run from midnight to the end time of the original multi-day event.

If the event is an update (it contains a RECURRENCE-ID), the original event is updated. If the referenced event does not exist (e.g., it was deleted after the update), then the event is added as a new event.
An example of each hash is below.

iCal::Parser::SAX is a Perl module to generate SAX events from an iCalendar.

SYNOPSIS

use iCal::Parser::SAX;
my $parser=iCal::Parser::SAX->new(Handler=>SAXHandler,%args);
$parser->parse_uri($file);
$parser->parse_uris(@files);

This module uses iCal::Parser to generates SAX events for the calendar contents.

The xml document generated is designed for creating monthly calendars with weeks beginning on monday (e.g., by passing the output through an xsl styleheet).

The basic structure of the generated document (if output through a simple output handler like XML::SAX::Writer), is as follows:

< ical>
< calendars>
< calendar id="cal-id" index="n" name="..." description="..."/>
< /calendars>
< events>
< year year="YYYY">
< month month="[1-12]">
< week week="n">
< day date="YYYY-MM-DD">
< event uid="event-id" idref="cal-id" [all-day="1"]>
< !-- ... -->
< /event>
< /day>
< /week>
< /month>
< /events>
< todos>
< todo idref="cal-id" uid="...">
< !--- ... -->
< /todo>
< /todos>
< /ical>

Along with basics, such as converting calendar attributes to lowercase elements (e.g., a DTSTART attribute in the input would generate a sax event like element({Name=dtstart})>), a number of other processes occur:

day elements are are generated for each date within the months from the first month in the input to the last, even if there are no calendar events on that day. This guarantees a complete calendar month for further processing. If there is an overlap between two or more events, the attribute conflict, containing the number of concurrent overlaps, is added to the element.

If the beginning or end of the month does not start on a monday, or end on a sunday, the days from the previous (next) month month are duplicated within the first (last) week of the current month, including duplicate copies of any calendar events occuring on those days. This allows for displaying a monthly calendar the same way a program such as Apples iCal would, with calendar events showing up if they fall within the overlapping days in the first or last week of a monthly calendar.

Data::ICal::Entry::Todo is a Perl module that represents a to-do entry in an iCalendar file.

SYNOPSIS

my $vtodo = Data::ICal::Entry::Todo->new();
$vtodo->add_properties(
summary => "go to sleep",
status => INCOMPLETE,
# Dat*e*::ICal is not a typo here
dtstart => Date::ICal->new( epoch => time )->ical,
);

$calendar->add_entry($vtodo);

$vtodo->add_entry($alarm);

A Data::ICal::Entry::Todo object represents a single to-do entry in an iCalendar file. (Note that the iCalendar RFC refers to entries as "components".) It is a subclass of Data::ICal::Entry and accepts all of its methods.

Java iCal Group Scheduler enables several users to get together for a meeting, by using JICAL to translate their iCalendar files into their available free/busy time and post it automatically to your Web server.

This project enables Ximian Evolution desktop users to book meetings with each other (and Outlook users) via a Web server storing their Free/Busy information as specified in RFC2445.

It works with Evolution, Korganiser, Apple iCal, and MS Outlook (for meetings), and enhances your workgroup and personal calendar views. Shell scripts for converting to various image formats are also included.

Data::ICal::Entry::TimeZone is a Perl module to represents a time zone definition in an iCalendar file.

SYNOPSIS

my $vtimezone = Data::ICal::Entry::TimeZone->new();
$vtimezone->add_properties(
tzid => "US-Eastern",
tzurl => "http://zones.stds_r_us.net/tz/US-Eastern"
);

$vtimezone->add_entry($daylight); # daylight/ standard not yet implemented
$vtimezone->add_entry($standard); # :-(

$calendar->add_entry($vtimezone);

A Data::ICal::Entry::TimeZone object represents the declaration of a time zone in an iCalendar file. (Note that the iCalendar RFC refers to entries as "components".) It is a subclass of Data::ICal::Entry and accepts all of its methods.

This module is not yet useful, because every time zone declaration needs to contain at least one STANDARD or DAYLIGHT component, and these have not yet been implemented.

Data::ICal::Entry::Alarm::Audio represents an audio alarm in an iCalendar file.

SYNOPSIS

my $valarm = Data::ICal::Entry::Alarm::Audio->new();
$valarm->add_properties(
attach => [ "ftp://host.com/pub/sounds/bell-01.aud", { fmttype => "audio/basic" } ],
# Dat*e*::ICal is not a typo here
trigger => [ Date::ICal->new( epoch => ... )->ical, { value => DATE-TIME } ],
);

$vevent->add_entry($valarm);

A Data::ICal::Entry::Alarm::Audio object represents an audio alarm attached to a todo item or event in an iCalendar file. (Note that the iCalendar RFC refers to entries as "components".) It is a subclass of Data::ICal::Entry and accepts all of its methods.