Read the statement by Michael Teeuw here.
Seperate Config for Web Access
-
@sdetweil Thanks for the suggestion. I was hopeful as the style inspector showed that I could pretty much do what I wanted with
.MMM-BackgroundSlideshow { display: none; }
Unfortunately, I wasn’t able to get it working based on the info in the link you sent. I did a little more digging and it looks like both Chrome and Firefox removed support for user stylesheets a few years back. My guess is that even if I could re-enable it (or find some extension that mimiced it) on the desktop, doing so on the mobile browser would probably be much difficult and/or impossible.
Do you know if the ability to have multiple configurations has been suggested before as a feature request? I’ve been mulling it over and I think I might have a way to implement this (in a limited sense) in a simpler way that wouldn’t require multiple config.js files.
-
@cweinhofer I have not seen such a request
the code loads all the modules and style sheets once
only thing I can think of is to have another module that can determine the client IP identity and use that to show/hide modules. as that is all mm can do currently
-
@cweinhofer try this… this what I was thinking before
https://www.trysmudford.com/blog/chrome-local-overrides/
it still works
then u could do like MMM-Pages
specify extra classes:
for the modules U want to show on client 1, and client 2
then in the overrides custom.css show that class
I think css is top down, so you could hide all of them (display:none)
and show only the one u care about here later (further down)takes a bit of setup on each client… make the folder, add the subfolders, turn it on in dev window for that url
one thing, if you use the display: none approach, the apis will still be called, and the module will still create the content, and then the browser will be told not to display it. the module does not know it’s content is hidden
-
-
-
@sdetweil Thanks for the updated alternative.
Unfortunately, it seems like this feature is only available on the desktop. In my case I’m using Android phones and/or tablets for my remote displays. I’ll be interested to see what the guy using the FireTVs and/or AndroidTVs is able to do.
Anyway, I wrote up a feature suggestion that would allow for what I want and posted it in that category.
https://forum.magicmirror.builders/topic/17226/seperate-config-for-web-access
-
@cweinhofer as mentioned over there, open an issue on GitHub for the project owners to examine
many old I* devices don’t support the es6 JavaScript operators that most of us are using and going to. so the code won’t run. don’t know about android, but would expect the same problem
I know there was a PR a couple years ago to restore the old operator based code, but it was not selected