Hello Manuel, it is nice to see that there is still a few active participants in this forum...
actioman wrote:I also am not a programmer, but with your help and the humility to come here (day after day) to ask for help I'm getting to improve the meteoelvas.

The AJAX/PHP scripts/templates can be a good learning experience for 'serious' programmers wanting to learn something about PHP and AJAX/JavaScript - I have been and I am still learning from those templates...
actioman wrote:The ideal would be the fusion of standard HTM templates supplied with Cumulus pages with PHP (here in the forum, there is already some work in this direction).
That is what I have tried doing with my <link removed> templates/web pages, although most of the code did not come out of the AJAX/PHP scripts/templates.
actioman wrote:Then I have to think in a solution...
Well, as I have suggested, you could use a smaller image which, when clicked-on, could open into larger image or could simply open a larger image into another tab/window...
actioman wrote:Ray, please look at these two print screens:
....
In the top of the fisrt one you can see the date format dd/mm/yyyy, but when the gizmo make the refresh (I think is this the correct name) change the format of date and becomes mm/dd/yy? The first format is the usual format in Portugal but the second one, but the other is not so common around here. Is there a way to fix this and these two be equal?
Manuel, I have been looking at that problem (on-and-off) for the past weeks (when I really started editing the usa templates) and I have not yet come up with a solution. The functions used in most scripts deal with the long date format and seem to completely ignore the short date format (also, it appears, one of the limitations of PHP) which is extensively being used by Cumulus and its different date format types, depending on the country the computer is running.
actioman wrote:Another issue, the Rain Rate (/hr), before the gizmo refresh it shows 0,0 mm, but then appears 0,00 mm. The correct format is the first, because my rain gauge has no such resolution.
Again, I have recently noticed that problem while editing the world scripts/templates - I do not know why two and even three decimal are being used by both the 'ajaxCUwx.js' and 'ajaxgizmo.js' scripts - Cumulus certainly does not deliver/produce those values! Oh, the same problems happen on the dashboard. I think I have the problem corrected in my modified usa templates, but I am only half way into the modifications...
actioman wrote:I had not noticed it yet, was a visitor to the website that sent me an email and alerted me to this...
Manuel, one easy way to view this reported problem would be to temporarily disable both 'ajaxCUwx.js' and 'ajaxgizmo.js' scripts (you just need to temporarily change the name of the scripts). True, there will be no realtime update during that time. But then, you will view the information processed by the 'ajax-dashboard.php' script (which gets its data from the 'CUtags.php' data file whereas the 'ajaxCUwx.js' and 'ajaxgizmo.js' scripts get their data from the 'realtime.txt' data file) which displays the weather information as the page is first loaded into a browser.
actioman wrote:Regarding Ray's script...
Which script are you writing about...

I know, it must be about the cloud base script...

Well, you must realize that the cloud base image is only created when the page is first loaded - it is not updated afterwards. But, if you have a look at my <link removed> page, there, the cloud base script is also processed by the 'ajaxWDwx.js' script (similar to the Cumulus 'ajaxCUwx.js' script but using data from the Weather Display 'clientrawXXX.txt' data files) thus the cloud base script (like the weather data on that page) is displayed in almost real time.
Manuel, as I wrote in a previous message, I am going through all scripts/templates of both usa and world packages, cleaning up the code (to 'my standards' so I can easily see what is being done in that script), removing repeated operations (by creating functions), creating new functions, etc. - it is a long process as I keep going backwards re-editing scripts that had already been modified because too many scripts contain the same function but under a slightly different name - I will probably end up doing the same modifications I have made for the canadian templates and centralise/move all functions into one and only one function script - it makes it more flexible as the same function can be used more than once on the same page without creating conflict - and so much easier when there is the need to edit a function. But, as I have written before, it is a learning experience for me and, as long as I have something to learn, I will continue editing/tweaking the scripts/templates...