Updated gitignore

Now user files are ignored
Updated for iOS 6

Now the app correctly asks for permission to use the calendar database.

There are some other changes in here regarding caching. Since this is an older project, the exact nature of this code is forgotten. In the future, a project should not be put on hold mid commit.
Added 4 inch launch image

This will allow the app to use the larger iPhone 5 screen.
Changed event retrieval system

Now events are requested by year, and cached by day.
Changed month background to image

This caused a noticeable improvement in performance.
Made _firstDayOffset more efficient

Rather than creating an extra NSDate, we assume the month property is the first day of the month.
Added calendarDate caching
Updated numberOfDaysInWeek to fire once

This should never change significantly.
Made massive performance improvements

While no where near what it needs to be, scrolling is a bit smoother after countless improvements.
Moved background drawing to drawRect

"Holy shit that's fast"

Rather than creating a UIImage and setting that to the contents of a layer, we just put it directly into drawRect. The improvement in speed was… noticeable.
Converted month label gradient to pattern

This is much, much faster than creating and drawing a `CGGradientRef`.
Fixed background bug

When the month was taller than the gradient pattern, there was a bad visual bug where the gradient stopped before the end of the month. Now, we check for that case, and use the more efficient method, only when we can.
Changed day selection to image

Same reason as before. It's faster.
Removed test code

This shouldn't have been committed.
Corrected day normalization

Now days are normalized any time they are set to a month view.

Previously, the calendar view wasn't normalizing days when scrolling into the future.
Added check for no object

Sometimes, events don't load. That's weird. But now we check for that and don't mark the year as being loaded.
Fixed concurrency bug

So you really can't use the NSString drawing methods at all, especially on devices with multiple cores. It just borks the whole thing up. But the much more complicated NSAttributedString drawing works just fine, so whatever.