The IBM developerWorks website has a new tutorial for those looking to get into the powerful combination of Ajax and PHP - an introduction to creating Ajax-based websites with PHP.

Learn the process of writing Asynchronous JavaScript + XML (Ajax) applications using native JavaScript code and PHP. This article introduces a few different frameworks and application program interfaces (APIs) that reduce the amount of code you need to write to achieve a complete Ajax-based Web application.

They (briefly) explain what Ajax is and the benefits of it before jumping right in to a sample page. They go for the "manual first" approach so developers know to make basic connections with the XMLHttpRequest object and handle the responses. They do mention some of the libraries offered that help with the connections too (like jQuery, Prototype and Dojo).

Paul Reinheimer has a suggestion on how to improve the PHP manual to be an even better resource - enhancing the "see also".

Something I'd like to see in PHP is a little more in the See Also section. They're pretty good, but it's not quite as spider-web like as I'd like. For example, yesterday I added a few links from md5() and sha1() to hash(). Lot of people know about md5() and sha1() within PHP, but I find hash() is rather unknown overall, which is a pity as it exposes a tone of different hashing algorithms.

You can see an example of his updates in the md5 manual page linking it to sha1_file, crc32, sha1 and the hash functions.

The PHP.net website has a note posted about the restructuring of the manual

A few weeks ago the manual was restructured to improve navigation and make room for per-extension chapters and usage examples along with improved documentation for object oriented extensions.

Changes were made in the function reference and in the predefined variables and context options/parameters sections as well as information on upcoming features like namespaces, late static bindings and Phar (to be included in PHP 5.3). The manual is now covered by the CreativeCommons Attribution license.

In this new post, Chris Hartjes takes a look at something that is one of the banes of most programmers' existence - documentation. In it he wonders what should really be considered documentation and the importance of it.

As a committed user of open source technologies, the difference between me using something and not using something is the documentation. Is there documentation for it? Is it easy to find? Does it answer my questions? Is there someone I can call an idiot if I disagree with the level of documentation? These are all very important questions.

He uses the illustration of the documentation of the CakePHP framework that's helpful, but only really after you learn how to use the framework in the first place. He mentions people on both sides of the fence - those that love the framework and love the documentation and those that moved on to something simpler because they just couldn't get it.

He also mentions the variety of sources that can provide "documentation" for the framework when you're getting a bit stuck - everything from blogs to The Bakery to a different sort of documentation, unit test.

Several updates have been made to the documentation for the PHP-GTK project including a version of the manual.

From Leon Pegg on the PHP-GTK Community site:

I have been working on the php-gtk documentation the last few weeks. I finally have an updated version of the manual. Unfortunately its not on the main site gtk.php.net, so I have uploaded it here: leonpegg.com/php-gtk-doc

The manual includes tutorials, the actual reference guide and an appendix of details on terms/other information.

In a new post, Greg Beaver talks about a few things, the main one being a new release of the phar extension he's made - phar version 2.0.0a1 - a reworking of the previous functionality with loads of new features including:

• Phar now supports tar and zip archives with the same API that is supports phar archives.
• Phar has a front controller for web applications that fully handles MIME types, supports mod_rewrite-like functionality with far more flexibility
• Phar supports phar:// stream wrappers in include_path for PHP 5.2+
• Phar supports creation and modification of data-only tar and zip archives (no executable phar stub) via the PharData class.

There've also been updates to the manual for the project to reflect this new version of its API. You can download this latest version here: source or Windows DLL.

Chris Hartjes has posted about a new resource that he "cannot stop recommending people to use [it] when searching for answers to their CakePHP problems" - the CakePHP Cookbook.

With a ton of help from Andy Dawson (AD7Six) the documentation for CakePHP 1.2 has moved forward immensely with the unveiling of the CakePHP Cookbook. It's a combination of manual and wiki, where people can flesh out the manual and make comments on the methods in there.

With the wiki in place, anyone can add to the communal CakePHP wisdom (or correct where others might have strayed) to make it a bigger and better resource for the whole range of CakePHP developers.

Finishing off their series on destructors in PHP5 applications today, DevShed has posted this new tutorial showing how to manually run the destructors of your class (in case there's ever a need).

In this final tutorial of the series I'm going to show you how to manually trigger a destructor, and in addition you'll learn how to emulate the behavior of this magic method when using PHP 4.

They not only talk about how to call the destructor manually but they also show how to call multiple destructors at the same time to destroy lots of objects at once. And, as promised, they include a method for being able to use a destructor-like bit of functionality in a PHP4 app as well.

New on the Developer Tutorials blog today is this post offering up a few ideas (five of them) on how they think you can become a better programmer.

In this post, I'll outline five ways to be a better developer, improve your productivity, write less code and achieve more with your web applications.There's always more to learn when it comes to PHP development. New core functions, new frameworks, new design patterns, new code documentation styles. Here are some of the best ways you can become a better PHP developer.

His five suggestions are:

• Read the manual
• Browse through some code
• Learn a new framework
• Research
• Learn OOP

I can understand where he's coming from on all but the third one - frameworks are nice, but it's more important to get the fundamentals down first before making a framework some of your first experience.

Sometimes, you just can't get to a web browser to look up something from the PHP manual (or might not want to). Another option is the command line and in this new post to the SitePoint PHP blog, Troels Knak-Nielsen shows you a method for getting the entire manual entry right at your prompt neatly formatted.

One thing, I missed with either of the two [other solutions mentioned], was the ability to see the entire manual entry. It's quite often, that the manual actually holds useful information (Who'd known that!), so I find myself using www.php.net a lot. Or I did, until I decided to do something about it. Now, shell-scripting isn't what I spent most of my time on, so it's not with out a bit of pride, that I present to you phpm two-oh.

Most of the rest of the post is his bash script ready top cut and paste as well as some simple instructions on getting it working. (An emacs bonus is also included - a method for binding the script to a key to act on the current word.)