puffer 0.0.29 → 0.0.30

data/Gemfile

@@ -14,6 +14,7 @@ group :development, :test do
   gem "rspec-rails"
   gem "capybara"
   gem 'database_cleaner'
+  gem 'ammeter'
 
   gem 'guard'
   gem 'libnotify'

data/Gemfile.lock

@@ -1,39 +1,43 @@
 GEM
   remote: http://rubygems.org/
   specs:
-    actionmailer (3.1.0)
-      actionpack (= 3.1.0)
+    actionmailer (3.1.1)
+      actionpack (= 3.1.1)
       mail (~> 2.3.0)
-    actionpack (3.1.0)
-      activemodel (= 3.1.0)
-      activesupport (= 3.1.0)
+    actionpack (3.1.1)
+      activemodel (= 3.1.1)
+      activesupport (= 3.1.1)
       builder (~> 3.0.0)
       erubis (~> 2.7.0)
       i18n (~> 0.6)
       rack (~> 1.3.2)
-      rack-cache (~> 1.0.3)
+      rack-cache (~> 1.1)
       rack-mount (~> 0.8.2)
       rack-test (~> 0.6.1)
-      sprockets (~> 2.0.0)
-    activemodel (3.1.0)
-      activesupport (= 3.1.0)
-      bcrypt-ruby (~> 3.0.0)
+      sprockets (~> 2.0.2)
+    activemodel (3.1.1)
+      activesupport (= 3.1.1)
       builder (~> 3.0.0)
       i18n (~> 0.6)
-    activerecord (3.1.0)
-      activemodel (= 3.1.0)
-      activesupport (= 3.1.0)
+    activerecord (3.1.1)
+      activemodel (= 3.1.1)
+      activesupport (= 3.1.1)
       arel (~> 2.2.1)
       tzinfo (~> 0.3.29)
-    activeresource (3.1.0)
-      activemodel (= 3.1.0)
-      activesupport (= 3.1.0)
-    activesupport (3.1.0)
+    activeresource (3.1.1)
+      activemodel (= 3.1.1)
+      activesupport (= 3.1.1)
+    activesupport (3.1.1)
       multi_json (~> 1.0)
+    ammeter (0.2.1)
+      activesupport (~> 3.0)
+      railties (~> 3.0)
+      rspec (~> 2.2)
+      rspec-rails (~> 2.2)
     arel (2.2.1)
-    bcrypt-ruby (3.0.0)
-    bson (1.3.1)
-    bson_ext (1.3.1)
+    bcrypt-ruby (3.0.1)
+    bson (1.4.1)
+    bson_ext (1.4.0)
     builder (3.0.0)
     capybara (1.1.1)
       mime-types (>= 1.16)
@@ -45,29 +49,28 @@ GEM
     childprocess (0.2.2)
       ffi (~> 1.0.6)
     database_cleaner (0.6.7)
-    devise (1.4.5)
+    devise (1.4.8)
       bcrypt-ruby (~> 3.0)
       orm_adapter (~> 0.0.3)
       warden (~> 1.0.3)
     diff-lcs (1.1.3)
     erubis (2.7.0)
-    fabrication (1.1.0)
+    fabrication (1.2.0)
     ffi (1.0.9)
-    forgery (0.4.3)
-      nokogiri (~> 1.4)
+    forgery (0.5.0)
     git (1.2.5)
-    guard (0.6.3)
+    guard (0.8.4)
       thor (~> 0.14.6)
-    guard-rspec (0.4.4)
-      guard (>= 0.4.0)
+    guard-rspec (0.5.0)
+      guard (>= 0.8.4)
     hike (1.2.1)
     i18n (0.6.0)
     jeweler (1.6.4)
       bundler (~> 1.0)
       git (>= 1.2.5)
       rake
-    json_pure (1.5.4)
-      spruz (~> 0.2.8)
+    json (1.6.1)
+    json_pure (1.6.1)
     kaminari (0.12.4)
       rails (>= 3.0.0)
     libnotify (0.5.7)
@@ -76,11 +79,11 @@ GEM
       mime-types (~> 1.16)
       treetop (~> 1.4.8)
     mime-types (1.16)
-    mongo (1.3.1)
-      bson (>= 1.3.1)
-    mongoid (2.2.0)
-      activemodel (~> 3.0)
-      mongo (~> 1.3)
+    mongo (1.4.1)
+      bson (= 1.4.1)
+    mongoid (2.3.2)
+      activemodel (~> 3.1)
+      mongo (~> 1.4)
       tzinfo (~> 0.3.22)
     multi_json (1.0.3)
     nested_set (1.6.8)
@@ -89,8 +92,8 @@ GEM
     nokogiri (1.5.0)
     orm_adapter (0.0.5)
     polyglot (0.3.2)
-    rack (1.3.2)
-    rack-cache (1.0.3)
+    rack (1.3.4)
+    rack-cache (1.1)
       rack (>= 0.4)
     rack-mount (0.8.3)
       rack (>= 1.0.0)
@@ -98,23 +101,24 @@ GEM
       rack
     rack-test (0.6.1)
       rack (>= 1.0)
-    rails (3.1.0)
-      actionmailer (= 3.1.0)
-      actionpack (= 3.1.0)
-      activerecord (= 3.1.0)
-      activeresource (= 3.1.0)
-      activesupport (= 3.1.0)
+    rails (3.1.1)
+      actionmailer (= 3.1.1)
+      actionpack (= 3.1.1)
+      activerecord (= 3.1.1)
+      activeresource (= 3.1.1)
+      activesupport (= 3.1.1)
       bundler (~> 1.0)
-      railties (= 3.1.0)
-    railties (3.1.0)
-      actionpack (= 3.1.0)
-      activesupport (= 3.1.0)
+      railties (= 3.1.1)
+    railties (3.1.1)
+      actionpack (= 3.1.1)
+      activesupport (= 3.1.1)
       rack-ssl (~> 1.3.2)
       rake (>= 0.8.7)
       rdoc (~> 3.4)
       thor (~> 0.14.6)
     rake (0.9.2)
-    rdoc (3.9.4)
+    rdoc (3.10)
+      json (~> 1.4)
     rspec (2.6.0)
       rspec-core (~> 2.6.0)
       rspec-expectations (~> 2.6.0)
@@ -129,24 +133,23 @@ GEM
       railties (~> 3.0)
       rspec (~> 2.6.0)
     rubyzip (0.9.4)
-    selenium-webdriver (2.5.0)
+    selenium-webdriver (2.8.0)
       childprocess (>= 0.2.1)
       ffi (>= 1.0.7)
       json_pure
       rubyzip
-    sprockets (2.0.0)
+    sprockets (2.0.2)
       hike (~> 1.2)
       rack (~> 1.0)
       tilt (~> 1.1, != 1.3.0)
-    spruz (0.2.13)
     sqlite3 (1.3.4)
     thor (0.14.6)
     tilt (1.3.3)
     treetop (1.4.10)
       polyglot
       polyglot (>= 0.3.1)
-    tzinfo (0.3.29)
-    warden (1.0.5)
+    tzinfo (0.3.30)
+    warden (1.0.6)
       rack (>= 1.0)
     xpath (0.1.4)
       nokogiri (~> 1.3)
@@ -155,6 +158,7 @@ PLATFORMS
   ruby
 
 DEPENDENCIES
+  ammeter
   bson_ext
   capybara
   database_cleaner

data/README.md

@@ -1,26 +1,34 @@
 # Puffer - YARAI (Yet Another Rails Admin Interface). Rails 3.1 only.
 
-Puffer was created to help project owner or moderators view and edit all the project`s data models. It is rails 3.1 only
+Puffer was created to help a project owner or moderators view and edit all the project's data models. It's compatible with Rails 3.1 only.
 
-## Keyfeatures
+## Discussion and help
 
-* Full rails integration. Puffer has no configs, just DSL to create interfaces. And this DSL depends on rails convensions.
+puffer@conference.jabber.org
+
+## Key features
+
+* Full Rails integration. Puffer has no configuration, just a DSL to create interfaces. And this DSL depends on Rails conventions.
 * Flexibility. Puffer designed to be as flexible as possible, so you can create your own modules easily.
 * I18n. Surely.
-* Bla bla
+* Puffer can support different ORMs or ODMs through orm_adapter.
+* Implemented full AR and Mongoid support.
 
 ## Installation.
 
-You can instal puffer as a gem:
-<pre>gem install puffer</pre>
+You can install puffer as a gem:
+
+`gem install puffer`
+
 Or in Gemfile:
-<pre>gem "puffer"</pre>
+
+`gem "puffer"`
 
 ## Introduction.
 
-So, you have some data structure of your project. Let it`ll be like this:
+Let's assume this is the data structure of your project:
 
-<pre>
+```
 create_table "users", :force => true do |t|
   t.string   "email"
   t.string   "password"
@@ -35,33 +43,35 @@ create_table "posts", :force => true do |t|
   t.datetime "created_at"
   t.datetime "updated_at"
 end
-</pre>
+```
 
-Also, you have two models:
+And let's also assume your models look like this:
 
-<pre>
-class User &lt; ActiveRecord::Base
+```
+class User < ActiveRecord::Base
   has_many :posts
   validates_presence_of :email, :password
   validates_length_of :password, :minimum => 6
 end
-</pre>
 
-<pre>
-class Profile &lt; ActiveRecord::Base
+class Profile < ActiveRecord::Base
   belongs_to :user
   validates_presence_of :name, :surname
 end
-</pre>
+```
+
+First, let's generate Puffer controllers:
+
+`rails g puffer:controller User`
 
-At first, lets generate puffers controllers:
-<pre>rails g puffer:controller User</pre>
 and
-<pre>rails g puffer:controller Post</pre>
 
-This will generate a kind of:
-<pre>
-class Admin::PostsController &lt; Puffer::Base
+`rails g puffer:controller Post`
+
+This will generate this:
+
+```
+class Admin::PostsController < Puffer::Base
   setup do
     group :posts
   end
@@ -85,37 +95,35 @@ class Admin::PostsController &lt; Puffer::Base
   end
 
 end
-</pre>
+```
 
-Puffer controller`s DSL creates all the actions we need. Next step - routing
+Puffer's controller DSL creates all the actions you need. Next step: routing.
 
-<pre>
-namespace :admin
+```
+namespace :admin do
   resources :users do
     resources :posts
   end
   resources :posts
 end
-</pre>
+```
 
-Let me explain this feature. Puffer tracks all the nested resources. So, with this routing structure we can access, for example, only specified user`s posts:
+Let me explain this feature. Puffer tracks all the nested resources. So, with this routing structure we can access, for example, only specified user's posts:
 
-<pre>
-/admin/users/1/post
-</pre>
+`/admin/users/1/post`
 
 Routing nesting defines admin interface resources nesting.
 
 ## Advanced usage
 
-Puffer can be used in other namespaces, then admin:
+Puffer can be used in other namespaces than admin:
 
-<pre>rails g puffer:controller moderator/posts</pre>
+`rails g puffer:controller moderator/posts`
 
-And we`ll get posts controller for moderator:
+And we'll get posts controller for moderators:
 
-<pre>
-class Moderator::PostsController &lt; Puffer::Base
+```
+class Moderator::PostsController < Puffer::Base
   before_filter :require_moderator
 
   setup do
@@ -137,14 +145,14 @@ class Moderator::PostsController &lt; Puffer::Base
     field :updated_at
   end
 end
-</pre>
+```
 
-As you can see, moderators can not destroy posts, also moderator`s posts controller placed at Posting tab of admin interface.
-And don`t forget about routing:
+As you can see, moderators can't destroy posts. The moderator's post controller is placed in the Posting tab of the admin interface.
 
-<pre>
+Finally, don't forget about routing:
+
+```
 namespace :moderator do
   resources :posts
 end
-</pre>
-
+```

data/VERSION

@@ -1 +1 @@
-0.0.29
+0.0.30

data/app/assets/javascripts/puffer/application.js

@@ -5,4 +5,6 @@
 //= require puffer/right-autocompleter-src
 //= require puffer/paginator
 //= require puffer/rails
-//= require puffer/puffer
+//= require puffer/puffer
+
+//= require_all ./puffer

data/app/assets/stylesheets/puffer/application.css

@@ -4,4 +4,6 @@
  *= require puffer/paginator
  *= require puffer/puffer
  *= require puffer/puffer_tree
+
+ *= require_all ./puffer
  */

data/app/assets/stylesheets/puffer/puffer.css

@@ -206,13 +206,9 @@ h2
 {
 	display: table-cell;
 	vertical-align: top;
-}
-
-.column,
-{
-	display: inline;
-	vertical-align: top;
-    width: expression(function(t){
+    _display: inline;
+    _vertical-align: top;
+    _width: expression(function(t){
       var sum = 0;
       for (var i = 0; i < t.parentNode.childNodes.length; i++) {
         if (t.parentNode.childNodes[i] != t) {
@@ -220,8 +216,8 @@ h2
         }
       }
       return t.parentNode.clientWidth - sum + 'px';
-	}(this));
-	zoom: 1;
+    }(this));
+    zoom: 1;
 }
 
 .sidebar

data/app/components/base_component.rb

@@ -9,7 +9,6 @@ class BaseComponent < Puffer::Component::Base
   end
 
   def filter
-
   end
 
 end

data/app/components/boolean/index.html.erb

@@ -1,3 +1,3 @@
 <%= component_wrap do %>
-  <%= link_to opts[:record].call_chain(field.to_s) ? 'True' : 'False', event_path(:update, :id => opts[:record].to_param), :remote => true %>
+  <%= link_to opts[:record].call_chain(field.to_s) ? 'True' : 'False', event_path(:change, :id => opts[:record].to_param), :remote => true %>
 <% end %>

data/app/components/boolean_component.rb

@@ -4,7 +4,7 @@ class BooleanComponent < BaseComponent
     render
   end
 
-  def update
+  def change
     opts[:record] = resource.member
     opts[:record].update_attributes field.to_s => !opts[:record].call_chain(field.to_s)
     replace :index

data/app/components/references_many/index.html.erb

@@ -0,0 +1 @@
+<%= link_to field.human, resource.children_hash[field.name].collection_path %>

data/app/components/references_many_component.rb

@@ -1,7 +1,15 @@
 class ReferencesManyComponent < Puffer::Component::Base
 
+  def index
+    render
+  end
+
   def form
     render
   end
+
+  def filter
+
+  end
   
 end