Problem/Motivation

Even as a maintainer, I find the current organization of the current views settings UI bewildering. I struggle to find the right place to make common changes.

Proposed resolution

Reorganize the UI. Provide fewer groupings, more intuitively structured.

Issue fork fullcalendar-3605095

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

mandclu created an issue. See original summary.

mandclu opened merge request !94

  • mandclu committed 0d7b8728 on 4.0.x 
    feat: #3605095 Reorganize views settings UI

By: mandclu
mandclu’s picture

mandclu commented
Status: Active » Fixed

The merged code changes reorganize the UI, with some additions:

If the Settings Tray module is enabled, that can be chosen as the preferred form display when adding a new event is triggered
In addition to double-clicking in the calendar, a site builder can also put a new fcAddEvent into the toolbar, which will create a translated "Add" button. Icon API support would be ideal, and will be deferred to a child task.

Two accompanying admin fields were added: "Add button text" (defaults to the translated string "Add" via Drupal.t()) and "Add button icon" (accepts CSS class(es) from any icon library loaded by the theme, e.g. fa-solid fa-plus). Leaving the text field blank while providing an icon produces an icon-only button.

FullCalendar v7 API corrections

During implementation, two breaking API changes in FullCalendar v7 were identified and fixed: customButtons was renamed to buttons, and the icon property was renamed from icon to iconClass. The form field description for the icon field was also corrected — FC v7 no longer ships an icon font, so iconClass sets a CSS className on a rather than referencing a built-in glyph.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.