MMM-CalendarExt3

MMRIZE

{
  module: "MMM-CalendarExt3",
  position: "bottom_bar",
  config: {
    mode: 'month',
    manipulateDateCell: (dom, events) => {
      let date = new Date(+dom.dataset.date)
      if (date.getMonth() == 8 && date.getDate() == 2) { // specific cell by absolute date
        dom.classList.add('specialHoliday')
        dom.style.backgroundColor = 'red'
        // do whatever you want.
      }

      if (events.some(e => e.title.search("Gelber") > -1)){ // specific cell by event
        dom.classList.add('specialEvent')
        dom.style.backgroundColor = 'yellow'
        // do whatever you want.
      }
    }
  }
},

nekreg9

How can I delay the start of the MMM-CalendarExt3 module? I have the default calendar module showing and I can see the 3 calendars load events into it. The problem is CalendarExt3 starts while the calendars are still loading. I changed the refreshInterval to more frequent to deal with that, but really a delay start would be more efficient.

I supposed this would only be a problem while I am troubleshooting.

MMRIZE

@nekreg9
There is a configurable option “waitFetch”.
But I doubt your real issue would be that. Because, CX3 starts rendering after one calendar which has at least one event have fetched successfully. (and in a “waitFetch”, no more calendar is fetched)
So if your CX3 starts late, It means your events source provider(usually default calendar module) might have timing issue to fetch calendars(e.g. too frequent fetch cycles or something else)

Kaisies 0

Is it at all possible to alter the grid to only divide the screen into 5 sections? I was able to alter code to only show m-f, but the sat and sun sections are still there. Just completely blank. For the life of me I can’t figure out where in the code it sets this part up.

MMRIZE

@Kaisies-0

MMRIZE

@Kaisies-0
Anyway,
For the firstDayOfWeek: 1 (Week starts from Monday), It could be achieved like below;

.CX3 .weekGrid {
  grid-template-columns: repeat(5, [cell-start] 1fr [cell-end]) 0fr 0fr;
}

.CX3 .weekday.weekday_6,
.CX3 .weekday.weekday_0 {
  display: none;
}

.CX3 .cell.weekday_6,
.CX3 .cell.weekday_0 {
  display: none;
}

This will work.

But for the firstDayOfWeek:0 or another case, .weekGrid should be adjusted more heavily. And not sure side-effects.

BKeyport

@MMRIZE I wanna do things a little different (of course) - what I’d like is to have CX3 display the calendar symbol only. No title, preferably horizontally. I can get the title out of the way, but the rest of it I’m not quite sure how - for some reason I’m having a hard time deconstructing how you build.

Thanks!

MMRIZE

@BKeyport

Is this what you want?

MMRIZE

@BKeyport
What a coincidence.
Yesterday, a user asked me how to manipulate day-cell and remove events together at the same time. It is ideally the same with your purpose.

To reach your goal; 1) extracting an icon from an event and 2) putting it into the daycell would be needed.
However, manipulateDayCell is executed after all events processes are done, so it cannot be achieved with CX3 alone. With manipulateDayCell, you can extract icons and inject them into the daycell, but you cannot remove original events together easily.

With MMM-ModuleMonkeyPatch, you can remove events after rendering (before revealing)

/* In MMM-CalendarExt3 config */
  manipulateDateCell: (cellDom, events) => {
    let body = cellDom.querySelector('.cellBody')
    Array.from(events).forEach((e) => {
      if (Array.isArray(e.symbol) && e.symbol.length > 0) {
        let icon = document.createElement('span') 
        icon.className = e.symbol
        body.appendChild(icon)
        icon.style.color = e.color
      }
      
    })
  },
  maxEventLines: 1,

/* MMM-ModuleMonkeyPatch */
{
  module: "MMM-ModuleMonkeyPatch",
  config: {
    patches: [
      {
        module: "MMM-CalendarExt3",
        method: "getDom",
        patch: function (original, args) {
          let dom = original(args)
          let target = Array.from(dom.querySelectorAll('.event')) || []
          target.forEach((e) => {
            e.style.display = 'none'
          })
          return dom
        }
      }
    ]
  }
},

These codes are just concept-proof. There are many holes like overflowed events, order of events, … I bet you can improve codes for your purpose.

BKeyport

@MMRIZE that would be perfect, yes.