I think you can add the caledar_name selector too from the ext3 doc .event` : Every event has this selector. Each event could have these class names together by its condition. - `.continueFromPreviousWeek`, `.continueToNextWeek` - `.calendar_{calendarName}` <-------

@sdetweil Modern browsers can directly import ESM through JS regardless it exists locally or externally. . (Anyway, the above code works really.) Loading ESM via <script type="module">tag will probably be the one way but It will have a global namespace scope. I’m afraid of the risks of collision among MM modules that might be using the same namespace. getScripts() doesn’t support script type. So some codes for injecting proper script tag is needed by the developer himself, To load ESM with MM-module-level scoping, using import() and binding the namespace to the MM module would be possible. however, there will be some pitfalls, import() is an asynchronous function. To prevent referencing unloaded ES modules or to avoid handling of DOM by ES Modules before DOM is created, so some tricks might be needed to confirm everything is ready. (Above my code is that.). So I’m just seeking another or better way if exists.

@MMRIZE Thank you for your quick reply! I really appreciate you taking the time to provide an example for me to work with. Most of this makes sense, despite my lack of programming skills. Can I use the predefined PageDown animation within the custom definition? I’d like to avoid having to remake animations you’ve already provided. My other question is how do I set temporary identifiers to the modules so the correct animation gets pulled? I don’t think module name or classes alone will work since I need the identifier to change based upon scene selection. Nor do I want to load multiple instances of the modules as I’m already pushing the heat up a bit. Please forgive my ignorance here, I’m sure it’s already well documented, I just don’t know where to begin.

@Tiller awesome!! thanks for the feedback

@cowboysdude Yup, Every developer can implement his own logic to display time-related stuff. And hundreds of MM modules are there, so hundreds of implementations are existing also, just to display “in 15 days”. I think it is a kind of waste. So I propose a reusable common HTML tag anyone can use anywhere. But the most benefit of this custom tag is, in my thought, Customizability and Locale-awareness separated from the module itself. Logic-neutral HTML tag could give the ability of easier user-customization without the developer’s effort. That is the purpose of this custom tag.

@marcelino The panel has a dedicated control board that has HDMI(for video and sound, yes, that cased-kit includes also stereo speaker set) and micro-USB(for power and touch input)

@mmrize Gotcha. Cool.

@MMRIZE I think he sees icons in front of the weather module, doesn’t realize MM is the desktop