Building Flex Application with the Swiz Framework Chris

Building Flex Application with the Swiz Framework Chris Scott, Senior Software Architect, Universal Mind

About Me. . . Enterprise Software Consultant Author of the Swiz Framework Co-Author of the Cold. Spring Framework Avid Open Source Contributor Long, long time Java, CF and Action. Script developer

What is Swiz anyway? ?

Swiz in a nutshell Simple IOC for Flex / AS Development MVC Architecture Simple tools for common tasks - Remote method invocation - Event Handling Utilities for advanced development

What Swiz is NOT Excessive JEE patterns Boilerplate code Verbose XML configuration Overly Prescriptive

Swiz 101 Flex Applications require: - Remote Services Data Logic Views

Swiz 101 Application Components need each other - Wire ourselves - Use Service Locators - Verbose XML configuration

Swiz 101 Application Components need each other - Inversion of Control - Annotations

Swiz 101 Views communicate with components - Standard Flex Events - Facilitates MVC Paradigm - Use Swiz Dynamic Mediators

Swiz 101 Applications Need Data - Async Token IResponder Implementations State Management Use Swiz Dynamic Responders

Swiz 101 Swiz features at a clance - Io. C for Autowiring Dynamic. Responder for remote data Dynamic. Mediator for events A whole lot more. . .

In. Sync example application. . . - first show views, clean, no script - now show main. mxml and beanloader, how defined - open Contact. Controller, show two autowire methdos - show mainview and autowire there too