My entirely arbitrary and prejudiced selection of the best of RejectConf at RailsConf Europe.
list_for a rails plugin to help with displaying sortable lists.
macistrano a native mac application for running capistrano.
braid does for git repositories what piston does for svn repositories.
conductor makes it easier to deal with rails actions that update more than one object.
Most entertaining presentation: Definitely Matthew Rudy with his plugin make_specs_better.
A few links if you want to follow what’s going on at RailsConf Europe.
Technorati, Google Blog Search, Flickr and
delicious.
I’ll update this post if I find more or better searches.
For some time now I’ve been putting about the idea in my company that we should have a smarter way of managing application exceptions. But the idea has never floated to the top of the pile.
Now there are two sites (maybe more) offering this as a feature. They both appear to collate stats on exceptions from your rails application, so that you can easily spot the difference between exceptions that bug your users every hour of the day, the ones that happen once in a blue moon, the ones that occur right after code deployment, etc.
They are getexceptional and hoptoad.
Look forward to playing with them.
I’ve discovered Luke Redpaths ActiveSpec gem, and it looks great, particularly for validating objects conditionally based on state. Example:
class User
must_satisfy :valid_user_specification
must_satisfy :activated_user_specification,
:if => :activated?
end
That’s a lot neater than lots of conditionals scattered through validation statements. And funnily enough, this precise scenario (users validating differently depending on activation) is something I was working on two weeks ago.
