bubble-wrap 1.0.0 → 1.1.0

data/.gitignore

@@ -1,6 +1,5 @@
 .rake_tasks~
 pkg/*
-Gemfile.lock
 build/
 .DS_Store
 .repl_history

data/.yardopts

@@ -0,0 +1,2 @@
+lib/**/*.rb
+motion/**/*.rb

data/CHANGELOG.md

@@ -1,3 +1,18 @@
+## 1.1.0
+
+[Commit history](https://github.com/rubymotion/BubbleWrap/compare/1.0...1.1])
+* Added `BubbleWrap::Reactor`,  a simplified implementation of the Event Machine API on top of GCD.
+* Added upload support to the HTTP wrapper.
+* Added `BubbleWrap.create_uuid` to generate a uuid string.
+* Added a program progress proc option to the HTTP wrapper.
+* Added a RSS parser.
+* Added a camera wrapper.
+* Split the various wrappers in self contained and requirable libraries.
+* Added a wrapper around the location/gps APIs.
+* Added a merge method to the persistence layer so multiple values can
+  be saved at once.
+* Added a way to create `UIColor` instances using a hex string: `'#FF8A19'.to_color` or color keyword: `'blue'.to_color`, `'dark_gray'.to_color`.
+
 ## 1.0.0
 
 * Improved the integration with RubyMotion build system.

data/Gemfile

@@ -1,4 +1,4 @@
 source 'https://rubygems.org'
 
 # Specify your gem's dependencies in bubble-wrap.gemspec
-gemspec
+gemspec

data/Gemfile.lock

@@ -0,0 +1,24 @@
+PATH
+  remote: .
+  specs:
+    bubble-wrap (1.1.0)
+
+GEM
+  remote: https://rubygems.org/
+  specs:
+    bacon (1.1.0)
+    metaclass (0.0.1)
+    mocha (0.12.0)
+      metaclass (~> 0.0.1)
+    mocha-on-bacon (0.2.0)
+      mocha (>= 0.9.8)
+    rake (0.9.2.2)
+
+PLATFORMS
+  ruby
+
+DEPENDENCIES
+  bacon
+  bubble-wrap!
+  mocha-on-bacon
+  rake

data/HACKING.md

@@ -20,7 +20,7 @@ require 'bubble-wrap'
 When `bubble-wrap` is required it immediately requires `bubble-wrap/loader` which sets up the infrastructure needed to manipulate the `Rakefile` build process.  Once that is done we can freely call
 
 ```ruby
-BubbleWrap.require 'motion/core**/*.rb'
+BubbleWrap.require 'motion/core/**/*.rb'
 ```
 
 `BubbleWrap.require` (or simply `BW.require`) is used to include
@@ -36,7 +36,7 @@ of `BW::Requirement` and thus has access to all it's class methods.
 The most common use cases are setting file dependencies:
 
 ```ruby
-BW.require('motion/core**/*.rb') do
+BW.require('motion/core/**/*.rb') do
   file('motion/core/device/screen.rb').depends_on 'motion/core/device.rb'
 end
 ```

data/README.md

@@ -13,16 +13,16 @@ gem install bubble-wrap
 
 ## Setup
 
-1. Edit the `Rakefile` of your RubyMotion project and add the following require line.
+1. Edit the `Rakefile` of your RubyMotion project and add the following require line:
 
 ```ruby
 require 'bubble-wrap'
 ```
 
 BubbleWrap is split into multiple modules so that you can easily choose which parts
-are included at compile-time. 
+are included at compile-time.
 
-The above example requires all the wrappers/helpers. If you wish to only
+The above example requires the `core` and `http` modules. If you wish to only
 include the core modules use the following line of code instead:
 
 ```ruby
@@ -35,6 +35,42 @@ If you wish to only include the `HTTP` wrapper:
 require 'bubble-wrap/http'
 ```
 
+If you wish to only include the `RSS Parser` wrapper:
+
+```ruby
+require 'bubble-wrap/rss_parser'
+```
+
+If you wish to only include the `Reactor` wrapper:
+
+```ruby
+require 'bubble-wrap/reactor'
+```
+
+If you wish to only include the UI-related wrappers:
+
+```ruby
+require 'bubble-wrap/ui'
+```
+
+If you wish to only include the `Camera` wrapper:
+
+```ruby
+require 'bubble-wrap/camera'
+```
+
+If you wish to only include the `Location` wrapper:
+
+```ruby
+require 'bubble-wrap/location'
+```
+
+If you want to include everything (ie kitchen sink mode) you can save time and do:
+
+```ruby
+require 'bubble-wrap/all'
+```
+
 
 Note: **DON'T** use `app.files =` in your Rakefile to set up your files once you've required BubbleWrap.
 Make sure to append onto the array or use `+=`.
@@ -56,6 +92,44 @@ use the versioned gem.
 
 ## Core
 
+### Misc
+
+UUID generator:
+```ruby
+BubbleWrap.create_uuid
+=> "68ED21DB-82E5-4A56-ABEB-73650C0DB701"
+```
+
+Localization (using `NSBundle.mainBundle.localizedStringForKey`):
+```ruby
+BubbleWrap.localized_string(:foo, 'fallback')
+=> "fallback"
+```
+
+Color conversion:
+```ruby
+BubbleWrap.rgba_color(23, 45, 12, 0.4)
+=> #<UIDeviceRGBColor:0x6db6ed0>
+BubbleWrap.rgb_color(23, 45, 12)
+=> #<UIDeviceRGBColor:0x8ca88b0>
+'blue'.to_color
+=> #<UICachedDeviceRGBColor:0xda535c0>
+'dark_gray'.to_color
+=> #<UICachedDeviceWhiteColor:0x8bb5be0>
+'#FF8A19'.to_color
+=> #<UIDeviceRGBColor:0x8d54110>
+```
+
+Debug flag:
+```ruby
+BubbleWrap.debug?
+=> false
+BubbleWrap.debug = true
+=> true
+BubbleWrap.debug?
+=> true
+```
+
 ### App
 
 A module with useful methods related to the running application
@@ -73,6 +147,8 @@ A module with useful methods related to the running application
 # creates and shows an alert message.
 > App.run_after(0.5) {  p "It's #{Time.now}"   }
 # Runs the block after 0.5 seconds.
+> App.open_url("http://matt.aimonetti.net")
+# Opens the url using the device's browser. (accepts a string url or an instance of `NSURL`.
 > App::Persistence['channels'] # application specific persistence storage
 # ['NBC', 'ABC', 'Fox', 'CBS', 'PBS']
 > App::Persistence['channels'] = ['TF1', 'France 2', 'France 3']
@@ -94,6 +170,7 @@ Other available methods:
 A collection of useful methods about the current device:
 
 Examples:
+
 ```ruby
 > Device.iphone?
 # true
@@ -119,23 +196,26 @@ Examples:
 # 320
 ```
 
-### Gestures
+### Camera
 
-Extra methods on `UIView` for working with gesture recognizers. A gesture recognizer can be added using a normal Ruby block, like so:
+Added interface for better camera access:
 
 ```ruby
-    view.whenTapped do
-      UIView.animateWithDuration(1,
-        animations:lambda {
-          # animate
-          # @view.transform = ...
-        })
-    end
-```
-
-There are similar methods for pinched, rotated, swiped, panned, and pressed (for long presses). All of the methods return the actual recognizer object, so it is possible to set the delegate if more fine-grained control is needed.
+# Uses the front camera
+BW::Device.camera.front.picture(media_types: [:movie, :image]) do |result|
+  image_view = UIImageView.alloc.initWithImage(result[:original_image])
+end
 
+# Uses the rear camera
+BW::Device.camera.rear.picture(media_types: [:movie, :image]) do |result|
+  image_view = UIImageView.alloc.initWithImage(result[:original_image])
+end
 
+# Uses the photo library
+BW::Device.camera.any.picture(media_types: [:movie, :image]) do |result|
+  image_view = UIImageView.alloc.initWithImage(result[:original_image])
+end
+```
 
 ### JSON
 
@@ -248,21 +328,51 @@ iso8601 formatted string into a Time instance.
 => 2012-05-31 21:41:33 +0200
 ```
 
-### UIControl / UIButton
+## Location
 
-Helper methods to give `UIButton` a Ruby-like interface. Ex:
+Added interface for Ruby-like GPS access:
 
 ```ruby
-button.when(UIControlEventTouchUpInside) do
-  self.view.backgroundColor = UIColor.redColor
+BW::Location.get do |result|
+  p "From Lat #{result[:from].latitude}, Long #{result[:from].longitude}"
+  p "To Lat #{result[:to].latitude}, Long #{result[:to].longitude}"
 end
 ```
 
+Also available is `BW::Location.get_significant`, for monitoring significant location changes.
+
+## UI
+
+### Gestures
+
+Extra methods on `UIView` for working with gesture recognizers. A gesture recognizer can be added using a normal Ruby block, like so:
+
+```ruby
+    view.whenTapped do
+      UIView.animateWithDuration(1,
+        animations:lambda {
+          # animate
+          # @view.transform = ...
+        })
+    end
+```
+
+There are similar methods for pinched, rotated, swiped, panned, and pressed (for long presses). All of the methods return the actual recognizer object, so it is possible to set the delegate if more fine-grained control is needed.
+
 ### UIViewController
 
 A custom method was added to `UIViewController` to return the content
 frame of a view controller.
 
+### UIControl / UIButton
+
+Helper methods to give `UIButton` a Ruby-like interface. Ex:
+
+```ruby
+button.when(UIControlEventTouchUpInside) do
+  self.view.backgroundColor = UIColor.redColor
+end
+```
 
 ## HTTP
 
@@ -295,16 +405,248 @@ BubbleWrap::HTTP.post("http://foo.bar.com/", {payload: data}) do |response|
     json = BubbleWrap::JSON.parse(response.body.to_str)
     p json['id']
   elsif response.status_code.to_s =~ /40\d/
-    alert("Login failed") # helper provided by the kernel file in this repo.
+    App.alert("Login failed")
   else
-    alert(response.error_message)
+    App.alert(response.error_message)
   end
 end
 ```
 
+A `:download_progress` option can also be passed. The expected object
+would be a Proc that takes two arguments: a float representing the
+amount of data currently received and another float representing the
+total amount of data expected.
+
+
+## RSS Parser
+**Since: > version 1.0.0**
+
+The RSS Parser provides an easy interface to consume RSS feeds in an
+asynchronous (non blocking) way.
+
+
+```ruby
+feed_parser = BW::RSSParser.new("http://feeds2.feedburner.com/sdrbpodcast")
+feed_parser.parse do |item|
+  # called asynchronously as items get parsed
+  p item.title
+end
+```
+
+The yielded RSS item is of type `RSSParser::RSSItem` and has the
+following attributes:
+
+* title
+* description
+* link
+* guid
+* pubDate
+* enclosure
+
+The item can be converted into a hash by calling `to_hash` on it.
+
+### Delegate
+**Since: > version 1.0.0**
+
+You can also designate a delegate to the parser and implement change
+state callbacks:
+
+```ruby
+feed_parser = BW::RSSParser.new("http://feeds.feedburner.com/sdrbpodcast")
+feed_parser.delegate = self
+feed.parse do |item|
+  p item.title
+end
+
+# Delegate method
+def when_parser_initializes
+  p "The parser is ready!"
+end
+
+def when_parser_parses
+  p "The parser started parsing the document"
+end
+
+def when_parser_is_done
+  p "The feed is entirely parsed, congratulations!"
+end
+```
+
+These delegate methods are optional, however, you might find the
+`when_parser_is_done` callback useful if you collected all the items and
+want to process all at once for instance.
+
+### Parsing a remote content or actual data
+
+You have the choice to initialize a parser instance with a string
+representing an URL, an instance of `NSURL` or my specifying that the
+passed param is some data to parse directly.
+
+```ruby
+# string representing an url:
+feed_parser = BW::RSSParser.new("http://feeds2.feedburner.com/sdrbpodcast")
+# a NSURL instance:
+url =  NSURL.alloc.initWithString("http://matt.aimonetti.net/atom.xml")
+feed_parser = BW::RSSParser.new(url)
+# Some data
+feed = File.read('atom.xml')
+feed_parser = BW::RSSParser.new(feed, true)
+```
+
+
+## Reactor
+**Since: > version 1.0.0**
+
+`BubbleWrap::Reactor` is a simplified, mostly complete implementation of
+the [Event Machine](http://rubyeventmachine.com/) API.  In fact 
+`BubbleWrap::Reactor` is aliased to `EM` in the runtime environment.
+
+### Deferables
+
+BubbleWrap provides both a `Deferrable` mixin and a `DefaultDeferrable`
+class, which simply mixes in deferrable behaviour if you don't want to
+implement your own.
 
+A deferrable is an object with four states: unknown, successful, failure
+and timeout.  When you initially create a deferrable it is in an unknown
+state, however you can assign callbacks to be run when the object
+changes to either successful or failure state.
+
+#### Success
+
+```ruby
+> d = EM::DefaultDeferrable.new
+=> #<BubbleWrap::Reactor::DefaultDeferrable:0x6d859a0>
+> d.callback { |what| puts "Great #{what}!" }
+=> [#<Proc:0x6d8a1e0>]
+> d.succeed "justice"
+Great justice!
+=> nil
+```
+
+#### Failure
+
+```ruby
+> d = EM::DefaultDeferrable.new
+=> #<BubbleWrap::Reactor::DefaultDeferrable:0x8bf3ee0>
+> d.errback { |what| puts "Great #{what}!" }
+=> [#<Proc:0x8bf3ef0>]
+> d.fail "sadness"
+Great sadness!
+=> nil
+```
+
+#### Timeout
+
+```ruby
+> d = EM::DefaultDeferrable.new
+=> #<BubbleWrap::Reactor::DefaultDeferrable:0x8bf5910>
+> d.errback { puts "Great scott!" }
+=> [#<Proc:0x8bf6350>]
+> d.timeout 2
+=> #<BubbleWrap::Reactor::Timer:0x6d920a0 @timer=#<__NSCFTimer:0x6d91990>>
+# wait...
+> Great scott!
+```
+
+### Timers
+
+*All timers can be cancelled using `EM.cancel_timer`.*
+
+#### One-shot timers
+
+```ruby
+> EM.add_timer 1.0 do
+>   puts "Great scott!"
+> end
+=> 146335904
+> Great scott!
+```
+
+#### Periodic timers
+
+```ruby
+> count = 0
+=> 0
+> timer = EM.add_periodic_timer 1.0 do
+>   count = count + 1
+>   puts "Great scott!"
+>   (count < 10) || EM.cancel_timer(timer)
+> end
+=> 146046832
+> Great scott!
+Great scott!
+Great scott!
+Great scott!
+Great scott!
+Great scott!
+Great scott!
+Great scott!
+Great scott!
+Great scott!
+```
+
+### Scheduling operations
+
+You can use `EM.schedule` to schedule blocks to be executed 
+asynchronously.  BubbleWrap deviates from the EventMachine
+API here in that it also provides `EM.schedule_on_main` which
+makes sure that the task is run asynchronously, but on the 
+application's main thread - this is necessary if you are 
+updating the user interface.
+
+```ruby
+> EM.schedule { puts Thread.current.object_id }
+146027920
+=> nil
+> EM.schedule_on_main { puts Thread.current.object_id }
+112222480
+=> nil
+```
+
+### Deferrable operations
+
+You can also use `EM.defer` in much the same way as `EM.schedule`
+with one important difference, you can pass in a second `proc` 
+which will be called when the first has completed, and be passed
+it's result as an argument. Just like `EM.schedule`, `EM.defer`
+also has an `EM.defer_on_main` version.
+
+```ruby
+> operation = proc { 99 }
+=> #<Proc:0x6d763c0>
+> callback = proc { |speed| puts speed >= 99 ? "Time travel!" : "Conventional travel!" }
+=> #<Proc:0x8bd3910>
+> EM.defer(operation, callback)
+=> nil
+Time travel!
+```
+
+### Events
+
+Although not part of the EventMachine API, BubbleWrap provides
+an `Eventable` mixin for use instrumenting objects with simple
+event triggering behaviour. `BubbleWrap::Reactor` uses this
+behind the scenes in several places, and as it's a very handy
+idiom it is available as a public API.
+
+```ruby
+> o = Class.new { include EM::Eventable }.new
+=> #<#<Class:0x6dc1310>:0x6dc2ec0>
+> o.on(:november_5_1955) { puts "Ow!" }
+=> [#<Proc:0x6dc6300>]
+> o.on(:november_5_1955) { puts "Flux capacitor!" }
+=> [#<Proc:0x6dc6300>, #<Proc:0x6dc1ba0>]
+> o.trigger(:november_5_1955)
+Ow!
+Flux capacitor!
+=> [nil, nil]
+```
+
+# Suggestions?
 
 Do you have a suggestion for a specific wrapper? Feel free to open an
 issue/ticket and tell us about what you are after. If you have a
 wrapper/helper you are using and are thinking that others might enjoy,
 please send a pull request (with tests if possible).
+