js-cookie-rails 2.0.0.pre.beta.1.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: 0d93cd5cb86cf64acb4343b2df2f698ea92f437c
+  data.tar.gz: 252b7b1e45c4bff85d5052fc24211a7557b36078
+SHA512:
+  metadata.gz: dd38489b5a015d55e97420467c06fbb39f577f1b6001680e39c082e2ddbb0cc994126f5b29e55f788f3b71625e52b8a9f5d70d2f2cdd46c712405c66f6961acb
+  data.tar.gz: 0955e0a3bccddc9c756634b31573602da7bec41f9c3ff7548557f55ff1f61a6c24c9a13812714684ed54f8d0733024f9c6a0553b6f0e0e8b42169cce9ad79122

data/Gemfile

@@ -0,0 +1,2 @@
+source 'http://rubygems.org'
+gemspec

data/LICENSE

@@ -0,0 +1,21 @@
+The MIT License
+
+Copyright (c) 2015 Ryan Scott Lewis <ryan@rynet.us>
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.

data/README.md

@@ -0,0 +1,35 @@
+# js-cookie-rails
+
+Adds [js-cookie](https://github.com/js-cookie/js-cookie) to the Rails 3 asset pipeline.
+
+## Installation
+
+In your Gemfile, add the following line:
+
+```ruby
+gem 'js-cookie-rails'
+```
+
+Now run `bundle install`.
+
+### Rails 3.2 or greater
+
+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`:
+
+    //= require js.cookie
+
+## Contributing
+
+* Check out the latest master to make sure the feature hasn't been implemented or the bug hasn't been fixed yet
+* Check out the issue tracker to make sure someone already hasn't requested it and/or contributed it
+* Fork the project
+* Start a feature/bugfix branch
+* Commit and push until you are happy with your contribution
+* Make sure to add tests for it. This is important so I don't break it in a future version unintentionally.
+* Please try not to mess with the Rakefile, version, or history. If you want to have your own version, or is otherwise necessary, that is fine, but please isolate to its own commit so I can cherry-pick around it.
+
+## Copyright
+
+Copyright © 2015 Ryan Scott Lewis. See LICENSE for details.

data/Rakefile

@@ -0,0 +1,71 @@
+require 'rubygems/package_task'
+require 'logger'
+require 'pathname'
+
+$logger       = Logger.new(STDOUT)
+$project_path = Pathname.new(__FILE__).dirname.expand_path
+$spec         = eval( $project_path.join('js-cookie-rails.gemspec').read )
+
+Rake::TaskManager.record_task_metadata = true
+
+def run_command(command)
+  result = `#{command}`.chomp.strip
+  message = command
+  
+  message << "\n" + result.lines.collect { |line| "  #{line}" }.join unless result.empty?
+
+  $logger.debug(message)
+
+  result
+end
+
+Gem::PackageTask.new($spec) do |task|
+  task.need_zip = false
+end
+
+namespace :js_cookie do
+  desc 'Update the `js-cookie` submodule'
+  task :update do
+    js_cookie_path = $project_path.join('lib', 'js-cookie')
+
+    run_command("cd #{js_cookie_path} && git pull origin master")
+    js_cookie_latest_tag = run_command("cd #{js_cookie_path} && git describe --abbrev=0 --tags")
+    run_command "cd #{js_cookie_path} && git checkout #{js_cookie_latest_tag}"
+  end
+
+  desc 'Copy the `js.cookie.js` file to the `vendor/assets/javascripts` folder'
+  task :vendor do
+    js_cookie_script_path = $project_path.join('lib', 'js-cookie', 'src', 'js.cookie.js')
+    vendor_path = $project_path.join('vendor', 'assets', 'javascripts')
+    vendor_path.mkpath
+
+    run_command "cp #{js_cookie_script_path} #{vendor_path}"
+  end
+end
+
+desc 'Update js-cookie and copy `js.cookie.js` into vendor'
+task :js_cookie => ['js_cookie:update', 'js_cookie:vendor']
+
+desc 'Update js-cookie, update js-cookie-rails version, tag on git'
+task :update => :js_cookie do
+  js_cookie_path = $project_path.join('lib', 'js-cookie')
+  js_cookie_latest_tag = run_command("cd #{js_cookie_path} && git describe --abbrev=0 --tags")
+  js_cookie_version = js_cookie_latest_tag.gsub(/^v/, '')
+
+  # Save new gem version
+  gem_version_path = $project_path.join('VERSION')
+  gem_version = "#{js_cookie_version}.0"
+
+  File.open(gem_version_path, 'w') {|f| f.write(gem_version) }
+
+  # Commit
+  run_command "git add ."
+  run_command "git commit -m \"Version bump to #{gem_version} (js-rails version #{js_cookie_version})\""
+  run_command "git tag #{gem_version}"
+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

data/VERSION

@@ -0,0 +1 @@
+2.0.0-beta.1.0

data/js-cookie-rails.gemspec

@@ -0,0 +1,31 @@
+# -*- encoding: utf-8 -*-
+Gem::Specification.new do |s|
+
+  # Variables
+  s.name        = 'js-cookie-rails'
+  s.author      = 'Ryan Scott Lewis'
+  s.email       = 'ryan@rynet.us'
+  s.summary     = 'Use js-cookie with Rails 3'
+  s.description = 'This gem provides js-cookie assets for your Rails 3 application.'
+  s.license     = 'MIT'
+
+  # Dependencies
+  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 '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 js-cookie-rails.gemspec LICENSE Rakefile README.md VERSION vendor/assets/javascripts/js.cookie.js)
+  s.files += Dir.glob('lib/*.rb')
+  s.files += Dir.glob('lib/js-cookie-rails/**/*.rb')
+  s.files += Dir.glob('spec/**/*')
+end

data/lib/js-cookie-rails.rb

@@ -0,0 +1 @@
+require 'js-cookie-rails/rails'

data/lib/js-cookie-rails/rails.rb

@@ -0,0 +1 @@
+require 'js-cookie-rails/rails/engine'

data/lib/js-cookie-rails/rails/engine.rb

@@ -0,0 +1,6 @@
+module JsCookie
+  module Rails
+    class Engine < ::Rails::Engine
+    end
+  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.