Calendar Display Component

Overview


The Groundswell Calendar Display, powered by ToastUI, gives designers the ability to quickly have a modern calendar display in their sites and dashboards with the simplicity of a single component. The dense, versatile display supports different calendar views with styling matching your site’s accent color. Example interfaces and utility rules are attached, which demonstrate usage and features of the component.

Key Features & Functionality

  • Display an array of events in Daily, Weekly, or Monthly format. Toggle days and weeks using an input parameter.
  • Automatic timezone shifting. By default, all provided events display in the timezone of your browser, but this can be overridden by providing TZ names ("America/Los_Angeles") OR a timezone code (EDT,CST,etc).
  • Multiple language support. Currently supports US English (en-US), UK English (en-GB), Spanish (es), Italian (it), Polish (pl), and Portuguese (pt).
  • Supports different date formats via a parameter.
  • Supports a detailed event pop-up of time, title, attendees, location, and event description.
  • Supports custom colors, font sizes, borders, and other attributes via applying custom themes.
  • Support for visible weeks, weekend display, and start of week for specific locale needs.
  • Allows event selection, should you want to edit an event or display details in addition to, or in lieu of, the detailed pop-up view.
  • Allows events to be "rescheduled" via drag and drop or through a modal
  • Allows events to be created and deleted directly from the calendar
  • Supports multiple calendars
  • More details and examples available in attached resources and sample application.
Anonymous
Parents Comment Children
  • Thanks for your reply. It's just to have the capability of a dynamic language support, with no need of deploying new versions of the plugin. We're using it in a project installed in different countries, but the countries are joining to the project dynamically, so we don't know the languages we'll need. If we can add custom translations, we can use the same version of the plugin just translating the values we provide as input.

    The way you say is great, because it simplifies the work for developers, but if we want to add an additional language ie Polish, it's needed a new version to add the literals in the plugin. If 2 months later we need the literal in Portuguese, another version is required, and so on.

    If you add two new params to provide custom translation of months and days, we could use the same plugin for every language, no depending on upgrades of the library