six-updater-web 0.24.8 → 0.24.9

data/lib/six-updater-web/script/destroy

@@ -1,3 +1,3 @@
-#!/usr/bin/env ruby
-require File.dirname(__FILE__) + '/../config/boot'
-require 'commands/destroy'
+#!/usr/bin/env ruby
+require File.dirname(__FILE__) + '/../config/boot'
+require 'commands/destroy'

data/lib/six-updater-web/script/plugin

@@ -1,3 +1,3 @@
-#!/usr/bin/env ruby
-require File.dirname(__FILE__) + '/../config/boot'
-require 'commands/plugin'
+#!/usr/bin/env ruby
+require File.dirname(__FILE__) + '/../config/boot'
+require 'commands/plugin'

data/lib/six-updater-web/test/functional/configs_controller_test.rb

@@ -1,8 +1,8 @@
-require 'test_helper'
-
-class ConfigsControllerTest < ActionController::TestCase
-  # Replace this with your real tests.
-  test "the truth" do
-    assert true
-  end
-end
+require 'test_helper'
+
+class ConfigsControllerTest < ActionController::TestCase
+  # Replace this with your real tests.
+  test "the truth" do
+    assert true
+  end
+end

data/lib/six-updater-web/test/functional/mods_controller_test.rb

@@ -1,8 +1,8 @@
-require 'test_helper'
-
-class ModsControllerTest < ActionController::TestCase
-  # Replace this with your real tests.
-  test "the truth" do
-    assert true
-  end
-end
+require 'test_helper'
+
+class ModsControllerTest < ActionController::TestCase
+  # Replace this with your real tests.
+  test "the truth" do
+    assert true
+  end
+end

data/lib/six-updater-web/test/functional/repositories_controller_test.rb

@@ -1,8 +1,8 @@
-require 'test_helper'
-
-class RepositoriesControllerTest < ActionController::TestCase
-  # Replace this with your real tests.
-  test "the truth" do
-    assert true
-  end
-end
+require 'test_helper'
+
+class RepositoriesControllerTest < ActionController::TestCase
+  # Replace this with your real tests.
+  test "the truth" do
+    assert true
+  end
+end

data/lib/six-updater-web/test/functional/servers_controller_test.rb

@@ -1,8 +1,8 @@
-require 'test_helper'
-
-class ServersControllerTest < ActionController::TestCase
-  # Replace this with your real tests.
-  test "the truth" do
-    assert true
-  end
-end
+require 'test_helper'
+
+class ServersControllerTest < ActionController::TestCase
+  # Replace this with your real tests.
+  test "the truth" do
+    assert true
+  end
+end

data/lib/six-updater-web/test/functional/settings_controller_test.rb

@@ -1,8 +1,8 @@
-require 'test_helper'
-
-class SettingsControllerTest < ActionController::TestCase
-  # Replace this with your real tests.
-  test "the truth" do
-    assert true
-  end
-end
+require 'test_helper'
+
+class SettingsControllerTest < ActionController::TestCase
+  # Replace this with your real tests.
+  test "the truth" do
+    assert true
+  end
+end

data/lib/six-updater-web/test/performance/browsing_test.rb

@@ -1,9 +1,9 @@
-require 'test_helper'
-require 'performance_test_help'
-
-# Profiling results for each test method are written to tmp/performance.
-class BrowsingTest < ActionController::PerformanceTest
-  def test_homepage
-    get '/'
-  end
-end
+require 'test_helper'
+require 'performance_test_help'
+
+# Profiling results for each test method are written to tmp/performance.
+class BrowsingTest < ActionController::PerformanceTest
+  def test_homepage
+    get '/'
+  end
+end

data/lib/six-updater-web/test/test_helper.rb

@@ -1,38 +1,38 @@
-ENV["RAILS_ENV"] = "test"
-require File.expand_path(File.dirname(__FILE__) + "/../config/environment")
-require 'test_help'
-
-class ActiveSupport::TestCase
-  # Transactional fixtures accelerate your tests by wrapping each test method
-  # in a transaction that's rolled back on completion.  This ensures that the
-  # test database remains unchanged so your fixtures don't have to be reloaded
-  # between every test method.  Fewer database queries means faster tests.
-  #
-  # Read Mike Clark's excellent walkthrough at
-  #   http://clarkware.com/cgi/blosxom/2005/10/24#Rails10FastTesting
-  #
-  # Every Active Record database supports transactions except MyISAM tables
-  # in MySQL.  Turn off transactional fixtures in this case; however, if you
-  # don't care one way or the other, switching from MyISAM to InnoDB tables
-  # is recommended.
-  #
-  # The only drawback to using transactional fixtures is when you actually 
-  # need to test transactions.  Since your test is bracketed by a transaction,
-  # any transactions started in your code will be automatically rolled back.
-  self.use_transactional_fixtures = true
-
-  # Instantiated fixtures are slow, but give you @david where otherwise you
-  # would need people(:david).  If you don't want to migrate your existing
-  # test cases which use the @david style and don't mind the speed hit (each
-  # instantiated fixtures translates to a database query per test method),
-  # then set this back to true.
-  self.use_instantiated_fixtures  = false
-
-  # Setup all fixtures in test/fixtures/*.(yml|csv) for all tests in alphabetical order.
-  #
-  # Note: You'll currently still have to declare fixtures explicitly in integration tests
-  # -- they do not yet inherit this setting
-  fixtures :all
-
-  # Add more helper methods to be used by all tests here...
-end
+ENV["RAILS_ENV"] = "test"
+require File.expand_path(File.dirname(__FILE__) + "/../config/environment")
+require 'test_help'
+
+class ActiveSupport::TestCase
+  # Transactional fixtures accelerate your tests by wrapping each test method
+  # in a transaction that's rolled back on completion.  This ensures that the
+  # test database remains unchanged so your fixtures don't have to be reloaded
+  # between every test method.  Fewer database queries means faster tests.
+  #
+  # Read Mike Clark's excellent walkthrough at
+  #   http://clarkware.com/cgi/blosxom/2005/10/24#Rails10FastTesting
+  #
+  # Every Active Record database supports transactions except MyISAM tables
+  # in MySQL.  Turn off transactional fixtures in this case; however, if you
+  # don't care one way or the other, switching from MyISAM to InnoDB tables
+  # is recommended.
+  #
+  # The only drawback to using transactional fixtures is when you actually 
+  # need to test transactions.  Since your test is bracketed by a transaction,
+  # any transactions started in your code will be automatically rolled back.
+  self.use_transactional_fixtures = true
+
+  # Instantiated fixtures are slow, but give you @david where otherwise you
+  # would need people(:david).  If you don't want to migrate your existing
+  # test cases which use the @david style and don't mind the speed hit (each
+  # instantiated fixtures translates to a database query per test method),
+  # then set this back to true.
+  self.use_instantiated_fixtures  = false
+
+  # Setup all fixtures in test/fixtures/*.(yml|csv) for all tests in alphabetical order.
+  #
+  # Note: You'll currently still have to declare fixtures explicitly in integration tests
+  # -- they do not yet inherit this setting
+  fixtures :all
+
+  # Add more helper methods to be used by all tests here...
+end

data/lib/six-updater-web/test/unit/config_test.rb

@@ -1,8 +1,8 @@
-require 'test_helper'
-
-class ConfigTest < ActiveSupport::TestCase
-  # Replace this with your real tests.
-  test "the truth" do
-    assert true
-  end
-end
+require 'test_helper'
+
+class ConfigTest < ActiveSupport::TestCase
+  # Replace this with your real tests.
+  test "the truth" do
+    assert true
+  end
+end

data/lib/six-updater-web/test/unit/helpers/configs_helper_test.rb

@@ -1,4 +1,4 @@
-require 'test_helper'
-
-class ConfigsHelperTest < ActionView::TestCase
-end
+require 'test_helper'
+
+class ConfigsHelperTest < ActionView::TestCase
+end

data/lib/six-updater-web/test/unit/helpers/mods_helper_test.rb

@@ -1,4 +1,4 @@
-require 'test_helper'
-
-class ModsHelperTest < ActionView::TestCase
-end
+require 'test_helper'
+
+class ModsHelperTest < ActionView::TestCase
+end

data/lib/six-updater-web/test/unit/helpers/repositories_helper_test.rb

@@ -1,4 +1,4 @@
-require 'test_helper'
-
-class RepositoriesHelperTest < ActionView::TestCase
-end
+require 'test_helper'
+
+class RepositoriesHelperTest < ActionView::TestCase
+end

data/lib/six-updater-web/test/unit/helpers/servers_helper_test.rb

@@ -1,4 +1,4 @@
-require 'test_helper'
-
-class ServersHelperTest < ActionView::TestCase
-end
+require 'test_helper'
+
+class ServersHelperTest < ActionView::TestCase
+end

data/lib/six-updater-web/test/unit/helpers/settings_helper_test.rb

@@ -1,4 +1,4 @@
-require 'test_helper'
-
-class SettingsHelperTest < ActionView::TestCase
-end
+require 'test_helper'
+
+class SettingsHelperTest < ActionView::TestCase
+end

data/lib/six-updater-web/test/unit/mod_test.rb

@@ -1,8 +1,8 @@
-require 'test_helper'
-
-class ModTest < ActiveSupport::TestCase
-  # Replace this with your real tests.
-  test "the truth" do
-    assert true
-  end
-end
+require 'test_helper'
+
+class ModTest < ActiveSupport::TestCase
+  # Replace this with your real tests.
+  test "the truth" do
+    assert true
+  end
+end

data/lib/six-updater-web/test/unit/repository_test.rb

@@ -1,8 +1,8 @@
-require 'test_helper'
-
-class RepositoryTest < ActiveSupport::TestCase
-  # Replace this with your real tests.
-  test "the truth" do
-    assert true
-  end
-end
+require 'test_helper'
+
+class RepositoryTest < ActiveSupport::TestCase
+  # Replace this with your real tests.
+  test "the truth" do
+    assert true
+  end
+end

data/lib/six-updater-web/test/unit/server_test.rb

@@ -1,8 +1,8 @@
-require 'test_helper'
-
-class ServerTest < ActiveSupport::TestCase
-  # Replace this with your real tests.
-  test "the truth" do
-    assert true
-  end
-end
+require 'test_helper'
+
+class ServerTest < ActiveSupport::TestCase
+  # Replace this with your real tests.
+  test "the truth" do
+    assert true
+  end
+end

data/lib/six-updater-web/test/unit/setting_test.rb

@@ -1,8 +1,8 @@
-require 'test_helper'
-
-class SettingTest < ActiveSupport::TestCase
-  # Replace this with your real tests.
-  test "the truth" do
-    assert true
-  end
-end
+require 'test_helper'
+
+class SettingTest < ActiveSupport::TestCase
+  # Replace this with your real tests.
+  test "the truth" do
+    assert true
+  end
+end

data/lib/six-updater-web/vendor/plugins/render_component/README

@@ -1,37 +1,37 @@
-Components allow you to call other actions for their rendered response while executing another action. You can either delegate
-the entire response rendering or you can mix a partial response in with your other content.
-
-  class WeblogController < ActionController::Base
-    # Performs a method and then lets hello_world output its render
-    def delegate_action
-      do_other_stuff_before_hello_world
-      render_component :controller => "greeter",  :action => "hello_world", :params => { :person => "david" }
-    end
-  end
-
-  class GreeterController < ActionController::Base
-    def hello_world
-      render :text => "#{params[:person]} says, Hello World!"
-    end
-  end
-
-The same can be done in a view to do a partial rendering:
-
-  Let's see a greeting:
-  <%= render_component :controller => "greeter", :action => "hello_world" %>
-
-It is also possible to specify the controller as a class constant, bypassing the inflector
-code to compute the controller class at runtime:
-
-<%= render_component :controller => GreeterController, :action => "hello_world" %>
-
-== When to use components
-
-Components should be used with care. They're significantly slower than simply splitting reusable parts into partials and
-conceptually more complicated. Don't use components as a way of separating concerns inside a single application. Instead,
-reserve components to those rare cases where you truly have reusable view and controller elements that can be employed
-across many applications at once.
-
-So to repeat: Components are a special-purpose approach that can often be replaced with better use of partials and filters.
-
+Components allow you to call other actions for their rendered response while executing another action. You can either delegate
+the entire response rendering or you can mix a partial response in with your other content.
+
+  class WeblogController < ActionController::Base
+    # Performs a method and then lets hello_world output its render
+    def delegate_action
+      do_other_stuff_before_hello_world
+      render_component :controller => "greeter",  :action => "hello_world", :params => { :person => "david" }
+    end
+  end
+
+  class GreeterController < ActionController::Base
+    def hello_world
+      render :text => "#{params[:person]} says, Hello World!"
+    end
+  end
+
+The same can be done in a view to do a partial rendering:
+
+  Let's see a greeting:
+  <%= render_component :controller => "greeter", :action => "hello_world" %>
+
+It is also possible to specify the controller as a class constant, bypassing the inflector
+code to compute the controller class at runtime:
+
+<%= render_component :controller => GreeterController, :action => "hello_world" %>
+
+== When to use components
+
+Components should be used with care. They're significantly slower than simply splitting reusable parts into partials and
+conceptually more complicated. Don't use components as a way of separating concerns inside a single application. Instead,
+reserve components to those rare cases where you truly have reusable view and controller elements that can be employed
+across many applications at once.
+
+So to repeat: Components are a special-purpose approach that can often be replaced with better use of partials and filters.
+
 Copyright (c) 2007 David Heinemeier Hansson, released under the MIT license

data/lib/six-updater-web/vendor/plugins/render_component/Rakefile

@@ -1,22 +1,22 @@
-require 'rake'
-require 'rake/testtask'
-require 'rake/rdoctask'
- 
-desc 'Default: run unit tests.'
-task :default => :test
- 
-desc 'Test the components plugin.'
-Rake::TestTask.new(:test) do |t|
-  t.libs << 'lib'
-  t.pattern = 'test/**/*_test.rb'
-  t.verbose = true
-end
- 
-desc 'Generate documentation for the components plugin.'
-Rake::RDocTask.new(:rdoc) do |rdoc|
-  rdoc.rdoc_dir = 'rdoc'
-  rdoc.title = 'Components'
-  rdoc.options << '--line-numbers' << '--inline-source'
-  rdoc.rdoc_files.include('README')
-  rdoc.rdoc_files.include('lib/**/*.rb')
+require 'rake'
+require 'rake/testtask'
+require 'rake/rdoctask'
+ 
+desc 'Default: run unit tests.'
+task :default => :test
+ 
+desc 'Test the components plugin.'
+Rake::TestTask.new(:test) do |t|
+  t.libs << 'lib'
+  t.pattern = 'test/**/*_test.rb'
+  t.verbose = true
+end
+ 
+desc 'Generate documentation for the components plugin.'
+Rake::RDocTask.new(:rdoc) do |rdoc|
+  rdoc.rdoc_dir = 'rdoc'
+  rdoc.title = 'Components'
+  rdoc.options << '--line-numbers' << '--inline-source'
+  rdoc.rdoc_files.include('README')
+  rdoc.rdoc_files.include('lib/**/*.rb')
 end

data/lib/six-updater-web/vendor/plugins/render_component/init.rb

@@ -1,2 +1,2 @@
-require 'components'
-ActionController::Base.send :include, Components
+require 'components'
+ActionController::Base.send :include, Components