In a new entry to his blog today, Alexander Netkachev takes a look at the Eclipse project formerly known as "PHP IDE" - the "PDT, PHP Development Tools" project.

PHP IDE developers have changed the name of their project to PHP Development Tools, to place it into the line of Eclipse project Development Tools with C/C++ Development Tools, J Development Tools, and others. So, if you use PHP IDE in your work, do not forget to update it to the new version of the project with a few bugs fixed and new features added.

He also includes the instructions to make the update to this latest version and the screenshots of a before and after the update's run.

In a new entry to his blog today, Alexander Netkachev takes a look at the Eclipse project formerly known as "PHP IDE" - the "PDT, PHP Development Tools" project.

PHP IDE developers have changed the name of their project to PHP Development Tools, to place it into the line of Eclipse project Development Tools with C/C++ Development Tools, J Development Tools, and others. So, if you use PHP IDE in your work, do not forget to update it to the new version of the project with a few bugs fixed and new features added.

He also includes the instructions to make the update to this latest version and the screenshots of a before and after the update's run.

In this new entry on his blog, Alexander Netkachev shares a hint for those PHP IDE Eclipse users out there frustrated with php.ini issues.

You may notice that the IDE does not load options specified in the php.ini and this makes customizing extensions impossible. I run into this problem today and looked over the source code of PHP plugin for it.

The solution he found was in an update he found to one of the Java files, pointing it to the correct location. Changing this changes the default setting for the editor.

In this new entry on his blog, Alexander Netkachev shares a hint for those PHP IDE Eclipse users out there frustrated with php.ini issues.

You may notice that the IDE does not load options specified in the php.ini and this makes customizing extensions impossible. I run into this problem today and looked over the source code of PHP plugin for it.

The solution he found was in an update he found to one of the Java files, pointing it to the correct location. Changing this changes the default setting for the editor.

Wanting to try out something new in the IDE department, Ben Ramsey reached for the Eclipse PHP IDE to see how it ran. His latest post details the installation process he went through to get things up and running.

I already had a working Eclipse installation that I had used to try out PHPeclipse for Eclipse (not to be confused with the PHP IDE), so I didn't want to bother downloading a brand new full package of Eclipse that includes the PHP IDE and all its requirements. So, I set about on a tedious journey to figure out how to install PHP IDE using the Eclipse Update Manager. These are my notes.

There's really only three main steps he went through: disable PHPeclipse (if installed), install the other software needed by PHP IDE, and finally, install the PHP IDE plugin itself. That's it (assuming all goes well with the prerequisites).

You can grab the latest copy of the Eclipse PHP IDE from the project's website.

Wanting to try out something new in the IDE department, Ben Ramsey reached for the Eclipse PHP IDE to see how it ran. His latest post details the installation process he went through to get things up and running.

I already had a working Eclipse installation that I had used to try out PHPeclipse for Eclipse (not to be confused with the PHP IDE), so I didn't want to bother downloading a brand new full package of Eclipse that includes the PHP IDE and all its requirements. So, I set about on a tedious journey to figure out how to install PHP IDE using the Eclipse Update Manager. These are my notes.

There's really only three main steps he went through: disable PHPeclipse (if installed), install the other software needed by PHP IDE, and finally, install the PHP IDE plugin itself. That's it (assuming all goes well with the prerequisites).

You can grab the latest copy of the Eclipse PHP IDE from the project's website.

Following on the heels of these comments from Alexander Netkachev, the Zend Developer Zone has posted the full project plan for the next release of the PHP IDE Zend is working on, version 0.7.

The plan of the 0.7 version is based on the initial SRS which is available here. On top of that SRS many bugs were submitted together with enhancement requests that were/will be included in the 0.7 release. You can find all PHP IDE open bugs here.

The announcement is broken up into three sections - the release deliverables, the release milestones, and the target operating environments - each with plenty of details to show you exactly what the team is working towards.

Following on the heels of these comments from Alexander Netkachev, the Zend Developer Zone has posted the full project plan for the next release of the PHP IDE Zend is working on, version 0.7.

The plan of the 0.7 version is based on the initial SRS which is available here. On top of that SRS many bugs were submitted together with enhancement requests that were/will be included in the 0.7 release. You can find all PHP IDE open bugs here.

The announcement is broken up into three sections - the release deliverables, the release milestones, and the target operating environments - each with plenty of details to show you exactly what the team is working towards.

According to this post from the Eclipse site (mailing list), the PHPIDE code for Zend's project is undergoing a legal review and is awaiting a "legal authorization code".

There's not much more information than that in the main post, but several of the commentators are wondering if this will cause a delay for the next code release, if it will affect the Zend Debugger as well, and if it was an expected legal review.

There's no response yet from Guy Harpaz, the original poster of the thread, but we'll keep you updated.

According to this post from the Eclipse site (mailing list), the PHPIDE code for Zend's project is undergoing a legal review and is awaiting a "legal authorization code".

There's not much more information than that in the main post, but several of the commentators are wondering if this will cause a delay for the next code release, if it will affect the Zend Debugger as well, and if it was an expected legal review.

There's no response yet from Guy Harpaz, the original poster of the thread, but we'll keep you updated.