A complete AngularJS directive for the Arshaw FullCalendar.
- (AngularJS)
- (fullcalendar.js 2.0 and it's dependencies)
- optional - (gcal-plugin)
We use karma and grunt to ensure the quality of the code.
npm install -g grunt-cli
npm install
bower install
grunt
We use bower for dependency management. Add
dependencies: {
"angular-ui-calendar": "latest"
}
To your components.json
file. Then run
bower install
This will copy the ui-calendar files into your components
folder, along with its dependencies. Load the script files in your application:
<script type="text/javascript" src="bower_components/jquery/jquery.js"></script>
<script type="text/javascript" src="bower_components/jquery-ui/ui/jquery-ui.js"></script>
<script type="text/javascript" src="bower_components/angular/angular.js"></script>
<script type="text/javascript" src="bower_components/angular-ui-calendar/src/calendar.js"></script>
<script type="text/javascript" src="bower_components/fullcalendar/fullcalendar.js"></script>
<script type="text/javascript" src="bower_components/fullcalendar/gcal.js"></script>
Add the calendar module as a dependency to your application module:
var myAppModule = angular.module('MyApp', ['ui.calendar'])
Apply the directive to your div elements. The calendar must be supplied an array of decoumented event sources to render itself:
<div ui-calendar ng-model="eventSources"></div>
Define your model in a scope e.g.
$scope.eventSources = [];
All the Arshaw Fullcalendar options can be passed through the directive. This even means function objects that are declared on the scope.
myAppModule.controller('MyController', function($scope) {
/* config object */
$scope.uiConfig = {
calendar:{
height: 450,
editable: true,
header:{
left: 'month basicWeek basicDay agendaWeek agendaDay',
center: 'title',
right: 'today prev,next'
},
dayClick: $scope.alertEventOnClick,
eventDrop: $scope.alertOnDrop,
eventResize: $scope.alertOnResize
}
};
});
<div ui-calendar="uiConfig.calendar" ng-model="eventSources">
The ui-calendar directive plays nicely with ng-model.
An Event Sources objects needs to be created to pass into ng-model. This object will be watched for changes and update the calendar accordingly, giving the calendar some Angular Magic.
The ui-calendar directive expects the eventSources object to be any type allowed in the documentation for the fullcalendar. docs Note that all calendar options which are functions that are passed into the calendar are wrapped in an apply automatically.
To avoid potential issues, by default the calendar object is not available in the parent scope. Access the object by declaring a calendar attribute name:
<div ui-calendar="calendarOptions" ng-model="eventSources" calendar="myCalendar">
Now the calendar object is available in the parent scope:
$scope.myCalendar.fullCalendar
This allows you to declare any number of calendar objects with distinct names.
You can use fullcalendar's eventRender
option to customize how events are rendered in the calendar.
However, only certain event attributes are watched for changes (they are id
, title
, url
, start
, end
, allDay
, and className
).
If you need to automatically re-render other event data, you can use calendar-watch-event
.
calendar-watch-event
expression must return a function that is passed event
as argument and returns a string or a number, for example:
$scope.extraEventSignature = function(event) {
returns "" + event.price;
}
<ui-calendar calendar-watch-event="extraEventSignature" ... >
// will now watch for price
There is no mechanism to $watch the displayed date range on the calendar due to the JQuery nature of fullCalendar. If you want to track the dates displayed on the calendar so you can fetch events outside the scope of fullCalendar (Say from a caching store in a service, instead of letting fullCalendar pull them via AJAX), you can add the viewRender callback to the calendar config.
$scope.calendarConfig = {
calendar:{
height: "100%",
...
viewRender: function(view, element) {
$log.debug("View Changed: ", view.visStart, view.visEnd, view.start, view.end);
}
}
};
The calendar works alongside of all the documentation represented here
Make sure that if a new feature is added, that the proper tests are created.