Kevin:

This looks pretty good.  Two really minor comments below.

I think ChipX86 or purple_cow should give this a once-over before it get's shipped - we're reusing some code here, and it might be more awkward than they'd like.

Thanks,

-Mike

I think this is a little confusing/misleading.  Developers might try to set options as a list of ActionHook objects.

Maybe say, "a list of ActionHook-style dicts".

I'm not sure if that's any clearer.  :/

space before "actions"

The comment should be more like the one above. It should be clear from reading it exactly what it's purpose is.

First line, on the """, in the form of a quick summary without "This is" or similar.

Shouldn't have so many spaces after the :

I'm also confused about this. Also the "see above." What should be in here? Is it actually ActionHook instances?

One line.

This must wrap to < 80 characters. Probably want one parameter per line.

Also, spaces after ",".

The image path is being hard-coded and doesn't contain a media serial. Please use:

{{MEDIA_URL}}rb/images/dropdown.png?{{MEDIA_SERIAL}}

No spaces before this. Instead, put spaces after the {% for indenting.

Committed with a few style fixes. Thanks!

There are a few small question marks in my head about the bet way to implement this dropdown actionhook. I almost want a standard ActionHook to be able to supply sub-items. Also, I sort of think it should be more generic so it can be used in the diff viewer too. However, it's fine for now, and I think it's very likely we'll be revisiting how actionhooks work by the time we ship extensions in a release.