giga-safe-tool 0.0.1

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: 006b9486d891b55fd52e25f8e735d1955ac7b44cd62ee12c380ccd6bd2155b50
+  data.tar.gz: 96909fdb0c260fb557c01c03791484006b0c248087bafaef2d1edb16b7716f51
+SHA512:
+  metadata.gz: 202fec7a0f75c16bc2d5bafd1422df38c42585a149a0eeea4869cdf50ab945ea92595b918150177f9530b1f7ea7488b2520f66e1ad439ed171d861a5b8eeef9d
+  data.tar.gz: 9edfc04bc63de7de22f0ea3bcc8ce856066de695c10e050b12c99d73c10c78ab9611b02f8fafca792ca4c75cb55124c2a28f3f790597a48922f57a526546309b

data/cocoon-1.2.15/Gemfile

@@ -0,0 +1,33 @@
+source "http://rubygems.org"
+
+
+group :development, :test do
+  gem "rails", "~> 4.2"
+  gem "sqlite3", '1.3.13'
+  gem "json_pure"
+  gem "jeweler", git: 'git@github.com:technicalpickles/jeweler'
+  # gem "jeweler", "~> 2.3"
+  gem "rspec-rails", "~> 3.0.0"
+  gem "rspec",       "~> 3.0.0"
+  gem "actionpack",  ">=4.0.0"
+  gem "simplecov", :require => false
+  gem "rake", "~> 10.1"
+
+  gem 'nokogiri'
+
+  gem "generator_spec"
+
+  platforms :rbx do
+    gem 'rubysl'
+    gem 'rubysl-test-unit'
+    gem 'psych', '~> 2.2'
+    gem 'racc'
+    gem 'rubinius-developer_tools'
+  end
+
+end
+
+
+# To use debugger (ruby-debug for Ruby 1.8.7+, ruby-debug19 for Ruby 1.9.2+)
+# gem 'ruby-debug'
+# gem 'ruby-debug19'

data/cocoon-1.2.15/History.md

@@ -0,0 +1,197 @@
+# Change History / Release Notes
+
+## Version 1.2.6
+
+* added some explicit documentation we use haml. Fixed the formtastic example.
+* "unfreeze" frozen objects. Fixes #193.
+* IE8 jquery fix (thanks @niuage).
+* merged #191 which fixes an issue with a monkeypatched CGI. For more info, see
+  ticket #191. Thanks gsmendoza.
+
+## Version 1.2.5
+
+* fix gem dependencies: we added gems to allow building for rubinius, but those are only
+  needed when developing
+
+## Version 1.2.4
+
+* the wrapper class is now configurable. Before it was assumed to be `nested-fields`.
+  Now it is configurable by handing. See #180. Thanks Yoav Matchulsky.
+* fix build on travis-ci for rubinius (thanks brixen).
+
+## Version 1.2.3
+
+* add license info
+
+## Version 1.2.2
+
+* added option to add multiple items on one click. See #175.
+* cleaned up javascript code. See #171.
+
+
+## Version 1.2.1
+
+* added a `:form_name` parameter (fixes #153) which allows to use a self-chosen
+  parameter in the nested views. Up until now `f` was assumed (and enforced).
+* improvement of creation of the objects on the association (thanks to Dirk von Grünigen). This
+  alleviates the need for the `:force_non_association_create` option in most cases.
+  That option is for now still kept.
+* after validation errors, already deleted (but not saved) nested elements, will remain deleted
+  (e.g. the state is remembered, and they remain hidden, and will be correctly deleted on next
+  succesfull save) (fixes #136).
+
+## Version 1.2.0
+
+* support for rails 4.0
+
+## Version 1.1.2
+
+* pull #118 (thanks @ahmozkya): remove the deprecated `.live` function, and use `.on` instead.
+  Note: at least jquery 1.7 is required now!
+
+## Version 1.1.1
+
+* added the to be added/deleted element to the event, this allows to add animations/actions onto them
+* added extra option :wrap_object, allowing to use Decorators instead of the association object
+* added an option :force_non_association_create, that will allow to use `link_to_add_association` inside the fields-partial
+
+## Version 1.1.0
+
+* BREAKING: the triggered javascript events `removal-callback`, `after-removal-callback`, and `insertion-callback` are renamed to the more correct and symmetric
+  `cocoon:after-insert, cocoon:before-insert, cocoon:after-remove, cocoon:before-remove`. Also the events are namespaced to prevent collisions with other libraries.
+* allow created objects to be decorated with a callable. This is especially useful if you are using Draper or some decorator instead of the plain model in your views.
+* it is now possible to specify a relative node, and use standard jquery traversal methods on insertion
+* trigger insertion event on correct `insertionNode`
+* thanks to #90 cocoon now supports non-AR associations and array-fields, you just have to supply your own `build_<association>` methods
+
+I would really really like to thank all contributors, check them out https://github.com/nathanvda/cocoon/graphs/contributors
+They made cocoon way more awesome than I could have done in my lonesome.
+
+## Version 1.0.22
+
+* Fix that it still works for mongoid
+
+## Version 1.0.21
+
+* Use association build methods instead of assoc.klass.new. This avoids mass-assignment errors and other misbehaviors around attribute accessibility.
+
+
+## Version 1.0.20
+
+* improved handing of the `:partial`: remove the extra options-hash, and just make it use the single hash, so now we can just write
+
+     = link_to_add_association 'add something', f, :tasks, :partial => 'shared/task_fields'
+     = link_to_add_association 'add something', f, :tasks, :class => 'your-special-class', :partial => 'shared/task_fields'
+
+
+## Version 1.0.19
+
+* pull #53 (@CuriousCurmudgeon): fixed some bugs introduced in previous version (ooooops! Thanks!!!)
+
+## Version 1.0.18
+
+* pull in #51 (@erwin): adding an `after-removal-callback` in javascript, very useful if you want to recalculate e.g. total-items or indexes
+* pull in #42 (@zacstewart): allow to hand extra `:locals` to the partial
+* updated documentation
+
+## Version 1.0.17
+
+* fix: make sure that cocoon still works for rails 3.0, where the `conditions` is not available yet
+
+## Version 1.0.16
+
+* merged pull request #33 (@fl00r): added the a custom partial option! genius :)
+  Also the creation of the nested objects takes any available conditions into account.
+  Now you can write
+
+     = link_to_add_association 'add something', f, :tasks, {}, :partial => 'shared/task_fields'
+
+## Version 1.0.15
+
+* added `data-association-insertion-method` that gives more control over where to insert the new nested fields.
+  It takes a jquery method as parameter that inserts the new data. `before`, `after`, `append`, `prepend`, etc. Default: `before`.
+* `data-association-insertion-position` is still available and acts as an alias. Probably this will be deprecated in the future.
+
+
+## Version 1.0.14
+
+* When playing with `simple_form` and `twitter-bootstrap`, I noticed it is crucial that I call the correct nested-fields function.
+  That is: `fields_for` for standard forms, `semantic_fields_for` in formtastic and `simple_fields_for` for simple_form.
+  Secondly, this was not enough, I needed to be able to hand down options to that method. So in the `link_to_add_association` method you
+  can now an extra option `:render_options` and that hash will be handed to the association-builder.
+
+  This allows the nested fields to be built correctly with `simple_form` for `twitter-bootstrap`.
+
+## Version 1.0.13
+
+* A while ago we added the option to add a javascript callback on inserting a new associated object, I now made sure we can add a callback on insertion
+  and on removal of a new item. One example where this was useful for me is visible in the demo project `cocoon_simple_form_demo` where I implemented a
+  `belongs_to` relation, and either select from a list, or add a new element.
+  So: the callback-mechanism has changed, and now the callback is bound to the parent container, instead of the link itself. This is because we can also
+  bind the removal callback there (as the removal link is inserted in the html dynamically).
+
+  For more info, see the `README`.
+
+## Version 1.0.12
+
+* using "this" in `association-insertion-node` is now possible
+
+If you are using rails < 3.1, you should run
+
+    rails g cocoon:install
+
+to install the new `cocoon.js` to your `public/javascripts` folder.
+
+
+## Version 1.0.11
+
+
+## Version 1.0.10
+
+* Fuck! Built the gem with 1.9.2 again. Built the gem again with 1.8.7.
+
+## Version 1.0.9
+
+* is now rails 3.1 compatible. If you are not using Rails 3.1 yet, this should have no effect.
+  For rails 3.1 the cocoon.js no longer needs to be installed using the `rails g cocoon:install`. It is
+  automatically used from the gem.
+
+## Version 1.0.8
+
+* Loosened the gem dependencies.
+
+## Version 1.0.7 (20/06/2011)
+
+Apparently, the gem 1.0.6 which was generated with ruby 1.9.2 gave the following error upon install:
+
+      uninitialized constant Psych::Syck (NameError)
+
+This is related to this bug: http://rubyforge.org/tracker/?group_id=126&atid=575&func=detail&aid=29163
+
+This should be fixed in the next release of rubygems, the fix should be to build the gem with ruby 1.8.7.
+Let's hope this works.
+
+## Version 1.0.6 (19/06/2011)
+
+* The javascript has been improved to consistently use `e.preventDefault` instead of returning false.
+
+Run
+
+    rails g cocoon:install
+
+to copy the new `cocoon.js` to your `public/javascripts` folder.
+
+
+## Version 1.0.5 (17/06/2011)
+
+* This release make sure that the `link_to_add_association` generates a correctly clickable
+  link in the newer rails 3 versions as well. In rails 3.0.8. the html was double escaped.
+
+If you are upgrading from 1.0.4, you just have to update the gem. No other actions needed. If you are updating
+from earlier versions, it is safer to do
+
+    rails g cocoon:install
+
+This will copy the new `cocoon.js` files to your `public/javascripts` folder.
+
+

data/cocoon-1.2.15/LICENSE

@@ -0,0 +1,20 @@
+Copyright 2011 Nathan Van der Auwera
+
+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.