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 fb1dbd63cf new callback: eventDestroy 12 years ago
build 470c8b9313 move Bower and CDNJS configs into build folder 13 years ago
demos ba7d28d915 upgrade to jQuery UI v1.10.2 13 years ago
lib ba7d28d915 upgrade to jQuery UI v1.10.2 13 years ago
src fb1dbd63cf new callback: eventDestroy 12 years ago
tests d910bb8fcd eventStartEditable/startEditable AND eventDurationEditable/durationEditable 12 years ago
.gitignore 9b4bfc1681 build for CDNJS 13 years ago
Gruntfile.js 3857ada289 tweak grunt clean:cdn command 13 years ago
changelog.txt 8c3e610215 update changelog 12 years ago
fullcalendar.jquery.json 155b78cc1a increment version 12 years ago
license.txt b7e644bf4e change to single MIT license. update banners in source files 13 years ago
lumbar.json ba7d28d915 upgrade to jQuery UI v1.10.2 13 years ago
package.json 95c16e274f new lumbar-based solution for building fullcalendar submodules 13 years ago
readme.md 4de5421081 updated docs for development workflow. added grunt dev command 13 years ago

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 to have the Grunt build system installed globally (-g) on your system:

npm install -g grunt-cli

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.