Book Update: interaction with datepicker and event filtering

I have published a new version of the book:

1. New chapter showing how to use external widgets to manipulate a calendar instance: datepicker for navigating and checkbox for filtering.

2. Added code in the database persistence samples to save updates when resizing or dragging events.

3. Fixed bugs in code samples from the database persistence chapter. Also updated Web2py sample project with those fixes.

Buyers from previous versions will get these updates for free.  Interested developers can get their own copy and future updates will be free.

Thank you all for your support!

 

 

New version soon: fullCalendar with datepickers and event filtering

I am currently adding to the book two examples showing how to interact with fullCalendar using widgets such as datepickers or checkboxes. These are the examples:

fc-interact-datepicker

 

 

fc-events-visibility

The price will increase again in a few days when I publish this version.  This version is already published.  As always, previous buyers will not be affected by this and will receive these updates at no additional cost.

You can take advantage of the current price if you get the book now.

Thanks for your support.

 

Book Update: fullCalendar with database persistence

Just finished the chapter on the basics of how to use a database to manage fullCalendar’s events and you can buy the new version now.

These are the topics:

  • Database representation of a fullCalendar event
  • Saving events
  • Loading events
  • Modifying events
  • Deleting events

The actual code to save to or retrieve events from the database depend on your back end: libraries, framework or database.  The samples in the book are just to give you an idea about how to build the interaction with your back end through JSON.

I plan to extend this chapter with examples showing how to save events to a database after drag and drop actions.  Although I think that, after going through the examples in the new chapter, you will readily get the idea on how to do it.  It is a matter of choosing inside which fullCalendar’s callback to put your save, update and delete functions calls.

As announced before, the price increased again for new buyers. If you already bought the book you should be receiving soon an email with the updated materials at no additional charge.

If you have not bought the book yet, get it at the current price and receive future updates for free.

 

 

 

 

fullCalendar integration with a few frameworks

Here are some links to libraries, components and tutorials that show how to integrate fullCalendar with different JavaScript and web frameworks:

Yii2

yii2fullcalendar component –  simple component exposing fullCalendar’s model. Seems to be based on fullCalendar 2.2.3

Ruby On Rails

FullCalendar Events and Scheduling – this is a screencast based on version 2.9.1 of fullCalendar. Shows how to use dialogs and a date range picker.

Web2py

The book contains a Web2py application showing how you could integrate fullCalendar with the framework.

Flask

flask-fullcalendar – Example of a simple integration with flask. I included a different example with the book.

Laravel

Laravel fullCalendar component – a component to integrate fullCalendar in Laravel projects.

Vue.js

Vue fullCalendar component –  sample code to integrate fullCalendar with the Vue.js framework.

AngularJS

Fullcalendar Walk through with AngularJS – blog post showing a very simple integration with AngularJS.

ReactJS

FullCallendar with React and ES6 – sample code showing how to load fullCalendar as a component in ReactJS.

Most of these examples will give you the basics of integrating fullCalendar in your projects. After that very important step, you can use the examples in the book to customize its use.

Next: fullCalendar Database persistence

I am halfway through the chapter about persisting fullCalendar’s events in a database. Topics include:

  1. Saving events
  2. Loading events from database
  3. Modifying events
  4. Deleting events

The examples will be based on the jQuery Dialogs version of the tutorials.

The server side code cannot be very specific because there are many ways to implement the CRUD interface depending on the libraries or frameworks you use, but I will include some sample code in Python to give you an idea.

The price of the book will increase when this chapter is done.  However, current buyers will get the updates for free.  Now is the time to get the book at the current price .

 

 

Basic fullCalendar callbacks

Use these callbacks in fullCalendar to respond when:

  1. Event’s content is about to be rendered: eventRender
  2. Event is clicked: eventClick
  3. Event is resized: eventResize
  4. Event finished been dragged and dropped: eventDrop
  5. Event is already dropped and rendered: eventReceive
  6. Event stopped been dragged, but still not dropped: eventDragStop