RubyGems - rails - Versions diffs - 0.9.5 → 0.10.0 - Mend

rails 0.9.5 → 0.10.0

Potentially problematic release.

This version of rails might be problematic. Click here for more details.

Files changed (77) hide show

@@ -1,3 +0,0 @@
-Order Deny,Allow
-Deny from all
-Allow from 127.0.0.1

data/doc/index.html DELETED

@@ -1,70 +0,0 @@
-<html>
-<head>
-  <title>Rails: Welcome on board</title>
-  <style>
-    body { background-color: #fff; color: #333; }
-    body, p, ol, ul, td {
-      font-family: verdana, arial, helvetica, sans-serif;
-      font-size:   12px;
-      line-height: 18px;
-    }
-    li {
-      margin-bottom: 7px;
-    }
-    pre {
-      background-color: #eee;
-      padding: 10px;
-      font-size: 11px;
-    }
-    a { color: #000; }
-    a:visited { color: #666; }
-    a:hover { color: #fff; background-color:#000; }
-  </style>
-</head>
-<body>
-<h1>Congratulations, you've put Ruby on Rails!</h1>
-<p><b>Before you move on</b>, verify that the following conditions have been met:</p>
-<ol>
-  <li>The log directory and the empty log files must be writable to the web server (<code>chmod -R 666 log/*</code>).
-  <li>
-    The shebang line in the public/dispatch* files must reference your Ruby installation. <br/>
-    You might need to change it to <code>#!/usr/bin/env ruby</code> or point directly at the installation.
-  </li>
-  <li>
-    Rails on Apache needs to have the cgi handler and mod_rewrite enabled.  <br/>
-    Somewhere in your httpd.conf, you should have:<br/>
-    <code>AddHandler cgi-script .cgi</code><br/>
-    <code>LoadModule rewrite_module     libexec/httpd/mod_rewrite.so</code><br/>
-    <code>AddModule mod_rewrite.c</code>
-  </li>
-</ol>
-<p>Take the following steps to get started:</p>
-<ol>
-  <li>Create empty development and test databases for your application.<br/>
-    <small>Recommendation: Use *_development and *_test names, such as basecamp_development and basecamp_test</small><br/>
-    <small>Warning: Don't point your test database at your development database, it'll destroy the latter on test runs!</small>
-  <li>Edit config/database.yml with your database settings.
-  <li>Create controllers and models using the generator in <code>script/generate</code> <br/>
-    <small>Help: Run the generator with no arguments for documentation</small>
-  <li>See all the tests run by running <code>rake</code>.
-  <li>Develop your Rails application!
-  <li>Setup Apache with <a href="http://www.fastcgi.com">FastCGI</a> (and <a href="http://raa.ruby-lang.org/list.rhtml?name=fcgi">Ruby bindings</a>), if you need better performance
-</ol>
-<p>
-  Having problems getting up and running? First try debugging it yourself by looking at the log files. <br/>
-  Then try the friendly Rails community <a href="http://www.rubyonrails.org">on the web</a> or <a href="http://www.rubyonrails.org/show/IRC">on IRC</a>
-  (<a href="irc://irc.freenode.net/#rubyonrails">FreeNode#rubyonrails</a>).
-</p>
-</body>
-</html>

data/generators/controller/USAGE DELETED

@@ -1,28 +0,0 @@
-GENERATOR
-     controller - create controller and view stub files
-SYNOPSIS
-     generate controller ControllerName action [action ...]
-DESCRIPTION
-     The controller generator takes the name of the new controller as the
-     first argument and a variable number of view names as subsequent arguments.
-     The controller name should be supplied without a "Controller" suffix. The
-     generator will add that itself.
-     Controller generates a controller file in app/controllers with a render
-     action for each of the view names passed, a test suite in test/functional
-     with one passing test case, and HTML stubs for each view in app/views
-     under a directory with the same name as the controller.
-EXAMPLE
-     ./script/generate controller Blog list display new edit
-     This will generate a BlogController class in
-     app/controllers/blog_controller.rb, a BlogHelper class in
-     app/helpers/blog_helper.rb and a BlogControllerTest in
-     test/functional/blog_controller_test.rb, and list.rhtml,
-     display.rhtml, new.rhtml, and edit.rhtml in app/views/blog.
-     The BlogController class will have list, display, new, and edit actions.
-     Each action will render the associated view by default.

data/generators/controller/controller_generator.rb DELETED

@@ -1,26 +0,0 @@
-require 'rails_generator'
-class ControllerGenerator < Rails::Generator::Base
-  attr_reader :actions
-  def generate
-    @actions = args
-    # Controller class, functional test, and helper class.
-    template "controller.rb", "app/controllers/#{file_name}_controller.rb"
-    template "functional_test.rb", "test/functional/#{file_name}_controller_test.rb"
-    template "helper.rb", "app/helpers/#{file_name}_helper.rb"
-    # Create the views directory even if there are no actions.
-    FileUtils.mkdir_p "app/views/#{file_name}"
-    # Create a view for each action.
-    actions.each do |action|
-      template "view.rhtml", "app/views/#{file_name}/#{action}.rhtml", binding
-    end
-  end
-  def full_class_name
-    class_name + "Controller"
-  end
-end

data/generators/controller/templates/functional_test.rb DELETED

@@ -1,17 +0,0 @@
-require File.dirname(__FILE__) + '/../test_helper'
-require '<%= file_name %>_controller'
-# Re-raise errors caught by the controller.
-class <%= full_class_name %>; def rescue_action(e) raise e end; end
-class <%= full_class_name %>Test < Test::Unit::TestCase
-  def setup
-    @controller = <%= full_class_name %>.new
-    @request, @response = ActionController::TestRequest.new, ActionController::TestResponse.new
-  end
-  # Replace this with your real tests.
-  def test_truth
-    assert true
-  end
-end

data/generators/mailer/USAGE DELETED

@@ -1,27 +0,0 @@
-GENERATOR
-     mailer - create mailer and view stub files
-SYNOPSIS
-     generate mailer MailerName action [action ...]
-DESCRIPTION
-     The mailer generator takes the name of the new mailer class as the
-     first argument and a variable number of mail action names as subsequent
-     arguments.
-     Mailer generates a class file in app/models with action methods for each
-     of the mail action names passed, a test suite in test/unit with a stub
-     test case and fixture per action, and template stubs for each action in
-     app/views under a directory with the same name as the class.
-EXAMPLE
-     ./script/generate mailer Notifications signup forgot_password invoice
-     This will generate a Notifications class in
-     app/models/notifications.rb, a NotificationsTest in
-     test/unit/notifications_test.rb, and signup, forgot_password, and invoice
-     in test/fixture/notification. It will also create signup.rhtml,
-     forgot_password.rhtml, and invoice.rhtml in app/views/notifications.
-     The Notifications class will have the following methods: signup,
-     forgot_password, and invoice.

data/generators/mailer/mailer_generator.rb DELETED

@@ -1,22 +0,0 @@
-require 'rails_generator'
-class MailerGenerator < Rails::Generator::Base
-  attr_reader :actions
-  def generate
-    @actions = args
-    # Mailer class and unit test.
-    template "mailer.rb", "app/models/#{file_name}.rb"
-    template "unit_test.rb", "test/unit/#{file_name}_test.rb"
-    # Test fixtures directory.
-    FileUtils.mkdir_p "test/fixtures/#{table_name}"
-    # View template and fixture for each action.
-    args.each do |action|
-      template "view.rhtml", "app/views/#{file_name}/#{action}.rhtml", binding
-      template "fixture.rhtml", "test/fixtures/#{table_name}/#{action}", binding
-    end
-  end
-end

data/generators/model/USAGE DELETED

@@ -1,17 +0,0 @@
-GENERATOR
-     model - create model stub files
-SYNOPSIS
-     generate model ModelName
-DESCRIPTION
-     The model generator takes a model name and generates an empty model in
-     app/models, a test suite in test/unit with one passing test case, and a
-     fixtures YAML file in the test/fixtures directory.
-EXAMPLE
-     ./script/generate model Account
-     This will generate an Account class in app/models/account.rb, an
-     AccountTest in test/unit/account_test.rb, and the fixtures file
-     test/fixtures/account.yml.

data/generators/model/model_generator.rb DELETED

@@ -1,10 +0,0 @@
-require 'rails_generator'
-class ModelGenerator < Rails::Generator::Base
-  def generate
-    # Model class, unit test, and fixtures.
-    template "model.rb", "app/models/#{file_name}.rb"
-    template "unit_test.rb", "test/unit/#{file_name}_test.rb"
-    template "fixtures.yml", "test/fixtures/#{table_name}.yml"
-  end
-end

data/generators/model/templates/fixtures.yml DELETED

	@@ -1 +0,0 @@
1	- # Read about fixtures at http://ar.rubyonrails.org/classes/Fixtures.html

data/generators/scaffold/USAGE DELETED

@@ -1,27 +0,0 @@
-GENERATOR
-     scaffold - create a model and basic controller
-SYNOPSIS
-     generate scaffold ModelName [ControllerName] [action ...]
-DESCRIPTION
-     The scaffold generator takes the name of the new model as the
-     first argument, an optional controller name as the second, and
-     an optional list of controller actions as the subsequent arguments.
-     If the controller name is not specified, the plural form of the model
-     name will be used. Any actions with scaffolding code available
-     will be generated in your controller; others will be left as stubs.
-     The generated controller has the same code that "scaffold :model"
-     uses, so it's easy to migrate when you want to start customizing
-     your controller.
-EXAMPLE
-     ./script/generate scaffold Account Bank debit credit
-     This will generate the Account model with unit tests and fixtures,
-     the BankController controller with actions, views, and tests for
-     index, list, show, new, create, edit, update, and destroy.
-     Now create the accounts table in your database and browse to
-     http://localhost/bank/ -- voila, you're on Rails!

data/generators/scaffold/scaffold_generator.rb DELETED

@@ -1,60 +0,0 @@
-require 'rails_generator'
-class ScaffoldGenerator < Rails::Generator::Base
-  def generate
-    # Model.
-    generator('model').generate
-    # Fixtures.
-    template "fixtures.yml", "test/fixtures/#{table_name}.yml"
-    @controller_class_name = args.empty? ? Inflector.pluralize(class_name) : args.shift.sub(/^[a-z]?/) { |m| m.capitalize }
-    @controller_name        = Inflector.underscore(@controller_class_name)
-    # Controller class, functional test, helper, and views.
-    template "controller.rb", "app/controllers/#{@controller_name}_controller.rb"
-    template "functional_test.rb", "test/functional/#{@controller_name}_controller_test.rb"
-    template "controller/helper.rb", "app/helpers/#{@controller_name}_helper.rb"
-    # Layout and stylesheet.
-    unless File.file?("app/views/layouts/#{@controller_name}.rhtml")
-      template "layout.rhtml", "app/views/layouts/#{@controller_name}.rhtml"
-    end
-    unless File.file?("public/stylesheets/scaffold.css")
-      template "style.css", "public/stylesheets/scaffold.css"
-    end
-    # Scaffolded views.
-    scaffold_views.each do |action|
-      template "view_#{action}.rhtml", "app/views/#{@controller_name}/#{action}.rhtml"
-    end
-    # Unscaffolded views.
-    unscaffolded_actions.each do |action|
-      template "controller/view.rhtml",
-               "app/views/#{@controller_name}/#{action}.rhtml",
-               binding
-    end
-  end
-  def full_class_name
-    class_name + "Controller"
-  end
-  protected
-    def scaffold_views
-      %w(list show new edit)
-    end
-    def scaffold_actions
-      scaffold_views + %w(index create update destroy)
-    end
-    def unscaffolded_actions
-      args - scaffold_actions
-    end
-    def suffix
-      "_#{singular_name}" if options[:suffix]
-    end
-end