There's been a lot of talk about decorators and presenters (which are almost the same) in Rails and how they help you with a "real" OO code. There are great gems and there's even a Railscast (pro) on how to build a presenter from scratch. But, in the new project I'm working on, we (he) have this very simple setup which I feel kind of cleaner.

What we wanted to have was a present method in the controller and build the view from its methods. So, we created an ActiveSupport::Concern called Presentable and included it in our application controller. Here's our (once again, his) code for that module.

# app/concerns/controllers/presentable.rb

# Presentable Concern
# Include this module in the controllers where
# you need the `present` method.
module Presentable
  # This method returns a Presenter Object to work
  # with in the view.
  # Attributes:
  #   object:   The object to present
  # Supported Options
  #    as:   The presenter class. If this is not suplied
  #          the method will try to guess the class
  #          e.g: UserPresenter for a User object.
  def present(object, options = { })
    if object.respond_to?(:first)
      return [] if object.empty?
      presenter = "#{object.first.class.to_s.pluralize}Presenter"
      presenter = "#{object.class}Presenter"

    presenter = options.fetch(:as) { eval(presenter) }

Now, we just need to create each presenter. But, since there's a lot of shared logic between presenters we (he) just created a parent Presenter class with all that. Notice that our presenter takes an object as parameter, so we just delegated all the method calls to our record (thank you method missing) if it responded to that method. You could also send the view context to access Rails helpers inside your presenter. Here's our Presenter base class.

# Base presenter class
# All presenters should inherit from this one.
class Presenter
  # Include all the modules you need or
  # send the view context to access rails helpers.
  include Rails.application.routes.url_helpers
  # ...

  include Presentable

  attr_reader :record

  def initialize(record)
    @record = record
    @klass = record.class

  def method_missing(name, *arguments, &block)
    super unless record.respond_to?(name)
    record.send(name, *arguments, &block)

  def translate_field_name(name)

  # UrlHelper was being an ass, easier to go commando.
  def link_to(name, url, options={})
    href = { :href => url }
    content_tag(:a, name, options.merge(href))

Then, we just need to inherit from the Presenter class and add our custom, clean methods. Using delegate and method missing will help us keep the class clean. I won't show you a presenter here, they'll look a lot like Ryan's one in his Railscasts so check that out first.

I will show you our controller though. Using the decent_exposure gem we managed to get super tiny controllers. Here's 1 of them:

class RequestsController < ApplicationController
  expose(:filter) { params.fetch(:filter) { :all} }
  expose(:filtered_requests) { Request.filter(filter) }
  expose(:requests) { present(filtered_requests) }

  before_filter :find_request, :only => [:show, :destroy]

  def index

  def show
    extend(RequestRedirector) # Another concern

  def destroy
    redirect_to requests_path(:filter => "new_requests"), :notice => "Se ha eliminado la solicitud"

  def find_request
    @request = Request.find(params[:id])

Combining presenters and form builders will make your views even cleaner, giving a lot of pleasure to the future you! So please, just pretty-please, start using presenters and builders and leave helpers as simple as possible. Or, leave them for good.

You'll be amazed how different you'll feel when reading some old code or some co-worker's code.