inherited_resources_views 0.1.2 → 0.2.0

data/README.md

@@ -25,7 +25,6 @@ If you are confused about the difference to some other similarly named projects,
 
 ## Dependencies
 
-* **Rails 3.0+**
 * [Inherited Resources](http://github.com/josevalim/inherited_resources)
 
 ## Installation
@@ -44,7 +43,7 @@ It is *extremely* simple to use Inherited Resources Views. The only step you nee
 
     rails generate inherited_resources_views
 
-This will generate a set of views in your `app/views/inherited_resources_views` folder. Edit away!
+This will generate a set of views in your `app/views/inherited_resources` folder. Edit away!
 
 ## Author
 

data/Rakefile

@@ -26,13 +26,13 @@ begin
   require 'jeweler'
   Jeweler::Tasks.new do |s|
     s.name = "inherited_resources_views"
-    s.version = "0.1.2"
+    s.version = "0.2.0"
     s.summary = "A lot of times resources share the same views, so why not DRY 'em up using Inherited Resources Views!"
     s.description = "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!"
     s.email = "ifredwu@gmail.com"
     s.homepage = "http://github.com/fredwu/inherited_resources_views"
     s.authors = ["Fred Wu"]
-    s.add_dependency("inherited_resources", ">= 1.1")
+    s.add_dependency("inherited_resources", ">= 1.0")
   end
   Jeweler::GemcutterTasks.new
 rescue LoadError

data/app/views/inherited_resources/_form.html.erb

@@ -1,5 +1,5 @@
 <table>
-<%= form_for(resource) do |f| %>
+<%- form_for(resource) do |f| %>
   <% if resource.errors.any? %>
   <tr>
     <td colspan="2">

data/inherited_resources_views.gemspec

@@ -5,11 +5,11 @@
 
 Gem::Specification.new do |s|
   s.name = %q{inherited_resources_views}
-  s.version = "0.1.2"
+  s.version = "0.2.0"
 
   s.required_rubygems_version = Gem::Requirement.new(">= 0") if s.respond_to? :required_rubygems_version=
   s.authors = ["Fred Wu"]
-  s.date = %q{2010-08-06}
+  s.date = %q{2010-08-07}
   s.description = %q{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!}
   s.email = %q{ifredwu@gmail.com}
   s.extra_rdoc_files = [
@@ -26,6 +26,7 @@ Gem::Specification.new do |s|
      "app/views/inherited_resources/new.html.erb",
      "app/views/inherited_resources/show.html.erb",
      "inherited_resources_views.gemspec",
+     "init.rb",
      "lib/generators/inherited_resources_views_generator.rb",
      "lib/inherited_resources_views.rb",
      "lib/inherited_resources_views/action_view.rb",
@@ -47,12 +48,12 @@ Gem::Specification.new do |s|
     s.specification_version = 3
 
     if Gem::Version.new(Gem::VERSION) >= Gem::Version.new('1.2.0') then
-      s.add_runtime_dependency(%q<inherited_resources>, [">= 1.1"])
+      s.add_runtime_dependency(%q<inherited_resources>, [">= 1.0"])
     else
-      s.add_dependency(%q<inherited_resources>, [">= 1.1"])
+      s.add_dependency(%q<inherited_resources>, [">= 1.0"])
     end
   else
-    s.add_dependency(%q<inherited_resources>, [">= 1.1"])
+    s.add_dependency(%q<inherited_resources>, [">= 1.0"])
   end
 end
 

data/init.rb

@@ -0,0 +1 @@
+require "inherited_resources_views"

data/lib/inherited_resources_views/action_view.rb

@@ -14,6 +14,13 @@ module InheritedResourcesViews
       rescue ::ActionView::MissingTemplate
         super(path, "inherited_resources", partial, details, key)
       end
+      
+      def find_template(original_template_path, format = nil, html_fallback = true)
+        super
+      rescue ::ActionView::MissingTemplate
+        original_template_path.sub!(/^[\w]+/, "inherited_resources")
+        super
+      end
     end
   end
 end

metadata

@@ -1,13 +1,12 @@
 --- !ruby/object:Gem::Specification 
 name: inherited_resources_views
 version: !ruby/object:Gem::Version 
-  hash: 31
   prerelease: false
   segments: 
   - 0
-  - 1
   - 2
-  version: 0.1.2
+  - 0
+  version: 0.2.0
 platform: ruby
 authors: 
 - Fred Wu
@@ -15,7 +14,7 @@ autorequire:
 bindir: bin
 cert_chain: []
 
-date: 2010-08-06 00:00:00 +10:00
+date: 2010-08-07 00:00:00 +10:00
 default_executable: 
 dependencies: 
 - !ruby/object:Gem::Dependency 
@@ -26,11 +25,10 @@ dependencies:
     requirements: 
     - - ">="
       - !ruby/object:Gem::Version 
-        hash: 13
         segments: 
         - 1
-        - 1
-        version: "1.1"
+        - 0
+        version: "1.0"
   type: :runtime
   version_requirements: *id001
 description: 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!
@@ -52,6 +50,7 @@ files:
 - app/views/inherited_resources/new.html.erb
 - app/views/inherited_resources/show.html.erb
 - inherited_resources_views.gemspec
+- init.rb
 - lib/generators/inherited_resources_views_generator.rb
 - lib/inherited_resources_views.rb
 - lib/inherited_resources_views/action_view.rb
@@ -71,7 +70,6 @@ required_ruby_version: !ruby/object:Gem::Requirement
   requirements: 
   - - ">="
     - !ruby/object:Gem::Version 
-      hash: 3
       segments: 
       - 0
       version: "0"
@@ -80,7 +78,6 @@ required_rubygems_version: !ruby/object:Gem::Requirement
   requirements: 
   - - ">="
     - !ruby/object:Gem::Version 
-      hash: 3
       segments: 
       - 0
       version: "0"