Page 1 of 1
About parsing files
Posted: Wed 08 Dec 2010 7:17 pm
by nitrx
I know the principe of the standard files indexT.htm andso-on but when I want to make another file like index.php on the server do I have to call it indexT.php locally ?
Re: About parsing files
Posted: Wed 08 Dec 2010 7:52 pm
by Synewave
Not quite sure what you are trying to achieve.
But if you have a indexT.htm present, Cumulus will process any webtags in it and replace those values with data and upload it to your webserver.
If you want to make another file with a different name, with webtags in, list it in the Cumulus Internet settings with a remote filename with whatever you want to call it i.e. indexnew.htm. Tick Process and FTP, and cumulus will upload it to your site with the webtags processed.
If you need a clearer explanation, just ask.
Re: About parsing files
Posted: Wed 08 Dec 2010 8:10 pm
by nitrx
Well I'm (trying) to make a page like dezemaandjaar.htm do I've to name it dezemaandjaarT.htm or can i give it anyname i want by example : exampe.htm<--including webtags, local on my disk let it process by cumulus and ftp it with the name dezemaandjaar.htm (brr I'm getting confused

)
*Edit* read it again and undertstood thanks Paul.
Re: About parsing files
Posted: Wed 08 Dec 2010 8:16 pm
by steve
The 'T' in the standard files can be a bit confusing. It was just my way, in the very early days of Cumulus, to make sure that the 'input' file had a different name to the 'output' file - the file that ended up on the web site. So, indexT.htm was processed to make index.htm.
For files that are explicitly listed on the files tab, I avoided the name clash by adding 'tmp' to the output file name. So you can call your own files whatever you want, they don't have to have a 'T' in them.
Re: About parsing files
Posted: Wed 08 Dec 2010 8:50 pm
by Synewave
Following on from what Steve has said, if you have a file on your pc, called anything.htm with webtags in (and listed in the files section of the Internet Settings), the remote filename can be anything.htm. If you have Process and FTP ticked, the page will appear on the website with the relevant data.
Re: About parsing files
Posted: Wed 08 Dec 2010 9:08 pm
by nitrx
Well it's clear to me
http://www.apeldoorn.tk/weer/maandjaar.htm (have to add the units it's raw) Just wondering why the are no timetags for some webtags
http://wiki.sandaysoft.com/a/BETA_webtags
Re: About parsing files
Posted: Wed 08 Dec 2010 9:40 pm
by steve
Which time tags do you think are missing?
Re: About parsing files
Posted: Wed 08 Dec 2010 9:46 pm
by nitrx
steve wrote:Which time tags do you think are missing?
<#YearMinTempH> This years highest daily minimum temperature by example they are listed in the table
http://wiki.sandaysoft.com/a/BETA_webtags under yearly
Re: About parsing files
Posted: Wed 08 Dec 2010 9:54 pm
by steve
You're not going to like my explanation, because I've tried to explain this to others before and failed, and I can't give you a 'scientific' explanation, but... it's because for the lowest max and highest min, the time they occurred isn't really significant, it's the whole day which is significant.
There, I said you wouldn't like it.
Re: About parsing files
Posted: Wed 08 Dec 2010 9:58 pm
by nitrx
LOL , well I can live with it.
Re: About parsing files
Posted: Wed 08 Dec 2010 10:08 pm
by steve
If people feel strongly that it should be there, I could add the web tags. But I might resist adding it to Cumulus itself.
Re: About parsing files
Posted: Wed 08 Dec 2010 11:03 pm
by beteljuice
There is a 'problem' with files like index.xxx unless Steve has changed things.
If you use "Include Standard Files", then create an alternative index.php (for example), Cumulus ftp sends your files first, then the 'Standard' ones - So there will always be eg. index.htm on your site !
You would have to disable "Include Standard Files" and separately state each individual file to upload.
I repeat this only applies if you are using Cumulus ftp facility.
Re: About parsing files
Posted: Thu 09 Dec 2010 12:10 am
by serowe
steve wrote:You're not going to like my explanation, because I've tried to explain this to others before and failed, and I can't give you a 'scientific' explanation, but... it's because for the lowest max and highest min, the time they occurred isn't really significant, it's the whole day which is significant.
There, I said you wouldn't like it.
The time can actually be significant - especially when the max or min was also related to a major event. For example, the Black Saturday bushfires in Victoria (nearly 200 killed and many many hundreds of homes and properties destroyed in one afternoon) had a later than normal extreme temperature peak - in my case 46.2 C at 1733 and stayed within .3 C for nearly an hour afterwards - normally, even in summer, our peak temperatures are reached between about 1500 and before 1700 and then start to drop off quite significantly, even on very hot days. Even the minimum temperatures over this 4-5 day period were reached abnormally late in the morning - on a few of the days during this heat wave, they were reached *after* 9am.
Not 'arguing' with your thinking, but for some events, these times can be important.
So whilst I understand your belief about them 'not being important' if the information is available, why not have a webtag for it - this way, the user gets to decide if they want to use it or not? Currently I parse all of my data to display this info whenever an annual, monthly or daily page is displayed.
(As an aside to this, when I was contacted by our Water Authority recently about them accessing all of my rain data for the past 27 years, one of the things they wanted to know was whether my rainfall data was broken down during each 24 hour period and to what resolution it was available.)