How sudhirsb2003/rails3_fullcalendar works
This is a Rails 3 example integrating a browser calendar with REST-style event management. The main workflow is to open the calendar, request events for the displayed time range, and render them; users can also create, edit, and delete events through Rails views and controller actions. FullCalendar and jQuery REST are documented client capabilities. The excerpts establish routing and controller-to-model behavior, but do not show the calendar template or client initialization, so those links are limited to documented relationships.
Main entry points: events_controller.rb Events controller · calendar.js Calendar setup · jquery.rest.js jQuery REST · routes.rb Routes
Components 12
Calendar client
- FullCalendar
public/javascripts/fullcalendar.js - Calendar setup
public/javascripts/calendar.js - jQuery
public/javascripts/jquery.js - jQuery REST
public/javascripts/jquery.rest.js - Calendar page
app/views/calendar/index.html.erb
Rails request routing
- Routes
config/routes.rb - Calendar controller
app/controllers/calendar_controller.rb
Event management
- Events controller
app/controllers/events_controller.rb - Event pages
app/views/events
Event storage
- Event model
app/models/event.rb - Event records
db
Other components
- Calendar user
Connections 12
- Calendar user → Routes: opens calendar
README - Routes → Calendar controller: routes calendar
config/routes.rb - Routes → Events controller: routes events
config/routes.rb - Calendar controller → Calendar page: renders page
- Calendar page → Calendar setup: configures calendar
- Calendar setup → FullCalendar: uses plugin
README - Calendar setup → jQuery REST: requests events
README - jQuery REST → jQuery: extends AJAX
public/javascripts/jquery.rest.js - jQuery REST → Events controller: calls REST API
README - Events controller → Event model: queries and updates
app/controllers/events_controller.rb - Events controller → Event pages: renders pages
app/controllers/events_controller.rb - Event model → Event records: persists records