Fixed 2 memory leaks
More code cleanup
Fixed an animation bug.

-[UIView setAnimationsEnabled:] is *not* scoped to the UIView animation transaction. So if you turn off animations, make sure you turn them back on immediately after the animation is triggered.
KalViewController's designated initializer is now 'init'. HolidaysDemo now shows how to push a details view controller when the user taps a holiday listed below the calendar.
New feature: show and select arbitrary dates

1) When creating a KalViewController, you can now specify the initial selected date (before it always just displayed and selected today's date)
2) You can now send a message to KalViewController to show and select an arbitrary date (before you could only tell it to show today's date).
Renamed the '*IfVisible' methods and added an assertion that the date's corresponding tile can actually be found (i.e. it is visible)
Updated the README
Updated project file to build with iOS 4.0 SDK
Significant changes to how Kal is built.

- Refactored the project structure into 2 Xcode projects: one that builds the static library and one that builds an example app using Kal.
- Switched over to the iOS 4.0 SDK (in preparation for EventKit demo and Retina Display support).
Added EventKit example
Added support for the KalDataSource to notify Kal that the UI needs to be refreshed. Added EKEventStoreChangedNotification handling to NativeCal example app.
Added hi-res graphics for iPhone4 Retina Display support. Thanks Paul Calnan.
Updated README. Please read.
Updated EventKit example app to asynchronously fetch events from the EKEventStore using a GCD queue.
CRITICAL BUG FIX: today's date and iOS 4.0 multitasking.

Root cause: If an application using Kal is suspended in the background for an extended period of time (specifically, crossing the midnight threshold), when the app is resumed, Kal will still think that "today" has not changed. In my original implementation, I had naively assumed that the app would never be used for such an extended period of time, but iOS 4.0 multitasking makes my assumption invalid.

Solution: Listen for the UIApplicationSignificantTimeChangeNotification from the OS and respond appropriately by recaching today's date and refreshing the UI.
Follow-up to f2f9ff84: now redraws the current month if a significant time change occurred.
Follow-up to follow-up to f2f9ff84: Uggh. Ok, I think this is the final part to the bugfix. I wish I would have tested this sooner on the real device.
Fixed bug in calendar month header where month name was incorrectly displayed for languages such as Russian which have a separate stand-alone form of the month name.
Bugfix for Issue #7: 'Adjacent' days, when selected, the gray fill is not filled correctly.
Updated projects to use iOS 4.1 as the Base SDK