But then still, after starting you would instantly see the message, right?

Margin issue should be fixed now.

Indeed, when hidden it is pushing down other modules. Will fix this in an upcoming release. (This is actually a core issue … When it’s hidden. It should not push other modules down.)

I’m not a fan of an alert since these are very obstructive. In some cases you won’t have the time to immediately update. If we use notifications, these would stay in the way.

Since most mirrors aren’t restarted very often, a message at start up would not make much sense.

@Jopyth exactly. Wich wouldn’t make much sense.

The new default module updatenotification will display a message whenever a new version of the MagicMirror application is available. It will show the number of commits behind on the current branch and the name of the active branch.

The new module is included in the new sample config. Make sure you add it to your own config if you want to add it:

{
    module: "updatenotification",
    position: "top_center"
}

This module uses new default translations. Any pull requests with translation in other languages are welcome! (English and Dutch already included.)

It would be nice if you can extend the module with hide/show options:

 {
    keyword: "simpleMode",   // keyword 
    description: "Say 'Simple Mode' to switch to the simple UI.",
    file: "simpleMode.pmdl", // trained model file name
    message: false,   // Unused in this command. Can be omitted.
    show: "simple foo bar",  // Show these modules.
    hide: "advanced" // Hide these modules.
}

When activating this command, it shows all modules with de classes defined in the show variable. And it hides all modules defined in the hide variable.

When implementing this, make sure you use the Visibility Locking mechanism that will be introduced in version 2.1.0: https://forum.magicmirror.builders/topic/241/2-1-0-api-revising-the-show-hide-mechanism/9

@Jopyth: The problem is that there is no way to find out which module requested the hide method. Therefor I can’t use that identifier by default. This must be provided by the module itself.

It works perfectly fine on a Mac. To be honest: this was one of the goals during the development (because of this project: http://michaelteeuw.nl/post/150349424992/mirror-mirror-on-the-wall-who-has-the-biggest-of).

To install it, make sure you have the latest version of node installed. You can download the installer here: https://nodejs.org/dist/v6.8.0/node-v6.8.0.pkg

Next, open your terminal, and clone the MagicMirror² repository:

git clone https://github.com/MichMich/MagicMirror.git

Then, go to the MagicMirror folder and run the installer.

cd MagicMirror
npm install

Make a copy of the sample config to your custom config:

cp config/config.js.sample config/config.js

Run MagicMirror to see if it works:

npm start

If everything works fine, you can modify your config to match your preferences …
If you want to run it full screen on a mac, you might want to enable the kiosk mode in the config. (See documentation: https://github.com/MichMich/MagicMirror#configuration)

Enjoy!

Starting from version 2.1.0 (currently the develop branch) the default modules will add the following functionality: Possibility to use the the calendar feed as the source for the weather (currentweather & weatherforecast) location data.

When the location and locationID are both not set, the location will be based on the information provided by the calendar module. The first upcoming event with location data will be used.

Since this feature is still in the develop branch, it’s not final and might change. Suggestions are welcome.

@darrene It’s available in the develop branch now. Happy coding!

Starting from MagicMirror² v2.1.0 (currently in develop stage) the default calendar module will broadcast all the events to all other modules with the notification message: CALENDAR_EVENTS. The event objects are stored in an array and contain the following fields: title, startDate, endDate, fullDayEvent, location and geo.

Since this feature is still in the develop branch, it’s not final and might change. Suggestions are welcome.

An other small suggestion: delay all show effects with the a delay equal to the animation time. This way all Modules that will need to hide will nicely hide before any new modules fade in.

No, the translations are frontend only.

About the translations: just make a modular specific english translations file. When that is done, others can send you a pull request with other languages.

One other feature request:

It would be nice if there is a way to schedule a hide show based on a classname. This way I can give all my modules a class like “day” and “night”, and make a schedule:

 {
        module: 'MMM-ModuleScheduler',
        config: {
            visibility_schedule: [
                {classes: 'day', schedule: {from: '0 6 * * *', to: '0 22 * * *' }},
                {classes: 'night',  schedule: {from: '0 22 * * *', to: '0 6 * * *' }}
            ]
        }
},

It might be a good idea to make use of the available translations. The words “Today”, “Tomorrow” and “Day After” are all part of the system translations. Check the documentation on how to use it. :)

Most of the time when I develop, I run server only mode and test most of the work in a default browser.

Very awesome work on this module! It might be interesting to look at the new show/hide mechanism: https://forum.magicmirror.builders/topic/241/revising-the-show-hide-mechanism/9