Project

inherited_resources_views

0.03
No commit activity in last 3 years
No release in over 3 years
inherited_resources_viewsfredwu/inherited_resources_viewsHomepageDocumentationSource CodeBug Tracker
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!
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
 Popularity
Downloads
42,597
Stars
60
Forks
12
Watchers
3
 Releases
Current version
0.4.1
Total releases
8
First release
2010-08-04
Latest release
2010-11-03
 Issues
Open Issues
0
Closed Issues
13
Total Issues
13
Issue Closure Rate
100%
 Pull Requests
Open Pull Requests
0
Closed Pull Requests
3
Merged Pull Requests
0
Pull Request Acceptance Rate
0%
 Development
Primary Language
Ruby
Average date of last 50 commits
2010-10-05
Reverse Dependencies
1

 Dependencies

Development

hpricot
>= 0
ruby_parser
>= 0

Runtime

inherited_resources
>= 1.0
 Project Readme

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 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.

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 adds the ability to render views from parent controllers. It does not share views between different resources.

Difference to Inherited Views

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.

Dependencies

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 (http://fredwu.me), released under the MIT license