creationPolicy="all" merit and demerit

4 views
Skip to first unread message

vincent

unread,
Sep 29, 2010, 9:59:02 AM9/29/10
to flex_...@googlegroups.com, flex.india...@gmail.com, flexa...@googlegroups.com
hi Friends


               

1.       what is the merit and demerit of using creation Policy="all" in TabNavigator


  

--
Regards,

Vincent P

m prasath

unread,
Sep 29, 2010, 10:16:15 AM9/29/10
to privi...@gmail.com, flex_...@googlegroups.com, flex.india...@gmail.com, flexa...@googlegroups.com
vinent
     when you give creationpolicy = "all" all the childs in the tabs will get created at the tab creation itself, if creationpolicy = "auto" the child in the tabs will get created only when you click on that tab.
--
M Prasath
Senior Software Engineer
Corent Technology Pvt. Limited
www.corenttech.com
Office : 91 ( 044) 2817 1763
Mobile: 91-9865003890

Muniraju A

unread,
Sep 30, 2010, 12:15:32 AM9/30/10
to flexa...@googlegroups.com, privi...@gmail.com, flex_...@googlegroups.com, flex.india...@gmail.com
Hi prasath


                    Please understood the question and then answer ,he is not asking how creation policy works ,
he is asking merits and demerits of creation policy of the tab navigator .
--
A Muniraju

Corent Technology Pvt. Limited
<http://www.corenttech.com>

Office : 91 ( 044) 2817 1763
Mobile: 91-8015760719

Nithi S

unread,
Sep 30, 2010, 2:41:10 AM9/30/10
to flexa...@googlegroups.com, flex_...@googlegroups.com, flex.india...@gmail.com

Hi Friends,

 Deferred instantiation is great.


If the children of the ViewStack or TabNavigator are few and simple, then instead of jumping through hoops trying to deal with deferred instantiation in the framework, be a slacker and  simply set creationPolicy=all in your ViewStack and be done with it. All the children will be available when on creationComplete and you can just attach your Mediators.

 

This advice is only for the simplest cases!!! Deferred instantiation is the default behavior because it is expected that you want the most optimal startup experience. And if you have a ViewStack with many children it may take a long time to instantiate them, leading to a slower perceived response time. And since the user may never navigate to these children, it is wasteful of memory as well. 


On Wed, Sep 29, 2010 at 7:29 PM, vincent <privi...@gmail.com> wrote:



--
Thanks & Regards,
(¨`•.•´¨) Always
`•.¸(¨`•.•´¨) Keep
(¨`•.•´¨)¸.•´ Smiling!!
`•.¸.•´
With Love´¨)
  ¸ •´ ¸.•*´¨)   ¸.•*¨)
(¸.•´      (¸.•*      ♥♥♥...♪♪♪..... 
நித்தியானந்தன் சுந்தரேசன்

(M) : +91 98400 91207

Reply all
Reply to author
Forward
0 new messages