rm-extensions 0.1.0 → 0.1.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 9492c875dd1cedac32f756c747a6bb1dec24f2ac
-  data.tar.gz: 3f98058ac2b7e195413706d586332a135ad72bad
+  metadata.gz: bbafb71f1715936049bc7a87a9fb2806e31069a2
+  data.tar.gz: 6d65f8db493d1c0a58c60ff46969256795c5d3c2
 SHA512:
-  metadata.gz: fafe79e35d321d4999b7ebbd2a5c11addc69a42f9b74d28ab087a9ba9cb59fed73c23ae38ec6b31152dee1b4dba62da70f71d342cd8fc7259616da004c4b2db9
-  data.tar.gz: 6a8071578eabf1f8c7404c920812693cf137b26ca4c02c1fe00f34f8d6f5750bb69b49a5aa54d4cabefaf66f4474bb750cace04cbaf54d89743a486f8999661a
+  metadata.gz: 91c0e8421e4e203d3bdcd3c13f49fcb92cff53ece8ab9f28751b496f1badb2d08b81e3f7a64b37520d6d0ec3ed56f9247259e351b1d205b6ab61f5974ef5f8f2
+  data.tar.gz: 523156ea087b13f2eea0796bf931c2f07a031519c0de8af6fe805e8f1cbd81b2b8bcb5ee5754e10bb8e78177884315d5d9abffbd34a8246930c153ff36f1494c

data/README.md

@@ -16,13 +16,13 @@ class MyViewController < UIViewController
       rmext_observe(@model, "name") do |val|
         p "name is #{val}"
       end
-      foo.on(:some_event) do |val|
+      foo.rmext_on(:some_event) do |val|
         p "some_event called with #{val.inspect}"
       end
     end
   end
   def test_trigger
-    foo.trigger(:some_event, "hello!")
+    foo.rmext_trigger(:some_event, "hello!")
   end
 end
 ```
@@ -30,17 +30,16 @@ end
 Differences from BW::KVO and BW::Reactor::Eventable:
 
 - No need to include a module in the class you wish to use it on
-- The default is to observe and immediately fire the supplied callback
-- The callback only takes one argument, the new value
-- the object observing is not retained, and when it is deallocated, the observation
-  will be removed automatically for you. there is typically no need to clean up
-  and unobserve in viewWillDisappear, or similar.
-- the observation actually happens on a proxy object
+- the observation happens on a proxy object
+- KVO: The default is to observe and immediately fire the supplied callback
+- KVO: The callback only takes one argument, the new value
+- KVO: the object observing is not retained, and when it is deallocated, the observation
+  will be removed automatically for you. there is typically no need to clean up manually
 
 
 ## Accessors
 
-#### weak attr_accessors when you need to avoid retain-cycles:
+#### weak attr_accessors:
 
 ```ruby
 
@@ -53,7 +52,6 @@ class MyViewController < UIViewController
     super.tap do
       v = MyView.alloc.initWithFrame(CGRectZero)
       view.addSubview(v)
-      # if delegate was a normal attr_accessor, this controller could never be deallocated
       v.delegate = self
     end
   end
@@ -61,24 +59,6 @@ end
 
 ```
 
-## Deallocation
-
-#### watch for an object to deallocate, and execute a callback:
-
-```ruby
-def add_view_controller
-  controller = UIViewController.alloc.init
-  controller.rmext_on_dealloc(&test_dealloc_proc)
-  navigationController.pushViewController(controller, animated: true)
-end
-
-def test_dealloc_proc
-  proc { |x| p "it deallocated!" }
-end
-
-# now you can verify the controller gets deallocated by calling #add_view_controller
-# and then popping it off the navigationController
-```
 ## Queues
 
 #### Wraps GCD:

data/lib/rm-extensions/version.rb

@@ -1,3 +1,3 @@
 module RMExtensions
-  VERSION = "0.1.0"
+  VERSION = "0.1.1"
 end

data/lib/rm-extensions.rb

@@ -8,7 +8,6 @@ Motion::Project::App.setup do |app|
   %w(
     util
     accessors
-    deallocation
     observation
     queues
   ).reverse.each do |x|

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: rm-extensions
 version: !ruby/object:Gem::Version
-  version: 0.1.0
+  version: 0.1.1
 platform: ruby
 authors:
 - Joe Noon
@@ -23,7 +23,6 @@ files:
 - README.md
 - Rakefile
 - lib/motion/accessors.rb
-- lib/motion/deallocation.rb
 - lib/motion/observation.rb
 - lib/motion/queues.rb
 - lib/motion/util.rb

data/lib/motion/deallocation.rb

@@ -1,56 +0,0 @@
-module RMExtensions
-
-  module ObjectExtensions
-
-    module Deallocation
-
-      # perform a block before +self+ will dealloc.
-      # the block given should have one argument, the object about to be deallocated.
-      def rmext_on_dealloc(&block)
-        internalObject = ::RMExtensions::OnDeallocInternalObject.create("#{self.class.name}:#{object_id}", self, block)
-        @rmext_on_dealloc_blocks ||= {}
-        @rmext_on_dealloc_blocks[internalObject] = internalObject
-        nil
-      end
-      
-      # removes a previously added block from the deallocation callback list
-      def rmext_cancel_on_dealloc(block)
-        @rmext_on_dealloc_blocks ||= {}
-        if internalObject = @rmext_on_dealloc_blocks[block]
-          internalObject.block = nil
-          @rmext_on_dealloc_blocks.delete(block)
-        end
-        nil
-      end
-
-    end
-
-  end
-
-  # Used internally by +rmext_on_dealloc+.  The idea is this object is added to the
-  # object we want to watch for deallocation.  When the object we want to watch
-  # is about to dealloc, this object will dealloc first, so we can execute the block.
-  # the object it follows is kept only as a weak reference to not create
-  # a retain cycle.
-  class OnDeallocInternalObject
-    attr_accessor :description, :block
-    rmext_weak_attr_accessor :obj
-    def self.create(description, obj, block)
-      x = new
-      x.description = description
-      x.obj = obj
-      x.block = block
-      x
-    end
-    def dealloc
-      # p "dealloc OnDeallocInternalObject #{description}"
-      if block
-        block.call(obj)
-        self.block = nil
-      end
-      super
-    end
-  end
-
-end
-Object.send(:include, ::RMExtensions::ObjectExtensions::Deallocation)