The top calendar in the first example is perfect apart from the colours .
The default modules are a sort of ‘Theme’ I have been sticking to but the one I have been thinking of maybe trying but like said I really suck at css / html.
If the first one was just subtle greyscales where and when needed it would be perfect.
First one apart from the colours as trying to keep all greyscale across modules.
Layout is great on the first one but boy it just doesn’t fit.
Even my MMM-News is grey thanks to eouia with:-
Add this into your css/custom.css
#NEWS .articleImage {
filter: grayscale(100%);
}
You can use other filters like sepia or blur, etc. See https://www.w3schools.com/cssref/css3_pr_filter.asp
pi@raspberrypi:~/MagicMirror/modules/MMM-MovieInfo$ npm install --productive
npm WARN deprecated browserslist@1.7.7: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
npm WARN deprecated circular-json@0.3.3: CircularJSON is in maintenance only, flatted is its successor.
npm notice created a lockfile as package-lock.json. You should commit this file.
added 384 packages from 448 contributors and audited 1138 packages in 799.653s
found 1 low severity vulnerability
run `npm audit fix` to fix them, or `npm audit` for details
Node about 0.3%
{
module: 'MMM-MovieInfo',
position: 'top_right',
config: {
api_key: '50543fe5151a1e58768462815ce4d0f8',
discover: {
"primary_release_date.gte": "now", //now
"primary_release_date.lte": "month" //day, week, month, quarter or year
}
}
},
Well didn’t expect it to work but working ?!
classes: ‘small’,
remoteFile: ‘xxxxx.json’,
updateInterval: 126060*1000,
Is that all you need to do to partition config.js?
As that is a top tip and ‘small’ ? remoteFile: can that be a local folder such as the corresponding modules folder?
@lavolp3 Yeah hence why I was so surprised at what it fetched. It did look like the whole install again but in the mmm-movie module directory.
Actually it wasn’t to be honest as it only took 10 - 15 minutes whilst mm takes approx 35 - 40 on the zero.
I will give it a go but just not yet as just want to see if I can find ‘my’ perfect set of modules for what I would call ‘my’ complete mirror.
I was almost there and finishing things off and did my usual of romping ahead without saving copies of config so starting from scratch.
I will give it a go tomorrow as I am expecting on a zero if you do a --productive first that is what kills things.
Also I think I have hit the worst thing about the zero and not running electron as I will not have any console logs?
I think I can get them with the selenium webdriver for chromium but haven’t been back since I was playing with it.
Or at least I can get some form of log browser side as at the moment I have none but then again could just do it with a command line input I guess.
Decided not to as have a hunch on what is happening as saw it download electron last time.
It prob bypasses the server-only and guess launched electron on a Zero I will just leave it for someone else as it takes just too long to install on the Zero and will try it another time when I have the time to kill and install.
I really suck generally but even more so with CSS & HTML :)
https://codepen.io/afontcu/pen/bapBxv but https://freefrontend.com/css-calendars/ have 35 to choose from :)
Actually thought if the colours where flipped and pink went of the action https://codepen.io/tomcwatts/pen/PmaWpZ would actually be quite cool.
Maybe it Pi Zero then I will do it once more… :face_screaming_in_fear:
About an hour to reinstall on the lowly pi0w though
The module folder was full of folders after that and Node was just choking the CPU @ 97% with PM2 trying to restart.
Someone else give it a go as I have done it once already :)
Dunno :)
Installation
Clone this repo into ~/MagicMirror/modules directory.
Get a free api_key here
Configure your ~/MagicMirror/config/config.js:
{
module: 'MMM-MovieInfo',
position: 'top_right',
config: {
...
}
}
Run command npm install --productive in ~/MagicMirror/modules/MMM-MovieInfo directory
Followed the instructions and on reboot NPM was taking up so much resources couldn’t connect the client and the mmm-movie folder was littered with js folders.
Even after deleting that folder and removing from config.js my MM became a Norwegian Blue and positively deceased.
--production --productive
Guess it was as now to reinstall.
Run command npm install --productive in ~/MagicMirror/modules/MMM-MovieInfo directory
What does that install!? Seems bigger than MM itself?
Many thanks got similar great info from discord as never have patience, apols.
One last thing as I said because I have done a little script for Pi Zero https://github.com/StuartIanNaylor/MagicMirrorPi0StretchLite that has chromium with all the commandline settings need for the above.
I said to Mich I was just looking @ Selenium as thinking of doing a Chromium watchdog and he suggest mm_watchdog.
Then I barbled on but with hindsight does mm_watchdog also work with standalone chromium?
As if so all I have to do is work out why plymouth confuses me so much as to if it will work or not and maybe show on whatever chance that might maybe :)
Thanks for a great explanation though.
One more question is how do you mark as solved?
Hi,
As I only have a Pi Zero at the moment I am just wondering what is the difference and advantage of electron rather than say chromium browser.
If it just bloat and the electron framework is just lightweight or are there extra advantages and calls via the client script?
Yes and actually multiple places as to which modules you installed as that is the whole point of dividing the config.js into smaller module based configs.
I am presuming it could also pre-parse and raise errors to which module the error is located.
Only starts getting relevant with complex setups as the base is extremely simple but rather than linux having a single file in /etc/… the config is divided to make working easier.
@sdetweil said in Divide Config.js into modules:
Well, there is one problem.
Once u put the info in each module folder, you will lose the ability to order the modules differently
Nope the modules are declared in /config/config.js not that I have much experience but my new noob experience of MM is that with complexity it starts to get a bit cumbersome.
As an example would you really want to add compliments to your main config.js.
I am just wondering if it could be split and presented slightly more cleanly and simpler for the likes of me.
module: "calendar",
header: "Calendar",
position: "top_left",
Would still be the same place and it would in essence just be the same but the bloat of
config: {
Would be elsewhere.
Also if it was loaded serially as different objects declared by config.js then each module config could have some form of isolation and error checking?
Gson gson = new Gson();
JsonObject jsonObj = gson.fromJson (jsonStr, JsonElement.class).getAsJsonObject();
jsonObj.add(“criterias”, “Location”);
Dunno as really know naff about NodeJS but thinking you could even make it more robust with feedback to which module config error?
Maybe hopefully this can be done, but I am having a lousy time breaking config.js from time to time.
Is it possible to have something like includes where you can have separate config.js for each module in its module directory?
@analogcheep give this a try as will need little programming and gives you bit more of the config
https://github.com/StuartIanNaylor/MagicMirrorPi0StretchLite
[edit]
Scrap that as after some playing now do things totally different and its much easier for the zero. Slightly unsure why such complicated methods exist for the pi0 as its really simple.
Haven’t even bothered with a script as its easy and the NodeJS tools are extremely user friendly.
https://github.com/StuartIanNaylor/MagicMirror-Install-Guide-Raspberry-0-to-3
Try that instead now I have a week under my belt with a zero and MM :)
Yet Another Pi Zero Installer.
https://github.com/StuartIanNaylor/MagicMirrorPi0StretchLite
Picks up the latest NodeJS LTS from the 10 series and creates sym links rather than dumping everything in …/bin so cleaner to remove and update.
Also will automatically pick the latest.
Stretch lite on the poor old wee zero isn’t that bad with MM running as above.
Automated installing just git clone and run the script.
"In the console ignore the password complaints and at the prompt pi@raspberrypi:~ $ type sudo apt-get install git Then press enter You will have to wait for some wonderfull Pi0 speed but next we will clone (copy) this repository to the pi. Then again at the prompt pi@raspberrypi:~ $ type git clone https://github.com/StuartIanNaylor/MagicMirrorPi0StretchLite Which you can copy by clicking on the green clone or download button and the copy command or just copy and paste the above.
Then either type or copy & paste chmod a+x ~/MagicMirrorPi0StretchLite/RaspberryPi0.sh && sh ~/MagicMirrorPi0StretchLite/RaspberryPi0.sh"
I have done some research on that and generally its a nope as the adhesive is designed for glass whilst monitors have various different coatings on them.
Its prob a no because they can not be sure of what a monitor screen will be but prob better safe than sorry.