Would be interesting to see what happens if electron 6 gets installed.
Anybody here ready to give it a try and crash his mirror?

@sdetweil
Thanks Sam!
As for the getDom() method: Is this being called separately for every module or called for all modules when one module requests it?

I see I have to dig deeper into the MM core code…

@DavidBhai
First there’s no example.
Second: are css selectors what you are looking at?
https://www.w3schools.com/cssref/sel_hover.asp

I think I understand (and like!) what you are trying to do, but the downside is that you’re going to create one hell of a file. The module configs are in a lot of cases much bigger than what the module creator suggests users to change. The clock you’ve shown is a very good example.

However, it might lead to a very promising function, so I’d be happy to support.

I would very much like to see the web interface to be limited to layers with a drop-down function
First layer: all installed modules.
Click on a module -> open dropdown with all config parameters for this module.
(Somehow) limit the possibilities to change config options to prevent semantic errors. E.g. for boolean parameters, the user should only be able to switch between true and false. String parameters should be converted to strings automatically. Numbers be parsed to number and so on…

If you create a web interface that gives the user the possibility to easily change config options AND that prevents semantic errors (e.g. by checking the new input instantly).

…then you’re the hero!!

The more I write about it the more I like it…

Is there somethin on github that I can have a look at already?

I really need to get some sleep, but before I’d like to place a question.

Considering I have a module with a .njk template running, I do not understand what function/procedure is called at which point.
I guess there could be some flowchart to visualize. However, I am not sure, e.g. at which points exactly “getTemplateData” is called.
In my module it seems to be called right at the beginning although I have not invoked any getDom or updateDom yet (at least I don’t now of any…).
Hope the problem is understood and happy for any insight.

Also I have recognized that for some modules the start process is called twice and any setTimeout cycle as well.
This at least counts for the npm start devmode. So you can have e.g a 10 minute cycle calling an api. This is for several modules called twice in the beginning. Is this linked to the two “sockets” being used for the monitor and for an external browser?

@dnovacik Well this module uses the strava-v3 nodejs library by unboundev.
github link.
I guess that is where the new token procedure should be implemented isn’t it?
Care to take a look?

@earlman I have to say I really love the grid concept. I have a monitor sitting in the lower right corner of the mirror and a grid design would look much better.
Can you share your main.css or is it on GitHub?
Sorry just saw the latest reply with all the information I needed. Thanks man!!

@MistriHD said in On-Demand Music:

So you’re saying that it’s illegal to use the Spotify client?

No he didn’t say that.

@MistriHD it is as it is. Ripping is against their eula. Sean is of course right. The songs you download through their app have a protection so you can’t use them elsewhere. If you download and save an mp3 it’s against the terms. Obviously.
And I for myself would never do such thing.
Never!!

@evroom said in Blank mm after update:

In my case a
$ npm audit fix

solved the dependency issues it found.

The npm audit warnings do not create any problems in running the mirror as far as I know. They also do not show up in the pm2 logs.
I would even be very careful as an inexperienced user to do that. “Fixing” these npm warnings on the root MM install could break the whole mirror (not the mirror itself of course :-)). Especially if you mess with the electron/chromium dependencies.