jquery-qtip2-rails 0.2.0 → 0.3.0

data/README.md

@@ -42,46 +42,49 @@ File `app/assets/javascripts/application.js`:
 
     //= require jquery.qtip.basic.js
 
+File `app/assets/javascripts/application.css`:
+
+    //= require jquery.qtip.basic.css
+
 ### Customized version of qTip2
 
 You can also create your own `app/assets/javascripts/jquery.qtip.js` file:
 
-    //= include jquery-qtip/src/header.txt
     //= include jquery-qtip/src/intro.js
     //= include jquery-qtip/src/core.js
-    //= include jquery-qtip/src/ajax/ajax.js
-    //= include jquery-qtip/src/bgiframe/bgiframe.js
-    //= include jquery-qtip/src/imagemap/imagemap.js
-    //= include jquery-qtip/src/modal/modal.js
     //= include jquery-qtip/src/svg/svg.js
+    //= include jquery-qtip/src/ajax/ajax.js
     //= include jquery-qtip/src/tips/tips.js
+    //= include jquery-qtip/src/modal/modal.js
+    //= include jquery-qtip/src/viewport/viewport.js
+    //= include jquery-qtip/src/imagemap/imagemap.js
+    //= include jquery-qtip/src/bgiframe/bgiframe.js
     //= include jquery-qtip/src/outro.js
 
 And `app/assets/stylesheets/jquery.qtip.css` file:
 
     /*
-     *= include jquery-qtip/src/header.txt
      *= include jquery-qtip/src/core.css
-     *= include jquery-qtip/src/modal/modal.css
+     *= include jquery-qtip/src/basic.css
+     *= include jquery-qtip/src/css3.css
      *= include jquery-qtip/src/tips/tips.css
-     *= include jquery-qtip/src/styles.css
-     *= include jquery-qtip/src/extra.css
+     *= include jquery-qtip/src/modal/modal.css
     */
 
 This allows you to enable only the plugins that you need and thus reduce qTip2 size.
 This is possible thanks to the asset pipeline preprocessor `include` directive.
 Files `jquery.qtip.js` and `jquery.qtip.basic.js` provided with this gem work the exact same way.
 
-# Minification
+## Minification
 
 This gem does not include minified and compressed version of qTip2 since there is no need of.
 This is done automatically by [Rails asset pipeline](http://guides.rubyonrails.org/asset_pipeline.html).
 
-# qTip2 Twitter Bootstrap theme
+## qTip2 Twitter Bootstrap theme
 
 qTip2 includes a [Twitter Bootstrap theme](http://craigsworks.com/projects/qtip2/docs/style/#classes).
 
-![Bootstrap theme](https://a248.e.akamai.net/camo.github.com/088ac0e36bc7deffbdf49b1d32423c1ae6a999d3/687474703a2f2f696d6731352e686f7374696e67706963732e6e65742f706963732f33353330373571546970626f6f7473747261706f726967696e616c2e706e67)
+![Bootstrap theme](http://img11.hostingpics.net/pics/628782qtip2bootstrap2.png)
 
 How to use:
 
@@ -92,7 +95,7 @@ How to use:
       }
     })
 
-# License
+## License
 
 qTip2 is being developed by [Craig Thompson](http://craigsworks.com/) and is dual-licensed
 under the open source [MIT](http://en.wikipedia.org/wiki/MIT_License) and

data/jquery-qtip2-rails.gemspec

@@ -8,12 +8,15 @@ Gem::Specification.new do |gem|
   gem.summary       = %q{qTip2 packaged for the Rails 3.1+ asset pipeline}
   gem.homepage      = "http://github.com/tkrotoff/jquery-qtip2-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         = `git ls-files`.split($\)
+  gem.executables   = gem.files.grep(%r{^bin/}).map{ |f| File.basename(f) }
+  gem.test_files    = gem.files.grep(%r{^(test|spec|features)/})
   gem.name          = "jquery-qtip2-rails"
   gem.require_paths = ["lib"]
   gem.version       = Jquery::Qtip2::Rails::VERSION
 
-  gem.add_dependency "railties", ">= 3.1.0"
+  gem.add_dependency 'railties', '>= 3.1.0'
+
+  gem.add_development_dependency 'rails'
+  gem.add_development_dependency 'jquery-rails'
 end

data/lib/jquery-qtip2-rails/version.rb

@@ -1,7 +1,7 @@
 module Jquery
   module Qtip2
     module Rails
-      VERSION = "0.2.0"
+      VERSION = "0.3.0"
     end
   end
 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.

data/test/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/test/dummy/app/assets/javascripts/application.js

@@ -0,0 +1,16 @@
+// 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 jquery.qtip.js
+//= require_tree .

data/test/dummy/app/assets/javascripts/home.js

@@ -0,0 +1,48 @@
+// Place all the behaviors and hooks related to the matching controller here.
+// All this logic will automatically be available in application.js.
+
+$(document).ready(function() {
+  $('#title').qtip({
+    position: { target: 'mouse', adjust: { x: 10,  y: 10 } }
+  });
+
+  $('#no_title').qtip({
+    position: { target: 'mouse', adjust: { x: 10,  y: 10 } },
+    content: 'no_title'
+  });
+
+  $('#ui-tooltip-rounded').qtip({
+    position: { target: 'mouse', adjust: { x: 10,  y: 10 } },
+    content: 'ui-tooltip-rounded',
+    style: {
+      classes: 'ui-tooltip-rounded'
+    }
+  });
+
+  $('#ui-tooltip-bootstrap').qtip({
+    position: {
+      my: 'bottom center',
+      at: 'top center',
+      target: 'mouse',
+      viewport: $(window) // Keep the tooltip on-screen at all times
+    },
+    content: {
+      title: {
+        button: 'close',
+        text: 'ui-tooltip-bootstrap'
+      },
+      text: 'ui-tooltip-bootstrap'
+    },
+    style: {
+      classes: 'ui-tooltip-bootstrap'
+    }
+  });
+
+  $('#ui-tooltip-shadow-rounded').qtip({
+    position: { target: 'mouse', adjust: { x: 10,  y: 10 } },
+    content: 'ui-tooltip-shadow ui-tooltip-rounded',
+    style: {
+      classes: 'ui-tooltip-shadow ui-tooltip-rounded'
+    }
+  });
+});

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

@@ -0,0 +1,14 @@
+/*
+ * 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 jquery.qtip.css
+ *= require_tree .
+ */