@atomicobject http://spin.atomicobject.com
A Tour of RubyMotion
• Implementation of Ruby
• Similar object model to Objective C, natural language for
the platform
• UNIX Ethos
• Very Flexible
Slide 3
Slide 3 text
No content
Slide 4
Slide 4 text
No content
Slide 5
Slide 5 text
No content
Slide 6
Slide 6 text
From our app
directory, we can run
our app in the
simulator with a
simple command.
Slide 7
Slide 7 text
From-scratch implementation of Ruby.
Started by apple in 2007.
@atomicobject http://spin.atomicobject.com
Garbage Collection
(Sort of. Auto-release and retain, similar to ARC.)
Slide 11
Slide 11 text
No content
Slide 12
Slide 12 text
No content
Slide 13
Slide 13 text
No content
Slide 14
Slide 14 text
(App idea shamelessly ripped off from HipByte.)
Slide 15
Slide 15 text
No content
Slide 16
Slide 16 text
No content
Slide 17
Slide 17 text
No content
Slide 18
Slide 18 text
No content
Slide 19
Slide 19 text
No content
Slide 20
Slide 20 text
No content
Slide 21
Slide 21 text
@atomicobject http://spin.atomicobject.com
Ruby
Slide 22
Slide 22 text
No content
Slide 23
Slide 23 text
Classes and methods; no header files; rest arguments.
What you don’t see in the usual case is the flexibility of Ruby.
Slide 24
Slide 24 text
Method invocation syntax.
Slide 25
Slide 25 text
Keyword args: added to RubyMotion for Obj-C compatibility,
now standard in Ruby 2.0.
Slide 26
Slide 26 text
do is syntax for blocks. Very similar to Objective C blocks
parent= is just a method assumed to exist on el. Aliases to
setParent if el is an Objective C object.
Slide 27
Slide 27 text
These features of ruby make it great for creating internal DSLs.
Why create separate parsers for incomplete languages when your
primary language is so flexible?
Slide 28
Slide 28 text
Unlike most languages, there are no contexts where you can’t put code.
For example, within a class definition, you can do whatever you want.
Slide 29
Slide 29 text
For example, we could put a print statement in our class def.
Slide 30
Slide 30 text
No content
Slide 31
Slide 31 text
No content
Slide 32
Slide 32 text
This is how you’d normally write it.
Slide 33
Slide 33 text
Checking of valid objects in ActiveRecord
validates is a method on class objects inheriting from ActiveRecord::Base
Slide 34
Slide 34 text
@atomicobject http://spin.atomicobject.com
Rake
Slide 35
Slide 35 text
No content
Slide 36
Slide 36 text
No content
Slide 37
Slide 37 text
No content
Slide 38
Slide 38 text
No content
Slide 39
Slide 39 text
No content
Slide 40
Slide 40 text
No content
Slide 41
Slide 41 text
No content
Slide 42
Slide 42 text
No content
Slide 43
Slide 43 text
No content
Slide 44
Slide 44 text
No content
Slide 45
Slide 45 text
No content
Slide 46
Slide 46 text
No content
Slide 47
Slide 47 text
No content
Slide 48
Slide 48 text
No content
Slide 49
Slide 49 text
No content
Slide 50
Slide 50 text
No content
Slide 51
Slide 51 text
No content
Slide 52
Slide 52 text
No content
Slide 53
Slide 53 text
No content
Slide 54
Slide 54 text
No content
Slide 55
Slide 55 text
No content
Slide 56
Slide 56 text
@atomicobject http://spin.atomicobject.com
Specs
Slide 57
Slide 57 text
No content
Slide 58
Slide 58 text
No content
Slide 59
Slide 59 text
No content
Slide 60
Slide 60 text
No content
Slide 61
Slide 61 text
@atomicobject http://spin.atomicobject.com
REPL
Slide 62
Slide 62 text
No content
Slide 63
Slide 63 text
Now, if we hold command and click on an
element, the context of our REPL changes to
the clicked element. Right now our REPL says
(main), meaning we haven’t clicked an element.
Slide 64
Slide 64 text
If we command-click our text-box, we see
UILabel:0xf975. Now “self” refers to that element.
Slide 65
Slide 65 text
So we can set self.backgroundColor to see it change to red.
Or we can tweak frame size to get the positioning just right.
Slide 66
Slide 66 text
@atomicobject http://spin.atomicobject.com
What about
Objective-C?