- Introduction
- Modifying the architecture of existing Flex Robotlegs-based FlickrGallery
- Implementing UI interfaces with MadComponents
- Pros and cons of "static" and "extension" techniques to extending MadComponents
- Typed model and UIList's custom renderer
- You cannot access children views in Mediator.onRegister()
- Instead of conclusions
- Compile and try
- I was lazy
- Thoughts
- Summing up
Introduction
During last days I was playing with amazing AS3 library "MadComponents" - lightweight open-source UI framework for Flash. This library is maintained by Daniel Freeman and he claims that "MadComponents" targets mobile apps via Adobe AIR. And I could say that the library proves that point: it's fast and provides ready-to-use components, which fit to mobile UI, out of the box. One of the great features is a declarative UI markup: just feed framework with correct XML and it produces components' tree that automatically layouts depending on device screen dimensions.
protected const LAYOUT: XML = <horizontal alignH="right"> <input id="searchTermInput" width="150" /> <button id="submitSearchButton">search</button> </horizontal>;
I've created prototype for my commercial project very quickly utilizing MadComponents. Since prototype phase had satisfied my needs I've decided to introduce the library with my favourite ActionScript MVC framework RobotLegs.