admin_assistant 2.1.0 → 2.1.1

data/rails_3_0/README

@@ -1,256 +0,0 @@
-== Welcome to Rails
-
-Rails is a web-application framework that includes everything needed to create
-database-backed web applications according to the Model-View-Control pattern.
-
-This pattern splits the view (also called the presentation) into "dumb"
-templates that are primarily responsible for inserting pre-built data in between
-HTML tags. The model contains the "smart" domain objects (such as Account,
-Product, Person, Post) that holds all the business logic and knows how to
-persist themselves to a database. The controller handles the incoming requests
-(such as Save New Account, Update Product, Show Post) by manipulating the model
-and directing data to the view.
-
-In Rails, the model is handled by what's called an object-relational mapping
-layer entitled Active Record. This layer allows you to present the data from
-database rows as objects and embellish these data objects with business logic
-methods. You can read more about Active Record in
-link:files/vendor/rails/activerecord/README.html.
-
-The controller and view are handled by the Action Pack, which handles both
-layers by its two parts: Action View and Action Controller. These two layers
-are bundled in a single package due to their heavy interdependence. This is
-unlike the relationship between the Active Record and Action Pack that is much
-more separate. Each of these packages can be used independently outside of
-Rails. You can read more about Action Pack in
-link:files/vendor/rails/actionpack/README.html.
-
-
-== Getting Started
-
-1. At the command prompt, create a new Rails application:
-       <tt>rails new myapp</tt> (where <tt>myapp</tt> is the application name)
-
-2. Change directory to <tt>myapp</tt> and start the web server:
-       <tt>cd myapp; rails server</tt> (run with --help for options)
-
-3. Go to http://localhost:3000/ and you'll see:
-       "Welcome aboard: You're riding Ruby on Rails!"
-
-4. Follow the guidelines to start developing your application. You can find
-the following resources handy:
-
-* The Getting Started Guide: http://guides.rubyonrails.org/getting_started.html
-* Ruby on Rails Tutorial Book: http://www.railstutorial.org/
-
-
-== Debugging Rails
-
-Sometimes your application goes wrong. Fortunately there are a lot of tools that
-will help you debug it and get it back on the rails.
-
-First area to check is the application log files. Have "tail -f" commands
-running on the server.log and development.log. Rails will automatically display
-debugging and runtime information to these files. Debugging info will also be
-shown in the browser on requests from 127.0.0.1.
-
-You can also log your own messages directly into the log file from your code
-using the Ruby logger class from inside your controllers. Example:
-
-  class WeblogController < ActionController::Base
-    def destroy
-      @weblog = Weblog.find(params[:id])
-      @weblog.destroy
-      logger.info("#{Time.now} Destroyed Weblog ID ##{@weblog.id}!")
-    end
-  end
-
-The result will be a message in your log file along the lines of:
-
-  Mon Oct 08 14:22:29 +1000 2007 Destroyed Weblog ID #1!
-
-More information on how to use the logger is at http://www.ruby-doc.org/core/
-
-Also, Ruby documentation can be found at http://www.ruby-lang.org/. There are
-several books available online as well:
-
-* Programming Ruby: http://www.ruby-doc.org/docs/ProgrammingRuby/ (Pickaxe)
-* Learn to Program: http://pine.fm/LearnToProgram/ (a beginners guide)
-
-These two books will bring you up to speed on the Ruby language and also on
-programming in general.
-
-
-== Debugger
-
-Debugger support is available through the debugger command when you start your
-Mongrel or WEBrick server with --debugger. This means that you can break out of
-execution at any point in the code, investigate and change the model, and then,
-resume execution! You need to install ruby-debug to run the server in debugging
-mode. With gems, use <tt>sudo gem install ruby-debug</tt>. Example:
-
-  class WeblogController < ActionController::Base
-    def index
-      @posts = Post.find(:all)
-      debugger
-    end
-  end
-
-So the controller will accept the action, run the first line, then present you
-with a IRB prompt in the server window. Here you can do things like:
-
-  >> @posts.inspect
-  => "[#<Post:0x14a6be8
-          @attributes={"title"=>nil, "body"=>nil, "id"=>"1"}>,
-       #<Post:0x14a6620
-          @attributes={"title"=>"Rails", "body"=>"Only ten..", "id"=>"2"}>]"
-  >> @posts.first.title = "hello from a debugger"
-  => "hello from a debugger"
-
-...and even better, you can examine how your runtime objects actually work:
-
-  >> f = @posts.first
-  => #<Post:0x13630c4 @attributes={"title"=>nil, "body"=>nil, "id"=>"1"}>
-  >> f.
-  Display all 152 possibilities? (y or n)
-
-Finally, when you're ready to resume execution, you can enter "cont".
-
-
-== Console
-
-The console is a Ruby shell, which allows you to interact with your
-application's domain model. Here you'll have all parts of the application
-configured, just like it is when the application is running. You can inspect
-domain models, change values, and save to the database. Starting the script
-without arguments will launch it in the development environment.
-
-To start the console, run <tt>rails console</tt> from the application
-directory.
-
-Options:
-
-* Passing the <tt>-s, --sandbox</tt> argument will rollback any modifications
-  made to the database.
-* Passing an environment name as an argument will load the corresponding
-  environment. Example: <tt>rails console production</tt>.
-
-To reload your controllers and models after launching the console run
-<tt>reload!</tt>
-
-More information about irb can be found at:
-link:http://www.rubycentral.com/pickaxe/irb.html
-
-
-== dbconsole
-
-You can go to the command line of your database directly through <tt>rails
-dbconsole</tt>. You would be connected to the database with the credentials
-defined in database.yml. Starting the script without arguments will connect you
-to the development database. Passing an argument will connect you to a different
-database, like <tt>rails dbconsole production</tt>. Currently works for MySQL,
-PostgreSQL and SQLite 3.
-
-== Description of Contents
-
-The default directory structure of a generated Ruby on Rails application:
-
-  |-- app
-  |   |-- controllers
-  |   |-- helpers
-  |   |-- mailers
-  |   |-- models
-  |   `-- views
-  |       `-- layouts
-  |-- config
-  |   |-- environments
-  |   |-- initializers
-  |   `-- locales
-  |-- db
-  |-- doc
-  |-- lib
-  |   `-- tasks
-  |-- log
-  |-- public
-  |   |-- images
-  |   |-- javascripts
-  |   `-- stylesheets
-  |-- script
-  |-- test
-  |   |-- fixtures
-  |   |-- functional
-  |   |-- integration
-  |   |-- performance
-  |   `-- unit
-  |-- tmp
-  |   |-- cache
-  |   |-- pids
-  |   |-- sessions
-  |   `-- sockets
-  `-- vendor
-      `-- plugins
-
-app
-  Holds all the code that's specific to this particular application.
-
-app/controllers
-  Holds controllers that should be named like weblogs_controller.rb for
-  automated URL mapping. All controllers should descend from
-  ApplicationController which itself descends from ActionController::Base.
-
-app/models
-  Holds models that should be named like post.rb. Models descend from
-  ActiveRecord::Base by default.
-
-app/views
-  Holds the template files for the view that should be named like
-  weblogs/index.html.erb for the WeblogsController#index action. All views use
-  eRuby syntax by default.
-
-app/views/layouts
-  Holds the template files for layouts to be used with views. This models the
-  common header/footer method of wrapping views. In your views, define a layout
-  using the <tt>layout :default</tt> and create a file named default.html.erb.
-  Inside default.html.erb, call <% yield %> to render the view using this
-  layout.
-
-app/helpers
-  Holds view helpers that should be named like weblogs_helper.rb. These are
-  generated for you automatically when using generators for controllers.
-  Helpers can be used to wrap functionality for your views into methods.
-
-config
-  Configuration files for the Rails environment, the routing map, the database,
-  and other dependencies.
-
-db
-  Contains the database schema in schema.rb. db/migrate contains all the
-  sequence of Migrations for your schema.
-
-doc
-  This directory is where your application documentation will be stored when
-  generated using <tt>rake doc:app</tt>
-
-lib
-  Application specific libraries. Basically, any kind of custom code that
-  doesn't belong under controllers, models, or helpers. This directory is in
-  the load path.
-
-public
-  The directory available for the web server. Contains subdirectories for
-  images, stylesheets, and javascripts. Also contains the dispatchers and the
-  default HTML files. This should be set as the DOCUMENT_ROOT of your web
-  server.
-
-script
-  Helper scripts for automation and generation.
-
-test
-  Unit and functional tests along with fixtures. When using the rails generate
-  command, template test files will be generated for you and placed in this
-  directory.
-
-vendor
-  External libraries that the application depends on. Also includes the plugins
-  subdirectory. If the app has frozen rails, those gems also go here, under
-  vendor/rails/. This directory is in the load path.

data/rails_3_0/Rakefile

@@ -1,7 +0,0 @@
-# Add your own tasks in files placed in lib/tasks ending in .rake,
-# for example lib/tasks/capistrano.rake, and they will automatically be available to Rake.
-
-require File.expand_path('../config/application', __FILE__)
-require 'rake'
-
-Rails3Test::Application.load_tasks

data/rails_3_0/app/controllers/admin/appointments2_controller.rb

@@ -1,15 +0,0 @@
-class Admin::Appointments2Controller < ApplicationController
-  layout 'admin'
-
-  admin_assistant_for Appointment do |a|
-    a.form.multi = true
-  end
-  
-  protected
-  
-  def time_from_form(time)
-    time['1-3i'] =~ /(\d{4})-(\d{2})-(\d{2})/
-    utc_args = [$1, $2, $3, time['4i'], time['5i']]
-    Time.utc(*(utc_args.map(&:to_i))) unless utc_args.any?(&:blank?)
-  end
-end

data/rails_3_0/app/controllers/admin/appointments_controller.rb

@@ -1,11 +0,0 @@
-class Admin::AppointmentsController < ApplicationController
-  layout 'admin'
-
-  admin_assistant_for Appointment do |a|
-    a.form.multi = true
-    a.index.search do |search|
-      search.columns :subject, :time, :user
-      search[:time].compare_to_range = true
-    end
-  end
-end

data/rails_3_0/app/controllers/admin/blog_posts2_controller.rb

@@ -1,138 +0,0 @@
-class Admin::BlogPosts2Controller < ApplicationController
-  layout 'admin'
-
-  admin_assistant_for BlogPost do |a|
-    a[:user].label = 'Author'
-    
-    # When showing the textile field, say 'Yes' and 'No' instead of 'true'
-    # and 'false'
-    a[:textile].boolean_labels = %w(Yes No)
-        
-    # For the index view:
-    a.index do |index|
-      # Only show these columns
-      index.columns :user, :title, :tags, :published_at, :textile
-      
-      # Add the link 'All' to the top-right corner
-      index.actions['All'] = {:all => '1'}
-      
-      # Sort by published_at descending, then updated_at descending
-      index.sort_by "published_at desc, updated_at desc"
-      
-      # Show only 10 blog posts per page
-      index.per_page 10
-      
-      # Let's have specific fields for searching
-      index.search :id, :title, :body, :textile, :user
-      
-      # Make the author field a link
-      index[:user].link_to_args do |blog_post|
-        { :controller => 'admin/users', :action => 'edit',
-          :id => blog_post.user_id }
-      end
-
-      index.header do |params|
-        if params[:all]
-          "Blog posts (all)"
-        else
-          "Blog posts (unpublished)"
-        end
-      end
-    end
-    
-    # For any form page:
-    a.form do |form|
-      # Only show inputs for these fields
-      form.columns :user, :title, :body, :tags, :textile, :publish
-      
-      # 'publish' isn't defined on BlogPost, we have to specify that it's a
-      # check box
-      form[:publish].input = :check_box
-      
-      # In addition to the 'Create'/'Update' button at the bottom, we also have
-      # a 'Preview' button
-      form.submit_buttons << 'Preview'
-      
-      form[:publish].description =
-          "Click this and published_at will be set automatically"
-        
-      form[:user].select_options = {:include_blank => false}
-      
-      form[:body].text_area_options = {:cols => 20, :rows => 40}
-    end
-    
-    # Only show some columns on the show page
-    a.show.columns :user, :title, :body, :tags, :textile, :published_at
-  end
-  
-  protected
-  
-  # This is run after all saves, whether they're creates or updates
-  def after_save(blog_post)
-    unless blog_post.tags.empty?
-      blog_post.update_attribute(:tags_string, blog_post.tags.map(&:tag).join(','))
-    end
-  end
-  
-  # This is run before all saves, whether they're creates or updates
-  def before_save(blog_post)
-    if params[:blog_post][:publish] == '1' && blog_post.published_at.nil?
-      blog_post.published_at = Time.now.utc
-    end
-  end
-  
-  # This is run in the controller context, just before render is called
-  def before_render_for_index
-    if @index.records.any?
-      @var_set_by_before_render_for_index_hook = 'Confirmed that we have some records'
-    end
-  end
-  
-  # By default, only show unpublished blog posts unless params[:all] is
-  # passed in
-  def conditions_for_index
-    "published_at is null" unless params[:all]
-  end
-
-  # After a successful save, redirect to the edit page with preview=1 to show
-  # the preview pane. The HTML for the preview pane is generated in
-  # app/views/admin/blog_posts2/_after_form.html.erb
-  def destination_after_save(blog_post, params)
-    if params[:commit] == 'Preview'
-      {:action => 'edit', :id => blog_post.id, :preview => '1',
-       :origin => params[:origin]}
-    end
-  end
-  
-  # Preprocesses the 'tags' string from the form to an array of Tag objects.
-  # That way admin_assistant can say
-  #
-  #   blog_post.tags = params[:tags]
-  #
-  # and this will work fine with the BlogPost#tags association
-  def tags_from_form(tags_string, record_params, errors)
-    tags = tags_string.split(/\s+/).map { |tag_str|
-      Tag.find_by_tag(tag_str) || Tag.create(:tag => tag_str)
-    }
-    bad_tags = tags.select { |t| !t.valid? }
-    unless bad_tags.empty?
-      error_str = if bad_tags.size == 1
-        "contain invalid string '#{bad_tags.first.tag}'"
-      else
-        "contain invalid strings " +
-            bad_tags.map { |t| "'#{t.tag}'" }.join(',')
-      end
-      errors.add(:tags, error_str)
-    end
-    tags
-  end
-  
-  def validate(blog_post)
-    pub_str = params[:blog_post][:publish]
-    unless pub_str.nil? or [true, false, '0', '1'].include?(pub_str)
-      blog_post.errors.add(
-        :publish, "can't be \"#{params[:blog_post][:publish]}\""
-      )
-    end
-  end
-end

data/rails_3_0/app/controllers/admin/blog_posts3_controller.rb

@@ -1,76 +0,0 @@
-class Admin::BlogPosts3Controller < ApplicationController
-  layout 'admin'
-
-  admin_assistant_for BlogPost do |a|
-    a.model_class_name = 'post'
-    
-    a[:has_short_title].boolean_labels = %w(Yes No)
-    a[:published?].boolean_labels = %w(Yes No)
-
-    a.index do |index|
-      index.columns :id, :title, :created_at, :updated_at, :body, :textile,
-                    :published?, :user
-                    
-      index[:textile].ajax_toggle = false
-      
-      index.actions['All'] = {:all => '1'}
-      index.actions['Short title'] = {:short_title => '1'}
-      index.actions['Blank body'] = {:blank_body => '1'}
-      
-      # By default, only show unpublished blog posts unless params[:all] is
-      # passed in. This needs to work with or without use of the field search
-      # feature
-      index.conditions do |params|
-        if params[:all]
-        elsif params[:blank_body]
-          "(body is null or body = '')"
-        elsif params[:short_title]
-          "length(title) < 10"
-        else
-          'published_at is null'
-        end
-      end
-      
-      index.cache_total_entries 12.hours
-      
-      # Extended search configuration
-      index.search do |search|
-        search.columns :id, :title, :body, :textile, :user, :has_short_title
-        search[:body].blank_checkbox = true
-        search[:has_short_title].field_type = :boolean
-        search[:has_short_title].conditions do |has_short_title|
-          if has_short_title
-            "length(title) < 10"
-          elsif has_short_title == false
-            "length(title) >= 10"
-          end
-        end
-        search[:id].comparators = false
-        search[:user].match_text_fields_for_association
-      end
-      
-      # sort by user by default
-      index.sort_by :user
-    end
-    
-    a.form do |form|
-      form.columns_for_new  :title, :user, :published_at
-      form.columns_for_edit :title, :user, :published_at, :body, :merged_into
-      form[:published_at].datetime_select_options =
-          {:include_blank => false, :start_year => 2009}
-      form[:published_at].default do |controller|
-        controller.time_now_utc
-      end
-    end
-  end
-  
-  def time_now_utc
-    Time.now.utc
-  end
-  
-  protected
-  
-  def before_validation(blog_post)
-    blog_post.title = '(draft)' if blog_post.title.blank?
-  end
-end