We've now finished a screencast demonstrating PHP 5.3 namespace support in NetBeans IDE 6.8. (See Code Completion for Namespaces part I). The screencast also shows code hints for assigning variables, namespace naming hints, and how to set the options for PHP code completion.

You can check out the screencast in the bog entry or directly. You can find out more about the NetBeans IDE at Sun's NetBeans for PHP website.

After a few days, we would like to inform you that code coverage for PHP has been added to the NetBeans IDE. Thanks to PHPUnit (version 3.3 or newer required) we are able to provide code coverage for PHP files in a similar way as for Ruby or Python.

They give the step-by-step (screenshotted) process for running a coverage report on your current project and how to view which tests passed or failed validation.

I thought I'd start with a quick thank you to all those groups and entities involved indirectly with PHP. The PHP project relies on donations to provide our service infrastructure, this is in the form of hardware and hosting from both individual companies and hosting companies to provide collocation.

Besides the hardware support there's also companies willing to allow their employees time to work on the project (such as Pierre from Microsoft). Other companies that have made large contributions include IBM's large amount of testing, Sun's work to improve PHP on Solaris and, of course, Zend's support of the project and the time its employees spend developing the language.

Long dismissed as a "toy Java IDE", NetBeans - Sun's open source Integrated Development Evironment (IDE)-has really grown up in recent years. No longer is it just for Java, either: for web developers, NetBeans 6.5 now supports Ruby and PHP out of the box. Surprisingly, that support is so good that it now compares favourably to more established competitors like Eclipse, Komodo IDE, and Zend Studio.

He mentions the built-in/user-defined auto-complete the has built in as well as code templates, support for phpdoc documentation blocks, and other functionality for helping with Javascript, HTML and CSS.

As I switched my main system recently from Linux to OpenSolaris I compiled PHP. Quiet obvious things are a little bit different on Solaris. The usual ./buildconf && ./configure && make install doesn't work anymore. The good news: It's not much harder.

A few extra packages are required (like SUNWgmake, SUNWgcc and SUNWbison) and the Re2c library, but after that, it's just like a normal install. All commands needed to make the build are included in the post.

NetBeans, the open-source development environment sponsored by Sun, is planning to include support for PHP frameworks in its upcoming versions. As there are so many PHP frameworks, NetBeans developers have organized a public election to choose the two PHP frameworks that will be initially supported.

Instructions on how to vote are included (you will need to register to get to the voting form).

With all of the buzz floating around yesterday on this topic, I decided to let some of the dust settle before posting. From everything I've seen, the PHP community is largely positive about the news. [...] As I said, the community at large seems to be pleased with this news. Here are the links I've collected so far.

Names in the list include Andi Gutmans, Lukas Smith and Jaremy Zawodny. There's also a list of some comments from the "pundits" as to what this purchase could mean for the web as a whole.

un Java System Web Server is a mature, highly scalable, and secure web server that provides process redundancy, request scalability, and a wide range of application programming interfaces (APIs) to create and serve dynamic content. This document describes how to install and use PHP with Sun Java System Web Server (hereafter Web Server).

The tutorial is divided up into seven sections (including some reference material):

• Understanding PHP and Web Server
• Running the PHP Engine
• Installing the PHP Engine as a CGI Program
• Installing the PHP Engine as a FastCGI Server
• Installing the PHP Engine as an NSAPI Plugin
• Conclusion
• References