Read the statement by Michael Teeuw here.
MMM-CalendarExt3
-
@gonzonia when a module is hidden , nothing shows
-
My wife takes appointments for her business, so she has a lot of events each day she works. I want to be able to merge back-to-back events and show the start time of the first event and the end time of the last event to reduce the number of entries on the calendar.
Ideally, I would like something that could account for gaps between appointments as well since she will still be at work. Ie) I can set the transformer to combine all events that are <= 2 hours apart, and it will show me the start time of the first event and the end time of the last event. I know it’s asking for a lot, and it’s probably not even possible, but I wanted to ask.
-
@Ragged4310
Could you show me the example of the events? -
@MMRIZE said in MMM-CalendarExt3:
@Ragged4310
Could you show me the example of the events?I would like to consolidate the events with the little yellow massage person if its possible since she is gone for the whole time and it hogs up the event space. I tried using chatgpt and perplexity, but everytime they gave me something the calendar would not load.
For Dec 11 she has 3 appointments back to back, instead of it taking up 3 lines I would prefer if I could get it to show 2:00PM - 7:00PM for one event.
For Dec 23, she currently only has 2 appointments and there’s a small gap. Since the gap is < 2 hours I would like if I could consolidate that as well so it would show 10:00AM - 2:00PM.
I don’t know the event transformer too well, so I’m not sure if it can handle something like that.
Edit- Another thing I thought of… if it is possible to merge…
Is there a way to store how many events were merged? I’ll use the Dec 11 for the example again. If I can merge all 3 events into one, could I have it stored in a variable where I can display (3) at the end of the event to indicate there were 3 events? -
@Ragged4310
Now I c. I’ll try, wait a little. -
@Ragged4310
Instead ofeventTransformer
, we’ll useeventPayload
because, this conversion should be applied to whole events, not a single event.Insert this property into your config section of CX3 in
config/config.js
/* `MMM-CalendarExt3` config section in config/config.js */ eventPayload: (payload) => { const fulldays = payload.filter(ev => ev.fullDayEvent === true) const singleEvents = payload.filter(ev => ev.fullDayEvent === false).sort((a, b) => a.startDate - b.startDate || a.endDate - b.endDate) const EventsArranged = singleEvents.reduce((acc, ev) => { const dateObj = new Date(+ev.startDate) const key = `${ev.title}-${new Date(dateObj).toLocaleDateString('en-CA')}` if (!acc.has(key)) { acc.set(key, [ev]) } else { acc.get(key).push(ev) } return acc }, new Map()) const collapsed = Array.from(EventsArranged.entries()).map(([ key, value ]) => { const newEvent = { ...value[ 0 ] } if (value.length > 1) { newEvent.title = newEvent.title + ` <sub class="collapsed">${value.length}</sub>` newEvent.endDate = Math.max(...value.map(ev => ev.endDate)) newEvent.startDate = Math.min(...value.map(ev => ev.startDate)) } return newEvent }) return [ ...fulldays, ...collapsed ] },
And to beautify, add some CSS code into
css/custom.css
/* css/custom.css */ .CX3 .title sub::after, #CX3_POPOVER .title sub::after { content: "]"; } .CX3 .title sub::before, #CX3_POPOVER .title sub::before { content: "["; }
It will work like;
BEFORE
AFTER
- This code will not affect the fullday events.
- Not considered every aspect, like inter-day events or untested errors.
-
@MMRIZE Thanks for the reply! I haven’t had too much time to play around with it just yet. Would I be completely replacing the event transformer with the payload, or would I be using both? If I’m using both, does the order matter?
I currently use the transformer to set the icons and transform the title. Does your code only account for stuff that has the same name? With my wife’s schedule, her bookings are all something like this:
Jane Doe: 60 - Deep Tissue Massage
Jane Doe: 60 - Reflexology
Break
Jane Doe: 30 - Reikietc., but I transform it to hide her client’s names on our calendar since it’s visible to whoever is in the house.
eventTransformer: (ev) => { const formatTime = (date) => new Intl.DateTimeFormat("en-US", { hour: "numeric", minute: "numeric", hour12: true, }).format(new Date(date)); const startTime = formatTime(ev.startDate); const endTime = formatTime(ev.endDate); if (!ev.originalTitle) { ev.originalTitle = ev.title; } const titleParts = ev.originalTitle.split(":"); const eventTitle = titleParts.length > 1 ? titleParts[1].trim() : ev.originalTitle; // Set default icon ev.symbol = ["fluent:vehicle-car-profile-ltr-clock-16-filled"]; // Check if the event is not an all-day event if (!ev.isFullday) { ev.title = `${startTime} ${eventTitle}`; } else { ev.title = eventTitle; } // Rest of your existing conditions if (ev.originalTitle.toLowerCase().includes('work')) { ev.symbol = ["material-symbols:work-history-outline-sharp"]; ev.title = `${startTime} - ${endTime}`; } if (ev.calendarName === "Family" && ev.originalTitle.toLowerCase().includes('windcreek')) { ev.symbol = ["mdi:casino"]; } if (ev.calendarName === "Family" && ev.originalTitle.toLowerCase().includes('board')) { ev.symbol = ["mdi:cards-playing-spade-multiple"]; } if (ev.calendarName === "Abigail") { if (ev.originalTitle.match(/kung fu|tai chi/i)) { ev.symbol = ["icon-park-solid:kungfu"]; ev.title = `${startTime} - ${endTime}`; } else if (ev.originalTitle.match(/massage|reiki|trade|break|reflexology|deep|initial visit/i)) { ev.symbol = ["tabler:massage"]; ev.title = `${startTime} - ${endTime}`; } } else if (ev.calendarName === "Sebastian") { ev.title = `${startTime} - ${endTime}`; } else if (ev.calendarName == "Birthday") { ev.symbol = ["mingcute:cake-fill"]; } else if (ev.calendarName == "Appointment") { ev.symbol = ["lsicon:work-order-appointment-outline"]; } else if (ev.calendarName == "Holiday") { ev.symbol = ["openmoji:flag-us-outlying-islands"]; } return ev; }
Instead of checking the title directly, could I use some a contains check to see if it contains the character ‘:’ or ‘-’? I’ll be playing around with this tomorrow once I have some free time available.
-
@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.
-
@gonzonia awesome
-
@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
ordescription
field, and only include the task (e.g., Deep Tissue Massage) in the eventtitle
. Then, you could group events with the samedescription
together.