Raphael Stolt, with some time on his hands, set up a local copy of Xinc, the "shiny new Continuous Integration(CI) server" as hosted on the Google code site and spent some time working with it:

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.

He includes the plugin class (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.

On the Killersoft blog today, Clay Loveless has posted his decision about his development environment - choosing Komodo Pro over the Zend Studio.

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.

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 Komodo Pro. 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 Xdebug extension.

He mentions that this is what he's working up his current project in, Mashery, with his own compiled version of XDebug integrated.

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.

On the Killersoft blog today, Clay Loveless has posted his decision about his development environment - choosing Komodo Pro over the Zend Studio.

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.

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 Komodo Pro. 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 Xdebug extension.

He mentions that this is what he's working up his current project in, Mashery, with his own compiled version of XDebug integrated.

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.