Yep, any useful reusable pattern is a candidate for a Royale layout. Even the
OneFlexibleChild layouts are examples of that. In Flex you had to use VBox or
HBox and set the percentage on the child. In Royale, you just specify the
child and the layout figures out what to do to make it stretch.
-Alex
On 6/11/18, 9:12 AM, "Harbs" <harbs.li...@gmail.com> wrote:
Not disagreeing with anything you write here…
FWIW, I was thinking of adding a “constrainment” bead which would allow
left/right/top/bottom values. This would likely work in the context of other
layouts and be applied to components directly.
> On Jun 11, 2018, at 6:43 PM, Alex Harui <aha...@adobe.com.INVALID> wrote:
>
> So yeah, % works differently in Royale compared to Flex for some layouts,
but may not for other layouts. It is ok if Harbs app couldn't use some of our
Basic layouts without adding calc(). If other sites can go to production
without using calc() then our simplest layouts should allow them to do so. If
there is a pattern where many apps use calc() a certain way, that should be
encapsulated into another layout in Royale.
