But a problem I came across several times was the sheer complexity of recursive element conversion �'" <code> becomes <jsvalue> (or one of a dozen similar elements), <a> becomes <xref> �'� and that's all simple enough; but each of these elements might contain the other, or further child elements like <em>, and as we walk through the DOM so the incidence of potential recursion increases, until it gets to the point where my brain explodes.

His solution involves working with both regular expressions and document fragments. He loads the node he wants to work with, its parsed to prepare it and is passed off to do the "text-based mangling" to update it. The result is them pushed back into an XML object (fragment) and this is pushed back into the main document with a replaceChild call.

While I would personally prefer an exception to be thrown in the first place, it is pretty easy to convert errors to exceptions in PHP.

His example is pretty simple - you set a custom error handler in your script that pulls in the error information and tosses an exception based on the error number the handler is given. Then you can use the try/catch method to see if your script has tossed an exception of the fatal error type. Nice simple solution to handle an interesting little problem.

In this multi-part series I'll detail how to create and design a Wordpress theme from nothing more than your imagination using Photoshop, CSS, XHTML and PHP.

Here's the list so far:

• Part 1 - getting the tools and an overall layout idea
• Part 2 - splitting it up to make the layout parts
• Part 3 - converting the Photoshop template to XHTML
• Part 4 - cleaning up the XHTML and doing some styling with CSS
• Part 5 - how to preload some images with Javascript to make the page load faster
• Part 6 - creating the WordPress-specific markup
• Part 7 - working up the PHP functionality
• Part 8 - integrating PHP into the template
• Part 9 - marking up the "framework" of the site (header/footer/sidebar)
• Part 10 - adding additional files like a links page and changing the posting template
• Part 11 (?) - deploying the theme out to the public view

In this article I'm going to show you how you can use PHP to encode your data for transit. Most importantly, it will be done in a way that makes the data decodable, and therefore much more usable, by the receiving page.

His encryption method - sending everything in a single string and modifying the scheme each time - uses static pairs of values (of your choosing) to "encode" the outgoing string. It actually consists of three different files: the script itself, a single-use script that makes the third file, an include file to handle the conversion back from the encoded results.

When you're dealing with special characters in a database, you have to make sure that the charset and collation are dumped *with* the database, so that when you move it to another server the tables and data create properly. The biggest annoyance so far is converting tables back to UTF-8, as when this is done through the MySQL shell or phpmyadmin is had to be done table-by-table.

The script logs into the database and pulls all of the table information out (could be a lengthy list depending on the database) and runs an ALTER TABLE to change its character set to 'UTF8'.

With a function on this site: explodeTree(), you can explode any single-dimensional array into a full blown tree. The function uses a user-specified delimiter found in the keys of the original array to separate nodes and determine hierarchy.

Sample: with 3 lines of code you could have a full directory hierarchy in a multi-dimensional array if you specify the delimiter to be a '/' (slash).

Not only is the code included to make the tree from the data, but an example block of code showing how to use the result.

So, as I�'�ve written in an earlier article on how to install FFMPEG on your server, while there are those who probably use a �'�YouTube Clone�'� script, there might be those who want to create their own using FFMPEG & PHP. FLV is the most widely used type of codec that runs on most Flash players.

The tutorial started with a diagram that outlines how the mini-app will work and is followed by the source. The script sets up the environment then grabs the file and sends it to the FFMPEG handler to be parsed and output as the FLV file (courtesy of a few handy command line parameters).

Until recently I thought that currently popular scripting languages, which mostly evolved over last 10 years or something, must allow for easier portability across different platforms compared to ye good olde C/C++.

However, PHP just brought me a new definition of "portable" - and that was when working with... integers.

He points out that PHP isn't able to correctly handle unsigned integers ("and converts values over 2^31 to signed"). He goes on to talk about how this differs between platforms too (32 vs 64 bit) and some of the research he did to find out just what was going on (including some code examples to illustrate the point).

The reason I'm revisiting blackjack is because I have a C++ version and I want to port it to PHP, for fun. If you want to have a simple project for learning a language, other than "Hello World," then Blackjack is a good project.

Since Blackjack is a relatively simple game (as far as the rules go, that is) he chose a simple C++ version to port over. He sets up some guidelines first - break down the code into simple, reusable parts and keeping it as simple as possible. Most of the rest of the code is dedicated to the code:

• Game start
• Statistics handling
• Randomization
• Looping
• Conditional statements

With the growing popularity of Web 2.0, a new data interchange format called JavaScript Object Notation (JSON) is emerging as a useful way to represent data in the business logic running on browsers. Learn how PHP-based server programs can convert XML-formatted enterprise application data into JSON format before sending it to browser applications.

The article starts with the basics, XML and JSON, then moves quickly on to other topics like "browser-side data processing" and "xml-to-json conversion". From there, it's all about the code - creating the xml2json script to make the transition simple. It incorporates the Services_JSON package to help with the handling.

The entire code is laid out in one block, making it simple to cut & paste and mess with a bit. They even include a sample of its usage as a command line script, complete with sample input and the resulting output.