More Related Content Similar to Robotlegs AS3 from Flash and the City 2010 (20) Robotlegs AS3 from Flash and the City 20102. Me
Joel Hooks
Robotlegs Enthusiast
on the web
www.joelhooks.com
@jhooks
email
joelhooks@gmail.com
4. Not to mention...
Till Schneidereit
SwiftSuspenders Maestro
find him
http://www.tillschneidereit.de/
@tschneidereit
5. Contributors
Robert Penner @robPenner
Jonnie Hallman @DestroyToday
Sean Hess @seanhess
Craig Wickesser @codecraig
and so many others have contributed to the community
through support, ideas, and examples...
7. What’s in it for me?
do you need a
a pure Actionscript 3 micro-architecture
for flash, flex and air?
8. What’s in it for me?
are you using a framework but feel sad about...
9. What’s in it for me?
are you using a framework but feel sad about...
casting
10. What’s in it for me?
are you using a framework but feel sad about...
casting
Singletons
11. What’s in it for me?
are you using a framework but feel sad about...
casting
Singletons
service locators
12. What’s in it for me?
are you using a framework but feel sad about...
casting
Singletons
service locators
display list event bus
13. What’s in it for me?
do you want a better mechanism for...
14. What’s in it for me?
do you want a better mechanism for...
wiring your objects together
15. What’s in it for me?
do you want a better mechanism for...
wiring your objects together
managing dependencies
16. What’s in it for me?
do you want a better mechanism for...
wiring your objects together
managing dependencies
managing events
17. What’s in it for me?
do you want a better mechanism for...
wiring your objects together
managing dependencies
managing events
structured MVC
19. Robotlegs is...
a pure Actionscript 3 micro-architecture
robotlegs has no Flex framework dependencies.
22. Robotlegs is...
a mechanism for wiring objects together
focused solely on this limited scope
23. Robotlegs is...
a mechanism for wiring objects together
focused solely on this limited scope
by providing kickass tools to get your job done
30. Why Robotlegs?
MVC+S reference implementation
a little prescription goes a long way...
31. Why Robotlegs?
MVC+S reference implementation
a little prescription goes a long way...
but...
33. Why Robotlegs?
whatever you need it to be
highly extensible to support YOUR workflow and style
34. Why Robotlegs?
whatever you need it to be
highly extensible to support YOUR workflow and style
MVCS provides documentation and common ground for teams...
38. Why Robotlegs?
objects communicate via native events
custom events with strongly typed properties
39. Why Robotlegs?
objects communicate via native events
custom events with strongly typed properties
or maybe you prefer AS3-Signals?
41. Why Robotlegs?
fully unit tested
because your project is important.
42. Why Robotlegs?
stable
strict semantic versioning
http://semver.org/
44. Why Robotlegs?
knowledge.robotlegs.org
Community supported through Tender
49. Robotlegs in Action
Flickr Image Gallery Demo*
*part of the Robotlegs Demo Bundle available here: http://github.com/robotlegs/robotlegs-demos-Bundle
53. Context
Context initializes the framework
55. Context
Context provides an event bus
57. Context
not limited to a single Context
58. Context
not limited to a single Context
multiple Contexts for modular development
59. Context
not limited to a single Context
multiple Contexts for modular development
thereʼs a utility for that...
60. Actor
Actor is the base class for
Model and Service classes
62. Actor
eventDispatcher is injected
into Actor
63. Actor
Actor provides a dispatch(event) method
64. Actor
Actor is for your convenience
65. Model
Models extend Actor
66. Model
Models provide an API for data
68. Model
Models sit between application data
and other actors
69. Model
Models should not
listen for framework events
70. Model
Models dispatch framework events
75. Service
Services can parse results
from external services
76. Service
Services can parse results
from external services
foreign data should be converted at the first opportunity
78. Service
Services do not store data
79. Service
Services do not store data
data is stored on a Model
80. Service
Services do not
receive framework events
81. Service
Services dispatch framework events
83. View
the View is represented by your
view components and their Mediators
90. View
Mediators listen for framework events
92. View
Mediators dispatch framework events
94. View
view components are not coupled to
their Mediators
95. View
view components are not coupled to
their Mediators
or any other framework class
96. View
view components are not coupled to
their Mediators
or any other framework class
period.
97. View
Mediators are coupled to their
view components
98. View
Mediators can access
Service and Model classes directly
99. View
Mediators can access
Service and Model classes directly
but this will couple the Mediator to the Actor
102. Controller
Commands are executed in response
to framework events
105. Controller
Commands are stateless
they execute and die
106. Controller
Commands are stateless
they execute and die
performing a single unit of work
108. Controller
Commands perform work on
Service and Model classes
109. Controller
Commands perform work on
Service and Model classes
and occasionally Mediators
112. Controller
Commands receive data from the
events that trigger them
114. Controller
Commands dispatch framework events
118. Controller
Commands do not receive framework events
outside of the event that triggers them
which is available for injection