Read the statement by Michael Teeuw here.
Problems With Weather
-
Well, I’m not going to do that because the module is deprecated. Doesn’t make much sense to me. If you feel the need, have at it. :-)
-
@csoogos said in Problems With Weather:
How do I run the mirror from within the directory?
- Open a terminal
- Change directory to MagicMirror. Usually done by
cd MagicMirrorunless you installed somewhere else. - Then
npm start
-
MagicMirror is a web page (see index.html) loaded by a browser (electron)
the main core of mm is a JavaScript wrapper around standard dynamic html, which allows api calls to manipulate the web page (DOM) content.
there are predefined areas (positions) for scripts (modules) to place their content in.
the mm runtime calls the module to get it’s content contribution. and then puts that content in the position defined for this module (in config.js module entry)all content is provided by module entries in config.js otherwise the page is empty ( see index.html)
some additional functions are provided by the runtime.
inter module communications, by way of typeless broadcast messages. the receiver must understand and handle the data format of any message it proposes to process.
due to browser security constraints, a module (running in the browser) cannot access the file system or any hardware.
so a ‘server’ side module component is launched in the background, ‘node_helper’… which CAN , and communications are supported between the helper and the browser module code, in a similar way as between modules. except the flow is only between the module and ITS helper.
the implementation of the helper/module communications supports messaging over networks, so the helper is where the ‘server’ is and the browser can be where the user is… the browser can be any es6 or above browser
electron chrome firefox edge…
as it’s a web page all the standard css techniques are available to style the content, by module or collectively…
-
@csoogos Not sure I’ve seen calcium temperature LOL
-
Rolling
