QuickDEV
  • ▶️Quick start
    • 🔃Overview
    • 🔑Security
  • 🎭Users management
    • 👨‍👩‍👦‍👦Members and groups
    • 🔐Permission for resources
  • 🖥️Applications
    • ➕Create applications
      • ⤴️Create application/module
      • 🔲Module
      • ✅Version and Release Management
    • 🎨Application editor
      • 👁️‍🗨️Visual components
        • ⚙️Common component settings
        • ⬆️File upload
        • 📊Charts and graphs
        • 🌄Image
        • 📋Option lists
        • 📑List view
        • ⬜Drawer
        • 🗺️Google maps
        • 📩Messages / Toast
        • 📅Calendar
        • Custom component
      • #️⃣Use markdown
      • ⌨️Keyboard shortcuts
    • 🔗Navigation
    • ⏯️Actions editor
      • ⏱️Date handling
      • 🟰Data selection & JavaScript
      • ⚡Event handlers
      • 🔎JavaScript Query
      • ✖️Dynamic variable
      • 💱Transformers
      • 🧮Data responder
      • ↕️Built-in JS functions
      • 📚Third-party libraries
    • 🖌️Styling
      • 📝Themes
      • 🖍️Customize styles
  • 🚀Database & API
    • 🔎Queries
    • 🧰Query repository
    • 📡Datasources
      • 🌎API
        • 1️REST API
        • 2️GraphQL
        • 3️Google Sheets
      • 🟠SQL Databases
        • 1️Oracle
        • 2️Microsoft SQL Server
        • 3️MySQL
        • 4️PostgreSQL
        • 5️MariaDB
      • 🟡NoSQL Databases
        • 1️MongoDB
        • 2️CouchDB
        • 3️DynamoDB
      • 🔴REDIS
      • 🟢BigData & OLAP
        • 1️Big Query
        • 2️Snowflake
        • 3️ClickHouse
        • 4️Elasticsearch
      • 🌐WebSocket
  • 💻Integrations
    • 1️ANGULAR
    • 2️HTML Pages
Powered by GitBook
On this page
  • Dynamic data for events
  • Editable calendar
  • Premium views
  1. Applications
  2. Application editor
  3. Visual components

Calendar

PreviousMessages / ToastNextCustom component

Last updated 12 months ago

The Calendar Component provides a comprehensive solution for managing and editing date and calendar entries within QuickDEV. To ensure an exceptional calendar experience, we've seamlessly integrated the Project.

Dynamic data for events

Within the "Basic" section, you can establish a binding with your Datasource, enabling the calendar to populate with your existing Events.

The JSON structure consists of an array of objects, where each object denotes a single event on the calendar. Here's an overview of the meaning of each key within the object:

  • id: A unique identifier for the event, aiding in distinguishing each event from others.

  • title: The name or title of the event. This is a brief description that will be displayed on the calendar to represent the event.

  • start: The start date and time of the event, formatted as "YYYY-MM-DD HH:MM:SS". For all-day events, the time part can be omitted, providing only the date.

  • end: The end date and time of the event adhere to the same format as the start date. For multi-day all-day events, this denotes the end date.

  • color: (Optional) A hexadecimal color code string used to determine the event's display color on the calendar. This facilitates visual differentiation between various event types.

  • allDay: (Optional) A boolean value (true or false) indicating whether the event spans the entire day. When set to true, the event will be displayed as an all-day event, potentially in a separate section of the calendar or styled differently. If this key is omitted, the event is assumed to have specific start and end times.

[
    {
        "id": "1",
        "title": "QuickDEV",
        "start": "2024-01-03 16:00:00",
        "end": "2024-01-03 17:00:00",
        "color": "#179568",
        "allDay": true
    },...
]

Once a user edits or adds a new Event, the data object undergoes an update, allowing you to persist this change on your chosen Datasource.

// Access all calendar event data
return calendar.events;

Editable calendar

Depending on the "Editable" setting, you can enable your application users to add or edit their own Calendar Events. A compact modal window appears, facilitating the entry of Event information.

Premium views

You can input the License Key within the Property Settings Menu. Upon entering the License Key, the Premium Views become accessible within the "Default View" dropdown menu.

Access to Premium Views such as the Resource Timeline and Resource Grid requires purchasing a license per Developer Seat at . This license extends to all App Users assigned the "Member/Viewer" role.

🖥️
🎨
👁️‍🗨️
📅
FullCalendar
FullCalendar