Realtime Parameters Parsing

yours.mukul

@Sean can you please tell me a method to parse configuration after a module has been started ?

A Former User

@yours.mukul
More detailed information is needed. Exactly what do you want? Your question is so ambiguous.
As I guess, You may want to change URL of iFrame module at runtime.
First, there are several iFrame related modules. I’ve searched them from google.(https://goo.gl/jLVXsE) So, which module did you intend?

yours.mukul

@Sean The iFrame is just an example I’m giving here. My question is for every module, like a youtube module or google maps module or any other module. Is it possible to change parameters of any module at runtime ?

A Former User

@yours.mukul
I can say just case-by-case. There is no common way to manipulate other modules except official notification mechanism.

Every module works differently. Some modules are initialized in .start() with configuration values. In some reason, some modules are initialized when DOM_OBJECTS_CREATED notification received.(Yes, I usually use that.)

So, what is your real intention? Just to get and change module.config? Yes. you can access module.config.

MM.getModules().enumerate((m)=>{
  console.log(m.name, m.config)
})

Test it when modules are loaded.

However, just modifying that value doesn’t work as your wish. Modifying is available, but the result might not be something you want.
Every module uses configuration values by their own convenience. So, if you could success to change the url value of MMM-SomeIFrameView at some specific time, That doesn’t mean changing the view of that module automatically. Because that module wouldn’t use that value anymore after once used in .start(). In that case, your modifying is just useless.

Therefore, I just can say case-by-case. There is no common way for your wish.

yours.mukul

@Sean
what if i reinitialize the module after parsing the value or what if I just refresh the module after parsing the value ?

A Former User

@yours.mukul
Maybe you can do like this;

MM.getModules().enumerate((m)=>{
  m.config = YourNewConfig
  m.start() //  Yes. It works!
})

you can execute .start() of other module like above. But It could cause the serious problem for other modules. Maybe clock or other simple modules could work well. But some modules might have huge complexity and not bullet-proofed. (no one has not imagined his module could be re-configurable.) Twice initilizing is not recommended.