The Ruby Gems
Gemfile for the project:
source :rubygems gem 'bubble-wrap' gem 'cocoapods' gem 'motion-cocoapods' gem 'motion-testflight' gem 'ib'
There were not a lot of extra Ruby gems needed to put this together. The most useful were bubble-wrap, with its simplification of many things in the iOS Framework, and ib, which allowed me to use Interface Builder to layout the UI.
The other gems are fairly self explanatory. cocoapods and motion-cocoapods allowed me to choose from many existing Obj-C libraries and avoid re-inventing the wheel. motion-testflight made it easy to upload test builds for beta testers to try builds of the app during development. If you haven’t had a chance to try out TestFlight, you should definitely check it out.
Including the Ruby Gems
Using Bundler made it easy to manage the dependencies. After creating the
Gemfile and making sure that Bundler was installed,
gem install bundler, I just needed to download and install all the Ruby gems with a
bundle install. I could also update the gems to the latest version with a
bundle update. It should be noted that you can specify versions of gems in the
Gemfile and you will probably want to do this to avoid getting updated gems that break something or change things underneath you.
To include the gems in the project, I just had to add a couple of lines to the
$:.unshift('/Library/RubyMotion/lib') require 'motion/project' require 'bundler' Bundler.require ...
Not all Rubygems will work for Rubymotion. There is no
require functionality in Rubymotion, so you will need to find gems that have been built to work with Rubymotion.
There are a lot existing open source Obj-C libraries out there that can be included in iOS projects. Fortunately, we can also leverage many of those via Cocoapods, which aims to be the package manager for Obj-C projects (think Bundler). Normally, you would have a
Podfile, but for Rubymotion projects with the
motion-cocoapod gem, you add your Pod dependencies to your
... app.pods do pod 'ViewDeck' pod 'QuickDialog' pod 'JSONKit' pod 'CMPopTipView' pod 'ShareKit/Facebook' pod 'ShareKit/Twitter' end ...
Much like Bundler, you can specify specific versions to avoid the pods getting updated beneath you. The Pods are installed into your project
vendor/Pods directory where you can look through all the source when you need.
Here is how each Pod was used:
- ViewDeck: slide out a view from the left or right, similar to Facebook or Path apps. Used to make navigating and searching questions easier.
- QuickDialog: made the settings form slightly easier to build. Documentation is weak and you will need to be comfortable spelunking.
- JSONKit: even though
bubble-wraphas helpers for parsing JSON, it relies on iOS 5 features. If your project needs to support iOS 4.3+, you will need to use something like JSONKit.
- CMPopTipView: A nice little tooltip library to make the tutorial and show off features when some first installs the app.
- ShareKit: A swiss army knife of sharing content to a number of sites. I only needed Facebook and Twitter, but there are a bunch more that can be used.
Adding new Pods, it may sometimes appear that the Pod isn’t available or working. I found that because some Pods affect the project
.pch file, it is sometimes neccessary to
rake clean to get things working again.
It is easy enough to leverage the growing number of Rubymotion gems and Obj-C iOS libraries. The challenge can be finding them so that you don’t re-invent the wheel.