edit_mode 1.0.2 → 1.0.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: e991c6ba65550a2509c7893bbfd55d7a44851ecc
-  data.tar.gz: 0add910a65b79645005eded01a224d3dc893a604
+  metadata.gz: b8c8da9af88f71e7c611d676721fdc74bccd79b0
+  data.tar.gz: c890638b27883a0afd1d16d7b86d2ca3f71e5a4a
 SHA512:
-  metadata.gz: 631103c22235104b9eb1a383ab6f5d6e597b7c46127ad15396646aeceab7a45ec92aa3603e14cd1dea2c05efec4116237cede0bf9500bbfb79c5e66d83f53326
-  data.tar.gz: f74c522bca1d7074ac97b4e8f9b86fbf0755cd4454ee5da68d09fe42aa5a7f0d9f50e11957bfd4d6f479938d95fa5dcf776efef3bfaf2bcbc600d222a85ebbd3
+  metadata.gz: d32d9e17d1bae533428cde75ba6ffb10e3895faf5cede22bf2142a3fa18abc582f79253c7754ac062897b850b607f7cb21b4151b1dec67cca2b4da7c348799ad
+  data.tar.gz: 9a574ca2380631d544283ad97d22323e2288fc30fc126f959a4c88e4eac9947742d57afcca9e7346dcdcad248e0487a18cc891aa0b475c37fc016df2b0fc987f

data/Gemfile

@@ -34,4 +34,5 @@ gem 'coffee-rails'
 gem 'sqlite3', '>= 1.3.10'
 gem 'launchy'
 
-gem 'eventmachine', '>= 1.0.7'
+gem 'eventmachine', '>= 1.2.3'
+gem 'json', '>= 1.8.6'

data/Gemfile.lock

@@ -9,7 +9,7 @@ GIT
 PATH
   remote: .
   specs:
-    edit_mode (1.0.2)
+    edit_mode (1.0.3)
       jquery-rails
       jquery-turbolinks
       rails (>= 3.2)
@@ -65,7 +65,7 @@ GEM
     coffee-script-source (1.6.3)
     diff-lcs (1.1.3)
     erubis (2.7.0)
-    eventmachine (1.0.7)
+    eventmachine (1.2.3)
     execjs (2.0.2)
     faye-websocket (0.4.7)
       eventmachine (>= 0.12.0)
@@ -87,7 +87,7 @@ GEM
       turbolinks
     jquery-ui-rails (4.1.0)
       railties (>= 3.1.0)
-    json (1.8.1)
+    json (1.8.6)
     launchy (2.4.3)
       addressable (~> 2.3)
     libv8 (3.16.14.3)
@@ -170,8 +170,9 @@ GEM
     treetop (1.4.15)
       polyglot
       polyglot (>= 0.3.1)
-    turbolinks (2.5.3)
-      coffee-rails
+    turbolinks (5.0.1)
+      turbolinks-source (~> 5)
+    turbolinks-source (5.0.3)
     tzinfo (0.3.38)
     websocket (1.0.7)
     xpath (0.1.4)
@@ -185,12 +186,13 @@ DEPENDENCIES
   capybara (= 1.1.2)
   coffee-rails
   edit_mode!
-  eventmachine (>= 1.0.7)
+  eventmachine (>= 1.2.3)
   execjs
   guard (= 1.0.1)
   guard-rspec (= 0.5.5)
   jquery-rails (>= 2.2.0)
   jquery-ui-rails
+  json (>= 1.8.6)
   launchy
   nokogiri
   poltergeist
@@ -203,3 +205,6 @@ DEPENDENCIES
   sass-rails
   sqlite3 (>= 1.3.10)
   therubyracer
+
+BUNDLED WITH
+   1.15.2

data/lib/assets/javascripts/edit_mode/edit_mode_group.js.coffee

@@ -32,15 +32,15 @@ $( document ).on( "cancel", ".edit_mode_group", ->
 
     edit_mode_group = $( this )
     cancel_button = $( this ).find( ".cancel_button" )
-    
+
     # if there is a cancel button, animate it and then cancel all elements.
-    if cancel_button.size() > 0  
+    if cancel_button.length > 0
       button_effect( cancel_button, ->
         edit_mode_group.find( ".editable" ).trigger( "cancel" )
       )
-      
+
     # if no cancel button exists, just trigger each element's cancel event.
-    else  
+    else
       edit_mode_group.find( ".editable" ).trigger( "cancel" )
 
 )

data/lib/assets/javascripts/edit_mode/make_modal.js.coffee

@@ -5,7 +5,7 @@
 # If the user clicks on the shaded (grey) area outside, the edit_mode_group is saved.
 
 $( document ).on( "edit", ".edit_mode_group", ->
-  if $( document ).find( ".edit-mode-modal" ).size() == 0
+  if $( document ).find( ".edit-mode-modal" ).length == 0
     #unless $( this ).hasClass( "edit-mode-modal" )
     modal_edit_mode_group = $( this )
     $( this ).addClass( "edit-mode-modal" )

data/lib/edit_mode/version.rb

@@ -1,3 +1,3 @@
 module EditMode
-  VERSION = "1.0.2"
+  VERSION = "1.0.3"
 end

data/test_app/README.md

@@ -0,0 +1 @@
+../README.md

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: edit_mode
 version: !ruby/object:Gem::Version
-  version: 1.0.2
+  version: 1.0.3
 platform: ruby
 authors:
 - Sebastian Fiedlschuster
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2015-06-09 00:00:00.000000000 Z
+date: 2017-07-24 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rails
@@ -236,7 +236,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 2.4.5
+rubygems_version: 2.5.1
 signing_key: 
 specification_version: 4
 summary: Toggle an edit mode on a show view. Think of it as a grouped in-place editing.

data/test_app/README.md

@@ -1,170 +0,0 @@
-# EditMode  [![Build Status](https://secure.travis-ci.org/fiedl/edit_mode.png?branch=master)](http://travis-ci.org/fiedl/edit_mode)
-
-<img src="https://github.com/fiedl/edit_mode/raw/master/test_app/app/assets/images/screenshot.png" height="300" align="right" vspace="20" hspace="20" />
-
-*edit_mode* is a *ruby on rails gem* that allows you to toggle an edit mode on a normal show view.
-Think of it as a grouped in-place editing.
-This also toggles [best_in_place](https://github.com/bernat/best_in_place) fields.
-
-The edit mode is activated by pressing an 'edit' button on a show view. This shows additional editing tools
-and switches on the best_in_place form fields. When editing is finished, use 'save' or 'cancel' buttons to
-quit the edit mode and return to a normal show view.
-Several editing groups per page are supported. Thus, you can have several 'boxes' to edit on a page.
-
-## Demo
-
-You might want to have a look at [this demo app at heroku](http://edit-mode-test-app.herokuapp.com/).
-
-The [code of this demo app can be found here](https://github.com/fiedl/edit_mode/tree/master/test_app).
-
-## Installation
-
-Add this line to your application's Gemfile:
-
-    gem 'edit_mode'
-
-And then execute:
-
-    $ bundle
-
-Or install it yourself as:
-
-    $ gem install edit_mode
-
-### Include Assets
-
-In `app/assets/javascripts/application.js`, add:
-
-```javascript
-//= require jquery.turbolinks
-//= require edit_mode
-```
-
-If you experience trouble with javascript, check the correct loading order from [the jquery.turbolinks README](https://github.com/kossnocorp/jquery.turbolinks#usage).
-
-In `app/assets/stylesheets/application.css`, add:
-
-```css
-/*
- *...
- *= require edit_mode
- */
-```
-
-## Usage
-
-### Basic View
-
-For a basic example, see: https://github.com/fiedl/edit_mode/blob/master/test_app/app/views/users/show.html.erb
-
-### edit_mode_group
-
-The edit mode is toggled within a `<span class="edit_mode_group"></span>`. The buttons to 'edit', 'save' and 'cancel' should also be placed inside this span.
-
-You can also have several edit_mode_group spans on a page, as shown in the demo app.
-
-### Tool Buttons
-
-To enter and exit the edit mode, use buttons 'edit', 'save' and 'cancel'. These can be anchors, images, et cetera. They only have to have the correct css classes:
-
-```html
-<span class="edit_mode_group">
-  <a class="edit_button" href="#">edit</a>
-  <a class="save_button" href="#">save</a>
-  <a class="cancel_button" href="#">cancel</a>
-  ...
-</span>
-```
-
-### show_only_in_edit_mode
-
-Within the edit_mode_group span, you may place certain elements that should only be shown when in edit mode. You can use this for 'add' buttons or 'destroy' buttons.
-
-```html
-<span class="edit_mode_group">
-  ...
-  <span class="show_only_in_edit_mode">
-    <a href="#">add</a>
-  </span>
-</span>
-```
-
-The same, the other way round:
-
-```html
-<span class="edit_mode_group">
-  ...
-  <span class="do_not_show_in_edit_mode">
-    <img src="..." alt="This picture is not shown in edit mode." />
-  </span>
-</span>
-```
-
-### best_in_place
-
-In the edit_mode_group span, all [best_in_place](https://github.com/bernat/best_in_place) elements are toggled as well.
-
-### '.editable' Triggers
-
-If you need custom behaviour inside the edit_mode_group span, you can use these triggers: For all elements of the class `.editable`, the events `edit`, `save` and `cancel` are triggered, when entering or exiting edit mode.
-
-```html
-<span class="edit_mode_group">
-  ...
-  <span class="editable custom_element">Test</span>
-</span>
-```
-
-Bind the event via JavaScript, e.g. with jQuery:
-
-```coffee
-jQuery ->
-  $( ".custom_element" ).bind( "edit", ->
-    alert( "This element has just entered edit mode." )
-  )
-```
-
-### Adding .editable Elements Using Ajax
-
-If you would like to add .editable elements (e.g. `.best_in_place` elements or `.show_only_in_edit_mode` elements) using
-ajax, you have to call `apply_edit_mode()` on the newly added elements in order to have them provide the proper methods
-and triggers.
-
-For example, if you have added a `<span id="my_new_edit_mode_span">...</span>` containing
-the edit_mode elements using ajax, just call via javascript (jQuery):
-
-```javascript
-$( "#my_new_edit_mode_span" ).apply_edit_mode()
-```
-
-And if you want to enter edit_mode for this span, call instead:
-
-```javascript
-$( "#my_new_edit_mode_span" ).apply_edit_mode().trigger( "edit" )
-```
-
-### Deactivating the Modal
-
-If you do not want the edit mode span to get modal when entering the edit mode, have a look at [the solution to issue #2](https://github.com/fiedl/edit_mode/issues/2).
-
-## Documentation
-
-http://rubydoc.info/github/fiedl/edit_mode/frames
-
-## Demo App
-
-* http://edit-mode-test-app.herokuapp.com/
-* https://github.com/fiedl/edit_mode/tree/master/test_app
-* Add heroku remote to git: http://stackoverflow.com/questions/5129598
-  * `brew install heroku-toolbelt`
-  * `heroku keys:add`
-  * `heroku git:remote -a edit-mode-test-app`
-* Push test app to heroku: `git subtree push --prefix test_app heroku master` or `git push heroku \`git subtree split --prefix test_app master\`:master --force` ([SO](http://stackoverflow.com/a/10648623/2066546))
-
-## Contributing
-
-1. Fork it
-2. Create your feature branch (`git checkout -b my-new-feature`)
-3. Commit your changes (`git commit -am 'Added some feature'`)
-4. Push to the branch (`git push origin my-new-feature`)
-5. Create new Pull Request