Now with Time

Now with Time (3.1.0)
=================
Whoa! This was fast and big! Another major update in 3 days, well, faster the better. But, why not `v4.0.0` the reason is pretty clear, we are implementing partial feed. Calendario won't do that, but it will send processed dates to a php file which will create **microformats-2 hCalendar** events. There are many other **hCalendar** parsers which will parse the **microformats-2** to **json** and eventually **json** to **iCal** format. That is so far so good!

Features and New Implementations
============================
* First thing first, the amazing way **Calendario** makes it easy to process data, so why only dates have events, we added time too. Example, (**NOTE:** Time to be in **24 hour** format only). Not implemented for dates like `10-DD-YYYY` and `11-DD-2012`, Aim v4.0.0.
```Javascript 
'11-16-2014' : {content: '<span>event two</span>', startTime: '06:30', endTime: '07:15'}
```
* With time it support zone, we didn't want to disturb your schedule so, we disturbed the time your event occurs in other time zones. For example, If your time zone is say **+05:30 (IST)**, so if you don't provide this zone, it will treated as a time of **Greenwich Time Zone**, so a time 14:00 will be the time at GMT and 19:30 at IST. Which may not be the way you desired. Moreover, zone helps you to set events fixed, If your event occurs at 06:00 at IST then a person at GMT will have the event set to 00:30. **Time interchangeability is the key feature**.

* No more clutter. With time support, change was must. 
     *  `start` and `end` is changed to `startDate` and `endDate`
     * `'onDay' + eventname`, passed the current element, contentElement and dateProperties, now
       it returns current Element, array of content, clutter free as mentioned in your **data.js**. Date 
       properties now contain 3 more options `startTime`, `endTime`, `allDay`. All these are arrays        
       containing startTimes, endTime and allDay in the order of the event. startTime and endTime   
       contain Date objects and allDay contains boolean. Refer to demo4 (index4.html) to see how to 
       use them.
     * `getCell` now returns the **cell jQuery object** and not the events data, so now more power in 
        **your hands**.

* Check Updates, you can easily turn it off by setting passing the option `checkUpdate` to false, like, `checkUpdate : false`. It contacts calendario **update.js** for details and checks if any new version is available. If any new version is available you can find details in browser console.

* `shown.calendar.calendario` jQuery trigger, is triggered when calendar finishes rendering. If first use, then it passes the current **instance**, If month is changed, the calendar is re-render, that time also it is triggered, no instance is returned after re-rendering.
```Javascript 
$(document).on('shown.calendar.calendario', function(e, instance){ /* something */ });
```
* New version function, instance now has a new function i.e. `.version()`, it returns the version of the Calendario you are using.

* Partial feed, instances `.feed()` send a post request to the file url, set by `feed` option. Soon, the parser will be launched, along with Calendario 4.0, till then you can experiment.

* Minified version of the JS has been added.

* And a new timeline demo, which shows how you can use time to create date and time events.