lalala 4.0.0.dev.141 → 4.0.0.dev.144

data/vendor/deps/active_admin/docs/2-resource-customization.md

@@ -1,256 +0,0 @@
-# Customize The Resource
-
-## Rename the Resource
-
-By default, any references to the resource (menu, routes, buttons, etc) in the
-interface will use the name of the class. You can rename the resource by using
-the <tt>:as</tt> option.
-
-    ActiveAdmin.register Post, :as => "Article"
-
-The resource will then be available as /admin/articles
-
-## Customize the Namespace
-
-By default, resources live in the "admin" namespace.
-
-You can register resources in different namespaces:
-
-    # Available at /today/posts
-    ActiveAdmin.register Post, :namespace => "today"
-
-    # Available at /posts
-    ActiveAdmin.register Post, :namespace => false
-
-
-## Customize the Menu
-
-The resource will be displayed in the global navigation by default. To disable
-the resource from being displayed in the global navigation, pass `false` to the
-`menu` method:
-
-    ActiveAdmin.register Post do
-      menu false
-    end
-
-The menu method accepts a hash with the following options:
-
-* `:label` - The string or proc label to display in the menu. If it's a proc, it
-  will be called each time the menu is rendered.
-* `:parent` - The string label of the parent to set for this menu
-* `:if` - A block or a symbol of a method to call to decide if the menu item
-  should be displayed
-* `:priority` - The integer value of the priority. Defaults to 10
-
-### Labels
-
-To change the name of the label in the menu:
-
-    ActiveAdmin.register Post do
-      menu :label => "My Posts"
-    end
-
-By default the menu uses a pluralized version of your resource name.
-
-If you wish to translate your label at runtime, store the label as a proc
-instead of a string. The proc will be called each time the menu is rendered.
-
-    ActiveAdmin.register Post do
-      menu :label => proc{ I18n.t("mypost") }
-    end
-
-### Drop Down Menus
-
-In many cases, a single level navigation will not be enough for the
-administration of a production application. In that case, you can categorize
-your resources and creating drop down menus to access them.
-
-To add the menu as a child of another menu:
-
-    ActiveAdmin.register Post do
-      menu :parent => "Blog"
-    end
-
-Note, the "Blog" menu does not even have to exist yet. It will be generated on
-the fly as a drop down list for you.
-
-### Menu Priority
-
-By default Active Admin sorts menus alphabetically. Some times you want specific
-resources to show up at the beginning or the end of your menu.
-
-Each menu item is given an integer priority value (default 10). You can set it
-to edit the location of the menu item.
-
-    ActiveAdmin.register Post do
-      menu :priority => 1
-    end
-
-This would ensure that the Post menu item, is at the beginning of the menu.
-
-### Conditionally Showing / Hiding Menu Items
-
-Menu items can be shown or hidden at runtime using the `:if` option.
-
-    ActiveAdmin.register Post do
-      menu :if => proc{ current_admin_user.can_edit_posts? }
-    end
-
-The `proc` will be called in the context of the view, so you have access to all
-your helpers and current user session information.
-
-### Adding Custom Menu Items
-
-Sometimes it's not enough to just customize the menu label. In this case, you
-can customize the menu for the namespace within the Active Admin initializer.
-
-    # config/initializers/active_admin.rb
-    ActiveAdmin.setup do |config|
-      config.namespace :admin do |admin|
-        admin.build_menu do |menu|
-          menu.add :label => "The Application", :url => "/", :priority => 0
-
-          menu.add :label => "Sites" do |sites|
-            sites.add :label => "Google", :url => "http://google.com", :html_options => { :target => :blank }
-            sites.add :label => "Facebook", :url => "http://facebook.com"
-            sites.add :label => "Github", :url => "http://github.com"
-          end
-        end
-      end
-    end
-
-This block will be run once on application startup to build the menu before each
-of the resources are added to it.
-
-## Scoping the queries
-
-If your administrators have different access levels, you may sometimes want to
-scope what they have access to. Assuming your User model has the proper
-has_many relationships, you can simply scope the listings and finders like so:
-
-    ActiveAdmin.register Post do
-      scope_to :current_user
-
-      # or if the association doesn't have the default name.
-      # scope_to :current_user, :association_method => :blog_posts
-    end
-
-That approach limits the posts an admin can access to ```current_user.posts```.
-
-If you want to do something fancier, for example override a default scope, you can
-also use :association_method parameter with a normal method on your User model.
-The only requirement is that your method returns an instance of ActiveRecord::Relation.
-
-    class Ad < ActiveRecord::Base
-      default_scope lambda { where :published => true }
-    end
-
-    class User < ActiveRecord::Base
-      def managed_ads
-        # Overrides Ad's default_scope
-        Ad.unscoped
-      end
-    end
-
-    ActiveAdmin.register Ad do
-      scope_to :current_user, :association_method => :managed_ads
-    end
-
-In case you just need to customize the query independently of the current user, you can
-override the `scoped_collection` method on the controller:
-
-    ActiveAdmin.register Post do
-      controller do
-        def scoped_collection
-          Post.includes(:author)
-        end
-      end
-    end
-
-## Customizing resource retrieval
-
-If you need to completely replace the record retrieving code (e.g., you have a custom
-`to_param` implementation in your models), override the `resource` method on the controller:
-
-    ActiveAdmin.register Post do
-      controller do
-        def resource
-          Post.where(id: params[:id]).first!
-        end
-      end
-    end
-
-In fact, the controllers use [Inherited Resource](https://github.com/josevalim/inherited_resources),
-so you can use all the
-[customization features in Inherited Resource](https://github.com/josevalim/inherited_resources#overwriting-defaults).
-
-
-## Belongs To
-
-It's common to want to scope a series of resources to a relationship. For
-example a Project may have many Milestones and Tickets. To nest the resource
-within another, you can use the `belongs_to` method:
-
-    ActiveAdmin.register Project do
-    end
-
-    ActiveAdmin.register Ticket do
-      belongs_to :project
-    end
-
-Projects will be available as usual and tickets will be availble by visiting
-"/admin/projects/1/tickets" assuming that a Project with the id of 1 exists.
-Active Admin does not add "Tickets" to the global navigation because the routes
-can only be generated when there is a project id.
-
-To create links to the resource, you can add them to a sidebar (one of the many
-possibilities for how you may with to handle your user interface):
-
-    ActiveAdmin.register Project do
-
-      sidebar "Project Details" do
-        ul do
-          li link_to("Tickets", admin_project_tickets_path(project))
-          li link_to("Milestones", admin_project_milestones_path(project))
-        end
-      end
-
-    end
-
-    ActiveAdmin.register Ticket do
-      belongs_to :project
-    end
-
-    ActiveAdmin.register Milestone do
-      belongs_to :project
-    end
-
-
-In some cases (like Projects), there are many sub resources and you would
-actually like the global navigation to switch when the user navigates "into" a
-project. To accomplish this, Active Admin stores the `belongs_to` resources in a
-seperate menu which you can use if you so wish. To use:
-
-    ActiveAdmin.register Ticket do
-      belongs_to :project
-      navigation_menu :project
-    end
-
-    ActiveAdmin.register Milestone do
-      belongs_to :project
-      navigation_menu :project
-    end
-
-Now, when you navigate to the tickets section, the global navigation will
-only display "Tickets" and "Milestones". When you navigate back to a
-non-belongs_to resource, it will switch back to the default menu.
-
-You can also defer the menu lookup until runtime so that you can dynamically show
-different menus, say perhaps on user permissions or level.  For example:
-
-    ActiveAdmin.register Ticket do
-      belongs_to: :project
-      navigation_menu do
-        authorized?(:manage, SomeResource) ? :project : :restricted_menu
-      end
-    end

data/vendor/deps/active_admin/docs/3-index-pages/index-as-block.md

@@ -1,16 +0,0 @@
-<!-- Please don't edit this file. It will be clobbered. -->
-
-# Index as a Block
-
-If you want to fully customize the display of your resources on the index
-screen, Index as a Block allows you to render a block of content for each
-resource.
-
-    index :as => :block do |product|
-      div :for => product do
-        h2 auto_link(product.title)
-        div do
-          simple_format product.description
-        end
-      end
-    end

data/vendor/deps/active_admin/docs/3-index-pages/index-as-blog.md

@@ -1,61 +0,0 @@
-<!-- Please don't edit this file. It will be clobbered. -->
-
-# Index as Blog
-
-Render your index page as a set of posts. The post has two main options:
-title and body.
-
-    index :as => :blog do
-      title :my_title # Calls #my_title on each resource
-      body  :my_body  # Calls #my_body on each resource
-    end
-
-## Post Title
-
-The title is the content that will be rendered within a link to the
-resource. There are two main ways to set the content for the title
-
-First, you can pass in a method to be called on your
-resource. For example:
-
-    index :as => :blog do
-      title :a_method_to_call
-    end
-
-This will result in the title of the post being the return value of
-Resource#a_method_to_call
-
-Second, you can pass a block to the tile option which will then be
-used as the contents fo the title. The resource being rendered
-is passed in to the block. For Example:
-
-    index :as => :blog do
-      title do |post|
-        span post.title, :class => 'title'
-        span post.created_at, :class => 'created_at'
-      end
-    end
-
-## Post Body
-
-The body is rendered underneath the title of each post. The same two
-style of options work as the Post Title above.
-
-Call a method on the resource as the body:
-
-    index :as => :blog do
-      title :my_title
-      body :my_body # Return value of #my_body will be the body
-    end
-
-Or, render a block as the body:
-
-    index :as => :blog do
-      title :my_title
-      body do |post|
-        div truncate(post.title)
-        div :class => 'meta' do
-          span "Post in #{post.categories.join(', ')}"
-        end
-      end
-    end

data/vendor/deps/active_admin/docs/3-index-pages/index-as-grid.md

@@ -1,21 +0,0 @@
-<!-- Please don't edit this file. It will be clobbered. -->
-
-# Index as a Grid
-
-Sometimes you want to display the index screen for a set of resources as a grid
-(possibly a grid of thumbnail images). To do so, use the :grid option for the
-index block.
-
-    index :as => :grid do |product|
-      link_to(image_tag(product.image_path), admin_product_path(product))
-    end
-
-The block is rendered within a cell in the grid once for each resource in the
-collection. The resource is passed into the block for you to use in the view.
-
-You can customize the number of colums that are rendered using the columns
-option:
-
-    index :as => :grid, :columns => 5 do |product|
-      link_to(image_tag(product.image_path), admin_product_path(product))
-    end

data/vendor/deps/active_admin/docs/3-index-pages/index-as-table.md

@@ -1,105 +0,0 @@
-<!-- Please don't edit this file. It will be clobbered. -->
-
-# Index as a Table
-
-By default, the index page is a table with each of the models content columns and links to
-show, edit and delete the object. There are many ways to customize what gets
-displayed.
-
-## Defining Columns
-
-To display an attribute or a method on a resource, simply pass a symbol into the
-column method:
-
-    index do
-      column :title
-    end
-
-For association columns we make an educated guess on what to display by
-calling the following methods in the following order:
-
-    :display_name, :full_name, :name, :username, :login, :title, :email, :to_s
-
-This can be customized in config/initializers/active_admin.rb.
-
-If the default title does not work for you, pass it as the first argument:
-
-    index do
-      column "My Custom Title", :title
-    end
-
-Sometimes calling methods just isn't enough and you need to write some view
-specific code. For example, say we wanted a colum called Title which holds a
-link to the posts admin screen.
-
-The column method accepts a block as an argument which will then be rendered
-within the context of the view for each of the objects in the collection.
-
-    index do
-      column "Title" do |post|
-        link_to post.title, admin_post_path(post)
-      end
-    end
-
-The block gets called once for each resource in the collection. The resource gets passed into
-the block as an argument.
-
-To setup links to View, Edit and Delete a resource, use the actions method:
-
-    index do
-      column :title
-      actions
-    end
-
-You can also append custom links to the default links:
-
-    index do
-      column :title
-      actions do |post|
-        link_to "Preview", admin_preview_post_path(post), :class => "member_link"
-      end
-    end
-
-Or forego the default links entirely:
-
-    index do
-      column :title
-      actions :defaults => false do |post|
-        link_to "View", admin_post_path(post)
-      end
-    end
-
-## Sorting
-
-When a column is generated from an Active Record attribute, the table is
-sortable by default. If you are creating a custom column, you may need to give
-Active Admin a hint for how to sort the table.
-
-If a column is defined using a block, you must pass the key to turn on sorting. The key
-is the attribute which gets used to sort objects using Active Record.
-
-    index do
-      column "Title", :sortable => :title do |post|
-        link_to post.title, admin_post_path(post)
-      end
-    end
-
-You can turn off sorting on any column by passing false:
-
-    index do
-      column :title, :sortable => false
-    end
-
-## Showing and Hiding Columns
-
-The entire index block is rendered within the context of the view, so you can
-easily do things that show or hide columns based on the current context.
-
-For example, if you were using CanCan:
-
-    index do
-      column :title, :sortable => false
-      if can? :manage, Post
-        column :some_secret_data
-      end
-    end

data/vendor/deps/active_admin/docs/3-index-pages.md

@@ -1,141 +0,0 @@
-# Customizing the Index Page
-
-Filtering and listing resources is one of the most important tasks for
-administering a web application. Active Admin provides many different tools for
-you to build a compelling interface into your data for the admin staff.
-
-Built in, Active Admin has the following index renderers:
-
-* *Table*: A table drawn with each row being a resource ([View Table Docs](3-index-pages/index-as-table.md))
-* *Grid*: A set of rows and columns each cell being a resource ([View Grid Docs](3-index-pages/index-as-grid.md))
-* *Blocks*: A set of rows (not tabular) each row being a resource ([View Blocks Docs](3-index-pages/index-as-block.md))
-* *Blog*: A title and body content, similar to a blog index ([View Blog Docs](3-index-pages/index-as-blog.md))
-
-All index pages also support scopes, filters, pagination, action items, and
-sidebar sections.
-
-## Index Filters
-
-By default the index screen includes a "Filters" sidebar on the right hand side
-with a filter for each attribute of the registered model. You can customize the
-filters that are displayed as well as the type of widgets they use.
-
-To display a filter for an attribute, use the filter method
-
-    ActiveAdmin.register Post do
-      filter :title
-    end
-
-Out of the box, Active Admin supports the following filter types:
-
-* *:string* - A search field
-* *:date_range* - A start and end date field with calendar inputs
-* *:numeric* - A drop down for selecting "Equal To", "Greater Than" or "Less
-  Than" and an input for a value.
-* *:select* - A drop down which filters based on a selected item in a collection
-  or all.
-* *:check_boxes* - A list of check boxes users can turn on and off to filter
-
-By default, Active Admin will pick the most relevant filter based on the
-attribute type. You can force the type by passing the :as option.
-
-    filter :author, :as => :check_boxes
-
-The :check_boxes and :select types accept options for the collection. By default
-it attempts to create a collection based on an association. But you can pass in
-the collection as a proc to be called at render time.
-
-    # Will call available
-    filter :author, :as => :check_boxes, :collection => proc { Author.all }
-
-You can change the filter label by passing a label option:
-
-    filter :author, :label => 'Author'
-
-By default, Active Admin will try to use ActiveModel I18n to determine the label.
-
-Filters can also be disabled for a resource, a namespace or the entire
-application.
-
-To disable for a specific resource:
-
-    ActiveAdmin.register Post do
-      config.filters = false
-    end
-
-To disable for a namespace, in the initializer:
-
-    ActiveAdmin.setup do |config|
-      config.namespace :my_namespace do |my_namespace|
-        my_namespace.filters = false
-      end
-    end
-
-Or to disable for the entire application:
-
-    ActiveAdmin.setup do |config|
-      config.filters = false
-    end
-
-You can also add a filter and still preserve the default filters:
-
-    preserve_default_filters!
-    filter :author
-
-## Index default sort order
-
-You can define the default sort order for index pages:
-
-    ActiveAdmin.register Post do
-      config.sort_order = "name_asc"
-    end
-
-## Index pagination
-
-
-You can set the number of records per page per resources:
-
-    ActiveAdmin.register Post do
-      config.per_page = 10
-    end
-
-You can also disable pagination:
-
-    ActiveAdmin.register Post do
-      config.paginate = false
-    end
-
-## Disable CSV, XML and JSON export
-
-You can remove links to download CSV, XML and JSON exports:
-
-    index :download_links => false do
-    end
-
-## Customizing Download Links
-
-There are multiple ways to either remove the download links per resource listing, or customize the formats that are shown.  Customize the formats by passing an array of symbols, or pass false to hide entirely.
-
-Customizing the download links per resource:
-
-    ActiveAdmin.register Post do
-
-      # hide the links entirely
-      index :download_links => false
-
-      # only show a PDF export
-      index :download_links => [:pdf]
-
-    end
-
-If you want to customize download links for every resource throughout the application, configure that in the `active_admin` initializer.
-
-    ActiveAdmin.setup do |config|
-
-      # Disable entirely
-      config.download_links = false
-
-      # Want PDF added to default download links
-      config.download_links = [:csv, :xml, :json, :pdf]
-
-    end

data/vendor/deps/active_admin/docs/4-csv-format.md

@@ -1,32 +0,0 @@
-# Customizing the CSV format
-
-Active Admin provides CSV file downloads on the index screen for each Resource.
-By default it will render a CSV file with all the content columns of your
-registered model.
-
-Customizing the CSV format is as simple as customizing the index page.
-
-    ActiveAdmin.register Post do
-      csv do
-        column :title
-        column("Author") { |post| post.author.full_name }
-      end
-    end
-
-You can set custom csv options:
-
-    ActiveAdmin.register Post do
-      csv :options => { :force_quotes => true } do
-        column :title
-        column("Author") { |post| post.author.full_name }
-      end
-    end
-
-You can set options for the CSV format system-wide:
-
-    # config/initializers/active_admin.rb
-    # Set the CSV builder separator (default is ",")
-    config.csv_column_separator = ';'
-
-    # Set the CSV builder options (default is {})
-    config.csv_options = { :force_quotes => true }

data/vendor/deps/active_admin/docs/5-forms.md

@@ -1,39 +0,0 @@
-# Customizing the Form
-
-Active Admin gives complete control over the output of the form by creating a thin DSL on top of
-the fabulous DSL created by Formtastic (http://github.com/justinfrench/formtastic).
-
-    ActiveAdmin.register Post do
-
-      form do |f|
-        f.inputs "Details" do
-          f.input :title
-          f.input :published_at, :label => "Publish Post At"
-          f.input :category
-        end
-        f.inputs "Content" do
-          f.input :body
-        end
-        f.actions
-      end
-
-    end
-
-Please view the documentation for Formtastic to see all the wonderful things you can do:
-http://github.com/justinfrench/formtastic
-
-If you require a more custom form than can be provided through the DSL, you can pass
-a partial in to render the form yourself.
-
-For example:
-
-    ActiveAdmin.register Post do
-      form :partial => "form"
-    end
-
-Then implement app/views/admin/posts/_form.html.erb:
-
-    <%= semantic_form_for [:admin, @post] do |f| %>
-      <%= f.inputs :title, :body %>
-      <%= f.actions :commit %>
-    <% end %>