role-rails 1.1.0 → 1.2.0

data/.gitignore

@@ -0,0 +1,6 @@
+*.gem
+*.log
+.bundle
+Gemfile.lock
+tmp/
+pkg/*

data/.gitmodules

@@ -0,0 +1,3 @@
+[submodule "role"]
+	path = role
+	url = git://github.com/kossnocorp/role.git

data/Gemfile

@@ -1,13 +1,4 @@
 source 'http://rubygems.org'
 
-gem 'rails', '>=3.1.0'
-
-group :development, :test do
-  # Require Slim engine with support of configurable attribute shortcuts. Replace this with version when possible.
-  gem 'slim', :git => 'git://github.com/stonean/slim.git', :ref => "40cda599e54dbdb282405c855a817435ec7e5afe"
-  
-  gem 'sqlite3'
-  gem "shoulda", ">= 0"
-  gem "bundler", "~> 1.0.0"
-  gem "jeweler", "~> 1.6.4"
-end
+# Specify your gem's dependencies in role-rails.gemspec
+gemspec

data/Rakefile

@@ -1,37 +1,9 @@
-# encoding: utf-8
-
-require 'rubygems'
-require 'bundler'
-
-$:.push File.expand_path('../lib', __FILE__)
-require 'role-rails/version'
-
-
-begin
-  Bundler.setup(:default, :development)
-rescue Bundler::BundlerError => e
-  $stderr.puts e.message
-  $stderr.puts "Run `bundle install` to install missing gems"
-  exit e.status_code
-end
-require 'rake'
-
-require 'jeweler'
-Jeweler::Tasks.new do |gem|
-  # gem is a Gem::Specification... see http://docs.rubygems.org/read/chapter/20 for more options
-  gem.name = 'role-rails'
-  gem.homepage = "https://github.com/kossnocorp/role-rails"
-  gem.license = "MIT"
-  gem.summary = 'jQuery plugin to provide easy way to handle DOM elements by role attribute'
-  gem.description = 'jQuery plugin to provide easy way to handle DOM elements by role attribute'
-  gem.email = 'koss@nocorp.me'
-  gem.authors = ['Sasha Koss']
-  gem.rubyforge_project = 'role-rails'
-  gem.version = RoleRails::VERSION
-end
-Jeweler::RubygemsDotOrgTasks.new
-
+#!/usr/bin/env rake
+require 'bundler/gem_tasks'
 require 'rake/testtask'
+require 'rdoc/task'
+require 'fileutils'
+
 Rake::TestTask.new(:test) do |test|
   test.libs << 'lib' << 'test'
   test.pattern = 'test/**/*_test.rb'
@@ -39,8 +11,6 @@ Rake::TestTask.new(:test) do |test|
 end
 
 task :default => :test
-
-require 'rdoc/task'
 Rake::RDocTask.new do |rdoc|
   version = RoleRails::VERSION
 
@@ -49,3 +19,16 @@ Rake::RDocTask.new do |rdoc|
   rdoc.rdoc_files.include('README*')
   rdoc.rdoc_files.include('lib/**/*.rb')
 end
+
+namespace :role do
+
+  desc 'Pull role/master subtree.'
+  task :pull do
+    system "cd role ; git checkout v#{RoleRails::VERSION}"
+  end
+
+  desc 'Update role assets.'
+  task :update => 'role:pull' do
+    FileUtils.cp_r('role/lib/.', 'vendor/assets/javascripts')
+  end
+end

data/lib/role-rails.rb

@@ -1,6 +1,2 @@
-require 'rails'
 require 'role-rails/version'
-
-module RoleRails
-  require 'role-rails/engine'
-end
+require 'role-rails/engine'

data/lib/role-rails/engine.rb

@@ -1,12 +1,7 @@
-require 'rails'
-
 module RoleRails
   class Engine < ::Rails::Engine
     initializer "role-rails.register" do |app|
-      if defined?(Slim::Engine)
-        Slim::Engine.default_options[:shortcut] ||= {}
-        Slim::Engine.default_options[:shortcut].merge!('@' => 'div role')
-      end
+      defined?(Slim::Parser) && Slim::Parser.default_options[:shortcut].try(:[]=, '@', 'div role')
     end
   end
 end

data/lib/role-rails/version.rb

@@ -1,3 +1,3 @@
 module RoleRails
-  VERSION = '1.1.0'
+  VERSION = '1.2.0'
 end

data/role-rails.gemspec

@@ -1,59 +1,37 @@
-# Generated by jeweler
-# DO NOT EDIT THIS FILE DIRECTLY
-# Instead, edit Jeweler::Tasks in Rakefile, and run 'rake gemspec'
 # -*- encoding: utf-8 -*-
 
-Gem::Specification.new do |s|
-  s.name = "role-rails"
-  s.version = "1.1.0"
-
-  s.required_rubygems_version = Gem::Requirement.new(">= 0") if s.respond_to? :required_rubygems_version=
-  s.authors = ["Sasha Koss"]
-  s.date = "2012-03-23"
-  s.description = "jQuery plugin to provide easy way to handle DOM elements by role attribute"
-  s.email = "koss@nocorp.me"
-  s.files = [
-    "Gemfile",
-    "Rakefile",
-    "lib/role-rails.rb",
-    "lib/role-rails/engine.rb",
-    "lib/role-rails/version.rb",
-    "role-rails.gemspec",
-    "vendor/assets/javascripts/jquery.role.js",
-    "vendor/assets/javascripts/role.js"
-  ]
-  s.homepage = "https://github.com/kossnocorp/role-rails"
-  s.licenses = ["MIT"]
-  s.require_paths = ["lib"]
-  s.rubyforge_project = "role-rails"
-  s.rubygems_version = "1.8.15"
-  s.summary = "jQuery plugin to provide easy way to handle DOM elements by role attribute"
-
-  if s.respond_to? :specification_version then
-    s.specification_version = 3
-
-    if Gem::Version.new(Gem::VERSION) >= Gem::Version.new('1.2.0') then
-      s.add_runtime_dependency(%q<rails>, [">= 3.1.0"])
-      s.add_development_dependency(%q<slim>, [">= 0"])
-      s.add_development_dependency(%q<sqlite3>, [">= 0"])
-      s.add_development_dependency(%q<shoulda>, [">= 0"])
-      s.add_development_dependency(%q<bundler>, ["~> 1.0.0"])
-      s.add_development_dependency(%q<jeweler>, ["~> 1.6.4"])
-    else
-      s.add_dependency(%q<rails>, [">= 3.1.0"])
-      s.add_dependency(%q<slim>, [">= 0"])
-      s.add_dependency(%q<sqlite3>, [">= 0"])
-      s.add_dependency(%q<shoulda>, [">= 0"])
-      s.add_dependency(%q<bundler>, ["~> 1.0.0"])
-      s.add_dependency(%q<jeweler>, ["~> 1.6.4"])
-    end
-  else
-    s.add_dependency(%q<rails>, [">= 3.1.0"])
-    s.add_dependency(%q<slim>, [">= 0"])
-    s.add_dependency(%q<sqlite3>, [">= 0"])
-    s.add_dependency(%q<shoulda>, [">= 0"])
-    s.add_dependency(%q<bundler>, ["~> 1.0.0"])
-    s.add_dependency(%q<jeweler>, ["~> 1.6.4"])
-  end
-end
+require File.expand_path('../lib/role-rails/version', __FILE__)
+
+Gem::Specification.new do |gem|
+  gem.name              = "role-rails"
+  gem.rubyforge_project = "role-rails"
+  gem.version           = RoleRails::VERSION
+
+  gem.authors           = ["Sasha Koss"]
+  gem.email             = "koss@nocorp.me"
+  gem.date              = "2012-03-23"
+
+  gem.description       = "jQuery plugin to provide easy way to handle DOM elements by role attribute"
+  gem.summary           = "jQuery plugin to provide easy way to handle DOM elements by role attribute"
+  gem.homepage          = "https://github.com/kossnocorp/role-rails"
+
+  gem.executables       = `git ls-files -- bin/*`.split("\n").map{ |f| File.basename(f) }
+  gem.files             = `git ls-files`.split("\n")
+  gem.test_files        = `git ls-files -- {test,spec,features}/*`.split("\n")
+
+  gem.files.reject! { |fn| fn.include? "vendor/role" }
 
+  gem.licenses          = ["MIT"]
+
+  gem.require_paths     = ["lib"]
+
+  gem.rubygems_version  = "1.8.15"
+
+  gem.add_dependency "rails", ">= 3.1.0"
+
+  gem.add_development_dependency "slim", ">= 1.2.0"
+  gem.add_development_dependency "skim", ">= 0.8.1"
+  gem.add_development_dependency "sqlite3"
+  gem.add_development_dependency "shoulda"
+  gem.add_development_dependency "bundler", ">= 1.0.0"
+end

data/test/dummy/README.rdoc

@@ -0,0 +1,261 @@
+== 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.