Read the statement by Michael Teeuw here.
MMM-NOAA - Another Weather Module
-
@Zooooooom said in MMM-NOAA - Another Weather Module:
I would prefer not to mess with CSS files, because it would mean that updates might break my config.
No sir. Your config is unaffected by your custom.css entries. In fact, it’s the very reason there is a custom.css file, so that you can make those changes without changing the module files and you don’t lose your changes when the module is updated.
-
@Zooooooom put this in your custom.css file:
.MMM-NOAA .forehead {
display: none;
}
.MMM-NOAA .fmar {
display: none;
}after you do a git pull to update your NOAA css file :)
-
@Mykle1 Thanks, I didn’t realize that.
-
@cowboysdude Awesome, thanks!
-
I am using NOAA version 1 because I like this more than version 2.
Is there any problem going to be in the future with version 1?
Peter -
@Zooooooom said in MMM-NOAA - Another Weather Module:
@Mykle1 Thanks, I didn’t realize that.
You are welcome, sir. I see that @cowboysdude has given you some direct assistance above so I will bow out gracefully. Props to @cowboysdude for his wonderful module and fantastic support.
-
@Peter said in MMM-NOAA - Another Weather Module:
I am using NOAA version 1 because I like this more than version 2.
Is there any problem going to be in the future with version 1?
PeterNot sure what you mean. Do you mean you’d like to see future versions based on V1?
-
@cowboysdude yes; there are not going to be any updates for version 1?
Peter -
Same for me.
I will stay with V1, since the new one is too fancy (and way to big) for me.
Hope it will not getting corrupted by any changes with the new versions. -
Ideal would be to use the same core and develope different templates which could be chosen via config.