motion-objc-runtime 0.0.1 → 0.0.3
Sign up to get free protection for your applications and to get access to all the features.
- data/README.md +9 -8
- data/lib/motion-objc-runtime.rb +3 -1
- data/motion-objc-runtime.gemspec +6 -5
- metadata +6 -5
data/README.md
CHANGED
@@ -1,13 +1,14 @@
|
|
1
1
|
# motion-objc-runtime
|
2
2
|
|
3
|
-
motion-objc-runtime
|
4
|
-
|
5
|
-
|
6
|
-
|
7
|
-
|
8
|
-
|
9
|
-
|
10
|
-
|
3
|
+
motion-objc-runtime exposes the Objective-C runtime API. This allows
|
4
|
+
RubyMotion access building blocks necessary to provide the
|
5
|
+
metaprogramming capabilities currently lacking in RubyMotion. By
|
6
|
+
exposing the ObjC runtime, `define_method` and other metaprogramming
|
7
|
+
staples can be enabled for RubyMotion apps.
|
8
|
+
|
9
|
+
The Objective-C runtime is exposed the same way RubyMotion exposes C
|
10
|
+
functions from UIKit and other iOS frameworks, via BrideSupport files
|
11
|
+
created by the `gen_bridge_metadata` command.
|
11
12
|
|
12
13
|
## Installation
|
13
14
|
|
data/lib/motion-objc-runtime.rb
CHANGED
@@ -42,7 +42,9 @@ class << Motion::Project::App
|
|
42
42
|
real_setup.call(&block)
|
43
43
|
generate_bridgesupport(config.variables)
|
44
44
|
configs.each_value do |app|
|
45
|
-
app.bridgesupport_files
|
45
|
+
unless app.bridgesupport_files.include? BRIDGESUPPORT_FILE
|
46
|
+
app.bridgesupport_files << BRIDGESUPPORT_FILE
|
47
|
+
end
|
46
48
|
end
|
47
49
|
end
|
48
50
|
end
|
data/motion-objc-runtime.gemspec
CHANGED
@@ -3,7 +3,7 @@ Gem::Specification.new do |gem|
|
|
3
3
|
gem.name = 'motion-objc-runtime'
|
4
4
|
gem.description = 'Exposes Objective-C runtime in RubyMotion'
|
5
5
|
gem.homepage = "https://github.com/kastiglione/#{gem.name}"
|
6
|
-
gem.version = '0.0.
|
6
|
+
gem.version = '0.0.3'
|
7
7
|
|
8
8
|
gem.authors = ['Dave Lee']
|
9
9
|
gem.email = ['dave@kastiglione.com']
|
@@ -12,9 +12,10 @@ Gem::Specification.new do |gem|
|
|
12
12
|
gem.require_paths = ['lib']
|
13
13
|
|
14
14
|
gem.summary = <<-END.gsub(/^ +/, '')
|
15
|
-
motion-objc-runtime
|
16
|
-
|
17
|
-
|
18
|
-
|
15
|
+
motion-objc-runtime exposes the Objective-C runtime API. This
|
16
|
+
allows RubyMotion access building blocks necessary to provide the
|
17
|
+
metaprogramming capabilities currently lacking in RubyMotion. By
|
18
|
+
exposing the ObjC runtime, #define_method and other
|
19
|
+
metaprogramming staples can be enabled for RubyMotion apps.
|
19
20
|
END
|
20
21
|
end
|
metadata
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: motion-objc-runtime
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 0.0.
|
4
|
+
version: 0.0.3
|
5
5
|
prerelease:
|
6
6
|
platform: ruby
|
7
7
|
authors:
|
@@ -9,7 +9,7 @@ authors:
|
|
9
9
|
autorequire:
|
10
10
|
bindir: bin
|
11
11
|
cert_chain: []
|
12
|
-
date: 2012-07-
|
12
|
+
date: 2012-07-30 00:00:00.000000000 Z
|
13
13
|
dependencies: []
|
14
14
|
description: Exposes Objective-C runtime in RubyMotion
|
15
15
|
email:
|
@@ -47,7 +47,8 @@ rubyforge_project:
|
|
47
47
|
rubygems_version: 1.8.24
|
48
48
|
signing_key:
|
49
49
|
specification_version: 3
|
50
|
-
summary: ! 'motion-objc-runtime
|
51
|
-
|
52
|
-
|
50
|
+
summary: ! 'motion-objc-runtime exposes the Objective-C runtime API. This allows RubyMotion
|
51
|
+
access building blocks necessary to provide the metaprogramming capabilities currently
|
52
|
+
lacking in RubyMotion. By exposing the ObjC runtime, #define_method and other metaprogramming
|
53
|
+
staples can be enabled for RubyMotion apps.'
|
53
54
|
test_files: []
|