Building Flex Applications with the Swiz Framework (RIA Unleashed: Boston 2009)
Chris Scott
What is Swiz:
* Simple IoC for Flex / AS Development
* MVC Architecture
* Simple tools for common tasks: remote methods, event handling, modules
What Swiz is not:
* Excessive JEE patterns
* Boilerplate code
* Verbose XML configuration
* Overly prescriptive
Swiz uses dependency injection to satisfy component requirements.
Common dependencies:
* Remote services
* Data
* Logic
* Views
Other approaches:
* Wire ourselves
* Use Service Locators
* Verbose XML configuration
Swiz application:
* Define application it needs to use: remote objects, controllers, presentation models
* SwizConfig component in top level application
* [Autowire] metadata for dependency injection, two flavors (type reflection) or by bean name
* [Mediate(event="", properties="")]
* Swiz class called AbstractBaseController: executeServiceCall(async token, result, fault, arguments)
* Immediate run-time checking of event names
* Swiz:Prototype using class reference or name
* Module specific scope for Swiz config