https://github.com/fredwu/inherited_resources_views

Share and DRY up views between resources. Use with Inherited Resources.
https://github.com/fredwu/inherited_resources_views

Last synced: 12 months ago
JSON representation

Share and DRY up views between resources. Use with Inherited Resources.

• Host: GitHub
• URL: https://github.com/fredwu/inherited_resources_views
• Owner: fredwu
• License: mit
• Created: 2010-08-05T09:01:26.000Z (almost 16 years ago)
• Default Branch: master
• Last Pushed: 2011-05-20T09:19:59.000Z (about 15 years ago)
• Last Synced: 2025-06-05T08:13:57.640Z (about 1 year ago)
• Language: Ruby
• Homepage: http://fredwu.me/
• Size: 149 KB
• Stars: 60
• Watchers: 2
• Forks: 15
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: MIT-LICENSE

Awesome Lists containing this project

README

          
[![](http://stillmaintained.com/fredwu/inherited_resources_views.png)](http://stillmaintained.com/fredwu/inherited_resources_views)

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! :)

# Inherited Resources Views

## Introduction

Using [Inherited Resources](http://github.com/josevalim/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](http://envato.com) and [Wuit](http://wuit.com).

## Difference to Other Seemly Similar Projects

If you are confused about the difference to some other similarly named projects, please read on.

### Difference to Inherit Views

[Inherit Views](http://github.com/ianwhite/inherit_views) adds the ability to render views from parent controllers. It does not share views between different resources.

### Difference to Inherited Views

[Inherited Views](http://github.com/gregbell/inherited_views) tries to solve the same problem we're solving, but from a slightly different angle. It is more complex, requires [Formtastic](http://github.com/justinfrench/formtastic) and [WillPaginate](http://github.com/mislav/will_paginate), 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](http://github.com/josevalim/inherited_resources)), and it supports both erb and [haml](http://github.com/nex3/haml) templates.

## Dependencies

* [Inherited Resources](http://github.com/josevalim/inherited_resources)

## Limitations

When using Rails 2, the generator only generates `Erb` templates, whereas using Rails 3 it generates `Erb` or `Haml` templates accordingly.

## Installation

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

## Usage

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!

## Author

Copyright (c) 2010 Fred Wu (), released under the MIT license

* Envato - 

* Wuit -