{"id":8645,"date":"2014-07-28T05:15:18","date_gmt":"2014-07-27T19:15:18","guid":{"rendered":"http:\/\/www.rjmprogramming.com.au\/wordpress\/?p=8645"},"modified":"2014-07-28T05:15:18","modified_gmt":"2014-07-27T19:15:18","slug":"static-html-based-php-primer-tutorial","status":"publish","type":"post","link":"https:\/\/www.rjmprogramming.com.au\/ITblog\/static-html-based-php-primer-tutorial\/","title":{"rendered":"Static HTML Based PHP Primer Tutorial"},"content":{"rendered":"
\"Static<\/a>

Static HTML Based PHP Primer Tutorial<\/p><\/div>\n

Today’s tutorial is like a step back … a woah! … to people familiar with PHP. Even so, those PHP experts may like to rethink on things back to the day they first took it up … did you skirt past some of the PHP possibilities, possibly for good reasons like consistency and speed of coding, yet you would like to reassess other ways? What I am getting at, is that PHP, being the interpretive<\/i><\/a> web server-side (or desktop) language that it is, is quite flexible with styles of coding that can be used. We are not talking about code modules or include<\/i><\/a> or require<\/i><\/a> here … rather we are just paring it back to different ways you can think of PHP and its association with simple static HTML, which, today, we got from w3schools<\/a> … thanks.<\/p>\n

So today, would like you to put yourself in the position of being given some simple static HTML, that works. Yay! This is the most important thing, but here is the other thing … PHP is great at taking that simple working static HTML and turning it from a sow’s ear into a silk purse … personally, think the pig is kind of cute to begin with … but moi digresses.<\/p>\n

You can make the static HTML stand out by having many broken up <?php … ?> blocks (or none, for the odd scenario where your PHP is pure HTML).<\/p>\n

You can make the static HTML be immersed into the PHP by having only one or just a few <?php … ?> block(s).<\/p>\n

You can make the static HTML be like a data source used by the PHP by having the static HTML be read, via file_get_contents<\/i><\/a>, for example, and work the changes (business logic<\/i>) within one, or just a few <?php … ?> block(s).<\/p>\n

It is hard to say what you are going to think is progressive coding or not, and really think you should not sneer at any particular coding style unless you have a good reason never to use a particular style as above, perhaps for reasons of readability or modularization. Anyway, today we show two bits of original simple HTML (they have a red border, the original w3schools code being the top left one) and PHP coding style progressions off that in various styles. Use the code examinations below in conjunction with This Frame->View Frame Source and This Frame->View Frame Info to get the whole picture of various approaches to achieve (almost) the same ends.<\/p>\n

The HTML and PHP supervisory programming source code can be seen below:<\/p>\n