MMM-Page-Selector: A page switcher that can set positions of modules

Veldrovive

@rudibarani
Good stuff. I’m glad everything is working out.

rudibarani

@veldrovive I got the second page layout working with MMM-Watchdog: added a position-value to each module as you suggested and changed the settings to a heartbeat of 5 sec and a restart interval, in case the feedback is not sufficient, of 31 sec. Maybe the default values where just to tight and interfered with your tricks to layout the pages.

How does MMM-Page-Selector decide about the order in which modules within the same location are stacked on top of each other? I have would like to move an instance of MMM-DWD-WarnWeather below MMM-MyWeather but changing the order in the “pages” part of the layout does not have an effect on the order on the screen.

Veldrovive

@rudibarani Good to know that’s a solution.
Right now, modules are stacked in the order that they appear in the config file. If a module is above another in the config, it will be above that other one on the page.
However, with a little work, that could be changed. Do you think that it would be helpful to be able to change that on a page to page basis?

rudibarani

@Veldrovive The order seems to be exactly the other way round - if module A is below module B in the config file, it will be above module B on the mirror.

I guess it would be quite intuitive if the second layout option would sort the modules on the screen in the way they are ordered in each page definition. This would also support the concept, that the module definition contains the configurations and the pages part contains all the layout.

Personally, I would also benefit from this option as I use CSS styles to e.g. show only the weather warning symbols on one page and only the text version on another page. Both would be in different positions, if it were possible.

Veldrovive

Oh, that’s odd that it is going in inverse order. I must have made a mistake somewhere. I’ll be looking into that and reversing it.

I have finals coming up soon which means I don’t have very much time to support this and a more intuitive way of ordering the elements will take a bit of time.

Can you clarify what you mean with your last statement? If I am interpreting it correctly, you are saying that you would like a way of specifying CSS for specific pages. If I’m not mistaken, this would be a pretty quick and easy change as I would just update the class list to include the current page name.

rudibarani

Thanks - including the current page into the class list would be helpful.

From the usability point of view, having all layout-options in the “pages” section would be clean and intuitive. Going in from the outside, one gets easily that the modules part contains all config elements and the pages part does the layout of the pages.

Having the order of the config-elements in the “modules” section play the central part in sorting everything seems a little odd. It is OK - once you know it - but also involves moving around the modules and risking bracket- and comma-errors every time you want to try a new layout.

rudibarani

Dear @Veldrovive,
I am trying to use an old MacMini to host a mirror, as I would like play BluRays and Amazon Prime Videos on my mirror as well. Everything works fine - except for the option to save the current page.
Frist, I thought this might be a permission issue - but even setting the MagicMirror folder and all its contents recursively to “chmod 777” did not solve it. The mirror always goes back to the standard page and not the current page. Setting “persistentPages” to true does not have any effect.
As you know how you store and restore the “current page” - do you have any idea how to get this going again?
Thanks a lot for your help!

Veldrovive

Hey @rudibarani,
If there are no errors being thrown, then I would make sure that you are on the development branch and not master as I am still not sure how stable some changes are so I am refraining from merging.
If that is not the problem, I would open up thenode_helper.js file and put console.log() statements in some places to make sure they are running correctly.

Line 30 should be self.restorePage(). I would put on right before that. If it never runs, then there is a problem with how the frontend is handling the config.
Line 38 should then be jsonObj = JSON.parse(obj);. I would print out the value of jsonObj right after that runs to see if the page key is in it.
Line 57 should then be reject(err);. I see that I accidentally didn’t include any debug information when this rejects so put a log that prints out the error directly before this.

If the problem isn’t immediately obvious, posting the output of those logs would go a long way to figuring this out.

rudibarani

Dear @Veldrovive,
oh - I have to run and hide somewhere. I did forget to clone the development branch when setting up the Mac Mini. Sorry for bothering you with this :unamused_face:

As always, if you do things right, they work :smiling_face_with_smiling_eyes:

You said you it would be a quick change to update the class list to contain the current page. If you have time to add this, it would help me a lot!

Veldrovive

Ah right. I need to get around to making those changes. I’ll start on them in the morning.