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.

Zend Studio for Eclipse is a commercial edition of Eclipse plus the PDT plugin and various other additions. Unfortunately Zend decided to disable the Xdebug support of the Eclipse PDT plugin. Nonetheless if you'd like to use Xdebug for debugging your PHP scripts, follow these simple steps to restore the Xdebug functionality of Eclipse.

Its a simple six-step process (not including getting Zend Studio installed) to have the powerful debugging tool ready at your fingertips. You can find more information about setting up the tool here.

These courses further expand the portfolio of Zend training courses, which include PHP from introduction to advanced levels, as well as courses about PHP Security, creation of Rich Internet Applications, and the use of major Zend products.

Here's the details:

• Migrating Your Web Applications from PHP v4 to v5 - This webinar guides you through the basics of planning a migration, as well as discussing some of the tools to make the process easier, such as unit testing and PHPDoc. The current class will be held September 9th and 11th and will cost about $300 USD.
• Zend Studio for Eclipse - The Zend Studio for Eclipse Course is designed to provide PHP programmers with a practical, in-depth knowledge of the next generation tool in the Zend Studio IDE family. The current class will start August 25th and will run through September 5th. Cost for the class is about $800 USD.

My buddy Pete MacIntyre has been after me to review his book for some time now and honest Pete, it's been sitting on my desk since it arrived patiently awaiting my attention. So last night I broke down and went through it. I'll have to say I was impressed with what I saw.

He (the reviewer, Cal) notes that, while the book comes in at about 180 pages - light for a tech book these days - to still gives a great overview of the technology for those already familiar with the Eclipse setup.

The topic is "Best Practices" and all you have to do to enter is submit an article - long, short, good or bad - over in the Best Practices forum on their site. Want an example? Check this one out.

Now for the good part - there'll be two winners: the best two entries will get the top of the line prizes, licenses for Zend Studio for Eclipse) and, of those two, one will get inclusion of their article into a future issue of Linux Pro Magazine. The other will be gifted with a one year subscription to the same publication.

Others have already posted their articles - why haven't you? You don't have to be female or an expert in your field to contribute, just get out there and write something up for your chance to get in on the goods.

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.

To enter the competition all you have to do is submit a short article to our Best Practices forum before the end of July 2008. This area of the site is dedicated to little tips and pointers of how to improve your PHP coding - here is a good example which covers using constants. The competition is open to everyone, regardless of gender, age, location, or any other criteria I haven't thought of.

At the end of July, they'll take their two favorites out of the articles that've been submitted and hand out perpetual licenses for the Zend Studio for Eclipse software to the winners. Remember, you don't have to be female to participate - they're happy to take in content from anyone and everyone. Just sign up and add your topic to the Best Practices forum to submit - it's that easy!

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.