RubyMotion forces a certain background-radiation of schizophrenia due to the fact that it's build tools run using the system ruby via Rake. BubbleWrap manipulates the build environment in order to make it possible to include itself (and other code) into the build process from outside the project hierarchy.
This is where RubyGems goes looking for code when you call
bubble-wrap is required it immediately requires
which sets up the infrastructure needed to manipulate the
Rakefile build process.
Once that is done we can freely call
BubbleWrap.require (or simply
BW.require) is used to include
library code into the Rake build process used by RubyMotion.
BW.require is similar to ruby's standard
require method with
two major changes:
If a block is passed to
BW.require it is evaluated in the context
BW::Requirement and thus has access to all it's class methods.
The most common use cases are setting file dependencies:
BW.require('motion/core/**/*.rb') do file('motion/core/device/screen.rb').depends_on 'motion/core/device.rb' end
and specifying frameworks that need to be included at build time:
BW.require('motion/**/*.rb') do file('motion/address_book.rb').uses_framework 'Addressbook' end
motion directory you'll see the actual implementation code
which is compiled into RubyMotion projects that are using BubbleWrap.
motion/corecontains "core" extension, things that the developers reasonably think should be included in every BubbleWrap using project. Careful consideration should be taken when making changes to the contents and test coverage (in
spec/core) must be updated to match. This can be included in your project by requiring
bubble-wrap/corein your project
motion/httpcontains the "http" extension. This can be included by requiring
bubble-wrap/httpin your project
motion/test_suite_delegatecontains a simple
AppDelegatewhich can be used to enable the
rake specto run when developing a BubbleWrap gem. Using
require 'bubble-wrap/test'will include it in the build process and also configure the app delegate to point to
TestSuiteDelegate. See the BubbleWrap gem guide for more information.
If you think that your project would be of interest to the large number of RubyMotion users that use BubbleWrap in their daily development then feel free to fork the repository on GitHub and send us a pull request.
You should place your implementation files in a subdirectory of
motion/my_awesome_project), your tests in a subdirectory of
spec/my_awesome_project) and you can create a require file in
lib/bubble-wrap for example
require 'bubble-wrap/loader' BW.require 'motion/my_awesome_project.rb'
People will then be able to use it by adding:
to their project's
The developers wish to thank you so much for taking the time to improve BubbleWrap and by extension the RubyMotion ecosystem. You're awesome!