<?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, 22 May 2013 00:30:32 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Raphael Stolt's Blog: Hooking a Growl publisher plugin into Xinc]]></title>
      <guid>http://www.phpdeveloper.org/news/9998</guid>
      <link>http://www.phpdeveloper.org/news/9998</link>
      <description><![CDATA[<p>
<i>Raphael Stolt</i>, with some time on his hands, set up a local copy of <a href="http://code.google.com/p/xinc/">Xinc</a>, the "shiny new Continuous Integration(CI) server" as hosted on the Google code site and spent some time working with it:
</p>
<blockquote>
Since then the idea of building a Growl publisher plugin for Xinc was traveling my mind repeatedly, so the following post will break this circle and show a possible approach to build such a plugin, which can be used to notify the build result for continuously integrated projects and thereby provide an on-point/immediate feedback.
</blockquote>
<p>
He includes <a href="http://raphaelstolt.blogspot.com/2008/04/hooking-growl-publisher-plugin-into.html">the plugin class</a> (ready for cut&paste) as well as the task definition and how to hook it all in to the Xinc build system. There's also a little example of it in action - a happy/sad indicator showing if the build failed or was a success, right there on the desktop.
</p>]]></description>
      <pubDate>Fri, 18 Apr 2008 12:59:47 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Clay Loveless' Blog: Adios, Zend Studio. Hola, Komodo Pro!]]></title>
      <guid>http://www.phpdeveloper.org/news/6048</guid>
      <link>http://www.phpdeveloper.org/news/6048</link>
      <description><![CDATA[<p>
On the Killersoft blog today, <i>Clay Loveless</i> has posted <a href="http://killersoft.com/randomstrings/2006/08/15/adios-zend-studio-hola-komodo-pro/">his decision</a> about his development environment - choosing <a href="http://www.activestate.com/Products/Komodo/">Komodo Pro</a> over the <a href="http://www.zend.com/products/zend_studio">Zend Studio</a>.
</p>
<blockquote>
<p>
A long time BBEdit user, I bit the bullet and (mostly) switched to Zend Studio back in November 2005. I was frustrated by Zend Studio's clunky Subversion handling, but within a few weeks was willing to put up with that for Zend Studio's great debugging environment and intimate knowledge of PHP that helps speed coding along on a line-by-line basis.
</p>
<p>
The switch to an Intel Mac broke Zend Studio's great debugger. Whoops! There went at least half of why I was using Zend Studio in the first place. Enter <ahref="http://www.activestate.com/Products/Komodo/">Komodo Pro</a>. Komodo Pro 3 has supported Intel Macs for months. (Still no word from Zend on this issue.) Its debugging environment is based on the robust <a href="http://xdebug.org/">Xdebug extension</a>.
</p>
</blockquote>
<p>
He <a href="http://killersoft.com/randomstrings/2006/08/15/adios-zend-studio-hola-komodo-pro/">mentions</a> that this is what he's working up his current project in, <a href="http://www.mashery.com/">Mashery</a>, with his own compiled version of XDebug integrated.
</p>
<blockquote>
Komodo Pro lets me work the way I want to, with the tools (and versions of those tools) I want to use. Zend Studio, on the other hand, does not.
</blockquote>]]></description>
      <pubDate>Wed, 16 Aug 2006 07:12:53 -0500</pubDate>
    </item>
  </channel>
</rss>
