The document discusses the Flex component lifecycle and invalidation/validation model. It explains that the component lifecycle consists of 3 phases - initialization, updating, and destruction. It describes the key methods involved in each phase like createChildren(), commitProperties(), measure(), updateDisplayList(), etc. and how the invalidation/validation model helps optimize component updating by deferring work until the validation phase.

1. Creating Custom Components in Flex 3

4. Invalidation / Validation theory Flash player Rendering model

7. Flash player frames ! Answer !

8. The Elastic Racetrack Flex component lifecycle is built atop this frame model Invalidation/Validation takes advantage of the elastic racetrack to get work done in an efficient manner. Images courtesy of Sean Christmann Traditional Flash Player Elastic Racetrack

9. The Elastic Racetrack Images courtesy of Sean Christmann User Actions • Interact with any non- validation events from this frame (mouse movements, timers, ENTER_FRAME s etc.) • Dispatch invalidation events (invalidateProperties etc.) Invalidate Action • Process all validation calls (CommitProperties) Render Action • Do the heavy lifting - actually draw on the screen Event.updateAfterEvent -> Stage.Invalidate->Render event->Validation methods

10. Deferred Validation Model Waiting for update request Update Requested Invalidation Validation Validation occurs right before Rendering Invalidation Validation