<?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, 07 Sep 2008 15:40:04 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Felix Geisendorfer's Blog: Handling inline links to dynamic resources]]></title>
      <guid>http://www.phpdeveloper.org/news/6664</guid>
      <link>http://www.phpdeveloper.org/news/6664</link>
      <description><![CDATA[<p>
On the ThinkingPHP Blog today, there's <a href="http://www.thinkingphp.org/2006/11/06/handling-inline-links-to-dynamic-resources/">a look at</a> how to handle inline links to dynamic resources - specifically allowing users to create links in their own content to dynamic content elsewhere on the site.
</p>
<blockquote>
I thought of something that would be both, easy to implement and easy to use. What I finally came up with is tightly coupled to my <a href="http://www.thinkingphp.org/2006/09/18/dessert-11-welcome-back-friendly-urls/">new url system</a> that I'm using, so make sure to <a href="http://www.thinkingphp.org/2006/09/18/dessert-11-welcome-back-friendly-urls/">check it out</a> in case you've missed it.
</blockquote>
<p>
The basic idea of the system is that the URL of the page (made up partly of the title) would be the unique identifier for the page. For example, "[page 12]" would be expanded out to "/pages/12:my-title". <i>Felix</i> takes this idea and runs with it, showing how to implement it in a CakePHP project inside of a Model and a Component. The sample usage code is, of course, also included in <a href="http://www.thinkingphp.org/2006/11/06/handling-inline-links-to-dynamic-resources/">the post</a>.
</p>]]></description>
      <pubDate>Wed, 08 Nov 2006 07:21:00 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[DevShed: Unit Testing]]></title>
      <guid>http://www.phpdeveloper.org/news/6533</guid>
      <link>http://www.phpdeveloper.org/news/6533</link>
      <description><![CDATA[<p>
More and more talk is being given to testing applications these days. For some, that just means going through the functionality and ensuring that things seem to be working okay. That's one way to find problems in an application, but not the best way. A better way it through unit testing, a system of writing up various tests for the functions making up your application to ensure they're 100% working. Not familiar with it? That's what <a href="http://www.devshed.com/c/a/PHP/Unit-Testing/">this new tutorial</a> from DevShed is for - another excerpt from the Sams Publishing book "Advanced PHP Programming".
</p>
<blockquote>
All code is tested at some point-perhaps during its implementation, during a dedicated testing phase, or when it goes live. Any developer who has launched broken code live knows that it is easier to test and debug code during development than after it goes into production.
</blockquote>
<p>
Unit testing helps with finding these problems before they get into the hands of live users. <a href="http://www.devshed.com/c/a/PHP/Unit-Testing/">The tutorial</a> gives you a basic overview of how to work with this handy tool, specifically with the <a href="http://pear.php.net/PHPUnit">PHPUnit package</a>. They help you write a simple test, expand on this base with more elaborate tests, and how to package your tests right in with your libraries to make installation/packaging simpler.
</p>]]></description>
      <pubDate>Thu, 19 Oct 2006 10:12:00 -0500</pubDate>
    </item>
  </channel>
</rss>
