My knee jerk answer is to find the model of the screen, and search eBay for a driver for it. The driver board will have the ribbon cable you need to connect to that, and the board will have the standard HDMI input on it. Simply typing in ‘lcd driver board’ on eBay’s search bar will get you a long list of them. By also entering the model of the screen, you can narrow that down.

@MichMich, oooooh. I was about to start a new topic and demand access to those 'frowned' modules! :)

@MichMich, uh, een momentje, but what are 'frowned modules' ?

There are no clear rules for creating topics or responding to posts on forums in general. Each one is different, each one will have its own set of rules to abide to and what you can or can’t do. However, what we can do is offer guidelines. So here goes:

1. If you are a new user, please take the time to read the Announcements topic. Besides a warm welcome from the creator of MagicMirror, other forum specific announcements will be available there.
2. Search the forum to see if your topic is already covered. Perhaps another user had the same issue, perhaps a solution has already been posted.
3. Try to post your topic in the relevant forum section. This I can not state often enough.
4. And with that, stay on topic! If you’re responding to someone else’s post, please stay on topic and don’t interrupt the topic of discussion (or hijack their topic.)
5. When posting pieces of code, please use the available markdown to better highlight those sections. If you need help with the Markdown, please see this page on commonmark.org.
6. Please do not double post, as in, don’t post the same topic or question into multiple different categories. Not only does it make it difficult to follow a thread, it’s makes it hard on yourself to follow where someone has said what, and who’s responding to what. If you’ve posted something and you think it’s in the wrong category, let one of the admins know and if they feel it doesn’t belong there, your topic will get moved into the correct category.
7. When replying to a specific post, mind the quoting of the previous message in yours. If a post is right above yours and all you’re doing is responding with a ‘Yes.’, ‘Me too.’, ‘Where to get that?’, there is no sense in quoting the message. You can delete it, or click on the ‘Reply’ button below the thread as opposed to the message itself. If you DO need to quote someone, consider trimming the message to only the relevant parts that pertains to your response. Quoting entire messages just adds more stuff to scroll through and read and things get lost.
8. Be civil with each other, act in a give-and-take manner, don’t chastise a new user, instead help guide them. And particularly because this forum happens to have folks from several different countries with different languages, try to speak in a way that others will understand you. Using slang might be understood by some, but not others. The same applies to humor, some people might understand you, and others might not, and yet others who might get offended. I’m not suggesting you be strict and dry as a shriveled up prune, but just be mindful of the language barriers here.
9. Please use expressive titles that do not just consist of one word but give you a impression of what the topic is about.

Am I boring you yet? Well good, you read this far. :) Seriously folks, have fun, enjoy, post your mirror issues, questions, or other relevant topics. We’re all here to learn from one another, and showcase our work.

Go forth and code!

Yeah, I hear you there. I’ve been trying to recreate the problems on my end but … no such luck. It runs flawlessly on my server, both as a super user as well as an unprivileged user. So something happened on his end with he switched things … maybe permissions … maybe something else. We’re trying to figure that out. You … you keep your focus on MM. :)

Mainly GitHub for Windows (which is a GUI). And it’s really only for committing my changes, and syncing them back up to GitHub (online, into my fork). The only time I drop to command line is when I need to merge the upstream repo (so I stay current with stuff that you merge in.)

But the problem is that I have a tendency to push stuff up to GitHub (online) several times during the day, as opposed to just once at the end of the day. This then creates multiple commits in the PR. If I squash all of my commits into one, just prior to syncing, then the PR will only have 1 or 2 items in it, as opposed to one for every single commit I made throughout the day.

It’s a matter of changing how I interact with GitHub, which I suspect would be the same no matter what application I’m using.

So the short answer is to squash my commits prior to syncing to GitHub. Easy enough … I have to remember to do it and only sync once per session, so like at the end of my work day, or at the end of the evening at home. That should then create a cleaner PR. This is to be tested next … after I get rid of the current fork that I have that has dozens of commits on a PR (because I synced dozens of times.) Get rid of it, refork, add my stuff back in, and then get a clean(er) PR done. Oy … headache.

Also note the warning as stated on the wiki page:
Note: If a file can not be loaded, the boot up of the mirror will stall.

Meaning, if you tell getStyles to look for a file called 'myStyles.css' but in reality it’s called 'mystyles.css' (case matters) or 'coolcolor.css', the mirror will stall and not load. So be careful.

The same approach applies when you’re creating your own custom modules. Keep in mind that if you edit the default files, a future update can overwrite them and you lose your changes.

By the way, that colorful screen capture was simply demonstrating that if you want to edit the default modules, you can, and you can then color them any way you want. In this case, I opened calendar.js and in the 'getStyles' section, I added another file:

        // Define required scripts.
        getStyles: function() {
                return ["calendar.css", "font-awesome.css", "mystyles.css"];
        },

In this instance, 'mystyles.css' is my custom one, which I then created and added my own colors to the various elements:

#module_1_clock .time, #module_1_clock .date {
        color: #99F;
}

#module_1_clock .dimmed {
        color: #449;
}

#module_2_calendar header {
        color: #F00;
        border-bottom: 2px solid #600;
}

#module_2_calendar .title {
        color: #F99;
}

#module_2_calendar .time {
        color: #FBB;
}

#module_2_calendar .symbol {
        color: #FF0;
}