@Sean Thanks for all your help! I just pushed the release with these three added.
Read the statement by Michael Teeuw here.
Best posts made by j.e.f.f
-
RE: Help Translating Word Clock
-
RE: MMM-OpenWeatherForecast - Replacement for MMM-DarkSkyForecast
@fillilutten said in MMM-OpenWeatherForecast - Replacement for MMM-DarkSkyForecast:
What css do I do to change color of the slash in H/L in “extraCurrentConditions” ?
Yes:
.MMM-OpenWeatherForecast .temperature-container .temperature-separator, .MMM-OpenWeatherForecast .forecast-container .forecast-item .temperature-container .temperature-separator { color: #FF0000; /* makes it red */ }
@fillilutten said in MMM-OpenWeatherForecast - Replacement for MMM-DarkSkyForecast:
And can I remove “Powered by OpenWeather”?
Yes.
.MMM-OpenWeatherForecast .attribution { display: none; }
-
RE: Renault ZE Online
@fallandegubbe this is a great project to learn how to code, and JavaScript is quite a forgiving language, so it’s perfect for beginners. What you’ll need to do is pretty straightforward and common for MM modules.
First search for an online JavaScript 101… plenty of free resources available. Then download and examine the code for an existing module as a template to get an idea what the structure looks like. Finally do a bit of Googling to learn how to do specific things like make an AJAX for API data, and how to programmatically create HTML markup.
Try to keep it simple from the get go. You can accomplish what you want to do without anything fancy like a Node helper File or even an external CSS file. Once you have a working module (which will quite a satisfying accomplishment — congrats for sticking with it!) you can make improvements in order to learn some of the more advanced stuff.
You can do this! Speaking as someone who does not code for a living, nor would I consider myself a “programmer,” I can confidently say that you can learn everything you need with a couple days effort and liberal Googling, a dash of determination to stick with it. Also, this forum is a great place to ask questions when you get stuck. Lots of us got started in the exact same way.
Once you’ve finished your module, you can get the fancy “Module Developer” badge beside your name too!
-
RE: MMM-OpenWeatherForecast - Replacement for MMM-DarkSkyForecast
@fillilutten said in MMM-OpenWeatherForecast - Replacement for MMM-DarkSkyForecast:
Any way to change the order of the different extraCurrentConditions?
This is technically possible with CSS, but it’s likely more trouble than it’s worth for me to explain it here, and error prone. A better and easier option for you would be to modify the
mmm-openweather-forecast.njk
file to reorder these items as you like.Starting on line 39 you’ll see the templates for the extra current conditions. The order in which they appear here is the order in which they appear in the module.
Here are the first several lines of that section:
{# -------------- Extra Current Conditions -------------- #} {% if config.showExtraCurrentConditions %} <div class="extra-current-conditions-wrapper small bright"> {# -- High / Low Temp -- #} {% if config.extraCurrentConditions.highLowTemp %} <span class="temperature-container"> <span class="high-temperature">{{ forecast.currently.tempRange.high }}</span> <span class="temperature-separator dimmed">/</span> <span class="low-temperature">{{ forecast.currently.tempRange.low }}</span> </span> {% endif %} {# -- Sunrise -- #} {% if config.extraCurrentConditions.sunrise %} <span class="sunrise-container"> <img class="inline-icon sunrise-icon" src="{{ inlineIcons.sunrise }}" /> {{ forecast.currently.sunrise }} </span> {% endif %} {# -- Sunset -- #} {% if config.extraCurrentConditions.sunset %} <span class="sunset-container"> <img class="inline-icon sunset-icon" src="{{ inlineIcons.sunset }}" /> {{ forecast.currently.sunset }} </span> {% endif %}
Say you wanted the Hi / Lo temps to display after sunrise / sunset, just move the whole block as follows:
{# -------------- Extra Current Conditions -------------- #} {% if config.showExtraCurrentConditions %} <div class="extra-current-conditions-wrapper small bright"> {# -- Sunrise -- #} {% if config.extraCurrentConditions.sunrise %} <span class="sunrise-container"> <img class="inline-icon sunrise-icon" src="{{ inlineIcons.sunrise }}" /> {{ forecast.currently.sunrise }} </span> {% endif %} {# -- Sunset -- #} {% if config.extraCurrentConditions.sunset %} <span class="sunset-container"> <img class="inline-icon sunset-icon" src="{{ inlineIcons.sunset }}" /> {{ forecast.currently.sunset }} </span> {% endif %} {# -- High / Low Temp -- #} {% if config.extraCurrentConditions.highLowTemp %} <span class="temperature-container"> <span class="high-temperature">{{ forecast.currently.tempRange.high }}</span> <span class="temperature-separator dimmed">/</span> <span class="low-temperature">{{ forecast.currently.tempRange.low }}</span> </span> {% endif %}
Keep in mind that doing this will make it a touch more difficult to update my module as I release updates. When you want to update, you’ll need to to the following:
- Make a backup of your modified
mmm-openweather-forecast.njk
file (copy it to another location, for example) - Restore the original with
git checkout mmm-openweather-forecast.njk
- Update the code with
git pull
- Restore your modified version of
mmm-openweather-forecast.njk
from your backup
- Make a backup of your modified