jquery-cookie-rails 1.3.1 → 1.3.1.1

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: d77cfb804875276c74c5c3da4b64bcfbf82dd316
+  data.tar.gz: 956212961fb03bdfdb6437d223fa7a6bde18523d
+SHA512:
+  metadata.gz: 90e6cd50b947e2a5846f70eb84f09035719de4abccb5530f9063a5f9a8b1d8e72ed6e423f497b392c22237b96abc01f0a37a557c8e235a83808ebb43268c5a1c
+  data.tar.gz: 72a281be74f649f39aa3785a8bb4fe9ad15baebf18f9a9c14f7e708deacb44882c3b8ae0c200cb5cde7bd7e55e149b5f1a0a8d6af386cff267864240147092aa

data/README.md

@@ -12,15 +12,9 @@ gem 'jquery-cookie-rails'
 
 Now run `bundle install`.
 
-### Rails 3.0
+### Rails 3.2 or greater
 
-This gem adds a single generator to Rails 3, `jquery-cookie:install`.
-
-Running the generator will copy over the assets to your assets to your public directory.
-
-### Rails 3.1 or greater
-
-For Rails 3.1 and greater, the files will be added to the asset pipeline and available for you to use.
+For Rails 3.2 and greater, the files will be added to the asset pipeline and available for you to use.
 
 Simply the following to `app/assets/javascripts/application.js` after jQuery:
 
@@ -44,4 +38,4 @@ All props goto [Klaus Hartl](http://github.com/carhartl).
 
 ## Copyright
 
-Copyright (c) 2012 Ryan Scott Lewis. See LICENSE for details.
+Copyright (c) 2012 Ryan Scott Lewis. See LICENSE for details.

data/Rakefile

@@ -1,6 +1,13 @@
 require 'fancy_logger'
 require 'pathname'
 
+begin
+  require 'bundler/setup'
+  require 'bundler/gem_tasks'
+rescue LoadError
+  puts 'You must `gem install bundler` and `bundle install` to run rake tasks'
+end
+
 $logger       = FancyLogger.new(STDOUT)
 $project_path = Pathname.new(__FILE__).dirname.expand_path
 $spec         = eval( $project_path.join('jquery-cookie-rails.gemspec').read )
@@ -9,33 +16,33 @@ Rake::TaskManager.record_task_metadata = true
 
 def run_command(command)
   result = `#{command}`.chomp.strip
-  
+
   message = if result.empty?
     command
   else
     command + "\n" + result.lines.collect { |line| "  #{line}" }.join
   end
-  
+
   $logger.debug(message)
-  
+
   result
 end
 
 namespace :jquery_cookie do
   desc 'Update the `jquery-cookie` submodule'
-  task :update do    
+  task :update do
     jquery_cookie_path = $project_path.join('lib', 'jquery-cookie')
     latest_tag         = run_command("cd #{jquery_cookie_path} && git describe --abbrev=0 --tags")
-      
+
     run_command "cd #{jquery_cookie_path} && git checkout #{latest_tag}"
   end
-    
+
   desc 'Copy the `jquery.cookie.js` file to the `vendor/assets/javascripts` folder'
   task :vendor do
     jquery_cookie_path = $project_path.join('lib', 'jquery-cookie', 'jquery.cookie.js')
     vendor_path        = $project_path.join('vendor', 'assets', 'javascripts')
     vendor_path.mkpath
-    
+
     run_command "cp #{jquery_cookie_path} #{vendor_path}"
   end
 end
@@ -49,20 +56,14 @@ task :update => :jquery_cookie do
   latest_tag         = run_command("cd #{jquery_cookie_path} && git describe --abbrev=0 --tags")
   version            = latest_tag.gsub(/^v/, '')
   version_path       = $project_path.join('VERSION')
-  
+
   run_command "git add ."
   run_command "git commit -m \"Version bump to #{version}\""
   run_command "git tag #{version}"
 end
 
-require 'rubygems/package_task'
-Gem::PackageTask.new($spec) do |t|
-  t.need_zip = false
-  t.need_tar = false
-end
-
 task :default do
   Rake::application.options.show_tasks = :tasks  # this solves sidewaysmilk problem
   Rake::application.options.show_task_pattern = //
   Rake::application.display_tasks_and_comments
-end
+end

data/VERSION

@@ -1 +1 @@
-1.3.1
+1.3.1.1

data/jquery-cookie-rails.gemspec

@@ -1,6 +1,6 @@
 # -*- encoding: utf-8 -*-
 Gem::Specification.new do |s|
-  
+
   # Variables
   s.name        = 'jquery-cookie-rails'
   s.author      = 'Ryan Scott Lewis'
@@ -8,24 +8,25 @@ Gem::Specification.new do |s|
   s.summary     = 'Use jquery-cookie with Rails 3'
   s.description = 'This gem provides jquery-cookie assets for your Rails 3 application.'
   s.license     = 'MIT'
-  
+
   # Dependencies
-  s.add_dependency 'version',       '~> 1.0'
-  s.add_dependency 'railties',      '>= 3.2.0', '< 5.0'
-  s.add_dependency 'thor',          '~> 0.14'
-  s.add_dependency 'jquery-rails',  '~> 2.0'
+  s.add_dependency 'railties', '>= 3.2.0', '< 5.0'
+  s.add_development_dependency 'rails',        '~> 3.2'
+  s.add_development_dependency 'sqlite3',      '~> 1.3'
+  s.add_development_dependency 'uglifier',     '~> 1.3'
+  s.add_development_dependency 'sass',         '~> 3.2'
   s.add_development_dependency 'rake',         '~> 10.0'
   s.add_development_dependency 'fancy_logger', '~> 0.1'
+  s.add_development_dependency 'rspec-rails',  '~> 2.13'
+  s.add_development_dependency 'fuubar',       '~> 1.1'
   s.required_rubygems_version = ">= 1.3.6"
-  
+
   # Pragmatically set variables
   s.homepage = "http://github.com/RyanScottLewis/#{s.name}"
   s.version = Pathname.glob('VERSION*').first.read rescue '0.0.0'
   s.require_paths = ['lib']
-  s.files = %w(Gemfile Gemfile.lock jquery-cookie-rails.gemspec LICENSE Rakefile README.md VERSION vendor/assets/javascripts/jquery.cookie.js)
+  s.files = %w(Gemfile jquery-cookie-rails.gemspec LICENSE Rakefile README.md VERSION vendor/assets/javascripts/jquery.cookie.js)
   s.files += Dir.glob('lib/*.rb')
-  s.files += Dir.glob('lib/generators/**/*.rb')
   s.files += Dir.glob('lib/jquery-cookie-rails/**/*.rb')
   s.files += Dir.glob('spec/**/*')
-  
-end
+end

data/spec/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.

data/spec/dummy/Rakefile

@@ -0,0 +1,7 @@
+#!/usr/bin/env rake
+# 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__)
+
+Dummy::Application.load_tasks

data/spec/dummy/app/assets/javascripts/application.js

@@ -0,0 +1,15 @@
+// This is a manifest file that'll be compiled into application.js, which will include all the files
+// listed below.
+//
+// Any JavaScript/Coffee file within this directory, lib/assets/javascripts, vendor/assets/javascripts,
+// or vendor/assets/javascripts of plugins, if any, can be referenced here using a relative path.
+//
+// It's not advisable to add code directly here, but if you do, it'll appear at the bottom of the
+// the compiled file.
+//
+// WARNING: THE FIRST BLANK LINE MARKS THE END OF WHAT'S TO BE PROCESSED, ANY BLANK LINE SHOULD
+// GO AFTER THE REQUIRES BELOW.
+//
+//= require jquery
+//= require jquery_ujs
+//= require_tree .

data/spec/dummy/app/assets/stylesheets/application.css

@@ -0,0 +1,13 @@
+/*
+ * 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 .
+ */