The Air Calendar Plugin is a bubble plugin based on the FullCalendar.
A highly customizable calendar with several different views based on FullCalendar. FullCalendar is the most powerful calendar and scheduler used by several companies and projects.
This plugin was developed in response to the several limitations of the default bubble calendar and addresses the three main concerns: Performance, Customization, and Feature set.
It is a full-fledged calendar that you can even build your SAAS on (Timekit.io uses the same library, FullCalendar, that this plugin is based on)
full control of Look and Feel
internationalization (Locales and Timezones)
drag-and-Drop and Resize
drag to select
standard date representation
*Multiple views: Weekly, Monthly, Yearly views in timed grids or agenda grids. There are 9 different views by default.
*Custom views: In addition to the default views, you can also create your own views (currently two). For example, you can decide to create a 3-day workday schedule view. There is also an option for the browser to remember the last view the user was on (like google calendar).
*Full control of Look and Feel: The calendar is super customizable and by default provides only the calendar gird allowing you to create your own buttons and layout for navigation. For example, you can place the next and previous buttons anywhere, user buttons or dropdowns (like google calendar) to switch views, etc. There are also several options to set event colors, border colors, calendar background, and text colors, etc.
*Internationalization (Locales and Timezones): The calendar supports different locales (languages) and all the timezones in the world. You can even let your users switch between different timezones dynamically. The calendar provides you with a list of all timezone names (ids) allowing you to create a dropdown with it. Same for locales.
*On-demand fetching: Instead of loading all the calendar events at once causing huge delays like in other calendar plugins, Air Calendar allows you to fetch events that are only needed for the current view. The plugin exposes the current view's start and end dates which you can use to restrict the amount of data fetched from your database.
*Drag-and-Drop and Resize: You can easily drag-and-drop events and well resize them. It even has support for dragging events from one calendar to another (currently disabled).
*Easy setup: The calendar gives you full control over how to set up your database and how to connect to it. You can name your database fields whatever you want. You don't have to expose your data API. The plugin triggers events for when an event is added, dragged, resized and you use this to determine when and how you write event data to your database through whatever means you prefer.
*Drag to select: You can enable creating an event by dragging to select a time period. The plugin also has actions that allow you to select/unselect through workflow actions.
*Blocked dates/times: The plugin allows you to block all different kinds of periods. Users will not be able to drag-and-drop or resize events into blocked periods. Blocked periods are created just like normal events so there is no limitation on how to create the blocked periods. You can have blocked day ranges, in combination with single days in combination with single time periods and ranges.
*Standard date representation: The calendar uses the iCalendar standard for storing event dates. That is all end dates are exclusive. This allows you to easily import event data from other calendar systems as well as export your calendar data to other calendar systems. For more information on this see the documentation page.
⚙️released on 09 April 2021
LOTS OF GOOD STUFF 🎉
🔥 update: FullCalendar library to latest (5.6.0) version
😍 fix: split into two separate events when a single event is dragged from one date to another
🤩 fix: error when “Enable Resource/Scheduler view” checked
🤩 fix: dragging events only works when debug mode is active
🤩 fix: debugger error "Recursion when evaluating property"
🎉update: day\month render in x-axis when resourceTimelineWeak and resourceTimelineMonth is selected
Install the plugin from the plugin store
Add the element, AirCalendar, to your page and resize it to your needs.
At this point, if you preview your page you will see an empty calendar without any events and buttons.
Go to the Data tab in Bubble.
Create a new Thing. You can give it any name you like, e.g. Appointment.
At minimum AirCalendar requires and an Event start and end date field which is of type date. You can have other optional fields and any other fields you require for your application. Ideally, you should have the three fields in bold.
Event start date -
Event end date -
All day -
Event title -
Event background color -
Event border color -
Event text color -
To improve the speed of loading events into the calendar, Air Calendar fetches events on demand. This means instead of loading all the calendar events when the page loads, Air Calendar allows you to load just the events needed for a view.
To achieve this the Air Calendar exposes the
current view and the
current view start date and
current view end dates. So you can pass these as constraints to the event's
Do Search query.
Field "Type" in our table is a type of event display.
'auto' - in dayGrid, renders the event as a solid rectangle, if it is all-day or multi-day. If a timed event will render it with a dot. When in other views, will render normally.
'block' (default) - in dayGrid, renders the event as a solid rectangle. When in other views, will render normally:
'list-item' - in dayGrid, renders the event with a dot. When in other views, will render normally:
'background' - Events that appear as background highlights:
'inverse-background' - Like
'background', but fills the reverse space.
'none' - Won’t render the event at all.
AirCalendar provides actions and states that allow you the freedom to design your calendar navigation the way you like. The following actions, triggers, and states are provided.
The following actions are provided.
Go to Next view - Moves the calendar one step forward (by a month or week for example).
Go to Prev view - Moves the calendar one step back (by a month or week for example).
Go to Next year - Moves the calendar forward one year.
Go to Prev year - Moves the calendar back one year.
Go to Today - Moves the calendar to the current day
Go to date - Moves the calendar to the supplied date.
Air Calendar provides 9 different views plus two custom views that you can define yourself. Below are the different views, actions, triggers, and states.
A DayGrid view is a view with one or more columns, each representing a day. The pre-configured DayGrid views are dayGridDay and dayGridWeek.
dayGridDay: A view with one column listing the available events in the day. By default, it shows one day but you can create a custom view dayGridDay view to show any number of days. e.g. a 3-day dayGridDay.
dayGridWeek: A view with two or more columns each representing a day. By default, this will show a one-week view. But you can create a custom dayGridWeek view to show any number of weeks, e.g. a 2-week dayGridWeek.
dayGridMonth: This is a monthly view that displays the current month’s days, and usually a few days of the previous and next months, in a table-like format. There is no custom dayGridMonth view.
A TimeGrid view displays one or more horizontal days as well as an axis of time, usually midnight to midnight, on the vertical axis. The two predefined TimeGrid views are the timeGridWeek and timeGridDay views.
timeGridDay A view that displays horizontal days with a time axis. You can create a custom timeGridDay view with a different number of days.
timeGridWeek: A view that displays horizontal days with a time axis. You can create a custom timeGridWeek view with a different number of weeks.
A list view displays events in a simple vertical list for a specific interval of time.
There are 4 preset list views: listDay, listWeek, listMonth, and listYear.
You can create a custom list view that displays a different number of days, weeks, months, or years.
current view's name: The current view's name as text. Possible values are any one of the available views listed above. e.g. timeGridWeek. Note that this is case-sensitive (meaning the small letters and capital letters should be exactly as listed above)
current view's title : Title text that is displayed at the top of the header (such as “September 2009” or “Sep 7 - 13 2009”).
current view's activeStart date : A Date that is the first visible day. In month-view, this value is often before the 1st day of the month, because most months do not begin on the first day-of-week.
current view's activeEnd date : A Date that is the exclusive last visible day.
current view's currentStart date : A Date is the start of the interval the view is trying to represent. For example, in month view, this will be the first of the month. This value disregards hidden days. You can use this to restrict the number of events the calendar fetches.
current view's currentEnd date :A Date is the exclusive end of the interval the view is trying to represent. For example, in month view, this will be the day after the last day of the month (because it is exclusive). This value disregards hidden days. You can use this to restrict the number of events the calendar fetches.
view changes: Triggered when a calendar's view changes.
change view: Immediately switches the calendar to a different view.
Static view name: The name of the new view to switch to. Date: If you’d like to navigate to a new date while simultaneously switching to a new view, you can specify a date parameter.
Get view name dynamically: Check this box if you want to get the name of the view to switch to dynamically. This can be used if you're getting the view name from say a dropdown. This case you will call this action in the dropdown value's change event. Then you can get the dropdown value as
Dynamic view name: The view name to switch two. Can be any one of the supported view names:
timeGridDay, timeGridWeek, dayGridDay, dayGridWeek, dayGridMonth,listDay, listWeek, listMonth, listYear , customView1, customView2
Air Calendar is based on FullCalendar which uses exclusive end dates. Below is an explanation of what this means and how to set things up to work properly.
Yes, it might be confusing for users. But remember computers understand things differently from humans. For example, array indexes stars from 0 but humans count from 1. This means when dealing with arrays the indexes you display to your users will be different from what you use to perform your calculation. Bubble.io as a no-code platform makes life easy for its developer by counting from one but behind the scene, counting starts from 0.
So how do we make sure the users don't get confused?
When saving an All Day event, do the opposite by adding 1 day to the end date.
The current event is a very important state returned by the plugin. Below are details of the value.
current event : This is the current bubble event that has been left-clicked, right-clicked or hovered. Its type is your calendar's event type. For example, if your calendar things are called Appointment, this value will be an Appointment.
current event's rightclick pageX: The right-clicked horizontal coordinate (pageX) on an event.
current event's rightclick pageY: The right-clicked vertical coordinate (pageY) on an event.
Here is described the triggers and actions for reacting to event drags and resize on the calendar.
A unique feature of Air Calendar is that it doesn't automatically write changes in the calendar to the database. This allows you complete control on when and how to update your database.
The calendar provides the following states and events for updating an event in the database when it is modified on the calendar.
modified event: the current event that has just been dragged or resized. It's type is your calendar's event type so you can access all the thing's fields
modified event start : the start date of the modified event. This is a date type.
modified event end : the end date of the modified event. This is a date type.
modified all day : the new All-day field of the modified event. This a yes/no field. Currently, for some technical reasons, you can't drag an event from the All Day field to a timed region and vice versa so you don't need to use this field. You can get the all-day field from the event object itself. This value will become important when we enable the ability to drag events from All day region to time region or vice versa. So for you get the all-day field from the modified event thing itself.
event is modified : This is triggered when an event on the calendar is dragged or resized.
In the workflow tab add a new event and select AirCalendar event is modified.
2. Add a
make a change to a thing action and in the
Thing to change field select AirCalendar's
modified event. Then for your event's start and end dates select AirCalendar's
modified event start and AirCalendar's
modified event end states respectively.
Air calendar supports dynamic selection. User can click and drag to select a period of time to create an event. Below are the actions, triggers and states associated with selection.
To enable selection check the element property
Event and days are selectable . Once enabled the following states, triggers and actions can be used.
selected start date : The start date/time of the current selection. The value is a
selected end date : The end date/time of the current selection. The value is a
selection all day? : This is a boolean (
yes/no) that tells you if the selection occurred in an All Day (yes) cell or a timed cell (no).
selection is made : Triggered when a selection has been made. Once this event occurs the states defined above are available and can be used in a workflow. For example, you may want to show a popup with the selected dates to create an event in your database.
Air calendar allows you to programmatically select or cancel a selection. This is useful if after the user has selected an area decides to change the start or end time (see a demo at the start of this page). The following actions are provided.
Select: Selects a period of time on the calendar. It has the following fields
start date - Start date of the selection. The value should be a date.
end date - End of the selection. Optional. Default slot value will be used. The value should be a date. This value is exclusive, meaning if you want your last full-day selection to be Thursday, then specify Friday
All day - Specify if selection should happen in the All Day slot. Optional. Default is false.
Unselect: Cancels the current selection. It doesn't have any fields.
Here are described the triggers and actions for clicking on events and dates on the calendar.
See the current event states above.
event is clicked : Triggered when a calendar event is clicked.
date is clicked : Triggered when a calendar date is clicked.
calendars's event is right clicked : Triggered when an event is right-clicked. This is useful if you've disabled the default right-click context menu and want to show your own context menu when an event is right-clicked.
Owner's Timezone - this dropdown contains a list of timezones. The page owner must choose his own time zone so that the time difference between different time zones can be calculated.
Set Timezone - The incoming parameter is the ID (text) of the new time zone. Switches the timezone of the calendar to the selected one.
Reload Events - New action. Hides all events, and then displays again, updating all data (including calculating the time of the event in a new time zone).
timezone offset display seconds - This state stores information about the difference between the time zone of the owner of the calendar and the current time zone of the calendar. It is used to correctly display the event time when editing it, since by default the event is stored in the database in the owner's time zone.
timezone offset save seconds - This state stores information about the difference between the time zone of the owner of the calendar and the current time zone of the calendar. unlike the previous state in the sign, that is, it is the opposite (example: offset display = 120 => offset save = -120). Used for correct saving to the database. Changes the time of the added event from the user's time zone to the owner's time zone
2.6.0: Added a possibility to change the event display type. Fixed word-wrap in HTML titles.
Now users have the possibility to change the view type of an event from four types:
block ( it seems to display type in older versions of the calendar),
background ( is using for "blocked" events on our demo page),
inverse-background ( new view type. Like
'background',but fills the reverse space )
list-item ( new view type added in v5 of Fullcalendar and used by default ).
The default view is set to 'block' because this view was used in older versions. Type can be changed in the same way as the title or color of the event.
2.7.0: Fixed any issues after updating the library. Added possibility to import events from Google Calendar and possibility to change touch delay for mobile devices.
What was done:
🛠 fixed: colors changed in settings now work 🛠 fixed: information message in the left corner is removed 🛠 fixed: before the update, the color of the circle in the list view was taken by the color of the borders. now, if no border color is assigned to the event, the default color of the event will be used. ➕ added: possibility to import events from google calendar. Instruction on how to get API key and calendar id: https://fullcalendar.io/docs/google-calendar. ➕ added: possibility to change press delay for mobile devices.
2.8.0: HTML is customized to be as close as possible to the design from Seanhoots. Added getUTCFullYear error fix.
What was done:
🛠fixed: getUTCFullYear error when the Remember view checkbox is activated 🛠fixed: calendar design was customized as close as possible to the Seanhoots (old versions) 🛠fixed: removed outer borders from the week view ➕added: Google Calendar events functionality ➕added: the "Today" circle
2.12.0: Fixed plugin element settings
What was done:
🛠fixed: day header render
🛠fixed: error when the background color of the event is not changed
🛠fixed: displaying of event content then end time is not set
2.14.0: dayGridView rendering fix
What was done:
🛠fixed: dayGridView rendering
2.15.0: added timezone support
What was done:
➕ added timezone support. Added a field with the time zone of the page owner for the correct saving of events. It is needed to specify the page owner time zone in this filed in order to use this feature.
The "timezone offset display seconds" and "timezone offset save seconds" states the difference between the owner's time zone and the current calendar time zone. "Timezone offset display seconds" - used for correct time display. "Timezone offset save seconds" - used to save time correctly.