Introduction to Robotlegs 2

robotlegs

robotlegs 2.0

the goals

configurable because every project is unique

versatile rigidity sucks

conciseuse only what you need

fluentmake(tea).with(milk).butNot(sugar)

govt health warningthese examples are subject to change

the features

.context builder

Contexts in robotlegs circa v1

Contexts in robotlegs circa v1public class Context{ protected var _injector:IInjector; protected var _reflector:IReflector; protected var _contextView:DisplayObjectContainer; protected var _commandMap:ICommandMap; protected var _mediatorMap:IMediatorMap; protected var _viewMap:IViewMap;}

public class Container{ private var youCantSeeMe:SoLetsHopeIKnowWhatImDoing; protected var sureYouCanOverrideMe:ButYouAintGettingRidOfMe;}

public class Container{ private var youCantSeeMe:SoLetsHopeIKnowWhatImDoing; protected var sureYouCanOverrideMe:ButYouAintGettingRidOfMe;}in version one,features were bound to the context.

RL2 contexts are created with what you need not extended with what you don’t

Introducing the context builder

Introducing the context builderpublic interface IContextBuilder{ build():IContext; withBundle(bundle:IContextBuilderBundle):IContextBuilder; withConfig(config:IContextConfig):IContextBuilder; withContextView(value:DisplayObjectContainer):IContextBuilder; withDispatcher(value:IEventDispatcher):IContextBuilder; withExtension(extension:IContextExtension):IContextBuilder; withInjector(value:Injector):IContextBuilder; withParent(value:IContext):IContextBuilder; withProcessor(processor:IContextProcessor):IContextBuilder;}

.withConfig

.withConfigpublic interface IContextConfig{ function configure(context:IContext):void;}setup your configuration to execute once at build.

.withExtension

.withExtensionpublic interface IContextExtension{ function initialize(context:IContext):void; function install(context:IContext):void; function uninstall(context:IContext):void;}extensions add functionality at any time.

.withProcessor

.withProcessorpublic interface IContextProcessor{ function process(context:IContext, callback:Function):void;}processors asynchronously affect the build state.

.pre-configured bundles

four tasty flavours of robotlegs each representing a context builder bundle

Original»when plain old vanilla is just right.

light» when size and performance are paramount.

rapid»when time is of the essence.

» smart viewswhen you simply can’t live without view injection.

.type matching

Definion

Definionpublic class TypeMatcher{ function anyOf(... params):TypeMatcher; function noneOf(... params):TypeMatcher; function allOf(... params):TypeMatcher;}Usagenew TypeMatcher() .allOf(ISpaceShip, IEnemy) .noneOf(DeathStar)flexible and fluent type matching syntax

.view management

viewManager.addContainer(contextView); viewManager.addHandler(mediatorMap); viewManager.addWatcher(stageWatcher); viewManager.addContainer(myPopUp); wire view handlers to view watchers

viewManager.addContainer(contextView); viewManager.addHandler(mediatorMap); viewManager.addWatcher(stageWatcher); viewManager.addContainer(myPopUp); wire view handlers to view watchers viewManager.addContainer(myPopUp); viewManager.addContainer(myAIRWindow); native support for flex popups and air windows.

.mediate anything

mediatorMap.map(UserDetailsMediator).toView(IUserDetailsAware); map mediators to interfaces rather than concrete classes.

mediatorMap.map(UserDetailsMediator).toView(IUserDetailsAware); map mediators to interfaces rather than concrete classes.mediatorMap .map(SomeMenuMediator) .toMatcher() .anyOf(TopLevelMenu, AdminMenu, FootMenu);use type-matching to refine your mapping

.guards and hooks

possible use-cases for a guard:

possible use-cases for a guard:• prevent mediation when ...

possible use-cases for a guard:• prevent mediation when ...• prevent command execution when ...

possible use-cases for a guard:• prevent mediation when ...• prevent command execution when ...mediatorMap .map(UserDetailsMediator) .toView(IUserDetailsAware) .withGuard(UserIsAdminGuard);a guard represents conditional logic for anaction to occur.

scenarios for using a hook:

scenarios for using a hook:• customised logging

scenarios for using a hook:• customised logging• view skinning

scenarios for using a hook:• customised logging• view skinning• view localisation

scenarios for using a hook:• customised logging• view skinning• view localisation• instance configuration prior to command execution

scenarios for using a hook:• customised logging• view skinning• view localisation• instance configuration prior to command executioncommandMap .map(UserLoginCommand) .toEvent(UserLoginEvent.LOGIN, UserLoginEvent) .withHook(ConfigureUserDetails)

scenarios for using a hook:• customised logging• view skinning• view localisation• instance configuration prior to command executioncommandMap .map(UserLoginCommand) .toEvent(UserLoginEvent.LOGIN, UserLoginEvent) .withHook(ConfigureUserDetails)a hook enables pre-processing on an action.

.rule sets and command flow

possible uses of a rule:

possible uses of a rule:• adding or removing mediators

possible uses of a rule:• adding or removing mediators• loading or unloading commands

possible uses of a rule:• adding or removing mediators• loading or unloading commandsa rule can prevent or ensure an action’s occurrence.

command flows:

command flows:create a workflow of commands to represent acomplex sequence

command flows:create a workflow of commands to represent acomplex sequenceflows are pathways between commands

.swift-suspenders integration

//creates a new instance per injectioninjector.map(SomeType); //or injector.map(SomeType, ‘named’);//create new instance per injection and map toinjector.map(IService).toType(SomeService); //or value .toValue(someInstance)//map as singleton instanceinjector.map(SomeService).asSingleton(); //or .toSingleton(SomeService);//allows to easily specify custom providers to use for a mappinginjector.map(IService).toProvider(new CustomProvider());//prevents sharing the mapping with child injectors;injector.map(SomeService).local(); // .shared() reverts it//allow child injector to map if none existsinjector.map(SomeService).soft(); // .strong() maps regardless//prevents changes to the mapping; returns a unique key objectinjector.map(SomeService).seal(); //can revert with key and .unseal()full integration with swift suspenders 2leverages the entire toolkit.

.module integration

integrated module automation:

integrated module automation:• context wired up by parent once added to stage

integrated module automation:• context wired up by parent once added to stage• view events are collated in the one view manager

integrated module automation:• context wired up by parent once added to stage• view events are collated in the one view manager• child injectors created and wired to the parent

integrated module automation:• context wired up by parent once added to stage• view events are collated in the one view manager• child injectors created and wired to the parent• default injections to ensure modules work bothstandalone and when integrated.

integrated module automation:• context wired up by parent once added to stage• view events are collated in the one view manager• child injectors created and wired to the parent• default injections to ensure modules work bothstandalone and when integrated.in robotlegs 2, modules just work.

.robotlegs inspector

new inspector gadget tool to help you with your robotlegging.info here.

an example in covariance mediate behaviours not views

for comparison

for comparisonlet’s look at a simple robotlegs v1 application

invariant mediation (via classes)

invariant mediation (via classes) View

invariant mediation (via classes) View Mediator

invariant mediation (via classes) events View Mediator

invariant mediation (via classes) events View Mediator one mediator per view.

what’s wrong with this approach?

what’s wrong with this approach?• the mediator is tightly coupled to the view

what’s wrong with this approach?• the mediator is tightly coupled to the view• view is restricted to one mediator

what’s wrong with this approach?• the mediator is tightly coupled to the view• view is restricted to one mediator• no reuse of mediation

how to fix this in v1?

how to fix this in v1?using the variance utility

covariant mediation (via interfaces)

covariant mediation (via interfaces) View

covariant mediation (via interfaces) View IBehaviour A IBehaviour B IBehaviour C

covariant mediation (via interfaces) View Mediator A IBehaviour A IBehaviour B IBehaviour C Mediator B Mediator C

covariant mediation (via interfaces) e v e n t s View Mediator A e v e n t s IBehaviour A IBehaviour B e v e n t s IBehaviour C Mediator B Mediator C

covariant mediation (via interfaces) e v e n t s View Mediator A e v e n t s IBehaviour A IBehaviour B e v e n t s IBehaviour C Mediator B Mediator C n mediators per view.

what is wrong with this contract?

what is wrong with this contract? import flash.events.IEventDispatcher; [Event(name="doAsync", type="...ControlEvent")] public interface IServiceStarter extends IEventDispatcher { function serviceReturned():void; }we have to extend IEventDispatcher and there’s no enforcement of contract.

.enter signals, stage right

with signals, we define the contract

with signals, we define the contract import org.osflash.signals.ISignal; public interface IServiceStarter { function serviceReturned():void; function get start():ISignal; } and force the view to comply import org.osflash.signals.ISignal; private var startSignal:ISignal = new Signal(); public function serviceReturned():void { Alert.show("The service returned.","Guess what?"); } public function get start():ISignal { return startSignal; } ... <s:Button label=”Start” click=”start.dispatch” />

with covariance and signals

with covariance and signals View IBehaviour A IBehaviour B IBehaviour C

with covariance and signals View Mediator A IBehaviour A IBehaviour B IBehaviour C Mediator B Mediator C

with covariance and signals View Mediator A IBehaviour A IBehaviour B IBehaviour C Mediator B Mediator C each view is mediated bidirectionally.

to view this sample online go to j.mp/covariance Libraries used: • robotlegs 1.5.2 • robotlegs variance utility 1.1 • as3-signals 0.9-beta

so when is robotlegs 2 coming?

...now.

as of this afternoonrobotlegs 2 is in open beta.

Stay updated.

Stay updated. Add you name to the RL2 beta list by commenting on: j.mp/robotlegs2 Join the robotlegs google group Follow @robotlegs_as3 on Twitter.

fin.about.me/justinj@justinjmoses

http://www.video-flash.de	3247
http://testingbaires.com	55
http://a0.twimg.com	44
http://paper.li	40
http://coderwall.com	8
http://lanyrd.com	8
http://translate.googleusercontent.com	6
http://184.72.218.145	4
http://us-w1.rockmelt.com	2
http://www.video-im-www.de	1

Introduction to Robotlegs 2

by Justin J. Moses on Oct 28, 2011

Accessibility

Categories

Tags

Upload Details

Usage Rights

10 Embeds 3,415

Statistics

Introduction to Robotlegs 2 — Presentation Transcript