From: Yishay Weiss<mailto:[email protected]> Sent: Thursday, December 15, 2016 8:24 AM To: Alex Harui<mailto:[email protected]> Subject: RE: [FlexJS] About Component Cycle and Events
That was my intent, load it when necessary. My point was that there was no reason to attach event handlers when you need the bead, you can just check for its existence and load it if necessary. From: Alex Harui<mailto:[email protected]> Sent: Thursday, December 15, 2016 6:46 AM To: [email protected]<mailto:[email protected]> Subject: Re: [FlexJS] About Component Cycle and Events On 12/14/16, 1:50 PM, "[email protected] on behalf of OmPrakash Muppirala" <[email protected] on behalf of [email protected]> wrote: >On Wed, Dec 14, 2016 at 11:18 AM, Alex Harui <[email protected]> wrote: > >> >> >> On 12/14/16, 10:42 AM, "yishayw" <[email protected]> wrote: >> >>>Is there a reason not to proactively load the beads you need? If you use >> >org.apache.flex.utils.StrandUtils.loadBead(), you can be assured that >>the >> >bead has been loaded and retain a synchronous flow. >> > >> >> IMO, proactive is not PAYG. >> > >I'm a bit confused. How is loading a bead when needed not Pay-as-you-go? >What is your definition of pay-as-you-go? I read "proactive" to mean "so far in advance it is just-in-case". Of course you have to load a bead before you use it, but it should be as close to on-demand as you can get. -Alex
