motion-wiretap 1.0.0 → 1.1.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 446d7bb23634641466df4e37ffa85daaac5fdc8c
-  data.tar.gz: f7b9033df4a62d4f235b47f4d5f39e1efa0bac11
+  metadata.gz: 32d229b7cac40b4cc57a4ebd635fbd3769f8b502
+  data.tar.gz: 91cb977786be3bb50c5285085f832168af3f342c
 SHA512:
-  metadata.gz: 17981158a67d7424e538351070ac732a7591e364c515882e176f83156f6ad850d5922bbf0754cdc1a704e089f15a15fbc676c9b58b02c381d48dc76cf8f8ed34
-  data.tar.gz: 196a340c6afe69833db31d76f51751ede875d75d38e6e9b294fde372031a5c2de60dc17b689174dd7aea6fe07ca8d53186b9dbf192bde535b99d36fb4893fa1d
+  metadata.gz: f404b0770e2afdce819edc814eb07e8a878301f96515e2c3f74298a2b98d0cf1f5e12466609e2bde5330cdcc420be69df543456b6c3624429021ca1d45955ec8
+  data.tar.gz: 9df22ce3307342f031eeb643e760bfbb36be72046f6d2eca6218fad50f6d3c2c365d69f96d3e242dca81ab22713e0ce8ebc85e7c2d041486f1b2401f3923448f

data/README.md

@@ -32,10 +32,12 @@ Open these side by side to see the comparison:
 Usage
 -----
 
-Creating a wiretap is done using the factory method `Motion.wiretap()`.
+Creating a wiretap is done using the factory method `Motion.wiretap()`, also
+aliased as `MW()`.
 
 ```ruby
-@wiretap = Motion.wiretap(obj, :property)
+@wiretap = Motion.wiretap(obj, :property)  # this object will notify listeners everytime obj.property changes
+@wiretap = MW(obj, :property)
 ```
 
 If you want to use a more literate style, you can include the
@@ -52,29 +54,29 @@ notifications or control events.
 
 ### Let's start with something practical!
 
-This first example will use `motion-wiretap-polluting` methods, because that's
-my preferred aesthetic style, but the rest of this document will focus on the
-non-polluting version.
+In these examples I will use all three ways of creating a Wiretap
+(`MW(), Motion.wiretap(), object.wiretap`).
 
 ```ruby
 # assign the label to the text view; changes to the text view will be reflected
 # on the label.
-@label.wiretap(:text).bind_to(@text_view.wiretap(:text))
+MW(@label, :text).bind_to(MW(@text_view, :text))
 
 # assign the attributedText of the label to the text view, doing some
-# highlighting in-between
+# highlighting in-between.
 @label.wiretap(:attributedText).bind_to(@text_view.wiretap(:text).map do |text|
   NSAttributedString.alloc.initWithString(text, attributes: { NSForegroundColorAttributeName => UIColor.blueColor })
 end)
 
-# bind the `enabled` property to check on whether `username_field.text` and
-# `password_field.text` are blank
-@login_button.wiretap(:enabled).bind_to(
-  [
-    @username_field.wiretap(:text),
-    @password_field.wiretap(:text),
-  ].wiretap.combine do |username, password|
-    username && username.length > 0 && password && password.length > 0
+# This code will set the 'enabled' property depending on whether the username
+# and password are not empty.
+Motion.wiretap(@login_button, :enabled).bind_to(
+  Motion.wiretap([
+    Motion.wiretap(@username_field, :text),
+    Motion.wiretap(@password_field, :text),
+  ]).combine do |username, password|
+    # use motion-support to get the 'present?' method
+    username.present? && password.present?
   end
   )
 ```
@@ -82,11 +84,11 @@ end)
 ### Types of wiretaps
 
 - Key-Value Observation / KVO
-- Arrays (map/reduce)
+- Arrays (map/reduce/combine)
 - Jobs (event stream, completion)
-- NSNotificationCenter
 - UIView Gestures
 - UIControl events
+- NSNotificationCenter (needs specs)
 
 ### Key-Value Observation
 
@@ -94,7 +96,6 @@ end)
 class Person
   attr_accessor :name
   attr_accessor :email
-  attr_accessor :address
 end
 
 # listen for changes
@@ -129,7 +130,7 @@ person_1.name
 # => "BOB"
 
 # bind the property of one object to the value of another, but change it using `map`
-wiretap = Motion.wiretap(person_1, :name).bind_to(person_2.wiretap(:name).map { |value| value.upcase })
+wiretap = Motion.wiretap(person_1, :name).bind_to(Motion.wiretap(person_2, :name).map { |value| value.upcase })
 person_2.name = 'Bob'
 person_1.name # => "BOB"
 ```

data/lib/motion-wiretap/all/signal.rb

@@ -6,10 +6,9 @@ module MotionWiretap
   class Signal < Wiretap
     attr :value
 
-    def initialize(value=nil)
-      super()
+    def initialize(value=nil, &block)
       @value = value
-      trigger_changed(@value)
+      super(&block)
     end
 
     def next(value)
@@ -25,6 +24,13 @@ module MotionWiretap
       trigger_error(error)
     end
 
+    # The Signal class always sends an initial value
+    def listen(wiretap=nil, &block)
+      super
+      trigger_changed(@value)
+      return self
+    end
+
   end
 
 end

data/lib/motion-wiretap/all/wiretap.rb

@@ -1,3 +1,7 @@
+def MW(*args, &block)
+  Motion.wiretap(*args, &block)
+end
+
 module MotionWiretap
 
   class Wiretap

data/lib/motion-wiretap/ios/wiretap_ios.rb

@@ -4,10 +4,6 @@ module MotionWiretap
 
   class WiretapView < WiretapTarget
 
-    def dummy
-      UIButton.new.enabled = true
-    end
-
     def on(recognizer, options=nil, &block)
       if recognizer
         case recognizer

data/lib/motion-wiretap/version.rb

@@ -1,3 +1,3 @@
 module MotionWiretap
-  VERSION = '1.0.0'
+  VERSION = '1.1.0'
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: motion-wiretap
 version: !ruby/object:Gem::Version
-  version: 1.0.0
+  version: 1.1.0
 platform: ruby
 authors:
 - Colin T.A. Gray
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2014-02-28 00:00:00.000000000 Z
+date: 2014-03-04 00:00:00.000000000 Z
 dependencies: []
 description: |
   ReactiveCocoa is an amazing system, and RubyMotion could benefit from the