With what you have taught me and with the changes to the Video Player and the Kitchen timer,
I am gonna try to apply this to a few other programs I have ready to convert from JQuery.

I am also going through @cowboysdude’s Recipe module to see how to get JQuery to actually work with MM.

Today, I am spending time RE-LEARNING javascript and how to apply it to MM modules. :upside-down_face: :upside-down_face: :upside-down_face:

Maybe it will steer me away from JQuery in the future! :winking_face:

You can load your jquery either with the above getScripts or you can do in the getDom … I have a few things working with jQuery… go look at my MMM-Recipe module…for an example of how I did it.

the base framework defines the page layout and regions. each module can contribute ITS little piece of content by returning the top element of that content starting with a div.

the getDom module function is responsible for developing and returning that div tree.

sometime AFTER the getdom function returns with the div object

var wrapper=  document.createElement('div')
return wrapper

the div will be inserted into the dom at the module defined location. (position)
note that multiple modules may contribute to the same location, in a FIFO order. (as defined in config.js)
element.appendChild(new_content_anchor)

any code inside getDom() that attempts to locate elements by ID (search the single page dom) will FAIL,
as the modules dom contribution has not been inserted until AFTER sometime getdom() returns the div element

the jquery code is executing inline of the getDom() function, and the element selectors

$('#more')  is same as  (document.getElementById('more')) 

will fail as the content is not IN the html document yet