Spam: The other white meat

I recognize that this is old news for some, but I've finally had reason to use the Growl module for Drupal. Getting fast reporting of logged errors is really handy without having to flip through tabs to find out what thing I just broke. There are not any instructions with the module, but it is easy enough to get it up and running. The real trick is making sure that you have the grownotify script in the correct place.

While I'm a staunch proponent of building code that reuses other work as much as possible, there comes a time when new ideas, implementations, or just plain better work means either your dependencies are co-dependent (ha) or simply obsolete.

If you're interested in doing code profiling, KCachegrind is a great utility to investigate what part of your code is hogging CPU time. If you're on a debian or ubuntu machine, it is simple to install. If you're on OSX... well you've got a bit of work to do.

UDPATE: http://drupal.org/project/mail2og
I'm working on a connector between Mailhandler and organic groups that will allow site users to post content to groups via a specific email address. While mailhandler does support this the configuration that I'm interested in doesn't seem to exist yet. Instead of using Mailhandler's syntax for creating nodes, I want users to be able to post via a specific email address- for example groupname@mysite.com.

Frost posted some nice documentation on FLV Media Player

beksau posted a really helpful tutorial on how to integrate mobile technology (eg: mobile phones) with Media Mover to create an automatic transcoding system for posted content. Beksau's process uses mailhandler as a standalone rather than integrating directly with Media Mover, but from my perspective, it just showcases the fact that you can make very creative systems for handling content- Media Mover is flexible enough to plug in to what you are already using.

As I've been working on getting the 6.2x branch of Media Mover up and running, I've started going through the old code and cleaning up the Doxygen documentation so that my own documentation effort is a bit cleaner. I'm now generating daily snapshots of all three branches here: doxy documentation

UPDATED

After some consideration and discussion with Robin I think my first go at hook_media_mover is off the mark. Using hook_menu as the template, I think the process of defining media mover actions can be simplified:

function mm_node_media_mover() {
  $items = array();
  $items['set_node_status'] = array(
    'description' => t('Set node status'),
    'configuration' => 'mm_node_config_complete',
    'callback' => 'mm_node_complete',
  );
  return $items;
}

$items[NAME] identifies the specific action. The individual items for each action- description, configuration, callback, harvest provide information about what to do with this action.

In an attempt to improve the workflow of Media Mover, I'm going through the process of refining the main API aspect. The main reason for this is to move away from the 4 step model (harvest, process, store and complete) to a chainable set of definable actions.

These are some notes to self as I'm going through the process, but feedback is of course appreciated

function hook_media_mover() {
  return array(
    '#name' => t('My Media Mover module description'),
    '#actions' => array(
      array(
        // give each action in your module a unique id 
        '#action' => 'operation_1',
        // give your action a description
        '#description' => t('Do something with a file!'),
        // harvesting files is a special case. You only need

I've been helping to organize the Onion River Racing Criterium which debuts in just over a week. We've got a great course, three categories, and a great location. Check out the announcement, and registered on Bike Reg.

Course: The 0.9-mile circuit around National Life Group’s headquarters consists of a 300 meter long downhill followed by a hard right hand corner, a winding 350 meter uphill section in two steps, and a flat section through the upper parking lot to the start/finish on a flat straightaway near the main entrance. There will be no neutral support – so bring your own spare wheels. Free Lap rule in effect. Course closed to traffic.