Hi Harbs,

maybe I don't understand correctly your question, but for me there's no
distinction. If I have a button with a explicit width set up of 500px
the surrounding container (normaly a div) will behave accordingly right? So
if this is not what you are asking, can you explain a bit more or maybe
give some example?

thanks



2018-03-26 19:27 GMT+02:00 Harbs <[email protected]>:

> I agree with all of this too (mostly).
>
> I’m going to to repeat my question for the third time: How can we
> structure things so layout can know whether their parent layouts are
> “manual children-sized layouts” which need to have resize events  and which
> have parent layouts which don’t need these events?
>
> This is the key point here which we need to find the right answer to. I
> don’t have the answer to this myself. We need some brainstorming to come up
> with the right solution to this problem.
>
> Harbs
>
> > On Mar 26, 2018, at 8:18 PM, Alex Harui <[email protected]>
> wrote:
> >
> > I feel like several independent factors are being mixed together.  I
> think
> > it is better to address them separately.
> >
> > Also, IMO, there are two kinds of layout in Royale.  One group of layouts
> > just lets the browser do the layout, like VerticalLayout,
> HorizontalLayout
> > and the Layouts that use FlexBox.  The other group of layouts tries to
> run
> > code to solve layout issues that browsers don't make easy or to emulate
> > Apache Flex behavior.  This is things like VerticalColumnLayout,
> > VerticalLayoutWithPaddingAndGap, and the FlexibleChild layouts, and some
> > custom layouts like NumericStepper and the ProductsView layout in
> > RoyaleStore example.
> >
> > When we first started out on FlexJS/Royale six years ago, the only
> browser
> > layouts I knew about were setting the display style to "blocK" or
> > "inline-block" to get vertical or horizontal layout.  So we used it where
> > we could and wrote other custom layouts to handle other cases in the
> > second group.  Over time, new display styles have emerged as useful and
> > stable.  Mainly display="flex" a couple of years ago and now/soon
> > display="grid".  Slowly but surely, the browsers are solving the pain
> > points folks used to workaround.
> >
> > I agree with Carlos that we really want the browser to run its layout
> code
> > instead of us running our layout code where possible.
>
>


-- 
Carlos Rovira
http://about.me/carlosrovira

Reply via email to