I've just opened my Xdebug repository on github. Importing my old SVN repository was a bit of a task. With the help of Ole Marius Smestad I managed to cook up a bash script to import and fix-up the repository. In the meanwhile I've learned more about git than I ever wanted to know, but still not enough.

In a new post to the SitePoint PHP blog Troels Knak-Nielsen gives a check up for a project he's worked some on - an interface he came up with to talk, via the dbgp-protocol, to a XUL frontend.

Spectator is a XUL application, which should make it cross platform. I have tinkered a bit with XUL before, but not a full application. [...] So what can spectator do? Mind that this is a first version and I really just meant it as a proof of concept. I think I got a bit further than that, but it probably still has a few bugs. Still, with the current version, you can step through a program, set breakpoints and inspect the stack. Really all you would expect from a debugger.

In a new post on his blog, Guy Harpaz answers a few questions people have been having about the debugger protocol that the PHP IDE project uses.

Debugging a PHP application or a PHP web server requires connectivity between an IDE and a Debugger engine (a PHP module which is installed on the web server). The debug protocol defines this connection. [...] When the Eclipse Foundation approved the PHP IDE project, Zend Studio's debug protocol was opened source and was chosen to be the debug protocol of the PHP IDE project.

He goes through why they made the choice, touches a bit on the security aspect of the two debugging protocols he mentioned (DBGp and Zend Studio's) as well as their common methods for output.

Guy Harpaz, the product manager for Zend Studio, has sterted a new blog up today, and has already posted his first item, a look at PHP IDE debug protocols and why to choose Zend's.

Lately there were many questions and comments on blogs and in PHP related forums regarding the debugger protocol, which will be used in the PHP IDE project at Eclipse.org.

When the Eclipse Foundation approved the PHP IDE project, Zend Studio's debug protocol was opened source and was chosen to be the debug protocol of the PHP IDE project. Zend Studio was known for its debugging capability and it is considered one of its big advantages, therefore, the decision to open source the protocol was obviously a big decision.

He follows this with two reasons to make the choice of Zend's offering, and includes two more topics looking at the differences between the two main protocols (DBGp and PHP IDE debug).

Guy Harpaz, the product manager for Zend Studio, has sterted a new blog up today, and has already posted his first item, a look at PHP IDE debug protocols and why to choose Zend's.

Lately there were many questions and comments on blogs and in PHP related forums regarding the debugger protocol, which will be used in the PHP IDE project at Eclipse.org.

When the Eclipse Foundation approved the PHP IDE project, Zend Studio's debug protocol was opened source and was chosen to be the debug protocol of the PHP IDE project. Zend Studio was known for its debugging capability and it is considered one of its big advantages, therefore, the decision to open source the protocol was obviously a big decision.

He follows this with two reasons to make the choice of Zend's offering, and includes two more topics looking at the differences between the two main protocols (DBGp and PHP IDE debug).