{"id":26931,"date":"2016-12-16T03:01:31","date_gmt":"2016-12-15T17:01:31","guid":{"rendered":"http:\/\/www.rjmprogramming.com.au\/ITblog\/?p=26931"},"modified":"2016-12-15T23:02:56","modified_gmt":"2016-12-15T13:02:56","slug":"timezone-country-places-iframe-tutorial","status":"publish","type":"post","link":"https:\/\/www.rjmprogramming.com.au\/ITblog\/timezone-country-places-iframe-tutorial\/","title":{"rendered":"TimeZone Country Places Iframe Tutorial"},"content":{"rendered":"
\"TimeZone<\/a>

TimeZone Country Places Iframe Tutorial<\/p><\/div>\n

Just because a concept is simple doesn’t mean it should somehow be disrespected. For the most part, we often wonder why complicated things that supercede simple things that worked well (and were well understood) become obsolete. If we were to be a little less naive perhaps we’d understand, but that’s business. What we most respect here, are simple ideas, and ones that ask little, and give a lot, and ones that are renewable or leave a small footprint on the world … EOR … end of rave.<\/p>\n

Today’s “simple concept” is the HTML iframe<\/a> element, which to us means “child” in “parent\/child” or “client” in “server\/client” for web applications. A “child” talks to their “parent”, and vice vera. And a “child” can influence their “parent” … you bet! That’s a (metaphor for a) web application “parent” web page, and its relationship to an HTML iframe element. We find it the easiest way to understand (and practically arrange) the modularisation of web application functionality, where all that functionality can even be contained within the one piece of code, but just called differently, with a feel of recursion<\/a>.<\/p>\n

With our TimeZone Country Places Primer Tutorial<\/a> as shown below, we’d actually already started on HTML iframe work, because the Google Charts<\/a> Map Chart<\/a> functionality is already (contained) in an HTML iframe element. But we’re talking, today, about another level of HTML iframe use, by allowing for an HTML table row’s worth of TimeZone\/MapChart cells (up to 10). Why? We’ll let you know more tomorrow, but the obvious reason for today, is that you see information sidled up next to each other horizontally … simple and effective way we humans work … we naturally compare and contrast and observe data, ideally all within eyesight of each other.<\/p>\n

Which leaves us with our amended live run<\/a> PHP code tz_places.php<\/a> that changed in this way<\/a> for your perusal. Perhaps, today, you can visualize this web application’s practical use and can imagine what we are tempted to do next?<\/p>\n

\n

Previous relevant TimeZone Country Places Primer Tutorial<\/a> is shown below.<\/p>\n

\"TimeZone<\/a>

TimeZone Country Places Primer Tutorial<\/p><\/div>\n

We’ve elaborated on the PHP TimeZone functionalities today to write another web application where “when” meets “where” via TimeZones.<\/p>\n

Into the mix of the logic here, we need to venture into the world of two letter ISO Country Codes, and we work this with help from http:\/\/php.net\/manual\/en\/datetimezone.getlocation.php<\/a> and http:\/\/stackoverflow.com\/questions\/17842003\/php-intl-country-code-2-chars-to-country-name<\/a> and http:\/\/php.net\/manual\/en\/function.timezone-identifiers-list.php<\/a> and http:\/\/www.timezoneconverter.com\/<\/a> to “hardcode” our HTML select “dropdown” elements we create in the process, and offer TimeZone information HTML select “dropdown” elements as well.<\/p>\n

Also in the mix, as is so often the case for us here, when “where” is part of the “equation”, we use that wonderful Google Charts<\/a> Map Chart<\/a> functionality, to help us out.<\/p>\n

And so we have written our live run<\/a> of the PHP code tz_places.php<\/a> for your perusal.<\/p>\n

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