Cumulus Support

Hello everyone Antonio here with just a small question for anyone to answer especially steve.

Does the program Cumulus produce a htm or html page?

only asking as i am slowly working on my V 2.0 of my website and was wondering if i made the same page names but in a html format will cumulus be able to recognize those files and or am i able to name them something else?

and one last thing does the css file have to be called

weatherstyle? if not i would like to change it to style.css

Antonio

htm, that's what you've coded as your links!

The stylesheet can be called whatever you want it to be called. Not quite sure why you want to change it though.

so if i am correct naming my pages diffrently will work?

Antonio

Below is a preiview of how page index is going ( in early development)

htm & html are both exactly the same. I think the story goes like this.....Traditionally webservers were running on Linux/Unix machines so had an extension of "html" but then windows came along and could not use four letters in an extension so Microsoft decided to shorten it to "htm"

Luckily the world (and MS) have moved on and we can use both. I always use ".html"

Now on to Cumulus -- if you use the 'standard files' Cumulus will produce these as ".htm". In your new V2 website you will be best to stop using the standard files, and create new ones and ask Cumulus to process these. This means you can call them anything you want.

Just ensure you do not have index.htm and index.html on your website - you should have one or the other as the default home page.

Okay when the time comes i shall ask how i get cumulus to upload to my new pages

Also while naming my new files like the ones now do they need a index (T) in their name?

Antonio.

pacificblue03 wrote:Also while naming my new files like the ones now do they need a index (T) in their name?

No, you can call them anything you want.

You then go into the Internet Settings. You tell Cumulus the name of your local file (the one with the webtags in it) and the remote file (what you want it called on the web server). Tick Process and FTP. Cumulus will then read the local file, replace the webtags with data and upload to your webserver as the name you provided in "remote filenames". Do this for each of your website files

Example below...

Fantastic

Also has anyone checked my Preview zip?

if you do tell me if my structure is okay

Antonio.

pacificblue03 wrote:Fantastic

Also has anyone checked my Preview zip?

if you do tell me if my structure is okay

Antonio.

Why not put it online on your website and give the page a name as test.htm for example?

ok i will do that now so do i just upload it to my website?

Antonio.

OK i did it

TEST HERE http://www.ballina-nsw-weather-from-sto ... /test.html

Feedback is essentail

Enjoy V2.0

Antonio

It looks good except I think the colours used for the data area seem out of place and make the characters difficult to read. I think it would be better to stick with your shades of blue and possibly a shade of yellow for the characters.

Antonio is that what is being taught in school now-a-day?

Just kidding...

I looked at both the 'indexT.htm' and 'weatherstyle.css' files you have uploaded (in the 'Desktop.zip' file) and they are both good - I did not find any error nor missing closing element - but, being picky-me I would give you just a passing mark for the proper indentation of the lines. It is so important to write clear and concise code, not just for oneself but for others that would like to look at the code...

I also looked at the source code of the 'test.html' file you have online. Just before the '</head>' element, you have some CSS code that should be moved into the 'weatherstyle.css' file.

Further down the code, you are using an increasingly complicated way of producing and displaying the appropriate image for the forecast. If I was you (which I am not), I would use the forecast number (produced by the '<#forecastnumber>' Webtag) and numbered images thus reducing the script to three lines: Obviously, the image names (with commas and spaces, which is not very good Web page programming) would have to be replaced by single of double digits numbers.

The colour of the text used to display the weather information in the table (containing the 'Temperature and Humidity', the 'Rainfall', the 'Wind' and the 'Pressure' should be something other than black as black is very difficult to read on the background colours you have chosen.

You are slowly getting there...

All that gemini says ........

We have mentioned most of these techniques before

There is no need for JavaScript for the forecast at all ! - as outlined here: https://cumulus.hosiene.co.uk/viewtopic.php?f=14&t=1657
(Plus I did already say say there is no such forecast as 'Exceptional Weather' [It is a pre-fix])

Because your 'Force' graphics are the same names as the data, a similar simple html line will replace all your code. NB: if your images are all the same size it is good coding practise to declare the width= and height= values so that page layout is maintained whilst images are loading.


In terms of checking your page for syntax etc. you can go to these pages and either enter your url everytime, or put a clickable banner on your page which can automatically parse your html and css and give the results.

html: http://validator.w3.org/#validate_by_uri
css: http://jigsaw.w3.org/css-validator/

gemini06720 wrote:Antonio is that what is being taught in school now-a-day?

Just kidding...

I looked at both the 'indexT.htm' and 'weatherstyle.css' files you have uploaded (in the 'Desktop.zip' file) and they are both good - I did not find any error nor missing closing element - but, being picky-me I would give you just a passing mark for the proper indentation of the lines. It is so important to write clear and concise code, not just for oneself but for others that would like to look at the code...

I also looked at the source code of the 'test.html' file you have online. Just before the '</head>' element, you have some CSS code that should be moved into the 'weatherstyle.css' file.

Further down the code, you are using an increasingly complicated way of producing and displaying the appropriate image for the forecast. If I was you (which I am not), I would use the forecast number (produced by the '<#forecastnumber>' Webtag) and numbered images thus reducing the script to three lines:

Code: Select all

<script type="text/javascript">
 var imagen = <#forecastnumber>;
 document.write('<img src="images/'+imagen+'.png"/>');
</script>
Note: I could not test the scrip as my Cumulus does not process the files such as 'indexT.htm', etc.

Obviously, the image names (with commas and spaces, which is not very good Web page programming) would have to be replaced by single of double digits numbers.

The colour of the text used to display the weather information in the table (containing the 'Temperature and Humidity', the 'Rainfall', the 'Wind' and the 'Pressure' should be something other than black as black is very difficult to read on the background colours you have chosen.

You are slowly getting there...

So im guessing somewhere in cumulus there is a listing of the forecast numbers somewhere? and if so this means i just rename the images to 1 . 2 .5 etc?

For the data in the table i am going to make it white like the other data, for that line you were talking about moving --which one? ---

Beetlejuice thanks very much for the link to css validating but i have already been using validator . org on w3schools.

i think someone asked if this is being taught in class the answer to that is no.. i have set out a project like this for a while and now it is time to make it happen.

i must say CSS is slowly but surely becoming my best friend.

Antonio.

Read the topic link I gave. (Wiki too, but it only mentions for string.ini and not the full possible number sequence)

Together with the Link I gave, which points out the 'exceptions'

0 (zero) = Not available / Not Cumulus
-1 (neg one) = Exceptionally Fine
-26 (neg 26) = Exceptionally Bad

The 'normal' numbers are:

1=Settled fine
2=Fine weather
3=Becoming fine
4=Fine, becoming less settled
5=Fine, possible showers
6=Fairly fine, improving
7=Fairly fine, possible showers early
8=Fairly fine, showery later
9=Showery early, improving
10=Changeable, mending
11=Fairly fine, showers likely
12=Rather unsettled clearing later
13=Unsettled, probably improving
14=Showery, bright intervals
15=Showery, becoming less settled
16=Changeable, some precipitation
17=Unsettled, short fine intervals
18=Unsettled, precipitation later
19=Unsettled, some precipitation
20=Mostly very unsettled
21=Occasional precipitation, worsening
22=Precipitation at times, very unsettled
23=Precipitation at frequent intervals
24=Precipitation, very unsettled
25=Stormy, may improve
26=Stormy, much precipitation