PDT 2.0 was designed based on principles different to those of Eclipse PDT 1.0. For example, different techniques were used to model workspace projects. PDT 2.0 now uses an indexing and caching mechanism for improved performance and experience with code assist and navigation. Moreover, since PHP provides enhanced Object-Oriented features like inheritance and polymorphism, PDT 2.0 provides enhanced features such as type hierarchy, override indicators and type navigation for programmers who utilize these language properties.

The extension is now lighter and faster, making better use of the Eclipse framework for caching/indexing language elements. The release also includes a method for configuring your buildpath, a "mark occurrences" feature, an icon that notes overrides, improved code assist and much more.

You can grab this latest download from a Eclipse PDT page off of the Eclipse site.

This week, I found a need to do this same kind of remote debugging, but for a command-line PHP script. This seems to be something that Eclipse is not already designed to do, as there is no "perpetual listener" available for its debug client. Instructions for remote CLI debugging are available, which showed me that environment variables might be the missing link to getting it working with Eclipse. It turned out to be one of two missing links. The other link was tricking Eclipse into keeping a debug session open (and therefore "listening").

He found that by loading up the PHP file in a shell script with the XDEBUG_CONFIG and XDEBUG_SESSION variables defined, it allows the Eclipse listener to connect and work through the file like a normal web page request.

I've been using Zend Studio (ZS) for the last two years. It is developed by Zend, the company behind PHP. The very first time I used it and it was able to auto-complete my custom PHP classes I was sold. With version 6 of Zend Studio, they integrated Zend Studio with Eclipse, a popular IDE framework. I've been mostly happy with the new version, where as in some areas I felt that things were took a step back.

He compares their ease of installation, how easy they make it to refactor your code, debuggers included, the editor environment itself and, of course, the integration with Zend Platform/Zend Framework.

Happy dreams of PHP developers come true. Yesterday I received a letter from Eclipse PDT bugzilla with notification that my proposition about autocomplete for properties that submitted more than a year ago is implemented in PDT 2.0 nightly builds.

There's a screenshot included in the post and he points to the download page where you can grab the files you'll need.

You already know that Eclipse PDT provides autocompletion and hints for PHP's built in functions. In addition, commenting your code with PHPDoc adds autocompletion and hinting for your application's classes, methods, and variables. If you haven't already discovered, Eclipse PDT also provides autocompletion of PHP's control structures, class definitions, and methods through code templates.

He gives examples of both the templating and the snippets - inserting a switch() statement template and how to create a custom snippet of whatever code you choose.

As expected by many, Eclipse PDT's next major release has been postponed. While two milestones couldn't be released, it became clearer and clearer that the release date of September 15th 2008 couldn't be met.

The new deadline has been set though - December 29th, 2008. New improvements in this release will include a type hierarchy view, new PHP explorer functionality, code templates and a code assist for dynamic variables. There was also a large change to the API that set things back a bit.

With Eclipse PDT 2.0 to be released in September (or October) support for namespaces is already on the roadmap. Support for Phar archives has not been listed, yet. But in my opinion Eclipse PDT 2.0 must support handling Phar archives when PHP 5.3 will hit the street.

He points out some of the current lackings that the Eclipse extension has including the inability to browse phar archives and that there is no way to debug the archives. He's opened a feature request for the functonality to be added and suggested fleshing it out on the wiki.

This is where you come in - he wants to know what sort of support that developers out there would like for phar in this next release. Just leave comments on his blog with your ideas.

Enabling PHP-GTK2 code completion in Eclipse PDT for a project is very simple. The following example is given on Windows, but the steps should be the same on any supported platform

It's a simple eight step process (the steps are little) to get support working. You'll need to use the Gtk_Dumper to get the info the IDE will need for the completion.

The PHP Development Tools (PDT) plug-in, when installed with Eclipse Europa, gives you that ability to quickly write and debug PHP scripts and pages. PDT supports two debugging tools: XDebug and the Zend Debugger. Learn how to configure PDT for debugging PHP scripts and discover which perspectives you use when taking closer looks at your scripts.

You'll need to have a machine with PHP, Eclipse, Apache and the PHP Development Tools already installed to follow along (as well as a trial version of the Zend Studio Web Debugger). They also include the methods for setting up XDebug as the debugger.

Since there are more and more people in the Eclipse PHP Development Tools (PDT) community that start asking for diversity in the development side, Nick Boldt has suggested to help out and contribute patches to the project "if there's Zend folks willing to coach me...". Actually, I am very excited from his (and others) proposal, since it's the first time a group of people have stated that they want to contribute to PDT.

The event will happen on May 30th, 2008 and an effort will be made to squash as many from this list as possible (as well as potential others that might be found along the way). You can get more information about how to participate and help out the PDT project on this page on the Eclipse site.