Problem solved! 80-100 METERS of illumination!

At the moment, the module only does one at a time. If you’d like it to do more, you’ll have to write your own module. We welcome pull requests on modified versions of the defaults.

And yes, I suppose simply 'purge' would get the job done, but there are times I only want to remove the binaries, but leave my config files in place. I prefer forcing myself to actually add the '--purge' bit each time … sort of a mental check.

@MichMich, it is, by default, B/W. Users can set a custom CSS to change the colors, like I did as a test.

You need to be inside of the MagicMirror folder for that to work.

It won’t be the “default” style, but the config will set it as 'default'. The reason is because the actual 'styleDefault.css' file needs to be clean and not have anything in it other than setting the proper margin, padding, and table/cell views for the calendar and it gets included always. Custom CSS files are pulled in on top of that. That way, the user doesn’t need to set any of that themselves, but rather just over ride what they want with their own styles. So I can have a 'styleMichMich' [*] that I can set as the default style to have today highlighted in a white box.

[*] actual name to be determined still …

Never mind, went a slightly different route …

@patm189, my config is in the post above yours. I actually have 3 calendars listed that way.

Thanks. Slowly working through it.Need to roll in those multi-day events … seeing some stuff from our work calendar that isn’t displaying correctly … yet. Just a matter of proper parsing and displaying …

Those are configuration settings that are explained in the wiki. However, it’s worth noting that it only works if you have the 'x11-server-utils' package installed as you’ve discovered. On a stock Rasbian Jessie install, that package does get installed, but I suspect those with different distributions, or a Jessie-Lite install won’t have that. I’ll amend the wiki shortly. Thank you.

So just looking at this, and all you amazing folks who are eager to jump in and start writing code … seriously, you all should. That’s no joke … start somewhere. There’s plenty of information on the web, and several folks here who can also help.

Anyway, my take on this:
Doing a local folder with pictures, while possible, also adds a lot of unknowns. For example, the images might not necessarily all be the same physical dimension, and loading one might go really fast while loading another will be rather slow because it’s so much bigger and you’re scaling it down. Or, or you pre-process your images to a specific size and then upload them to the rpi. BUT! Why do that when there are services out there that automatically do that for you? Let’s look at options:

Flickr has a public API: https://www.flickr.com/services/api/
They even have a node.js API kit making it easier to integrate: https://www.npmjs.com/package/flickrapi

iCloud API … iCloud API … anyone, iCloud API? (sorry, Ferris Bueller reference there.)
Same goes for Facebook …
And unfortunately, also Google Photos. They terminated development on the Picasa API on May 1st, but have yet to open their Photos API to the public. So you’re stuck using the Picasa one for now till they completely shut it down, at which point you can only hope they would’ve released the new one.