Let the CALENDAR view type choose its initial view and time scale, and remember the view the user picked

Open
  • Is something wrong?
#1,959 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
java
Domain
frontend

Research direction

Start by tracing how CALENDAR object groups process OPTIONS and how group preferences are stored per user and form. Then inspect the calendar view’s month, week, and day settings, including the DATETIME time grid. Done means the configured initial view, time range, and slot duration work, and the user's last selected view is remembered across form reopens and calendar re-entry.

Written by the indexing model from the issue text.

Description

enhancement
Description

An object group with the CALENDAR view type always opens in the month view, and the view the user switches to (week, day) is lost when the form is opened again or the calendar is re-entered from another view type. The week view is a day grid even for DATETIME properties, and the day view's time scale always covers the whole day scrolled to 06:00. Nothing in the language or settings changes this: OPTIONS is accepted after CALENDAR but ignored.

Proposed: let OPTIONS of the group carry calendar settings — the initial view (month / week / day), a time-grid week view, the visible time range and slot duration — and keep the view the user last selected per user and form, as other group preferences are kept:

FORM schedule
    OBJECTS a = Appointment CALENDAR OPTIONS JSON FROM initialView = 'week', slotMinTime = '08:00', slotMaxTime = '20:00'
    PROPERTIES(a) title, dateTimeFrom, dateTimeTo
;
Reason

A scheduling screen with a dozen timed events a day is unusable in the month view (everything collapses into "+N more"); today the only way to start in the week or day view is a client-side script that clicks the calendar's own buttons on every opening.

Dominant language
Java
Stars
214
Forks
46
No merged PRs in 30d

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from lsfusion/platform

All issues in lsfusion/platform

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.