Have retained most of the original look and feel but have combined today and yesterday onto one page, month and year on another.
There is a new records page that replicates the function and options of the interface records page. I had started on this, combining record.htm and monthlyrecordT.htm. Have now extended this to also combine thismonthT.htm and thisyearT.htm before I noticed the current b3020 interface 'records' page - only use the interface (or the Cumulus1 console) for trouble shooting and reconfiguration).

So what does this mean?
With php the scripts are all static on the webserver and only data needs to be sent, not whole pages.
So the web folder only has the following files to process (for the standard setup - i.e. excluding the other 'features' that are not part of the standard site).
1. A tags file ( CUtagsT.txt) containing all the available tags (from the WebTags.txt file) plus a few extra variable formats sent at 'interval'.
2. realtimegaugesT.txt
3. a records.dat file which consists of the javascript block from the monthlyrecordT.htm file with additions for alltime (original record.htm data), thismonth and thisyear.
The other files sent are realtime.txt and the .json files.

Most of these files are used for all three sites. There is a different CUtags file for the Saratoga site as it uses some additional formatted variables but will probably combine them into one file.
The files that are used by more than one website are held in separate folder reducing data uploaded and maintenance.

Last edited by BCJKiwi on Sat 26 Sep 2015 11:28 pm, edited 7 times in total.

I used a large freeware windows software package ( called virtual moon atlas pro - http://www.ap-i.net/avl/en/start ) to generate the images and then resized them - took a lot of time.
The ones I have are for the Southern hemisphere.

It is a bit of a mashup !!
It uses the .json files, gauges and charts code from the standard Cumulus MX website (as used on the php CumulusMX website - first post).

For some pages it uses realtime and Cumulus tag files generated from the CumulusMX/web folder and the ajax .js code from the Saratoga templates (all as utilised in the php CumulusMX website - first post).
For other pages it adapts pages from the interface folder.
All pages were then styled from the interface .css and .js as required to get the same look and feel as the UI.

This was basically an exercise to see how it might be done.
However it really is a mix of old and new coding styles (tables as well as divs etc.) and thus is not very elegant as the source for much of the data is not the same as it is for the UI.

Last edited by BCJKiwi on Tue 14 Jul 2015 8:22 pm, edited 2 times in total.

Thanks
If you click the link in our signature below, you can get the Davis Console and Cloudbase scripts from our Scripts link.
While these scripts use PHP they will run in the standard Cumulus HTML website provided the webserver supports PHP and for the Cloudbase script GDI as well - both are pretty standard.
A comprehensive HowTo guide is included in the downloads. A number of Cumulus users have one or other or both these scripts running.

BCJKiwi wrote:Thanks
If you click the link in our signature below, you can get the Davis Console and Cloudbase scripts from our Scripts link.
While these scripts use PHP they will run in the standard Cumulus HTML website provided the webserver supports PHP and for the Cloudbase script GDI as well - both are pretty standard.
A comprehensive HowTo guide is included in the downloads. A number of Cumulus users have one or other or both these scripts running.