<?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>Wed, 19 Jun 2013 04:15:14 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Ruslan Yakushev's Blog: How to install PHP PEAR and phploc on Windows]]></title>
      <guid>http://www.phpdeveloper.org/news/15494</guid>
      <link>http://www.phpdeveloper.org/news/15494</link>
      <description><![CDATA[<p>
<i>Ruslan Yakushev</i> has a <a href="http://ruslany.net/2010/11/how-to-install-php-pear-and-phploc-on-windows/">recent post</a> about installing the <A href="http://pear.php.net">PEAR</a> tools and installing an example package, <a href="https://github.com/sebastianbergmann/phploc">phploc</a>.
</p>
<blockquote>
<a href="http://pear.php.net/">PEAR</a> (short for PHP Extension and Application Repository) is a framework and distribution system for reusable PHP components. In includes many useful tools and components that can be easily downloaded and installed by using PEAR package manager. This post describes how to install and configure PEAR package manager and then how to use it to install a PEAR package. An example PEAR package used in this post is <a href="https://github.com/sebastianbergmann/phploc">phploc</a>, which is a tool for measuring the size of PHP projects.
</blockquote>
<p>
He recommends installing PHP via the <a href="http://www.microsoft.com/web/webmatrix/">Web Platform Installer</a> and use the <a href="http://windows.php.net/download/">PHP 5.3 VC9 non-thread-safe</a> package with the <a href="http://phpmanager.codeplex.com/">PHP Manager</a>. All of the commands needed are included as well as some of the sample output that results. Once you get PEAR installed, then they show how to discover the PEAR channel and "pear install" the right packages for phploc (including the dependencies it might need).
</p>]]></description>
      <pubDate>Thu, 25 Nov 2010 12:38:12 -0600</pubDate>
    </item>
    <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[Raphael Stolt's Blog: Phplocing your projects with Phing]]></title>
      <guid>http://www.phpdeveloper.org/news/12004</guid>
      <link>http://www.phpdeveloper.org/news/12004</link>
      <description><![CDATA[<p>
In wanting to both keep his development streamlined and add in a new tool (<a href="http://github.com/sebastianbergmann/phploc/tree/master">phploc</a>), <i>Raphael Stolt</i> has <a href="http://raphaelstolt.blogspot.com/2009/02/phplocing-your-projects-with-phing.html">come up with a way</a> to integrate <a href="http://github.com/sebastianbergmann/phploc/tree/master">phploc</a> into a <a href="http://phing.info/trac/">Phing</a> buildfile and have it run as an automated task.
</p>
<blockquote>
Exactly one month ago Sebastian Bergmann, of PHPUnit fame, started to implement a similar tool dubbed <a href="http://github.com/sebastianbergmann/phploc/tree/master">phploc</a> which can give you an overview of the size for any given PHP project. As I wanted to automate the invocation of this handy tool and collect it's report output out of a Phing buildfile, I invested some time to develop a custom <a href="http://phing.info/trac/">Phing</a> task doing so.
</blockquote>
<p>
He includes instructions on installing phploc, creating the last in Phing (complete with code) and integrating it into your Phing build.
</p>]]></description>
      <pubDate>Mon, 23 Feb 2009 13:48:09 -0600</pubDate>
    </item>
  </channel>
</rss>
