<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Mon, 12 May 2008 22:24:00 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Tiger Heron Blog: First steps with PHP - booting a script, Part 1]]></title>
      <guid>http://www.phpdeveloper.org/news/9819</guid>
      <link>http://www.phpdeveloper.org/news/9819</link>
      <description><![CDATA[<p>
On the Tiger Heron blog, there's a <a href="http://www.tigerheron.com/article/2008/03/first-steps-php-booting-script-part-1">continuation of the series</a> that <i>Tony Freixas</i> has been writing to following the beginning steps of working with PHP. First there was the download/install, then setting up a development environment. This time, he actually gets around to writing a bit of basic code.
</p>
<blockquote>
Specifically, I will describe how I boot my PHP scripts and why I boot them the way I do. Part 1 shows how my requirements for code portability and maintainability influence the boot process. Part 2 will go into more detail about the specific steps executed by the boot code.
</blockquote>
<p>
His <a href="http://www.tigerheron.com/article/2008/03/first-steps-php-booting-script-part-1">basic task</a> for the first example is to make a templating sort of system, calling a Navigation class to output links in list items. He outlines the goals of the project, what he's found for his current solution and some alternatives he's discovered along the way.
</p>]]></description>
      <pubDate>Wed, 19 Mar 2008 08:48:48 -0500</pubDate>
    </item>
  </channel>
</rss>
