The document discusses the Swiz framework for structuring Flex applications. It covers presentation patterns like MVC, dependency injection using Swiz, event mediation, services, mocks and metadata processors. Swiz enables microarchitecture and dependency injection to remove concrete dependencies and make applications extensible. It provides utilities like service helpers, global error handling and tools for event handling and metadata processing.

1. Structuring Flex applications with the Swiz frameworkSpreker: Jamie Craane

2. AgendaPresentationpatternsSwizQ&A

3. PresentationPatternsAutonomous viewPresentation ModelCode BehindModel View PresenterModel View ControllerAnd many more…

4. Autonomous viewView

5. Code BehindViewMXMLCode-behindEventhandlersData Model

6. Model View PresenterUses contract to read/write view dataViewPresenterRead/writemodelModel

7. Presentation ModelViewPresentationmodelModel

8. Model View ControllerResponds to user eventsViewControllerUpdatesmodelModelNotifies view

10. MVCViewModelServicedisplayupdateupdatemediatorupdateinvokesinvokesinvokesController

11. Model: Representing StateRepresentsclient state

12. [Bindable] : dispatcheseventon state changesessionuserpersonListtaskListselectedPerson

13. View: Presentation and InteractionViewModelReferencespersonlisttaskdetailsNotifiesPresents model to the user

14. Responds to model changes, ({} databinding)

15. Responds to user actions, (Declarativeeventhandling)

16. MostlyMXMLController: ExposeActionsUser-initiatedactions

17. Invokes services

18. Updates modelViewControllercallServiceInvokeModelUpdates

19. Service: EncapsulatesbackendsServicesPersonServiceTaskServicePersonServiceMockService callsremotedestinations

20. HttpServiceorRemoteObject (ie. BlazeDS)

21. Returns anASyncToken

22. Logical place forstubsMediators: update viewUser-initiatedactionsUpdates viewUpdates model (ifneeded)MediatorInterfaceViewcallViewUpdatesModelUpdates

23. SwizMicro architecture and Dependency Injection framework

24. MircoArchitectureFramework“Enables, but not restricts, in the implementation of an application following any given architecture”

25. Swiz in a nutshellDependency InjectionEvent MediationUtilitiesServiceHelperGlobal exception handlerAnd more…MetaData processors

26. DependencyInjection 1How can a given object obtain a reference to another object?

27. DependencyInjection 2Object AObject BDepends on

28. DependencyInjection 3Object ADI frameworkObject BObject AObject BApplicationContext

29. Dependencyinjection 4[Inject]public var userController:UserController;<?xml version="1.0" encoding="utf-8"?><swiz:BeanProvider <controller:UserController/></swiz:BeanProvider>

30. Dependencyinjection 5Typically inject by typeSpecify Bean ID if necessaryWorks with interfaces and inheritance

31. WhyDependencyInjection?Removes dependencies on concrete implementationsNo ServiceLocatorEasy to see dependencies

32. EventMediationdispatcher.dispatchEvent(new TaskEvent(TaskEvent.SAVE_TASK_SUCCESS, true));[Mediate(event="TaskEvent.SAVE_TASK_SUCCESS")]publicfunction saveTaskSuccess():void { this.closeTaskDetailsWindow(); taskController.retrieveTasks();}