ajaxify_rails 0.9.2 → 0.9.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: fce3c3696ff1d1c543390f2916755a4349caff8b
-  data.tar.gz: ac2902f259d745682f43f896d642893469579467
+  metadata.gz: 1107c11b41b63db1244a65914330e9fcd94ea64c
+  data.tar.gz: f7ee15a6783e57e92571abd11264af80437bf09c
 SHA512:
-  metadata.gz: 7b7d6ca537d5eac8fbc1b276e4279024000126bdfc73c853cec4b080be79e69c76d2d54d5b16333f33ea6c51f022321cd9e681e6569e4fda6a963e32d6c93c40
-  data.tar.gz: 515702d5e892b8609e716ea34526a4226a50149d5d0dddceac6e3ccf39ba3294d0b396cceb43929bef2a57ff443695567567e0e40f8040642248a6c73016cd9a
+  metadata.gz: d2c55191253da220a9591c9f36afae09152c59a80125737cc0201324215e8fc37d7c5e71a7c6a97da6b8626bb14bb57a4fb09de410a78ec9bf04bc646df708ae
+  data.tar.gz: 924437a6b84adde5d9f787c065d4bbc5ece0bc89652171930ae3de39c5a3a92f81be69d0e2e7ee48f49ab15e2706f980c5f1ba3373b81f3ac60dc9b33d8387bd

data/README.md

@@ -1,13 +1,13 @@
 # Ajaxify Rails [![Build Status](https://secure.travis-ci.org/ncri/ajaxify_rails.png)](http://travis-ci.org/ncri/ajaxify_rails)
 
-No more full page reloads for your Rails app! Yay! 
+No more full page reloads for your Rails app! Yay!
 
 Automatically makes your app loading content in the background via Ajax.
 
-Works by turning all internal links into Ajax links that trigger an update of the page's content area. 
+Works by turning all internal links into Ajax links that trigger an update of the page's content area.
 Also form submissions are automatically turned into Ajax requests.
 
-Features: 
+Features:
 
 - Uses the html5 history interface for changing the url and making the browser's back and forward buttons work with Ajax.
 - Falls back to a hash based URL approach for browsers without the history interface (like Internet Explorer version <10).
@@ -47,7 +47,7 @@ In your application.js file add:
 
 Call `Ajaxify.init()` in your layout's javascript.
 Do this as early as possible to ensure Ajaxify's interchangeable url schemes (history api vs. hash based urls)
-work most effectively. 
+work most effectively.
 
 The later you call `init()`, the later potential redirects from one scheme to another are performed,
 which means the more unnecessary work the browser has to do.
@@ -63,14 +63,14 @@ If yield doesn't have a wrapper in your app yet, you need to supply one to get a
 
 You can set the content container of your app when initializing Ajaxify:
 
-    Ajaxify.init 
+    Ajaxify.init
       content_container: 'content_container_id'
 
 or later using `set_content_container`:
 
     Ajaxify.set_content_container('content_container_id')
-    
-    
+
+
 ### Loader Animation
 
 You probably like to have a loader image to be displayed to the user while content loads via Ajax.
@@ -100,14 +100,14 @@ Ajaxify correctly displays your flash messages after ajaxified requests.
 By default, only `flash[:notice]` is supported. If you are using for example `flash[:warning]` as well you have to add the flash_types
 option to the `Ajaxify.init()` call:
 
-    Ajaxify.init 
+    Ajaxify.init
       flash_types: ['notice', 'warning']
-    
+
 Also make sure that you supply invisible wrapper tags in your layout for each flash type you use, with the id set to the type, e.g.:
 
     #notice{ style: "#{'display:none' unless flash[:notice]}" }
-      = flash[:notice] 
-    
+      = flash[:notice]
+
 ### Full Page Reloads
 
 Sometimes requests change the layout of the page so significantly that loading only the main content via Ajax
@@ -122,7 +122,7 @@ For these cases you can turn off Ajaxify, by simply adding the class `no_ajaxify
 
 ### Root Redirects
 
-Sometimes you need to redirect on the root url. 
+Sometimes you need to redirect on the root url.
 
 For example you might have a localized application with the locale inside the url.
 When a user navigates to `your_domain.com` he/she gets redirected to e.g. `your_domain.com/en/`. This works fine in browsers supporting
@@ -175,6 +175,7 @@ Ajaxify provides a few jQuery events you can bind to:
 * `ajaxify:content_loaded` => Triggered after an ajaxify request finished successfully. Params: `data, status, jqXHR, url`.
 * `ajaxify:content_inserted` => Triggered after an ajaxify request finished but before extra content is stripped from the response.
 * `ajaxify:flash_displayed` => Triggered after a flash message is displayed. Parameters: `flash_type`.
+* `ajaxify:load_error` => Triggered if the ajaxify request goes wrong. Parameters: `data, status, jqXHR, url`.
 
 
 ### Javascript

data/lib/ajaxify_rails/version.rb

@@ -1,3 +1,3 @@
 module AjaxifyRails
-  VERSION = "0.9.2"
+  VERSION = "0.9.3"
 end

data/vendor/assets/javascripts/ajaxify_rails.js.coffee

@@ -143,6 +143,9 @@ load = (options, pop_state = false) ->
       success: (data, status, jqXHR) ->
         on_ajaxify_success data, status, jqXHR, pop_state, options
 
+      error: (data, status, jqXHR) ->
+        $(document).trigger('ajaxify:load_error', [data, status, jqXHR, options.url])
+
 
 # --------------------------------------------------------------------------------------------------------------------
 # private methods

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: ajaxify_rails
 version: !ruby/object:Gem::Version
-  version: 0.9.2
+  version: 0.9.3
 platform: ruby
 authors:
 - Nico Ritsche
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2013-10-23 00:00:00.000000000 Z
+date: 2013-10-31 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rails
@@ -243,7 +243,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 2.0.3
+rubygems_version: 2.1.10
 signing_key: 
 specification_version: 4
 summary: Rails gem for automatically turning internal links/forms into ajax links/forms