A Rails plugin that delivers a special message to DiggBar users, or runs frame-killer javascript.

SWFRIP is a Macromedia Flash resource extractor and editor. It can save resources in various formats, including SVG conversion from the flash vector format, decompile ActionScript, and remove the protect tag from SWF files.

In this presentation, I demoed Cucumber and Webrat. I also talked about Integrity and how I like to put it all together.

Integrity is the angel watching over your shoulder while you code. As soon as you push your commits, it builds, runs your tests, and makes sure everything works fine.

I believe that the current specification of the element is vague because it avoids the question whether the element is safe for historians. Right now it hurts historical research more than it helps

MMM (MySQL Master-Master Replication Manager) is a set of flexible scripts to perform monitoring/failover and management of MySQL Master-Master replication configurations (with only one node writable at any time). The toolset also has the ability to read balance standard master/slave configurations with any number of slaves, so you can use it to move virtual IP addresses around a group of servers depending on whether they are behind in replication.

Code smell detector for Ruby

Cache Money is a plugin for ActiveRecord that transparently provides write-through and read-through caching functionality using Memcached. With Cache Money, queries are automatically cached for you; and similarly, cache expiry happens automatically as after_save and after_destroy events.

HTML sanitizer by the wonko.com guy.

A simple web-based WYSIWYG editor, written in MooTools.

I’m working on a problem for a client which involves connecting to a Microsoft SQL Server 2005 database from Linux using Ruby. Here’s what I did to get it working, based off some useful instructions that are tailored for Ruby on Rails:

Central point to collect locale data for use in Ruby on Rails.

Unfortunately, by default plugin tests are pretty bland. They use the plain unit test suite supplied by Ruby, and not any of the extended Rails test framework. This will leave our plugin’s test classes with no access to fixtures, database.yml configuration, or any of those nice class auto-loading features.

A surprisingly large number of plugins have no tests at all. Part of the reason might be that writing a plugin test is a little bit harder than writing a normal unit test.

After 2 1/2 years of blood, sweat, tears, and the occasional Jägermeister, I’m finally officially announcing a project I’ve been quietly working on: state_machine.

Simplifies plugin testing by creating an isolated Rails environment that simulates its usage in a real application

This article is an introduction to testing Rails plugins.

It turned out that the test subject didn't know that longdesc even existed before the tester told him about it. Can you blame him?