That would make it a pretty thick wrapper. It would have to dispatch all the
events that layout beads expect ,and implement ILayoutChild and ILayoutParent.
Have a look at LayoutBase to see the dependencies on the strand assumed by
most layouts (and there are probably more in the concrete classes).
Adding a meager LayoutOnShow bead seems cleaner to me.
________________________________
From: Alex Harui <aha...@adobe.com.INVALID>
Sent: Monday, August 7, 2017 6:58:29 PM
To: dev@flex.apache.org
Subject: Re: FlexJS Bead dilemma
<SomeComponent>
<beads>
<LayoutOnlyWhenVisibleWrapperBead>
<VerticalLayout />
</LayoutOnlyWhenVisibleWrapperBead>
</beads>
A bead could have a property which is another bead.
Of course, I could be wrong...
-Alex
On 8/7/17, 11:13 AM, "yishayw" <yishayj...@hotmail.com> wrote:
>Alex Harui-2 wrote
>> A fancier alternative would be a bead that wraps a layout bead and adds
>> the visible check. That might be the best way to apply PAYG.
>
>Can you explain what you mean? How would you wrap a bead?
>
>
>
>
>--
>View this message in context:
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fle
>x-development.2333347.n4.nabble.com%2FFlexJS-Bead-dilemma-tp63681p63726.ht
>ml&data=02%7C01%7C%7C4491569503864889292108d4ddc03a7b%7Cfa7b1b5a7b34438794
>aed2c178decee1%7C0%7C0%7C636377265065337580&sdata=XfcOsF4uBbpuF9DW2Mt%2Fu5
>zxSJYQth3mYyAwjLWJ88s%3D&reserved=0
>Sent from the Apache Flex Development mailing list archive at Nabble.com.
