The Basic component set does not use any invalidation/validation. Mostly that is because the underlying HTMLElements don't have the same sort of update/render phases like Flash. They are what I call "immediate". Other, more sophisticated component sets can implement invalidation/validation if they want to. The MX/Spark port POC did, for example.
So, because your code typically doesn't have to wait for something to happen, I think we require fewer events. More inline... On 12/11/16, 12:25 AM, "[email protected] on behalf of Carlos Rovira" <[email protected] on behalf of [email protected]> wrote: >Hi, > >I open this thread to talk about FlexJS Component Cycle and the supported >events. >we need to know what to expect about : > >* When data is available in a component Not sure what you mean here, are you referring to item renderers? I just added dataChange to MXMLItemRenderer, but the other item renderer base classes don't dispatch an event. >* we don't have the classic methods like commitProperties, >updateDisplayList,... >* What events do we have? initComplete? creationComplete? and what >components have this: UIBase? MXMLItemRenderer? Some components like Container, and List dispatch initComplete. Again, because there aren't invalidation phases, it isn't clear that you need both initialize and creationComplete events. One event is probably good enough, but I could certainly be wrong, so provide more detail about your scenario. Yishay mentions beadsAdded. It really just means all beads have been added. There could be other work that happens afterwards before the call to addChild returns. HTH, -Alex
