MMM-CalendarExt3

[gonzonia]

@sdetweil Just to close the loop on this. I updated MMM-Pir (there was another update soon after I posted) and switched to the updated MMM-Scenes2 and everything seems stable now.

[sdetweil]

@gonzonia awesome

[MMRIZE]

@Ragged4310
According to the conditions you provided, the previous code cannot be used. Clear definition of the conditions is essential to come up with an appropriate solution.

First, we need to clearly define the events that need to be collapsed. Based on your description, it seems they are in the form of “Person’s Name - Task.” Are you looking to group them by “Person’s Name”? However, it also seems that you do not want the “Person’s Name” to be exposed. In that case, how should they be displayed? For example, would you like them to be labeled sequentially as “Reservation 1,” “Reservation 2,” and so on?

Please provide more details about the AS-IS and TO-BE states.

Alternatively, assigning additional properties to the events to be grouped might also be a good approach. For instance, you could write the person’s name (e.g., Jane Doe) in the location or description field, and only include the task (e.g., Deep Tissue Massage) in the event title. Then, you could group events with the same description together.

[Ragged4310]

@MMRIZE said in MMM-CalendarExt3:

@Ragged4310
According to the conditions you provided, the previous code cannot be used. Clear definition of the conditions is essential to come up with an appropriate solution.

First, we need to clearly define the events that need to be collapsed. Based on your description, it seems they are in the form of “Person’s Name - Task.” Are you looking to group them by “Person’s Name”? However, it also seems that you do not want the “Person’s Name” to be exposed. In that case, how should they be displayed? For example, would you like them to be labeled sequentially as “Reservation 1,” “Reservation 2,” and so on?

Please provide more details about the AS-IS and TO-BE states.

Alternatively, assigning additional properties to the events to be grouped might also be a good approach. For instance, you could write the person’s name (e.g., Jane Doe) in the location or description field, and only include the task (e.g., Deep Tissue Massage) in the event title. Then, you could group events with the same description together.

AS IS:
My Google Calendar currently looks like the examples below. I transform event names containing keywords related to my wife’s services into a format that shows only the start and end time of each service, along with a small icon indicating it’s related to her work (massage therapy) on CX3.

Example Events:

Jane Smith: 60 - Custom Massage
Event Time: 12:30pm - 2:00pm
Location: <My wife’s business address>
Description: Name of service / client’s phone number / client’s email

John Doe: 90 - Custom Massage
Event Time: 2:00pm - 4:00pm
Location: <My wife’s business address>
Description: Name of service / client’s phone number / client’s email

Mike Example: 120 - Deep Tissue Massage
Event Time: 4:00pm - 6:30pm
Location: <My wife’s business address>
Description: Name of service / client’s phone number / client’s email

Johnny Smith: 30 - Deep Tissue Massage
Event Time: 10:00pm - 10:30pm
Location: <My wife’s business address>
Description: Name of service / client’s phone number / client’s email

TO BE:
I’d prefer if the title in CX3 could show the time range of merged events only, along with the colored icon I’ve assigned for keywords (e.g., massage, reiki, trade, break, etc.) using ev.originalTitle.match.

Example Output:

12:30pm - 6:30pm [3]

10:00pm - 10:30pm

The 12:30 represents the start of the first service, and 6:30 represents the end of the last service. The [3] indicates the total number of collapsed events.

The final event, 10:00pm - 10:30pm, would ideally remain separate due to the large gap. However, if separating it is too complex, it’s fine to merge all events into one block.

The only consistent attribute across these events is the location. All events are synced from her booking software into her Google Calendar.

I cannot group by Person’s Name because each client appears only once per day (I realize I could have used different names for clarity in the examples).

I understand this request may be complex, and if a solution isn’t feasible, I can continue with my current setup. However, it would be great to have this functionality implemented as described.

[sdetweil]

@Ragged4310 said in MMM-CalendarExt3:

I understand this request may be complex, and if a solution isn’t feasible,

its just code, if you can do it in your head, then code can do it…

[MMRIZE]

@Ragged4310
Sure, that’s doable. There’s no reason why it shouldn’t be possible.

This kind of work is domain analysis, which is basically my real-world job.

However, it’s not exactly simple. By simple, I mean it’ll take more than the usual 10 minutes I’d spend diving into this hobby project that genuinely interests me.

And honestly, my rate is quite high. :D (Just kidding.)

Let’s clarify a few things first.

• CX3 is usually useful for viewing events from multiple calendars at once, so you’re probably using other types of calendars (e.g., personal meetings, family schedules) together. For this task, let’s assume that the target “customer reservation” events are in a separate, independent calendar. For convenience, I’ll call this calendar “Reservation” from now on.
• Given the nature of calendars, I assume that there won’t be any overlapping events in the Reservation calendar. Additionally, I’ll assume there are no full-day events or events that span midnight.

With these assumptions, I’ll give it a shot sometime tomorrow when I have some free time. I can’t make any promises, so please don’t get your hopes up too high.

[MMRIZE]

@Ragged4310

See the green events

eventPayload in CX3 config;

/* CX3 config section in `config/config.js` */
eventPayload: (payload) => {
	const targetCalendar = "Reservation"
	const divideGap = 1000 * 60 * 60 * 1
	const locale = 'en-US'
	const timeStyle = { timeStyle: 'short' }

	const condition = (ev) => { return (ev.calendarName === targetCalendar && ev.fullDayEvent === false) }
	const target = payload.filter(condition).sort((a, b) => a.endDate - b.endDate)
	const result = payload.filter(e => !condition(e))
	const dateStr = (dateValue) => Intl.DateTimeFormat(locale, timeStyle).format(new Date(+dateValue))
	const collapse = (template, ev) => {
		if (!template?.["title"]) template = { ...ev, collapseCount: 0, description: '', location: '' }
		template.collapseCount++
		template.startDate = String(Math.min(+template.startDate, +ev.startDate))
		template.endDate = String(Math.max(+template.endDate, +ev.endDate))
		template.title = `${dateStr(template.startDate)} - ${dateStr(template.endDate)}`
		if (template.collapseCount > 1) template.title += ` <span class="count">${template.collapseCount}</span>`
		template.description += `<div class="collapsedEvent">
			<p class="title">${ev.title}</p>
			<p class="period">${dateStr(ev.startDate)} - ${dateStr(ev.endDate)}</p>`
		if (ev.description) template.description += `<p class="description">${ev.description}</p>`
		if (ev.location) template.description += `<p class="location">${ev.location}</p>`
		template.description += '</div>'
		return template
	}
	const dateKey = (dateValue) => new Date(+dateValue).toLocaleDateString('en-CA')
	let collapsedEvent = {}
	for (const ev of target) {
		const currentKey = dateKey(ev.startDate)
		if (!collapsedEvent?.[ 'title' ]) {
			collapsedEvent = collapse(collapsedEvent, ev)
			continue
		}
		const collapsedKey = dateKey(collapsedEvent.startDate)
		if (collapsedKey !== currentKey || +ev.startDate - +collapsedEvent.endDate > divideGap) {
			result.push(collapsedEvent)
			collapsedEvent = collapse({}, ev)
		} else {
			collapsedEvent = collapse(collapsedEvent, ev)
		}
	}
	if (collapsedEvent?.[ 'title' ]) result.push(collapsedEvent)
	return result
}

You can modify targetCalendar, divideGap, locale ande timeStyle for your purpose.

To beautify;

/* css/custom.css */
.CX3 .event.calendar_Reservation .headline .time {
  display: none;
}

#CX3_POPOVER .title .count,
.CX3 .calendar_Reservation .title .count {
  font-weight: bold;
  color: gray;
}

#CX3_POPOVER .title .count::before,
.CX3 .calendar_Reservation .title .count::before {
  content: "[";
}

#CX3_POPOVER .title .count::after,
.CX3 .calendar_Reservation .title .count::after {
  content: "]";
}

#CX3_POPOVER .description .collapsedEvent {
  line-height: 115%;
  border-bottom: 2px solid silver;

  p {
    margin-top: 0;
    margin-bottom: 0;
  }

  .title {
    font-weight: bold;
  }

  .period {
    text-align: right;
  }

  .description {
    font-style: italic;
    white-space: pre;
    padding-left: 20px;
  }

  .location {
    font-style: italic;
    text-align: right;
  }
}