motion-kit 1.0.3 → 1.1.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 0809f323d3149b38020e0d4dbeef458c83bf936f
-  data.tar.gz: c610c4e21ad2de907bce51b884092266689cd340
+  metadata.gz: 7f25a8221661392838e777d1bc48bed110fd9857
+  data.tar.gz: 17f939c142298c5b5744bf688c1e93dab9f46ab9
 SHA512:
-  metadata.gz: d7a30089db1ea834657578e3ad013f8f9821151d326dc12fd878ec2b8fe44535eae0c7bacb994dee16abc68736a344212e23af49d33a2110f9d66da5d2357a94
-  data.tar.gz: 01fd1e8d1bd85bfca638bc339ae74f79868bbd26c2e09bb86831801b8039c20b611c4cf3bc736477dca66458963909c5473d5a424fc64d0a2aef2f1f9b7181d6
+  metadata.gz: b8f8534aaad7966740767eace569905f5213feacdfec9756b199014acdefe7802eddf11d101bc58f4f821452a8dd49ea518c98cce6ea99e094a22096d63e3f48
+  data.tar.gz: fc72309ba61213afd1040a94e8d392b4057ff64f8502128fe8165908f2a50fe93c91ffa55072802b8c1320c5d5799a6a7c05bca131a0ee7f5fc65d0486cc8a09

data/README.md

@@ -203,6 +203,31 @@ end
 ```
 
 
+### Dynamically adding views
+
+In MotionKit, it is easy to add views on the fly using the same API as used during layout. 
+```ruby
+def add_button style, button_title
+
+  context get(:inputs) do #Two very useful methods for accessing/modifying previously added views
+    add UIButton, :dynamic_button do 
+      title button_title
+      constraints do # if using autolayout
+        ...
+      end
+    end
+  end
+end
+```
+
+During layout, z-order is determined by the sequence in which views are added to the hierarchy. You can control this dynamically by supplying :behind, :in_front_of, or :z_index options
+```ruby
+add UIImageView, :highlight_square, behind: get(:dynamic_button)
+add UIImageView, :x_marks_the_spot, in_front_of: @selected_label 
+add UILabel, :subterranian_marker, z_index: 4 #becomes the 4th view in the subview hierarchy
+```
+
+
 ### Styles are compiled, simple, and clean
 
 In MotionKit, when you define a method that has the same name as a view

data/lib/motion-kit-ios/helpers/uiview_helpers.rb

@@ -11,8 +11,16 @@ module MotionKit
       view_class.alloc.initWithFrame(UIScreen.mainScreen.applicationFrame)
     end
 
-    def add_child(subview)
-      target.addSubview(subview)
+    def add_child(subview, options={})
+      if (sibling = options[:behind])
+        target.insertSubview(subview, belowSubview: sibling)
+      elsif (sibling = options[:in_front_of])
+        target.insertSubview(subview, aboveSubview: sibling)
+      elsif (z_index = options[:z_index])
+        target.insertSubview(subview, atIndex: z_index)
+      else
+        target.addSubview(subview)
+      end
     end
 
     def remove_child(subview)

data/lib/motion-kit/helpers/tree_layout.rb

@@ -215,7 +215,7 @@ module MotionKit
     # If there is no context, a default root view can be created if that has
     # been enabled (e.g. within the `layout` method).  The block is run in the
     # context of the new view.
-    def add(element, element_id=nil, &block)
+    def add(element, element_id=nil, options={}, &block)
       # make sure we have a target - raises NoContextError if none exists
       self.target
 
@@ -226,7 +226,7 @@ module MotionKit
       # We want to be sure that the element has a supeview or superlayer before
       # the style method is called.
       element = initialize_element(element, element_id)
-      self.apply(:add_child, element)
+      self.apply(:add_child, element, options)
       style_and_context(element, element_id, &block)
 
       element

data/lib/motion-kit/version.rb

@@ -1,3 +1,3 @@
 module MotionKit
-  VERSION = '1.0.3'
+  VERSION = '1.1.0'
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: motion-kit
 version: !ruby/object:Gem::Version
-  version: 1.0.3
+  version: 1.1.0
 platform: ruby
 authors:
 - Colin T.A. Gray