awesome_nested_fields 0.5.3 → 0.6.0

data/README.md

@@ -59,7 +59,7 @@ The next step is set up the form view with the `nested_fields_for` method. It re
       <% # person fields... %>
       
       <h2>Phones</h2>
-      <div class="container">
+      <div class="items">
         <%= f.nested_fields_for :phones do |f| %>
           <fieldset class="item">
             <%= f.label :number %>
@@ -79,7 +79,7 @@ The next step is set up the form view with the `nested_fields_for` method. It re
 
 The `nested_fields_for` method lists the phones this person has and also adds an empty template to the page for creating new phones. (Actually, there is too much code inside the block. If you're not working with a simple example like this you better extract this code into a partial and call just `render :phones` inside the block. Good coding practices, you know.)
 
-If you're paying attention, you noticed the key elements are marked with special class names. We *need* this for the javascript code, so it knows what to do with each HTML element: the one that have the children must have the class `container`; each child must be marked with the class `item`; inside an item, the link for removal must have the class `remove`; and the link to add new items must have the class `add`. We can change the names later, but these are the default choices. Finally, don't forget to add the `id` field, as it is needed by AR to identify whether this is an existing or a new element, and the `_destroy` field  to activate deletion when the user clicks on the remove link.
+If you're paying attention, you noticed the key elements are marked with special class names. We *need* this for the javascript code, so it knows what to do with each HTML element: the one that have the children must have the class `items`; each child must be marked with the class `item`; inside an item, the link for removal must have the class `remove`; and the link to add new items must have the class `add`. We can change the names later, but these are the default choices. Finally, don't forget to add the `id` field, as it is needed by AR to identify whether this is an existing or a new element, and the `_destroy` field  to activate deletion when the user clicks on the remove link.
 
 ### Javascript
 
@@ -135,7 +135,7 @@ Keep in mind that you can call the templates only after `nested_fields_for` and
 To make nested fields work dynamically, the JS code needs to know what elements to use. By default, this is made by marking key elements with CSS classes, but you can use other selectors (any valid jQuery selector will do). The available options are shown below.
 
 * `itemSelector` marks each item from the collection (`.item` by default)
-* `containerSelector` marks the element that contains the items (`.container` by default)
+* `containerSelector` marks the element that contains the items (`.items` by default). You can also use `.container` by default, but beware this class name conflicts with many CSS frameworks (Blueprint, 960.gs, Bootstrap, Foundation, ...)
 * `addSelector` marks the element that will add a new item to the container when clicked (`.add` by default)
 * `removeSelector` marks the element inside an item that will remove it when clicked (`.remove` by default)
 * `emptySelector` marks the element that is shown when there are no items; used in conjunction with `show_empty` option (`.empty` by default)
@@ -200,7 +200,7 @@ It is easy to have multiple nested fields on the same page. Instead of applying
     <!-- ERB Code -->
     <h2>Phones</h2>
     <div id="phones">
-      <div class="container">
+      <div class="items">
         <%= f.nested_fields_for :phones do |f| %>
           <% ... %>
         <% end %>
@@ -210,7 +210,7 @@ It is easy to have multiple nested fields on the same page. Instead of applying
     
     <h2>Addresses</h2>
     <div id="addresses">
-      <div class="container">
+      <div class="items">
         <%= f.nested_fields_for :addresses do |f| %>
           <% ... %>
         <% end %>
@@ -242,6 +242,7 @@ TODO
 * Make sure it can degrade gracefully
 * Implement jQuery autoload
 * Make `nested_fields_for` works without a block (looking for partials)
+* Document how to nest nested fields (yeah, you can do that) ;-)
 
 
 Copyleft

data/lib/awesome_nested_fields/version.rb

@@ -1,3 +1,3 @@
 module AwesomeNestedFields
-  VERSION = "0.5.3"
+  VERSION = "0.6.0"
 end

data/lib/rails/form_helper.rb

@@ -12,6 +12,7 @@ ActionView::Helpers::FormBuilder.class_eval do
     options[:escape_template] = options.key?(:escape_template) ? options[:escape_template] : true
     
     output = @template.capture { fields_for(association, &block) }
+    output ||= template.raw ""
     
     if options[:show_empty] and self.object.send(association).empty?
       output.safe_concat @template.capture { yield nil } 

data/vendor/assets/javascripts/jquery.nested-fields.js

@@ -15,7 +15,7 @@
     afterRemove: function(item) {},
     itemTemplateSelector: '.item.template',
     emptyTemplateSelector: '.empty.template',
-    containerSelector: '.container',
+    containerSelector: '.items, .container',
     itemSelector: '.item',
     emptySelector: '.empty',
     addSelector: '.add',
@@ -29,7 +29,7 @@
     init: function(options) {
       return this.each(function() {        
         var $this = $(this);
-        if($(this).data('nested-fields.options')) {
+        if($this.data('nested-fields.options')) {
           log('Nested fields already defined for this element. If you want to redefine options, destroy it and init again.');
           return $this;
         }
@@ -42,7 +42,7 @@
         $this.data('nested-fields.options', options); 
 
         bindInsertToAdd(options);
-        bindRemoveToItems(options);
+        bindRemoveToItems(options, $this);
       });
     },
     
@@ -105,8 +105,8 @@
     });
   }
   
-  function bindRemoveToItems(options) {
-    $(options.itemSelector, options.containerSelector).each(function(i, item) {
+  function bindRemoveToItems(options, $this) {
+    $(options.itemSelector, $this).each(function(i, item) {
       bindRemoveToItem(item, options);
     });
   }
@@ -178,7 +178,7 @@
     if(!options.skipBefore) {
       options.beforeRemove($element, remove);
       if(options.beforeRemove.length <= 1) {
-        insert();
+        remove();
       }
     } else {
       remove();

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: awesome_nested_fields
 version: !ruby/object:Gem::Version
-  version: 0.5.3
+  version: 0.6.0
   prerelease: 
 platform: ruby
 authors:
@@ -9,11 +9,11 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2011-09-07 00:00:00.000000000 Z
+date: 2011-12-25 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler
-  requirement: &70116503087320 !ruby/object:Gem::Requirement
+  requirement: &70151785785320 !ruby/object:Gem::Requirement
     none: false
     requirements:
     - - ! '>='
@@ -21,10 +21,10 @@ dependencies:
         version: 1.0.0
   type: :development
   prerelease: false
-  version_requirements: *70116503087320
+  version_requirements: *70151785785320
 - !ruby/object:Gem::Dependency
   name: rails
-  requirement: &70116503086600 !ruby/object:Gem::Requirement
+  requirement: &70151785784480 !ruby/object:Gem::Requirement
     none: false
     requirements:
     - - ! '>='
@@ -32,7 +32,7 @@ dependencies:
         version: 3.0.0
   type: :runtime
   prerelease: false
-  version_requirements: *70116503086600
+  version_requirements: *70151785784480
 description: Awesome dynamic nested fields for Rails and jQuery
 email: lailson@guava.com.br
 executables: []