Sounds like you're coming from a Flash background. While it's true that Flash is the output of the Flex app, it's often more useful to think of Flex like a state-based application with which you can do a lot of asynchronous things like Ajax. Are you doing something with animation where you are trying to understand the movement of an object or something?
As far as rendering, the render event is, I believe, the last event that fires right before any component becomes visible on the screen. So I guess you could think of rendering as the process of building a visual object from all the code you've created, assembling it and adding it to the stage, kind of like addChild in Flash.
Thanks for the reply ,
yes I am trying to make a stand alone air application , My confusion started when I started reading about custom components and methods like commitProperties and mesaure . The definition of these methods say that they are fired in the next render cycle after their corresponding methods are called i.e. invalidateProperties and invalidateSize . But I am not able to understand , when does the next render cycle happens. Is it something to do with frames and frame rate or is completely independent of it.
Ah. Got you. Google a couple of things:
Flex 4 Component Lifecycle (Flex 3's component lifecycle was a little different)
Also looks like they did a session at Max last year: http://tv.adobe.com/watch/max-2010-develop/flex-component-development/
Awesome , Thanks a lot John for the links . I was looking out for something like this.
Now I can make my hands dirty with these information.