view_models 1.5.2 → 1.5.3

Sign up to get free protection for your applications and to get access to all the features.
Files changed (4) hide show
  1. data/README.textile +12 -0
  2. data/Rakefile +3 -1
  3. data/VERSION.yml +2 -2
  4. metadata +32 -5
data/README.textile CHANGED
@@ -20,8 +20,20 @@ Important note: These guys rock! :)
20
20
 
21
21
  h2. Installation
22
22
 
23
+ h3. Rails Plugin
24
+
23
25
  @script/plugin install git://github.com/floere/view_models.git@
24
26
 
27
+ h3. Gem for use in Rails
28
+
29
+ @gem install view_models@
30
+
31
+ and then adding the line
32
+
33
+ @config.gem 'view_models'@
34
+
35
+ in your environment.rb.
36
+
25
37
  h2. Description
26
38
 
27
39
  A possible view_model solution, i.e. no view logic in model code.
data/Rakefile CHANGED
@@ -36,10 +36,12 @@ begin
36
36
  gemspec.summary = "A model proxy for Rails views. Helps you keep the representation of a model and the model itself separate."
37
37
  gemspec.email = "florian.hanke@gmail.com"
38
38
  gemspec.homepage = "http://floere.github.com/view_models"
39
- gemspec.description = "The view models gem adds the missing R (Representation) to Rails' MVC. It provides simple proxy functionality for your models and thus helps you keep the model and view representations of a model separate, as it should be. Also, you can define helper methods on the (view) model instead of globally to keep them focused, more quickly understood and more easily testable. View Models also introduce hierarchical rendering for your hierarchical models. If the account view is not defined for the subclass FemaleUser, it checks if it is defined for User, for example, to see when there is no specific view, if there is a general view. So, in other words: Polymorphism not just in the model, but also in the view."
39
+ gemspec.description = "The view models gem adds the missing R (Representation) to Rails' MVC. It provides simple proxy functionality for your models and thus helps you keep the model and view representations of a model separate, as it should be. Also, you can define helper methods on the (view) model instead of globally to keep them focused, more quickly understood and more easily testable. View Models also introduce hierarchical rendering for your hierarchical models. If the account view is not defined for the subclass FemaleUser, it checks if it is defined for User, for example, to see when there is no specific view, if there is a general view. So, in other words: Polymorphism not just in the model, but also in the view. Have fun!"
40
40
  gemspec.authors = ["Florian Hanke", "Kaspar Schiess", "Niko Dittmann", "Andreas Schacke"]
41
41
  gemspec.rdoc_options = ["--inline-source", "--charset=UTF-8"]
42
42
  gemspec.files = FileList["[A-Z]*", "{generators,lib,rails,spec}/**/*"]
43
+ gemspec.add_dependency 'rails', '>= 2.2.0'
44
+ gemspec.add_development_dependency 'rspec', '>=1.2.9'
43
45
  end
44
46
  Jeweler::GemcutterTasks.new
45
47
  rescue LoadError => e
data/VERSION.yml CHANGED
@@ -1,4 +1,4 @@
1
1
  ---
2
- :major: 1
3
2
  :minor: 5
4
- :patch: 2
3
+ :patch: 3
4
+ :major: 1
metadata CHANGED
@@ -5,8 +5,8 @@ version: !ruby/object:Gem::Version
5
5
  segments:
6
6
  - 1
7
7
  - 5
8
- - 2
9
- version: 1.5.2
8
+ - 3
9
+ version: 1.5.3
10
10
  platform: ruby
11
11
  authors:
12
12
  - Florian Hanke
@@ -19,9 +19,36 @@ cert_chain: []
19
19
 
20
20
  date: 2010-03-01 00:00:00 +01:00
21
21
  default_executable:
22
- dependencies: []
23
-
24
- description: "The view models gem adds the missing R (Representation) to Rails' MVC. It provides simple proxy functionality for your models and thus helps you keep the model and view representations of a model separate, as it should be. Also, you can define helper methods on the (view) model instead of globally to keep them focused, more quickly understood and more easily testable. View Models also introduce hierarchical rendering for your hierarchical models. If the account view is not defined for the subclass FemaleUser, it checks if it is defined for User, for example, to see when there is no specific view, if there is a general view. So, in other words: Polymorphism not just in the model, but also in the view."
22
+ dependencies:
23
+ - !ruby/object:Gem::Dependency
24
+ name: rails
25
+ prerelease: false
26
+ requirement: &id001 !ruby/object:Gem::Requirement
27
+ requirements:
28
+ - - ">="
29
+ - !ruby/object:Gem::Version
30
+ segments:
31
+ - 2
32
+ - 2
33
+ - 0
34
+ version: 2.2.0
35
+ type: :runtime
36
+ version_requirements: *id001
37
+ - !ruby/object:Gem::Dependency
38
+ name: rspec
39
+ prerelease: false
40
+ requirement: &id002 !ruby/object:Gem::Requirement
41
+ requirements:
42
+ - - ">="
43
+ - !ruby/object:Gem::Version
44
+ segments:
45
+ - 1
46
+ - 2
47
+ - 9
48
+ version: 1.2.9
49
+ type: :development
50
+ version_requirements: *id002
51
+ description: "The view models gem adds the missing R (Representation) to Rails' MVC. It provides simple proxy functionality for your models and thus helps you keep the model and view representations of a model separate, as it should be. Also, you can define helper methods on the (view) model instead of globally to keep them focused, more quickly understood and more easily testable. View Models also introduce hierarchical rendering for your hierarchical models. If the account view is not defined for the subclass FemaleUser, it checks if it is defined for User, for example, to see when there is no specific view, if there is a general view. So, in other words: Polymorphism not just in the model, but also in the view. Have fun!"
25
52
  email: florian.hanke@gmail.com
26
53
  executables: []
27
54