# DRYing up controllers

**URL:** <https://www.ruby-forum.com/t/drying-up-controllers/135788>\
**Category:** Rails\
**Created:** [April 24, 2008, 11:42pm UTC](https://www.ruby-forum.com/t/drying-up-controllers/135788 "2008-04-24T23:42:44Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![jasonb](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/a587f6/32.png) [@jasonb](https://www.ruby-forum.com/u/jasonb)\
**Post date:** [April 24, 2008, 11:42pm UTC](https://www.ruby-forum.com/t/drying-up-controllers/135788/1 "2008-04-24T23:42:44Z")

</div>

Hi

I’m a big fan of plugins such as Resource Controller  
[http://jamesgolick.com/2007/10/19/introducing-resource\_controller-focus-on-what-makes-your-controller-special](http://jamesgolick.com/2007/10/19/introducing-resource_controller-focus-on-what-makes-your-controller-special)

However, recently decided I don’t want to depend on a plugin for this,  
and would rather stick closer to the rails core.

So does anyone have any cool strategies or ideas for achieving this?

Or is there any move to make this possible in the edge rails?

thanks

---

<div class="post-metadata">

**Author:** ![jasonb](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/a587f6/32.png) [@jasonb](https://www.ruby-forum.com/u/jasonb)\
**Post date:** [April 26, 2008, 11:03am UTC](https://www.ruby-forum.com/t/drying-up-controllers/135788/2 "2008-04-26T11:03:57Z")

</div>

Anybody? any ideas?

---

<div class="post-metadata">

**Author:** ![jasonb](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/a587f6/32.png) [@jasonb](https://www.ruby-forum.com/u/jasonb)\
**Post date:** [April 26, 2008, 2:53pm UTC](https://www.ruby-forum.com/t/drying-up-controllers/135788/3 "2008-04-26T14:53:48Z")

</div>

Hi –

On Sat, 26 Apr 2008, jasonb wrote:

> > However, recently decided I don’t want to depend on a plugin for this,  
> > and would rather stick closer to the rails core.
> > 
> > So does anyone have any cool strategies or ideas for achieving this?
> > 
> > Or is there any move to make this possible in the edge rails?

Part of the difficulty in answering is that the plugin system _is_  
part of the Rails core, so it’s not clear why it’s not satisfactory.  
If you just want not to have to install the same plugin over and over,  
maybe you could adapt it as a gem and install it site-wide.

David

–  
Rails training from David A. Black and Ruby Power and Light:  
INTRO TO RAILS June 9-12 Berlin  
ADVANCING WITH RAILS June 16-19 Berlin  
INTRO TO RAILS June 24-27 London (Skills Matter)  
See [http://www.rubypal.com](http://www.rubypal.com) for details and updates!

---

<div class="post-metadata">

**Author:** ![jasonb](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/a587f6/32.png) [@jasonb](https://www.ruby-forum.com/u/jasonb)\
**Post date:** [April 27, 2008, 5:59am UTC](https://www.ruby-forum.com/t/drying-up-controllers/135788/4 "2008-04-27T05:59:50Z")

</div>

Well sometimes I feel it’s not a good idea to be dependent on plugins  
that make up for missing fundamentals. (In this case I think it is  
just that, but people might disagree).

Was just hoping people would have ideas on how to DRY up all that  
controller code in a more basic fashion. The related plugins tend to  
be feature rich, and using them feels like committing to a “branch” of  
rails.