NiceGui FullCalendar Example

This example is designed for NiceGui with non-premium FullCalendar plugins enabled.

• @fullcalendar/daygrid: Provides Month and DayGrid views: dayGridYear, dayGridMonth, dayGridWeek, dayGridDay, dayGrid (generic)
• @fullcalendar/timegrid: Provides TimeGrid views: timeGridWeek, timeGridDay, timeGrid (generic)
• @fullcalendar/list: Provides List views: listYear, listMonth, listWeek, listDay, list (generic)
• @fullcalendar/multimonth: Provides Multi-Month views: multiMonthYear, multiMonth (generic)
• @fullcalendar/icalendar: For loading events from an iCalendar feed
• @fullcalendat/rrule: For handling recurring events via rrule

• Event Creation Form: A form to create events.
• Date and Event Click Handling: Some code to handle date clicks and event clicks.

1. Clone this repository.

An example code for event creation is present in the main.py file.

Instead of loading all events at init time, you can let the calendar request events on-demand (e.g. per month/week) via a Python callback. This is useful for large datasets.

See the working example in basic_main.py.

The fetch mechanism is implemented in fullcalendar.py and fullcalendar.js — make sure these files are in the same folder as your script.

1. In your options dict, set events to any callable (e.g. lambda *a, **k: None).
2. Pass an on_fetch_events callback to FullCalendar.
3. Inside the callback, build the list of events and call info.response(events_list).

from fullcalendar import FullCalendar as fullcalendar

options = {
    "initialView": "dayGridMonth",
    "events": lambda *a, **k: None,  # enables fetch mode
}

def on_fetch(info):
    # info.start / info.end  -> ISO date strings
    # info.start_value / info.end_value -> epoch ms (for DB range queries)
    events = load_events_from_database(info.start, info.end)
    info.response(events)   # send the list back to the calendar

fullcalendar(options, on_fetch_events=on_fetch)

FetchInfoArguments exposes:

FullCalendar calls on_fetch_events automatically whenever the user navigates views. Only events intersecting the requested range are returned.

The FetchInfoArguments class and the calendar integration live in fullcalendar.py / fullcalendar.js.

Call info.failure("message") instead of info.response(...) to signal an error to FullCalendar (e.g. a database timeout).

Contributions are welcome! Please submit a pull request or open an issue to discuss the changes you want to make.