This repository is private.
All pages are served over SSL and all pushing and pulling is done over SSH.
No one may fork, clone, or view it unless they are added as a member.
Every repository with this icon (
) is private.
Every repository with this icon (
This repository is public.
Anyone may fork, clone, or view it.
Every repository with this icon (
) is public.
Every repository with this icon (
| name | age | message | |
|---|---|---|---|
| |
README | Thu Jun 12 22:16:31 -0700 2008 | [dball] |
| |
Rakefile | Thu Jun 05 16:24:04 -0700 2008 | [dball] |
| |
app/ | Fri Jun 13 14:15:49 -0700 2008 | [dball] |
| |
config/ | Thu Jun 12 21:58:24 -0700 2008 | [dball] |
| |
db/ | Thu Jun 05 16:30:31 -0700 2008 | [dball] |
| |
doc/ | Thu Jun 05 21:24:05 -0700 2008 | [dball] |
| |
lib/ | Thu Jun 12 21:58:24 -0700 2008 | [dball] |
| |
public/ | Thu Jun 05 21:24:05 -0700 2008 | [dball] |
| |
script/ | Thu Jun 05 21:24:05 -0700 2008 | [dball] |
| |
test/ | Fri Jun 13 15:03:30 -0700 2008 | [dball] |
| |
vendor/ | Thu Jun 12 21:38:37 -0700 2008 | [dball] |
README
== Acts As Calendar This rails plugin aims to provide support for calendar events, both discrete and recurring. The goal is to be able to attach a calendar to any model object, and to attach calendar events to any of that object's children or possibly descendents. The calendar data should be publishable in ical format, and possibly editable from as well, to the extent that the data model allows. Events may occur on specific dates, recur monthly on a given day (the 15th), a given day of a given week (1st Thursday, Last Saturday), or a given weekday (Every Friday), or any combination of the above. Recurring events are stored as patterns in the database, and are joined against a table of dates, decomposed into parts, into a view of event instances. This has the advantages of being easy and efficient to query, and of bypassing the typically non-standard database date functions. The disadvantage, of course, is that it requires a table of all potential dates against which to join. That being said, a century's worth of date data should only be a few hundred kilobytes, not large by today's standards. The limiting factor at the moment is in initially populating these data, it's fairly slow with ActiveRecord.




