ContainerCreationPolicy  - AS3 Flex

Immediately create all descendants.

Avoid using this creationPolicy because it increases the startup time of your application. There is usually no good reason to create components at startup which the user cannot see. If you are using this policy so that you can "push" data into hidden components at startup, you should instead design your application so that the data is stored in data variables and components which are created later "pull" in this data, via databinding or an initialize handler.

Delay creating some or all descendants until they are needed.

For example, if a navigator container such as a TabNavigator has this creationPolicy, it will immediately create all of its children, plus the descendants of the initially selected child. However, it will wait to create the descendants of the other children until the user navigates to them.

Do not create any children.

With this creationPolicy, it is the developer's responsibility to programmatically create the children from the UIComponentDescriptors by calling createComponentsFromDescriptors() on the parent container.

Add the container to a creation queue. Deprecated since Flex 4.0.