That sounds like a great way of dealing with it, thanks Grant!
Haha, while I am getting a lot of requests, I am well aware that most will only be implemented a fair way down the track (as that is what time allows). So all they really do is give me a defined route for the development, which is great. I just hope everyone else is aware of this as well :lol:
My worry about a separate thread is that keeping two things going like this (thread and github) is a recipe for things getting missed and take extra time. My view is that there should be one place and to me the sensible option is github as that is what it’s for - developing projects. A simple update here when a new version or point release is available is in my view all that should be required.
While I’m at it one more request (if not already mentioned) 
I believe the solar and UV should be optional as not everyone has these, actually far fewer have UV than solar.
Stuart
It is possible without the altitude button and also no solar and UV bar.
I see you have managed to change the labels language?
Yerren,
Perhaps it’s just my tired old eyes but, I am having difficulty seeing the difference in color of the flashing doughnut which indicates current, stale or no data coming in. The difference in the green (I think that is what the color is supposed to be) and gray is very difficult for me to see. Having a more distinct difference in color would make it easier for everyone to see a change in data currency. A brighter green, darker gray and brighter red would grab attention to this feature more quickly.
Yes, for the buttons you can do that in the InnerContent.js file.
I have already translated some labels and you can do that in the WidgetHandlers.min.js file. Not a nice way, but if you have a lot of time it is to do. In this file you have to look carefully where you can translate. The files can be downloaded from the Github of Yerren or look at the source code of my test page. You have to load the files on your own internet provider.
Goed gedaan!
You clearly know what you’re doing, and I am glad to see you’ve managed to work this out by yourself.
Honestly, it’s really not set up in a nice way to be editable, so I’m impressed. It’s looking really good, and I hope to make something like this easy for everyone to set up soon!
Do you have much web-development experience, or did you just figure it out? I’m just curious! 
Good plan, and it should be a pretty easy change. It will be snuck in next time I update things!
Yerren, many thanks for your selfless hard work on this!
All up and running here too.
Looking forward to the future developments with great anticipation.
Regards,
Paul.
Yerren, many thanks for your selfless hard work on this!
All up and running here too.
Looking forward to the future developments with great anticipation.
Best Regards from Canada,
Marian
I’m not sure what is happening here, but FreshWDL is hanging at the “Collecting data” point. All my “client” files are located in the root directory ie www.mikeymsweather.com/clientraw.txt etc.
Any help is greatly appreciated - Thanks
Cheers
:?
MikeyM
What’s the url of your FreshWDL page?
I’m a late comer to this thread, which Don kindly indicated in another forum.
First, amazing to have this older style, but still very nicely designed, program emulated with much more secure and stable work.
I have read some of the comments and the intricacies to make this work are beyond my grasp, but hats off to Yerren for his work in getting this up to speed.
While I realize this is still in the very early stages, alpha I believe, perhaps I can comment on a couple things. I think Don has already mentioned that the ‘heartbeat’ pulse in the upper left has colors from grey to light green that are far from adequate contrast for us older folks. Perhaps the green can be a really dark green, approaching the saturation seen with the Wind Speed green and purple.
Secondly, I have used the config.js file to select US units for my display. However, while the tick marks along the side of the daily rainfall are correct, the monthly and yearly marks are set at and stay in mm. In addition, when one cycles the various options for temperature from C to F and back, the inscriptions along side the thermometer change nicely. However the rain module only changes the area under each tube, and doesn’t affect the inscriptions or scaling along the side of all three.
Perhaps these are areas already identified, and I apologize for bringing them up again.
But it is all in my enthusiasm to see my old friend “WDL” gaining a new lease on life through the efforts of Yerren to bring it to this level.
Thank you. Dale
Goed werk PeeGee ! bedankt !! chapeau !
Got them from your test page works fine (out of the box for WDL html as well) thank you ! =D>
May not be the issue but I see a typo in “mph” in the config.js
wind: "mnph", //Options: "kmh" "mph" "kts" "ms" "mm" "inch"
Open config.js and correct wind units…
wind: “mnph”, //Options: “kmh” “mph” “kts” “ms” “mm” “inch”
to “mph”
It’s show stopper.
Gus
THANKS! =D> :D/ You guys are my heroes. That’s what happens when you do stuff at 1 am in the morning and I even checked and double checked it.
Thanks again.
Cheers
MikeyM
Can someone who understands the way this stuff works let me know if having this running on my web server which I rent from GoDaddy, is consuming their computer time, or does it somehow get loaded onto the computer of the person viewing FreshWDL, and only receive the packets with the updated values to then display on the viewer’s local computer?
If several folks are looking at the same time, are there as many instances of this code running at GoDaddy, and it’s computer is painting a new visual at very pulse, heartbeat, or refresh (whatever the correct term is now)?
Just curious as to where the horsepower is coming from, and while most of the time even I won’t be looking at the page, there may be times when I leave it up running constantly or if there is interesting weather going on several local folks may be viewing. I just don’t want to get a note from GoDaddy that I’m eating up more of their computer time than I get as part of my monthly fee.
Just curious. Thanks. Dale
This is an all JavaScript app … your webserver hosts the files containing the JavaScript (and the clientraw*.txt) files.
When the page is first loaded, the browser loads all the needed scripts from your website (and others), and after loaded, continues to supply the clientraw*.txt files as requested by the scripts.
The ‘heavy lifting’ CPU load is on the browser’s system, not on your webserver. The webserver will continue to respond to the clientraw*.txt file requests, but they have a negligible load on the webserver since they are plain-text files with no additional processing needed on the webserver (other than Apache offering the files to an http request).
Hope this helps…