:fireworks: I’ve just released MagicMirror² :fireworks:

To make sure everything is future proof, I’ve moved around some branches on GitHub:

• The old version is now the v1.0.0 branch.
• The stable release is now the master branch.
• The development release is now the develop branch.

If you send an Pull Request, make sure you’re using the development branch.

Enjoy using your MagicMirror²!

If you just put the following items in your css/custom.css you can change the font sizes of the mirror by adjusting the values.

.xsmall {
  font-size: 15px;
  line-height: 20px;
}

.small {
  font-size: 20px;
  line-height: 25px;
}

.medium {
  font-size: 30px;
  line-height: 35px;
}

.large {
  font-size: 65px;
  line-height: 65px;
}

.xlarge {
  font-size: 75px;
  line-height: 75px;
  letter-spacing: -3px;
}

I’ve just overhauled the installer script.

It now checks if Node needs to be upgraded or installed and gives a bit more visual feedback. It will also prevent overwriting older installations.

If you can, please test it and let me know if it works for you.

Thanks. I’ve closed the issue.

It’s as if the glass shops don’t want to sell it. They gave me so many useless warnings when I bought mine … 😩

The reflective coating on the glass is a bit more prone to scratching as it can’t have a protective coating. But to be honoust: My 2 year old MagicMirror doesn’t have any scratches.

@danito lol

Yeah, probably gonna move current master to 1.0, move v2-beta to master, and create a develop branch. Agree?

Most issues seem to be solved, and the translation system is completed. I’m waiting for some feedback on the “wonky” time overflow, and might then move beta to stable.

What do you guys suggest to be the best approach? Shall we keep a beta repository as well?

@Wilco89 It looks like you figured it out?

Here you go: https://github.com/MichMich/MagicMirror/commit/c4f3009bb5ee60d57cbebdcd536e2bf488091a8c

Let me look into this …

@MechMatt: any news regarding the overflow. Is it solved?

I’ve just finished the translation system which now includes core translations files and a solid fallback mechanism. This way your modules can benefit from existing translations (in the core translations files).

All the translations used by the default modules are defined in the core translation files, making is easy to translate the core of the system. Of course, 3rd party modules should use their own translation files.

The translation files can be found in /translations . Pull request with new or improved translations are more than welcome!

Note: although comments are officially not supported in JSON files, MagicMirror allows it by stripping the comments before parsing the JSON file. Comments in translation files could help other translators.

If you built your own module, and you run into translation strings from which the core system could benefit (generic texts), feel free to send a PR with updated translation files.

Today, Electron 1.0 finally released. Since MagicMirror² is heavily relies on Electron, I thought it was worth sharing: http://electron.atom.io/blog/2016/05/11/electron-1-0

I did not have the time yet to test if MagicMirror² still works under 1.0, but my best guess is, it does.

@Simon Hi Simon. Do you know if the google API is supported under Electron?

@MechMatt good to hear!

@KirAsh4 Lol … those are modules that are modified by my auto correct… ;)

Btw, thats weird. Since it has no config. it should only load the hello world module. Which doesn’t use Log. :-/

There is something wrong with your installation. Since it can’t find your config file.

And, somehow you’re using a module that uses the Log.log function in a node_helper. Log.log is only available in the frowned default modules.