hobo 2.0.0.pre10 → 2.0.0

data/CHANGES-1.4.txt

@@ -295,7 +295,7 @@ receive the following benefits:
 
 - code reduction in Hobo
 
-## `remote-method-button` and `update-button` broken
+## `remote-method-button` and `update-button` AJAX functionality removed
 {.nomove}
 
 `remote-method-button`, `update-button` and similar buttons such as
@@ -305,14 +305,22 @@ with the much more flexible forms.
 
 For backwards compatibility, most of these buttons have been updated
 to 2.0. However, the little used `remote-method-button` and
-`update-button` have not been converted to the 2.0 form.
+`update-button` have not been converted to support Hobo 2.0 AJAX.
 
 ## default field-list changed
 {.nomove}
 
 The default for `<field-list>` has changed to `<feckless-fieldset>`.
-The old behaviour is still available in `<field-list-v1>`.   Please
-provide feedback: we are open to reversion before final release.
+The old behaviour is still available in `<field-list-v1>`.
+
+## Chronic patches removed.
+
+HoboSupport's patches to Chronic have been removed because they are not
+supported in Ruby 2.0.0.
+
+## rapid_summary tags removed
+
+The rapid\_summary tags have been moved out of core Hobo into their own plugin, https://github.com/Hobo/hobo_summary, which is not yet in a working state
 
 ## Helper rearrangement
 {.todo}
@@ -337,6 +345,42 @@ config.hobo.include_deprecated_helper.
 
 Hobo 2.0 currently requires Rails 3.2 for operation.
 
+## Editors
+{.todo}
+
+Editors are no longer special-cased, they now use the standard DRYML
+part mechanism.
+
+There are two types of editors: `<click-editor>` and `<live-editor>`.
+click-editor is the click-to-edit type of control similar to what
+Rapid currently uses for a string, and live-editor always renders the
+input, and is similar to what Rapid currently uses for Boolean's and
+enum-strings.
+
+Please refer to the documentation for `click-editor` and `live-editor`
+for more details.
+
+`<editor>` is now a polymorphic input that uses either `<click-editor>` or
+`<live-editor>`.
+
+TBD: Right now live-editor and click-editor use `<formlet>`.  The
+major advantage of formlet is that it is safe to use inside of a form.
+I can't think of any good use cases for that behaviour, but it does
+seem like something people might do by accident.
+
+The alternative is to use `<form>`.   Since this implementation of
+editor starts with an input and switches to a view via Javascript,
+using a form would allow reasonable javascript-disabled behaviour.
+
+## Attribute Whitelist
+{.todo}
+
+Rails 3.2.3 and later changed the default for config.whitelist_attributes to true, so any newly generated Hobo apps will have this feature turned on.  Hobo heavily depends on mass attribute assignation, so this may cause inconveniences.
+
+Mass assignment protection is redundant in Hobo: your primary protection should come through the edit_permitted? function.   If all of your models have properly defined edit_permitted? then it is safe to turn off config.whitelist_attributes.
+
+If you choose not to turn off config.whitelist_attributes, any fields that are not in your attr_accessible declaration will not be available in forms.   Hobo's generators will now assist in the creation of attr_accessible declarations.
+
 ## Enhancements
 
 ### Nested caching
@@ -821,33 +865,6 @@ Because this is a respond_to block any formats you do not render will fall throu
 `<form>` has gained a new option, before-unload, which adds an
 onbeforeunload helper to the page.
 
-## Editors
-{.todo}
-
-Editors are no longer special-cased, they now use the standard DRYML
-part mechanism.
-
-There are two types of editors: `<click-editor>` and `<live-editor>`.
-click-editor is the click-to-edit type of control similar to what
-Rapid currently uses for a string, and live-editor always renders the
-input, and is similar to what Rapid currently uses for Boolean's and
-enum-strings.
-
-Please refer to the documentation for `click-editor` and `live-editor`
-for more details.
-
-`<editor>` is now a polymorphic input that uses either `<click-editor>` or
-`<live-editor>`.
-
-TBD: Right now live-editor and click-editor use `<formlet>`.  The
-major advantage of formlet is that it is safe to use inside of a form.
-I can't think of any good use cases for that behaviour, but it does
-seem like something people might do by accident.
-
-The alternative is to use `<form>`.   Since this implementation of
-editor starts with an input and switches to a view via Javascript,
-using a form would allow reasonable javascript-disabled behaviour.
-
 ## Changes behind the scenes
 
 ### reloading of part context
@@ -912,15 +929,6 @@ environment.
 
  MarkdownString will now use Kramdown, RDiscount or Maruku in preference to Bluecloth if they are availble in your bundle.
 
-## Attribute Whitelist
-{.todo}
-
-Rails 3.2.3 and later changed the default for config.whitelist_attributes to true, so any newly generated Hobo apps will have this feature turned on.  Hobo heavily depends on mass attribute assignation, so this may cause inconveniences.
-
-Mass assignment protection is redundant in Hobo: your primary protection should come through the edit_permitted? function.   If all of your models have properly defined edit_permitted? then it is safe to turn off config.whitelist_attributes.
-
-If you choose not to turn off config.whitelist_attributes, any fields that are not in your attr_accessible declaration will not be available in forms.   Hobo's generators will now assist in the creation of attr_accessible declarations.
-
 # jQuery rewrite
 
 FIXME: pull into separate document, along with interface specs

data/CHANGES-2.0.markdown

@@ -295,7 +295,7 @@ receive the following benefits:
 
 - code reduction in Hobo
 
-## `remote-method-button` and `update-button` broken
+## `remote-method-button` and `update-button` AJAX functionality removed
 {.nomove}
 
 `remote-method-button`, `update-button` and similar buttons such as
@@ -305,14 +305,22 @@ with the much more flexible forms.
 
 For backwards compatibility, most of these buttons have been updated
 to 2.0. However, the little used `remote-method-button` and
-`update-button` have not been converted to the 2.0 form.
+`update-button` have not been converted to support Hobo 2.0 AJAX.
 
 ## default field-list changed
 {.nomove}
 
 The default for `<field-list>` has changed to `<feckless-fieldset>`.
-The old behaviour is still available in `<field-list-v1>`.   Please
-provide feedback: we are open to reversion before final release.
+The old behaviour is still available in `<field-list-v1>`.
+
+## Chronic patches removed.
+
+HoboSupport's patches to Chronic have been removed because they are not
+supported in Ruby 2.0.0.
+
+## rapid_summary tags removed
+
+The rapid\_summary tags have been moved out of core Hobo into their own plugin, https://github.com/Hobo/hobo_summary, which is not yet in a working state
 
 ## Helper rearrangement
 {.todo}
@@ -337,6 +345,42 @@ config.hobo.include_deprecated_helper.
 
 Hobo 2.0 currently requires Rails 3.2 for operation.
 
+## Editors
+{.todo}
+
+Editors are no longer special-cased, they now use the standard DRYML
+part mechanism.
+
+There are two types of editors: `<click-editor>` and `<live-editor>`.
+click-editor is the click-to-edit type of control similar to what
+Rapid currently uses for a string, and live-editor always renders the
+input, and is similar to what Rapid currently uses for Boolean's and
+enum-strings.
+
+Please refer to the documentation for `click-editor` and `live-editor`
+for more details.
+
+`<editor>` is now a polymorphic input that uses either `<click-editor>` or
+`<live-editor>`.
+
+TBD: Right now live-editor and click-editor use `<formlet>`.  The
+major advantage of formlet is that it is safe to use inside of a form.
+I can't think of any good use cases for that behaviour, but it does
+seem like something people might do by accident.
+
+The alternative is to use `<form>`.   Since this implementation of
+editor starts with an input and switches to a view via Javascript,
+using a form would allow reasonable javascript-disabled behaviour.
+
+## Attribute Whitelist
+{.todo}
+
+Rails 3.2.3 and later changed the default for config.whitelist_attributes to true, so any newly generated Hobo apps will have this feature turned on.  Hobo heavily depends on mass attribute assignation, so this may cause inconveniences.
+
+Mass assignment protection is redundant in Hobo: your primary protection should come through the edit_permitted? function.   If all of your models have properly defined edit_permitted? then it is safe to turn off config.whitelist_attributes.
+
+If you choose not to turn off config.whitelist_attributes, any fields that are not in your attr_accessible declaration will not be available in forms.   Hobo's generators will now assist in the creation of attr_accessible declarations.
+
 ## Enhancements
 
 ### Nested caching
@@ -821,33 +865,6 @@ Because this is a respond_to block any formats you do not render will fall throu
 `<form>` has gained a new option, before-unload, which adds an
 onbeforeunload helper to the page.
 
-## Editors
-{.todo}
-
-Editors are no longer special-cased, they now use the standard DRYML
-part mechanism.
-
-There are two types of editors: `<click-editor>` and `<live-editor>`.
-click-editor is the click-to-edit type of control similar to what
-Rapid currently uses for a string, and live-editor always renders the
-input, and is similar to what Rapid currently uses for Boolean's and
-enum-strings.
-
-Please refer to the documentation for `click-editor` and `live-editor`
-for more details.
-
-`<editor>` is now a polymorphic input that uses either `<click-editor>` or
-`<live-editor>`.
-
-TBD: Right now live-editor and click-editor use `<formlet>`.  The
-major advantage of formlet is that it is safe to use inside of a form.
-I can't think of any good use cases for that behaviour, but it does
-seem like something people might do by accident.
-
-The alternative is to use `<form>`.   Since this implementation of
-editor starts with an input and switches to a view via Javascript,
-using a form would allow reasonable javascript-disabled behaviour.
-
 ## Changes behind the scenes
 
 ### reloading of part context
@@ -912,15 +929,6 @@ environment.
 
  MarkdownString will now use Kramdown, RDiscount or Maruku in preference to Bluecloth if they are availble in your bundle.
 
-## Attribute Whitelist
-{.todo}
-
-Rails 3.2.3 and later changed the default for config.whitelist_attributes to true, so any newly generated Hobo apps will have this feature turned on.  Hobo heavily depends on mass attribute assignation, so this may cause inconveniences.
-
-Mass assignment protection is redundant in Hobo: your primary protection should come through the edit_permitted? function.   If all of your models have properly defined edit_permitted? then it is safe to turn off config.whitelist_attributes.
-
-If you choose not to turn off config.whitelist_attributes, any fields that are not in your attr_accessible declaration will not be available in forms.   Hobo's generators will now assist in the creation of attr_accessible declarations.
-
 # jQuery rewrite
 
 FIXME: pull into separate document, along with interface specs

data/Gemfile

@@ -1,7 +1,7 @@
 source "http://rubygems.org"
 
 gem 'rubydoctest', :git => 'git://github.com/bryanlarsen/rubydoctest.git'
-gem 'rails', '3.2.11'
+gem 'rails', '3.2.12'
 gemspec :path => "../dryml"
 gemspec :path => "../hobo_support"
 gemspec :path => "../hobo_fields"

data/VERSION

@@ -1 +1 @@
-2.0.0.pre10
+2.0.0

data/lib/generators/hobo/user_model/templates/model_injection.rb.erb

@@ -7,7 +7,7 @@
     administrator :boolean, :default => false
     timestamps
   end
-  attr_accessible :name, :email_address, :password, :password_confirmation
+  attr_accessible :name, :email_address, :password, :password_confirmation, :current_password
 
   # This gives admin rights and an :active state to the first sign-up.
   # Just remove it if you don't want that

metadata

@@ -1,15 +1,15 @@
 --- !ruby/object:Gem::Specification
 name: hobo
 version: !ruby/object:Gem::Version
-  version: 2.0.0.pre10
-  prerelease: 6
+  version: 2.0.0
+  prerelease: 
 platform: ruby
 authors:
 - Tom Locke
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2013-02-20 00:00:00.000000000 Z
+date: 2013-02-27 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: hobo_support
@@ -18,7 +18,7 @@ dependencies:
     requirements:
     - - '='
       - !ruby/object:Gem::Version
-        version: 2.0.0.pre10
+        version: 2.0.0
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
@@ -26,7 +26,7 @@ dependencies:
     requirements:
     - - '='
       - !ruby/object:Gem::Version
-        version: 2.0.0.pre10
+        version: 2.0.0
 - !ruby/object:Gem::Dependency
   name: hobo_fields
   requirement: !ruby/object:Gem::Requirement
@@ -34,7 +34,7 @@ dependencies:
     requirements:
     - - '='
       - !ruby/object:Gem::Version
-        version: 2.0.0.pre10
+        version: 2.0.0
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
@@ -42,7 +42,7 @@ dependencies:
     requirements:
     - - '='
       - !ruby/object:Gem::Version
-        version: 2.0.0.pre10
+        version: 2.0.0
 - !ruby/object:Gem::Dependency
   name: dryml
   requirement: !ruby/object:Gem::Requirement
@@ -50,7 +50,7 @@ dependencies:
     requirements:
     - - '='
       - !ruby/object:Gem::Version
-        version: 2.0.0.pre10
+        version: 2.0.0
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
@@ -58,7 +58,7 @@ dependencies:
     requirements:
     - - '='
       - !ruby/object:Gem::Version
-        version: 2.0.0.pre10
+        version: 2.0.0
 - !ruby/object:Gem::Dependency
   name: will_paginate
   requirement: !ruby/object:Gem::Requirement