<?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>Fri, 24 May 2013 20:19:46 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Ibuildings techPortal: phploc: PHP Lines of Code]]></title>
      <guid>http://www.phpdeveloper.org/news/13925</guid>
      <link>http://www.phpdeveloper.org/news/13925</link>
      <description><![CDATA[<p>
On the Ibuildings techPortal today there's <a href="http://techportal.ibuildings.com/2010/01/28/phploc-php-lines-of-code/">a new article</a> from <i>Lorna Mitchell</i> looking at the <a href="http://github.com/sebastianbergmann/phploc">phploc tool</a> as a way to analyze your code and pick out a whole selection of statistics.
</p>
<blockquote>
This has been a feature of <a href="http://phpunit.de/">PHPUnit</a> for some time but has been released as a separate project in the phpunit pear channel. The nature of PHPUnit means that many of these statistics can be collected while the tests are running, which is why it was added to that tool in the first instance.
</blockquote>
<p>
Stats gathered include the number of directories, files, interfaces, methods, functions and constants with more details for each (like visibility, actual lines of code contained in them and the cyclomatic complexity). The tool is very simple to use - just call it from the command like and give it a path to your codebase. It does the rest and spits out a text-based report.
</p>]]></description>
      <pubDate>Thu, 28 Jan 2010 08:59:36 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[IBM developerWorks: Getting Graphic with PHP]]></title>
      <guid>http://www.phpdeveloper.org/news/10538</guid>
      <link>http://www.phpdeveloper.org/news/10538</link>
      <description><![CDATA[<p>
The IBM developerWorks site has a <a href="http://www.ibm.com/developerworks/edu/os-dw-os-php-graphic.html?ca=drs-tp2708">new tutorial</a> posted (registration/login required) talking about image creating in PHP using the GD library.
</p>
<blockquote>
The purpose of this tutorial is to show you how to get started with the GD library and to provide a variety of techniques you can apply to your Web-page coding. The tutorial doesn't cover every GD function, but it teaches you the basics. The Resources section provides Web sites where you can learn more about using the GD library.
</blockquote>
<p>
They <a href="https://www6.software.ibm.com/developerworks/education/os-php-graphic/index.html">go through</a> the creation of sample images, working with gradients and lines, adding text, saving the image data out to a file and how to work with existing graphics to modify them.
</p>]]></description>
      <pubDate>Thu, 03 Jul 2008 10:20:00 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[DevShed: Debugging and Performance]]></title>
      <guid>http://www.phpdeveloper.org/news/6761</guid>
      <link>http://www.phpdeveloper.org/news/6761</link>
      <description><![CDATA[<p>
In another part of their series of excerpts from the Zend PHP Certification Guide (from Zend), DevShed has posted <a href="http://www.devshed.com/c/a/PHP/Debugging-and-Performance/">this article</a> talking about debugging and performance issues and methods.
</p>
<blockquote>
Making mistakes is human, and so is fixing them. In your day-to-day programming adventures, it's inevitable to introduce bugs in your PHP code, especially when you're writing very complex applications with tens of thousands of lines of code spread across tens of files.
</blockquote>
<p>
In <a href="http://www.devshed.com/c/a/PHP/Debugging-and-Performance/">this article</a> they look at things like flattening if statements, spplitting single commands across multiple lines, and the difference between =, ==, and ===.
</p>]]></description>
      <pubDate>Thu, 23 Nov 2006 13:42:00 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[Tobin Bradley's Blog:  A Mapping Site in 19 Lines of Code]]></title>
      <guid>http://www.phpdeveloper.org/news/4862</guid>
      <link>http://www.phpdeveloper.org/news/4862</link>
      <description><![CDATA[On <i>Tobin Bradley</i>'s blog today, there's a follow up to a previous artcile posted concerning getting MapServer working on a Windows/IIS install. <a href="http://thepcnews.blogspot.com/2006/02/mapping-site-in-19-lines-of-code.html">This time</a>, they show how, with a few lines of PHP code, you can create a map quickly and easily.
<p>
<quote>
<i>
PHP/Mapscript makes this fantastically easy, with only 19 lines of code! You can download the code <a href="http://maps.co.mecklenburg.nc.us/website/the_pc_news/downloads/mapserver_sample.zip">here</a>.
</i>
</quote>
<p>
The <a href="http://thepcnews.blogspot.com/2006/02/mapping-site-in-19-lines-of-code.html">remainder of the post</a> steps you through the process of installing the script and, with a few simple calls, you have a functional map of your chosen location.
]]></description>
      <pubDate>Fri, 17 Feb 2006 07:15:33 -0600</pubDate>
    </item>
  </channel>
</rss>
