This is the theory, yes. A way to do your own thing using AS and MXML to
construct the app which then generates the right amount of HTML structure,
making it easier to style. Or use pre-built constructions and layouts as
templates that also generate the right amount of HTML structure.
I'm thinking that Panel would be a good case for a composite component and
maybe even move it into Express. In theory, you can compose a Panel from:
<Group> with VerticalFlexLayout
<Group> with Horizontal Flex Layout for the Title Bar
<Container> to provide scrollable area
<Group> with Horizontal Flex Layout for the Control Bar
</Group>
We'll see how this goes.
‹peter
On 3/6/17, 5:02 PM, "Alex Harui" <aha...@adobe.com> wrote:
>
>
>On 3/6/17, 1:26 PM, "piotrz" <piotrzarzyck...@gmail.com> wrote:
>
>>Hi Peter,
>>
>>It looks awesome. Cause if I'm enough skilled in CSS I can do whatever
>>layout I want and I don't need to know any other one. - In theory. :)
>
>True, but like with everything else in FlexJS, we are trying to
>encapsulate common patterns and make them easier to use.
>
>So for example if you have 3 children in a container and want to make the
>first one stretchy, you might have to write:
>
><Group style="display:flex" />
> <Label style="flex-grow: 2" />
> <Button style="flex-grow: 1" />
> <Button style="flex-grow: 1" />
></Group>
>
>Whereas with a layout you could write:
><Group>
> <beads>
> <FirstFlexibleChildLayout />
> </beads>
></Group>
>
>That way you don't have to remember the names of the styles or look up how
>to do it.
>
>Hopefully our Layouts will essentially do just that once Peter's done with
>this refactor.
>
>Of course, I could be wrong...
>-Alex
>
