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.





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 .