Alias motion_require to require_relative
Fix assorted file/path handling bugs

1. Add to app.files by union, to avoid duplicates in file list.
2. Prefix relative files with ./ to match RubyMotion build system.
3. Preserve relative/absolute-ness when generating path of required file.
Merge pull request #1 from kastiglione/path-handling-fix

Fix assorted file/path handling bugs
Fix regexp for matching for relative files

The regexp was looking for ./ and ../ but not /.
Merge pull request #3 from kastiglione/path-handling-fix

Fix regexp for matching for relative files
Merge pull request #2 from kastiglione/require_relative

Alias motion_require to require_relative
refactor Motion::Project::Config patch into a separate file
add specs
Merge branch 'master' of https://github.com/clayallsopp/motion-require
fixes #4
version++
Make `require_relative` opt-in via Motion::Require.require_relative_enabled
Merge pull request #5 from kastiglione/opt-in-require-relative

Make `require_relative` opt-in via Motion::Require.require_relative_enabled
Scan project file list by default

This emoves the need to specify which files are scanned. With this change, the
following two invocations do the same:

Motion::Require.all(Dir.glob('app/**/*.rb'))
Motion::Require.all
Update readme for require_relative
Merge pull request #6 from kastiglione/default-all

Use RubyMotion's default project file
Fix typo
Raise LoadError for unresolved require's

Prior to this change, RubyMotion's toolchain would report the error like so:

    ERROR! Can't resolve dependency `app/file3.rb'

With this change, the error message is more helpful:

    ERROR! In `./app/file1.rb', could not require `file3', file not found.

However, with this change, a stack trace is printed in the later case while
none is printed in the former.
Merge pull request #7 from kastiglione/raise-load-error-for-missing-files

Raise LoadError for unresolved require's
veresion++