{"id":5798,"date":"2014-01-07T05:05:50","date_gmt":"2014-01-06T18:05:50","guid":{"rendered":"http:\/\/www.rjmprogramming.com.au\/wordpress\/?p=5798"},"modified":"2014-01-07T05:05:50","modified_gmt":"2014-01-06T18:05:50","slug":"integrating-global-weather-into-geographicals-tutorial","status":"publish","type":"post","link":"https:\/\/www.rjmprogramming.com.au\/ITblog\/integrating-global-weather-into-geographicals-tutorial\/","title":{"rendered":"Integrating Global Weather into Geographicals Tutorial"},"content":{"rendered":"
\"Integrating<\/a>

Integrating Global Weather into Geographicals Tutorial<\/p><\/div>\n

Today’s tutorial is all about software integration and builds on yesterday’s<\/a> Ajax Global Weather HTTP Get Primer Tutorial<\/a> as shown below.<\/p>\n

Sometimes (well, in my experience) you get the best “kick”<\/i> out of integrating software components, rather than the writing of the component itself. Sounds weird, doesn’t it, but the fact is, the more functionality you can build into existing software frameworks you have built up, the more useful software becomes, rather than a whole lot of disparate functionality, which may be very cute, but the procedures for which can be forgotten by people in the length of time it takes to wander up the hallway with the mobile phone attached to one’s cranium (would the Queen do this?!).<\/p>\n

So yesterday’s “Get the Weather”<\/i> functionality has a geographical component, that is for sure … the “where”<\/i> in life is soooo programmable, isn’t it? … so we can integrate it into other Geographical software components we’ve been developing here on this blog.<\/p>\n

Part one (of two) of integration tasks is to associate the “Get the Weather”<\/i> with a placename in the world. This is the more obvious integration task and we show two bits of integration to make that happen below.<\/p>\n

Here is a new link to some downloadable PHP programming source code explaining changes made specifically for the “Get the Weather”<\/i> software component (from tutorial below) here<\/a>.<\/p>\n

Here is a new link to some downloadable PHP programming source code explaining changes made specifically for the Geographical supervisor of the “Get the Weather”<\/i> software component (and others) here<\/a> … lots of the changes here involve readiness for the other piece of integration that we will cover at another tutorial tomorrow.<\/p>\n

And finally here is the live run<\/a> to test all the integration (which now includes “Get the Weather”<\/i>) yourself.<\/p>\n

\n

Previous relevant Ajax Global Weather HTTP Get Primer Tutorial<\/a> is shown below.<\/p>\n

\"Ajax<\/a>

Ajax Global Weather HTTP Get Primer Tutorial<\/p><\/div>\n

Ajax techniques make your web pages very dynamic and useful, and there will be fewer changes of webpage required when using Ajax, because information derived from a data source (maybe a feed, maybe a database read, maybe a local source of data, maybe a web service website (as for this tutorial … thanks to GlobalWeather<\/a> here)) make many changes of webpage obsolete.<\/p>\n

Today we use HTTP Get methods to procure the data, but you will see other methods that can be used on that link above.<\/p>\n

Let’s have a look at Wikipedia’s thoughts on Ajax below<\/a>.<\/p>\n

Ajax (also AJAX; \/\u02c8e\u026ad\u0292\u00e6ks\/; an acronym for Asynchronous JavaScript and XML)[1] is a group of interrelated web development techniques used on the client-side to create asynchronous web applications. With Ajax, web applications can send data to, and retrieve data from, a server asynchronously (in the background) without interfering with the display and behavior of the existing page. Data can be retrieved using the XMLHttpRequest object. Despite the name, the use of XML is not required (JSON is often used instead. See AJAJ), and the requests do not need to be asynchronous.[2]<\/p>\n

Ajax is not a single technology, but a group of technologies. HTML and CSS can be used in combination to mark up and style information. The DOM is accessed with JavaScript to dynamically display, and allow the user to interact with, the information presented. JavaScript and the XMLHttpRequest object provide a method for exchanging data asynchronously between browser and server to avoid full page reloads.<\/p><\/blockquote>\n

Have a look at the PHP downloadable code which you could rename to get_weather.php<\/a>
\nTry a live run<\/a> here.<\/p>\n

\n

Previous relevant Ajax Preview Window Tutorial<\/a> is shown below.<\/p>\n

\"Ajax<\/a>

Ajax Preview Window Tutorial<\/p><\/div>\n

Ajax is a client-side meets server-side melding of PHP (or ASP.Net<\/a>) and Javascript and HTML and CSS and allows you to stay on the web page you are on doing many more things, rather than constantly changing web pages the way that HTML form tag makes you do. Ajax works with XMLHttpRequest object to quiz the server-side while staying on the client side. You may have guessed that we have been working up to this, and I refer you to the previous tutorial about JavaScript and the DOM Tutorial<\/a> and PHP + JavaScript + HTML Primer Tutorial<\/a> for important information to learn before tackling Ajax. Ajax shares similar restrictions to iFrames in limiting you to work within your own domain, generally speaking. Ajax normally makes use of the onmouseover (hence the amateurish added rendition of a cursor, where I was hovering over the option tag, but couldn’t take a snapshot of this … ie. too lazy to get the camera!) and onmouseout events of HTML elements and you may notice the less than ideal Internet Explorer behaviour for this Ajax code, and that is because for Internet Explorer the option tag has no onmouseover nor onmouseout event defined, so we did an awful kludge.<\/p>\n

Earlier tutorials … <\/strong><\/p>\n

JavaScript is a tremendous web client-side language to learn. You may have heard of a server-side JavaScript, but this tutorial only deals with client-side work. This tutorial builds a JavaScript layer on top of the PHP tutorial<\/a> made earlier, showing how the DOM can be used to change the look of your webpage dynamically, even if most of it is in an iFrame (but there are limits).<\/p>\n

PHP is a wonderful language to learn. It is usually associated with being a web server-side language (as with this tutorial, where it is being shown on a local MAMP<\/a> web server) but can be a command line tool<\/a> as well. If you like PHP you may eventually like ASP.Net<\/a> and\/or Python, and vice versa. It has sophisticated data structures, Object Oriented (the thinking that you can build classes with data and methods which define objects created as you run the program … eg. you might write a class for book and have data members for things like numPages and publisher, author, creationDate and have methods called things like getCreationDate, setCreationDate, getAuthor, setAuthor allowing the user to use these methods rather than changing the data members themselves … heaven forbid that!) code concepts, and really combines well with JavaScript<\/a> (as a client-side language). <\/p>\n

Download programming source code and rename to ajax.php<\/a> (but Ajax only works within the domain you use it, and this code mentions www.rjmprogramming.com.au so just use it for reference purposes or rewrite for purposes that suit you within your domain of interest).<\/p>\n

Regarding this topic<\/a> I really like “JavaScript & Ajax” seventh edition by Tom Negrino and Dori Smith<\/em> <\/p>\n

Did you know …<\/em><\/strong>
\nJavaScript makes a great easy-access Calculator?<\/p>\n

Try typing the lines below into the address bar of your favourite browser:<\/p>\n

Javascript: eval(512 \/ 380);
\nJavascript: eval(512 * 380);
\nJavascript: eval(512 – 380);
\nJavascript: eval(512 + 380);
\nJavascript: eval(512 % 380);<\/p>\n

These days we spend so much time on the Internet it is a much quicker way to get to a calculator!\n<\/p>\n

If this was interesting you may be interested in this<\/a> too.<\/p>\n