RubyGems - tabulous - Versions diffs - 1.3.1 → 1.3.2 - Mend

tabulous 1.3.1 → 1.3.2

Files changed (1453) hide show

data/spec/applications/simple_tabs/shared/spec/features/simple_tabs_spec.rb ADDED Viewed

@@ -0,0 +1,46 @@
+require 'spec_helper'
+describe 'home tab' do
+  before(:each) do
+    visit '/'
+  end
+  it 'should work' do
+    page.should have_content('This tests the most basic usage of tabulous.')
+  end
+end
+describe 'galaxies tab' do
+  before(:each) do
+    visit '/'
+    click_link 'Galaxies'
+  end
+  it 'should work' do
+    page.should have_content('Listing galaxies')
+    page.should_not have_content('Listing stars')
+    page.should_not have_content('Listing planets')
+  end
+end
+describe 'stars tab' do
+  before(:each) do
+    visit '/'
+    click_link 'Stars'
+  end
+  it 'should work' do
+    page.should_not have_content('Listing galaxies')
+    page.should have_content('Listing stars')
+    page.should_not have_content('Listing planets')
+  end
+end
+describe 'planets tab' do
+  before(:each) do
+    visit '/'
+    click_link 'Planets'
+  end
+  it 'should work' do
+    page.should_not have_content('Listing galaxies')
+    page.should_not have_content('Listing stars')
+    page.should have_content('Listing planets')
+  end
+end

data/spec/applications/subtabs/application_template.rb ADDED Viewed

@@ -0,0 +1,85 @@
+require File.expand_path('../../application_template_helper', __FILE__)
+generate_test_application do
+  #*****************************************************************************
+  #  MODELS AND SCAFFOLDING
+  generate(:model, 'galaxy name:string --old-style-hash')
+  generate(:scaffold, 'galaxies/elliptical_galaxy name:string --old-style-hash')
+  generate(:scaffold, 'galaxies/lenticular_galaxy name:string --old-style-hash')
+  generate(:scaffold, 'galaxies/spiral_galaxy name:string --old-style-hash')
+  generate(:model, 'planet name:string --old-style-hash')
+  generate(:scaffold, 'exoplanet name:string --old-style-hash')
+  generate(:scaffold, 'rogue_planet name:string --old-style-hash')
+  generate(:scaffold, 'star name:string --old-style-hash')
+  #*****************************************************************************
+  #  MORE CONTROLLERS AND VIEWS
+  generate(:controller, 'home index --old-style-hash')
+  replace_view 'home', 'index', <<-CODE.strip_heredoc
+    <h1>Explanation</h1>
+    This application is useful for testing that:
+    <ul>
+      <li>tabs can have subtabs</li>
+      <li>the scaffold styles work well with custom application styles (and a reset stylesheet)</li>
+      <li>scaffold styles can be customized</li>
+      <li>tabs work with namespaced resources</li>
+      <li>tabs and subtabs can be hidden</li>
+      <li>tabs and subtabs can be disabled</li>
+      <li>tabs and controllers do not need a one-to-one mapping</li>
+      <li>procs can be used in tab configuration</li>
+    </ul>
+  CODE
+  generate(:controller, 'misc always_hidden always_visible always_enabled always_disabled --old-style-hash')
+  replace_view 'misc', 'always_enabled', <<-CODE.strip_heredoc
+    <p>
+      This subtab is always enabled.  The neighboring subtab, called "always disabled",
+      should never be clickable.
+    </p>
+  CODE
+  replace_view 'misc', 'always_visible', <<-CODE.strip_heredoc
+    <p>
+      This subtab is always visible.  The neighboring subtab, called "always hidden",
+      should never be shown.
+    </p>
+  CODE
+  #*****************************************************************************
+  #  MORE ROUTES
+  route "root :to => 'home#index'"
+  route "get 'hidden/always_visible' => 'misc#always_visible'"
+  route "get 'hidden/always_hidden' => 'misc#always_hidden'"
+  route "get 'disabled/always_enabled' => 'misc#always_enabled'"
+  route "get 'disabled/always_disabled' => 'misc#always_disabled'"
+  #*****************************************************************************
+  #  LAYOUT
+  replace_application_layout <<-CODE.strip_heredoc
+    <!DOCTYPE html>
+    <html>
+    <head>
+      <title>Subtabs</title>
+      <%= stylesheet_link_tag 'reset' %>
+      <%= stylesheet_link_tag 'application' %>
+      <%= csrf_meta_tag %>
+    </head>
+    <body>
+      <header id="main">
+        <h1 id="title">Subtabs</h1>
+        <h2 id="subtitle">Test Application for Tabulous</h2>
+      </header>
+      <%= tabs %>
+      <%= subtabs %>
+      <div id="content">
+        <%= yield %>
+      </div>
+    </body>
+    </html>
+  CODE
+end

data/spec/applications/subtabs/rails_3-0-20/.gitignore ADDED Viewed

@@ -0,0 +1,4 @@
+.bundle
+db/*.sqlite3
+log/*.log
+tmp/

data/spec/applications/subtabs/rails_3-0-20/Gemfile ADDED Viewed

@@ -0,0 +1,12 @@
+source 'https://rubygems.org'
+gem 'tabulous', :path => "../../../.."
+gem 'sqlite3', '>= 1.3.7'
+group :test, :development do
+  gem "rspec-rails"
+end
+group :test do
+  gem 'capybara', "~> 2.0.2"
+  gem 'launchy'
+  gem 'redgreen' unless RUBY_VERSION >= "1.9"
+end
+gem 'rails', '~> 3.0.0'

data/spec/applications/subtabs/rails_3-0-20/README ADDED Viewed

@@ -0,0 +1,256 @@
+== 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/spec/applications/subtabs/rails_3-0-20/Rakefile ADDED Viewed

@@ -0,0 +1,7 @@
+# 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'
+Rails3020::Application.load_tasks

data/spec/applications/subtabs/rails_3-0-20/app/assets/stylesheets/application.css ADDED Viewed

@@ -0,0 +1,65 @@
+/*
+ * This is a manifest file that'll be compiled into application.css, which will include all the files
+ * listed below.
+ *
+ * Any CSS and SCSS file within this directory, lib/assets/stylesheets, vendor/assets/stylesheets,
+ * or vendor/assets/stylesheets of plugins, if any, can be referenced here using a relative path.
+ *
+ * You're free to add application-wide styles to this file and they'll appear at the top of the
+ * compiled file, but it's generally better to create a new file per style scope.
+ *
+ *= require_self
+ *= require_tree .
+ */
+// These styles are placed in app/assets/stylesheets for Rails 4 and public/stylesheets for Rails 3.0
+body {
+  font-family: 'Verdana', sans-serif;
+  font-size: 14px;
+}
+h1#title {
+  font-size: 30px;
+  text-align: center;
+  padding-top: 30px;
+}
+h2#subtitle {
+  text-align: center;
+}
+#main {
+  background-color: #cec;
+}
+ul {
+  list-style: disc;
+  margin: 1em 2em;
+}
+p, div {
+  margin: 1em;
+}
+h1 {
+  font-size: 24px;
+  font-weight: bold;
+  padding-bottom: 12px;
+}
+h2 {
+  font-size: 18px;
+  font-weight: bold;
+  padding-bottom: 9px;
+}
+h3 {
+  font-size: 16px;
+  font-weight: bold;
+  padding-bottom: 8px;
+}
+#content {
+  padding: 30px 50px;
+}