A full interactive Calendar UI built for Vanilla JS or use in other frontend frameworks.

#javascript #js #vanillajs #ui #frontend #webdev #website #html #css #jquery

Adam Shaw bc292a2008 update readme for installing Bower 12 éve
build 470c8b9313 move Bower and CDNJS configs into build folder 13 éve
demos 83f7d50501 leverage Bower for dependencies 12 éve
src 95c1aa9304 fix IE7 rendering bug. related to view switching refactor 12 éve
tests 4aff669965 remove firebug-lite 12 éve
.gitignore 83f7d50501 leverage Bower for dependencies 12 éve
Gruntfile.js 83f7d50501 leverage Bower for dependencies 12 éve
bower.json 83f7d50501 leverage Bower for dependencies 12 éve
changelog.txt 5b04354e25 update changelog 12 éve
fullcalendar.jquery.json c5005f90ee increment version 12 éve
license.txt b7e644bf4e change to single MIT license. update banners in source files 13 éve
lumbar.json 83f7d50501 leverage Bower for dependencies 12 éve
package.json ac42dbacaa make package.json more valid 12 éve
readme.md bc292a2008 update readme for installing Bower 12 éve

readme.md

FullCalendar - Full-sized drag & drop event calendar

This document describes how to modify or contribute to the FullCalendar project. If you are looking for end-developer documentation, please visit the project homepage.

Getting Set Up

You will need Git, Node, and NPM installed. For clarification, please view the jQuery readme, which requires a similar setup.

Also, you will need the grunt-cli and bower packages installed globally (-g) on your system:

npm install -g grunt-cli bower

Then, clone FullCalendar's git repo:

git clone git://github.com/arshaw/fullcalendar.git

Enter the directory and install FullCalendar's development dependencies:

cd fullcalendar && npm install

Development Workflow

After you make code changes, you'll want to compile the JS/CSS so that it can be previewed from the tests and demos. You can either manually rebuild each time you make a change:

grunt dev

Or, you can run a script that automatically rebuilds whenever you save a source file:

./build/watch

You can optionally add the --sourceMap flag to output source maps for debugging.

When you are finished, run the following command to write the distributable files into the ./build/out/ and ./build/dist/ directories:

grunt

If you want to clean up the generated files, run:

grunt clean

Writing Tests

When fixing a bug or writing a feature, please make a corresponding HTML file in the ./tests/ directory to visually demonstrate your work. If the test requires user intervention to prove its point, please write instructions for the user to follow. Explore the existing tests for more info.