initial generation of a rails 3.2 app
adding the two assets we are going to use for this demo
committing the consequences of my bundle install
adding lines to the application css and javascript files.

These lines really are the whole point of my asset gems.  Those gems
include the assets you need, and they are nice and versioned and tucked
away.  Should those things update, you know know through bundler, rather
than having to hunt down where files were downloaded and copied from.
adding an event resource.

These files were generated with the scafold command:

rails g scaffold event title:string starts_at:datetime ends_at:datetime
all_day:boolean description:text

I didn't check in the helper or the helper test though. They would be
empty in this app and distracting.
adding methods the model will need to provide to the javascript.

This code was taken verbatim from my earlier rails3_fullcalendar
example.
ignoring the schema.rb file, as good CM practices dictate.
adding the filtering the calendar will need to the events index
controller.
generating the singular 'calendar' resource.
renaming to plural controlle rresource.  The route is singular.  That bites me almost every time.
adding the javascript that initializes the calendar. We are getting close now...
removing the print stylesheet.  It shouldn't be part of the normal stylesheet
making the root url do something useful
changing the color from json data to a default in the stylesheet
adding a simple comment to show how we can set colors in the json
restoring a test that broken when I renamed the singular controller
adding a readme
resolving an issue with dates that cross calendar boundaries
modified events show to go back to the calendar view
cleaned distracting comments out of gemfile