<?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>Sun, 06 Jul 2008 21:52:00 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[IBM developerWorks: Five more PHP design patterns]]></title>
      <guid>http://www.phpdeveloper.org/news/9875</guid>
      <link>http://www.phpdeveloper.org/news/9875</link>
      <description><![CDATA[<p>
The IBM developerWorks site has a <a href="http://www.ibm.com/developerworks/opensource/library/os-php-designpatterns/index.html?ca=drs-tp1308">new article</a> posted that talks about design patterns, five of them in particular, that can help to "accelerate your PHP development" and make your code more maintainable down the line.
</p>
<blockquote>
As an application developer, you can have a lifelong career without ever knowing what any of the patterns are called or how or when they're used. However, I've found that a good working knowledge of these patterns, as well as those introduced in the developerWorks article "Five common PHP design patterns" (see <a href="http://www.ibm.com/developerworks/opensource/library/os-php-designpatterns/index.html?ca=drs-tp1308#resources">Resources</a>), allows you to do two things: Enable high-bandwidth conversations and reduce painful lessons.
</blockquote>
<p>
The patterns they talk about in this "five more" article of the series are:
</p>
<ul>
<li>Adapter Pattern
<li>Iterator Pattern
<li>Decorator Pattern
<li>Delegate Pattern
<li>State Pattern
</ul>
<p>
Diagrams are provided for each of them, showing how they flow along with brief code examples (structures really) to show how that transitions over to actual use.
</p>]]></description>
      <pubDate>Fri, 28 Mar 2008 08:49:35 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[DevShed: The Basics of Implementing Adapter Objects with PHP]]></title>
      <guid>http://www.phpdeveloper.org/news/6839</guid>
      <link>http://www.phpdeveloper.org/news/6839</link>
      <description><![CDATA[<p>
DevShed takes a look at another of the design patterns in a new series starting with <a href="http://www.devshed.com/c/a/PHP/The-Basics-of-Implementing-Adapter-Objects-with-PHP/">this new tutorial</a> - a look at the implementation of Adapter objects in PHP.
</p>
<blockquote>
You may have already encountered situations in coding PHP applications in which you would like to use inheritance, but could not for one reason or another. Fortunately, there is an alternative for these situations that can help you achieve the same result. In this first article in a two-part series, you'll learn about the adapter pattern.
</blockquote>
<p>
They <a href="http://www.devshed.com/c/a/PHP/The-Basics-of-Implementing-Adapter-Objects-with-PHP/">start off</a> with the basics of the Adapter pattern and move quickly into the first definition of a class using them - a directory processor. Once that's built, they show how it all works with a more practical example.
</p>]]></description>
      <pubDate>Wed, 06 Dec 2006 15:53:59 -0600</pubDate>
    </item>
  </channel>
</rss>
