I was having lots of problems with HTML email layouts. After doing some research, I came up with a method to get almost pixel-perfect positioning and sizing. It's not that hard.

Here's one for the noobs (from a noob). This demonstrates the use of shared memory. It's a program that spawns 10 children, and each one gets a special "babytalk" word to say.

I've never put a ID onto the BODY tag, but here's a situation where it's useful.

Normally, an article has an H1 tag that contains the title for the page.  You do this for SEO reasons, as well as semantics.

nzakas has a great presentation about speeding up Javascript loops but it applies to any language that uses C-like loop structures.

This rant is so right. SFF computers with power bricks suck.

One of the big problems with PHP is the include statement. You can include a file. You can define that file at runtime, and alter it during runtime.

Here's a way to cache data on the client side, via javascript. This was tested on Firefox 3.6.3 on Ubuntu.

The idea is to convert your data into Javascript, and then load it with the SCRIPT tag. You then use the Expires HTTP header to tell the client how long to cache the data. Finally, you use some Javascript code to display the data.

Here's some HTML and CSS to make an image with a transparent caption that displays over the image.

<style type="text/css">
  .caption-background {
      width: 500px;

Here is something I can't understand The CodeIgniter Loader class.

It's just weird. When you load a class, it's instantiated and made an attribute of the $this object. That has a real "Javascript" feel to it.

Beyond that, I think class loaders sometimes obfuscate where the included files reside. That might seem okay, or even "cool", but I find it annoying.

The old Slaptech framework had the old PHP includes problem, where one cannot to include() a file relative to the current file.

This small alteration to the PHPList code will produce better line breaks.

sendemaillib.php:

  $text = preg_replace("/<\/p\s*?>/i","<\/p>\n\n",$text);

So, the tokenizer's done, and the parser's code is written but not tested. The standard testing system included with NetBeans is JUnit.

Many years back, just before web pages got popular, I remember that some programs sent you as close as possible to your desired data whenever you searched.

I was messing around with some textual analysis, trying to figure out how to do a "related articles" feature in Drupal.

A few years back, method chaining got to be all the rage, and now it's common.