the_sortable_tree 2.6.1 → 2.6.2

data/spec/dummy_app/_test/fixtures/article_categories.yml

@@ -1,9 +0,0 @@
-# Read about fixtures at http://api.rubyonrails.org/classes/Fixtures.html
-
-one:
-  title: MyString
-  content: MyText
-
-two:
-  title: MyString
-  content: MyText

data/spec/dummy_app/_test/fixtures/comments.yml

@@ -1,13 +0,0 @@
-# Read about fixtures at http://api.rubyonrails.org/classes/Fixtures.html
-
-one:
-  name: MyString
-  email: MyString
-  raw_content: MyText
-  content: MyText
-
-two:
-  name: MyString
-  email: MyString
-  raw_content: MyText
-  content: MyText

data/spec/dummy_app/_test/fixtures/inventory/categories.yml

@@ -1,9 +0,0 @@
-# Read about fixtures at http://api.rubyonrails.org/classes/Fixtures.html
-
-one:
-  title: MyString
-  content: MyText
-
-two:
-  title: MyString
-  content: MyText

data/spec/dummy_app/_test/functional/inventory/category_controller_test.rb

@@ -1,14 +0,0 @@
-require 'test_helper'
-
-class Inventory::CategoryControllerTest < ActionController::TestCase
-  test "should get index" do
-    get :index
-    assert_response :success
-  end
-
-  test "should get manage" do
-    get :manage
-    assert_response :success
-  end
-
-end

data/spec/dummy_app/_test/performance/browsing_test.rb

@@ -1,12 +0,0 @@
-require 'test_helper'
-require 'rails/performance_test_help'
-
-class BrowsingTest < ActionDispatch::PerformanceTest
-  # Refer to the documentation for all available options
-  # self.profile_options = { :runs => 5, :metrics => [:wall_time, :memory]
-  #                          :output => 'tmp/performance', :formats => [:flat] }
-
-  def test_homepage
-    get '/'
-  end
-end

data/spec/dummy_app/_test/test_helper.rb

@@ -1,13 +0,0 @@
-ENV["RAILS_ENV"] = "test"
-require File.expand_path('../../config/environment', __FILE__)
-require 'rails/test_help'
-
-class ActiveSupport::TestCase
-  # 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/spec/dummy_app/_test/unit/admin/page_test.rb

@@ -1,7 +0,0 @@
-require 'test_helper'
-
-class Admin::PageTest < ActiveSupport::TestCase
-  # test "the truth" do
-  #   assert true
-  # end
-end

data/spec/dummy_app/_test/unit/article_category_test.rb

@@ -1,7 +0,0 @@
-require 'test_helper'
-
-class ArticleCategoryTest < ActiveSupport::TestCase
-  # test "the truth" do
-  #   assert true
-  # end
-end

data/spec/dummy_app/_test/unit/comment_test.rb

@@ -1,7 +0,0 @@
-require 'test_helper'
-
-class CommentTest < ActiveSupport::TestCase
-  # test "the truth" do
-  #   assert true
-  # end
-end

data/spec/dummy_app/_test/unit/helpers/inventory/category_helper_test.rb

@@ -1,4 +0,0 @@
-require 'test_helper'
-
-class Inventory::CategoryHelperTest < ActionView::TestCase
-end

data/spec/dummy_app/_test/unit/inventory/category_test.rb

@@ -1,7 +0,0 @@
-require 'test_helper'
-
-class Inventory::CategoryTest < ActiveSupport::TestCase
-  # test "the truth" do
-  #   assert true
-  # end
-end

data/spec/dummy_app/config/database.yml

@@ -1,7 +0,0 @@
-development:
-  adapter: sqlite3
-  database: db/development.db
-
-test:
-  adapter: sqlite3
-  database: db/test.db

data/spec/dummy_app/doc/README_FOR_APP

@@ -1,2 +0,0 @@
-Use this README file to introduce your application and point to useful places in the API for learning more.
-Run "rake doc:app" to generate API documentation for your models, controllers, helpers, and libraries.

data/spec/dummy_app/script/rails

@@ -1,6 +0,0 @@
-#!/usr/bin/env ruby
-# This command will automatically be run when you run "rails" with Rails 3 gems installed from the root of your application.
-
-APP_PATH = File.expand_path('../../config/application',  __FILE__)
-require File.expand_path('../../config/boot',  __FILE__)
-require 'rails/commands'

data/spec/dummy_app/spec/build_tree_helper.rb

@@ -1,39 +0,0 @@
-def build_test_tree klass = Page, count = 5
-  basic_content = "Hello World!"
-  counter = 0
-
-  count.times do |book_i|
-    var = klass.new
-    var.title        = "Book #{book_i}"
-    var.content      = basic_content + Faker::Lorem.sentence(5)
-    var.save
-
-    counter = counter.next
-    puts '.' + counter.to_s
-
-    count.times do |chapter_i|
-      var1 = klass.new
-      var1.title        = "Chapter #{chapter_i}"
-      var1.content      = basic_content + Faker::Lorem.sentence(5)
-      var1.save
-      var1.move_to_child_of var
-
-      counter = counter.next
-      puts '..' + counter.to_s
-
-      count.times do |page_i|
-        var2 = klass.new
-        var2.title        = "Page #{page_i}"
-        var2.content      = basic_content + Faker::Lorem.sentence(25)
-        var2.save
-
-        var2.move_to_child_of var1
-        counter = counter.next
-        puts '...' + counter.to_s
-      end
-    end
-  end
-
-  puts klass.to_s
-  puts klass.count
-end

data/spec/dummy_app/spec/spec_helper.rb

@@ -1,52 +0,0 @@
-# This file is copied to spec/ when you run 'rails generate rspec:install'
-ENV["RAILS_ENV"] ||= 'test'
-require File.expand_path("../../config/environment", __FILE__)
-require 'rspec/rails'
-require 'rspec/autorun'
-
-require 'capybara/rails'
-
-# Requires supporting ruby files with custom matchers and macros, etc,
-# in spec/support/ and its subdirectories.
-Dir[Rails.root.join("spec/support/**/*.rb")].each { |f| require f }
-
-# Checks for pending migrations before tests are run.
-# If you are not using ActiveRecord, you can remove this line.
-ActiveRecord::Migration.check_pending! if defined?(ActiveRecord::Migration)
-
-Capybara.configure do |config|
-  # config.default_wait_time = 2
-  # config.app_host    = '127.0.0.1'
-  config.server_port = 3111
-end 
-
-RSpec.configure do |config|
-  Capybara.default_driver = :selenium
-
-  # ## Mock Framework
-  #
-  # If you prefer to use mocha, flexmock or RR, uncomment the appropriate line:
-  #
-  # config.mock_with :mocha
-  # config.mock_with :flexmock
-  # config.mock_with :rr
-
-  # Remove this line if you're not using ActiveRecord or ActiveRecord fixtures
-  config.fixture_path = "#{::Rails.root}/spec/fixtures"
-
-  # If you're not using ActiveRecord, or you'd prefer not to run each of your
-  # examples within a transaction, remove the following line or assign false
-  # instead of true.
-  config.use_transactional_fixtures = true
-
-  # If true, the base class of anonymous controllers will be inferred
-  # automatically. This will be the default behavior in future versions of
-  # rspec-rails.
-  config.infer_base_class_for_anonymous_controllers = false
-
-  # Run specs in random order to surface order dependencies. If you find an
-  # order dependency and want to debug it, you can fix the order by providing
-  # the seed, which is printed after each run.
-  #     --seed 1234
-  config.order = "random"
-end

data/spec/dummy_app/spec/views/pages/index.html.haml_spec.rb

@@ -1,48 +0,0 @@
-require 'spec_helper'
-require 'build_tree_helper'
-
-describe "pages/index" do
-  include Capybara::DSL
-
-  before(:all) do
-    Benchmark.bm do |b|
-      b.report{
-        Page.all.each{|p| begin; p.destroy; rescue; end; }
-      }
-    end
-    puts "DB Cleaning"
-
-    # sleep 3
-
-    # 5 => 155
-    # 6 => 258
-    # 7 => 399
-    # 8 => 584
-    # 9 => 819
-    # 10 => 1110
-    Benchmark.bm do |b|
-      b.report{
-        build_test_tree Page, 10
-      }
-    end
-    puts "Tree Building"
-
-  end
-
-  it "render all pages without capybara" do
-    assign :pages, Page.all
-    render
-  end
-
-  it "pages/index" do
-    visit '/pages'
-    nodes = all('li', visible: true)
-    nodes.count.should be 15
-  end
-
-  it "pages/manage all pages" do
-    visit '/pages/manage'
-    nodes = all('li', visible: true)
-    nodes.count.should be 1110
-  end
-end

data/spec/old_tests/controlllers/controller_mixin_spec.rb

@@ -1,49 +0,0 @@
-require 'spec_helper'
-
-describe TheSortableTreeController do
-  describe "common variable definitions" do
-    class BigTest; end
-
-    module ParentModule
-      class TestsController < ApplicationController
-        include TheSortableTreeController::Rebuild
-      end
-
-      class BigTestsController < ApplicationController
-        include TheSortableTreeController::Rebuild
-      end
-    end
-
-    before do
-      @test_controller = TestsController.new
-      @variable, @collection, @klass = @test_controller.the_define_common_variables 
-    end
-
-    it "should define collection" do
-      @collection.should == 'tests'
-    end
-
-    describe "namespaced controllers" do
-      before do
-        @test_controller = ParentModule::TestsController.new
-        @variable, @collection, @klass = @test_controller.the_define_common_variables 
-      end
-
-      it "should handle namespaced collections" do
-        @collection.should == 'tests'
-      end
-
-    end
-
-    describe "camel cased and namespaced controllers" do
-      before do
-        @test_controller = ParentModule::BigTestsController.new
-        @variable, @collection, @klass = @test_controller.the_define_common_variables 
-      end
-
-      it "should handle namespaced collections" do
-        @collection.should == 'big_tests'
-      end
-    end
-  end
-end

data/spec/old_tests/dummy/README.rdoc

@@ -1,261 +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.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.org/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
-  |   |-- assets
-  |       |-- images
-  |       |-- javascripts
-  |       `-- stylesheets
-  |   |-- controllers
-  |   |-- helpers
-  |   |-- mailers
-  |   |-- models
-  |   `-- views
-  |       `-- layouts
-  |-- config
-  |   |-- environments
-  |   |-- initializers
-  |   `-- locales
-  |-- db
-  |-- doc
-  |-- lib
-  |   `-- tasks
-  |-- log
-  |-- public
-  |-- script
-  |-- test
-  |   |-- fixtures
-  |   |-- functional
-  |   |-- integration
-  |   |-- performance
-  |   `-- unit
-  |-- tmp
-  |   |-- cache
-  |   |-- pids
-  |   |-- sessions
-  |   `-- sockets
-  `-- vendor
-      |-- assets
-          `-- stylesheets
-      `-- plugins
-
-app
-  Holds all the code that's specific to this particular application.
-
-app/assets
-  Contains subdirectories for images, stylesheets, and JavaScript files.
-
-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. 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.