Emulating preprocess theme functions in Drupal 5

Drupal 6 introduced the concept of a theme preprocess function. In short, it allows themes, theme engines, and even modules to step into the theming process and manipulate the variables that get sent to a template. It replaces the older, clunkier _phptemplate_variables() function from Drupal 5's phptemplate templating engine, but serves much the same purpose.

While we can't backport all of that new functionality, it is possible to greatly simplify _phptemplate_variables() in Drupal 5 in a way that looks a lot like Drupal 6. Specifically, we can break up _phptemplate_variables() into separate functions that act like a theme's preprocess functions in Drupal 6.

Quote 88

Learning curve: Doing -> Experience -> Understanding -> Trust -> Patience

— Anonymous

Benchmarking magic

The day is nearly upon us! Drupal 7 will open up developers to PHP 5 functionality when it is released next year. Already, there is talk of how, and if, to leverage PHP 5's object handling now that we don't need to deal with the weirdness of PHP 4's object model. Of course, because it's Drupal, our army of performance czars want to know just what the cost is for object handling, and especially advanced object magic like __get(), __call(), the ArrayAccess interface, and so forth.

So let's find out. :-)

What file extension are you?

Given that I'm a Kubuntu user, I will try not to take this personally...

Good SPL intro

One of PHP 5's coolest features is the Standard PHP Library, or SPL. If you're operating in an OO way, SPL is a great way to easily leverage a huge amount of functionality.

Of course, the main problem is that the official documentation on it sucks. At best it points to an off-site series of class hierarchies. (Technically it's not off-site, but not internal to the manual.)

DrupalCon Barcelona: Best DrupalCon Ever!

So it's been a week since DrupalCon, which means I'm kinda sorta caught up enough to write about it. Hooray!

As with DrupalCon Sunnyvale, I came away with one conclusion fixed in my mind: The Community is Drupal's greatest strength. Virtually everyone upholds a strong community and open source spirit, and will gladly talk to you for hours about subjects both on topic and off, with or without beer (free or otherwise).

But enough about how cool we are. On with the rundown.

Limerickal Drupal

You know you're in a healthy community when people randomly offer limericks in return for code reviews.

And it's especially healthy when it randomly spills over into IRC:

Dropping Rails, but not its bad lingo

A ran across this article recently making the rounds. In it, the author discusses spending 2 years in Ruby on Rails land before finally giving up and coming home to PHP, wiser for the experience. It's a good article, but one thing in it really raised the hair on my neck.

Quote 81

Sometimes I feel like I'm trying to become an exception to the Turing Test.

— Colin Wyers

DrupalCon Barcelona Day 0

T'was the night before DrupalCon and all through the city, not a hacker was typing, not even a key.

Syndicate content