Skip to content
A port of fullcalendar-rails with bootstrap baked in.
Ruby Shell
Branch: master
Clone or download
Pull request Compare This branch is even with mariusbutuc:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
bin
lib/fullcalendar/bootstrap
test
vendor/assets
.gitignore
.travis.yml
Gemfile
README.md
Rakefile
fullcalendar-bootstrap-rails.gemspec

README.md

Fullcalendar::Bootstrap::Rails

  1. Want to display the events in your Rails app as a calendar?
    FullCalendar is a quick and dirty way to do it.
  2. Want it all bundled up nicely as an asset gem for use with Rails' asset pipeline? fullcalendar-rails is one of the best options.
  3. Tried to make it look consistent with the rest of your Bootstrap-powered views? Welcome!

Installation

Add this gem and its momentjs dependency to your application's Gemfile:

gem 'momentjs-rails'
gem 'fullcalendar-bootstrap-rails'

And then execute:

$ bundle

Or install it yourself as:

$ gem install fullcalendar-bootstrap-rails

At this point, the files from the FullCalendar project are in your asset pipeline's path… all you have to do is require them in the appropriate places.

Here is an example:

  • CSS:

    // app/assets/stylesheets/application.scss
    
    @import "bootstrap-sprockets";
    @import "bootstrap";
    // after the bootstrap dependency
    @import "fullcalendar";
  • javascript:

    // app/assets/javascripts/application.js
    
    //= require bootstrap-sprockets
    //= require moment
    // after the bootstrap and moment dependencies
    //= require fullcalendar

For more details and options, check the fullcalendar-rails installation section.

A note on versioning

First noticed this type of versioning with @bokmann's fullcalendar-rails:

I am going to version this gem with the version of the FullCalendar code I use, adding an extra digit if I need to release any maintenance versions of the gem itself.

Makes sense to me: It's Semantic Versioning, just that a different semantic. I'm inheriting it, this way you can explicitly require a specific version of FullCalendar, if available:

gem 'fullcalendar-bootstrap-rails', '~> 2.3.1.0'

where the digit after the semantical patch version indicates the release of this gem.

Usage

HTTP/1.1 302 Found
Location: http://fullcalendar.io/

I mean, not much to say here. You're more interested in how to use FullCalendar.

Development

After checking out the repo, run bin/setup to install dependencies. Then, run bin/console for an interactive prompt that will allow you to experiment.

To install this gem onto your local machine, run bundle exec rake install. To release a new version, update the version number in version.rb, and then run bundle exec rake release to create a git tag for the version, push git commits and tags, and push the .gem file to rubygems.org.

Contributing

  1. Fork it ( https://github.com/mariusbutuc/fullcalendar-bootstrap-rails/fork )
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Add some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create a new Pull Request
You can’t perform that action at this time.