Since Rails 3.1 has view inheritance built in, it effectively renders this gem useless. The amount of time and effort to get all the issues sorted and tests added are too significant to warrant any more releases. If anyone is interested in taking over the project, please let me know! :)
Using Inherited Resources is an excellent way to reduce the amount of repetition in your controllers. But what about views? A lot of times resources share the same views, so why not DRY 'em up using Inherited Resources Views!
Brought to you by Envato and Wuit.
If you are confused about the difference to some other similarly named projects, please read on.
Inherit Views adds the ability to render views from parent controllers. It does not share views between different resources.
Inherited Views tries to solve the same problem we're solving, but from a slightly different angle. It is more complex, requires Formtastic and WillPaginate, and it only generates erb templates. Inherited Resources Views on the other hand, is extremely simple, is library-agnostic (it only depends on Inherited Resources), and it supports both erb and haml templates.
When using Rails 2, the generator only generates Erb templates, whereas using Rails 3 it generates Erb or Haml templates accordingly.
As a Rails plugin:
# rails 3
rails plugin install git://github.com/fredwu/inherited_resources_views.git
# rails 2
script/plugin install git://github.com/fredwu/inherited_resources_views.git
As a gem:
gem install inherited_resources_views
It is extremely simple to use Inherited Resources Views. The only step you need to do after the installation is to customise the default views:
# rails 3
rails generate inherited_resources_views
# rails 2
script/generate inherited_resources_views
# Please remember to restart your server!
This will generate a set of views in your app/views/inherited_resources folder. Edit away!
Copyright (c) 2010 Fred Wu (http://fredwu.me), released under the MIT license
- Envato - http://envato.com
- Wuit - http://wuit.com