When you use Ajax with PHP, PHP does the calculations that it needs to do on the server and sends the result back to the page. You then use JavaScript to display these results in a predefined place. The demo application you will learn how to build in this article is a very simple Suggestion box, just like the one that Google made famous and thus ushered in the Ajax era.

The example (you can download it here) creates a basic form text field and the Javascript you'll need to make the callback to the waiting PHP script. It doesn't use any external libraries (like jQuery or Prototype) so be ready for bare-bones Javascript.

Since I last posted here we also published the schedule. We were overwhelmed by the quality of the call for papers and there are some cracking sessions, excellent speakers, and lots of overlap between the two! [...] Finally, this year PHPNW is expanding and has added an informal schedule on the Sunday morning since we know lots of people will be staying over. This will run from 9 til 1 and we've put out a call to ask what people would like to see on the schedule.

The Sunday event (held here) is a time for both current presenters and attendees to cast their vote on topics they really want to hear about (outside of the excellent sessions already lined up, of course).

For more information about the conference or to purchase your tickets, check out the page for this year's event. The deadline for the early bird ticket pricing is September 12th.

I've annoyed PHP enthusiasts, friends and colleagues alike, with my distaste for PHP. There's nothing intrinsically bad, buggy or poorly performing about PHP per se. It's real simple: a lot of PHP code that I've had to pick up the hood on is a mess and is susceptible to worlds of instability and bugs.

I'm confident that I or someone else could eventually derive a tool set that meets a rigorous standard for maintainable code. What concerns me are the prevalent practices and establishing best practices. I want to work with the someone else to establish them.

Among his suggestions are included things like "use clear APIs in classes" and "use frameworks to encourage separation of concerns". He also suggests a more wide use of unit testing in PHP to help rid your apps of common issues...]]> Wed, 15 Feb 2006 07:30:06 -0600