On 1/13/19, 4:12 AM, "Carlos Rovira" <[email protected]> wrote:
*So, to refocus on the topic that open this thread. For me the decision is
about:*
*a) To use NaN in width and height, make this little change in setWidth to
be able to use NaN*
*this.positioner.style.width = isNaN(_width) ? "initial" : value.toString()
+ 'px'; *
*(don't see other way to deal with this)*
NaN may not be a legal value on some runtimes/platforms. I haven't followed
this part of the thread. What is the scenario? UIBase.width is a Number
because folks coming from Flex will expect it. The underlying CSS is a
separate issue, IMO.
*b) for max and min we can go with getter/setters baked in UIBase, or
create a Bead for each one.*
IMO, we have the width/height properties that just about everybody will need in
UIBase and everything else has to be added as a bead for PAYG reasons.
Remember that a top-level-component aggregates beads and proxies them to the
API surface, so it is up to the component set developers to decide which
properties to proxy. There is no requirement to create a bead for each
property, you can group them into a MinMaxWidthHeight bead or something like
that. It doesn't matter since different component sets can use different beads.
If you want to add a setStyle() API or have properties like minWidth added to
Jewel that's totally fine. I don't think Basic should have it. There are
lower cost ways of setting CSS already in Basic.
My 2 cents,
-Alex
Thoughts?
Carlos
El vie., 11 ene. 2019 a las 20:59, Kessler CTR Mark J
(<[email protected]>) escribió:
> I'm slow getting to these emails, so if I've missed any, I apologize.
>
> After this last two weeks I've come to the realization that the FlexBox
> CSS style is greatly more flexible(no pun intended twice) than most of
what
> we have in AS. I could write a pile of examples for most common layouts
if
> it had enough interest. These were styles I ended up assigning using CSS
> selectors assigned to MXML via the className property. I could even fix
> formatting issues I was having in Jewel by overriding the styles this way.
>
>
> If you really wanted to use a max width without adding coding overhead to
> the SDK you could just add in CSS file selector to use max-width.
>
>
> .MyStyle
> {
> Max:width: 200px;
> }
>
>
> <j:VGroup className="MyStyle">
> <child />
> <child />
> </ j:VGroup>
>
>
> It would cut off any overflow by default. If you'd prefer you could use
> the "flex-wrap: wrap" to have it wrap the children in the cross axis
> direction.
>
> I'll have to add more to the email later on, but this part can go out
> now. Could make a very large wiki page on layout in MXML with the flexbox
> logic.
>
> -Mark K
>
>
>
>
> -----Original Message-----
> From: Carlos Rovira [mailto:[email protected]]
> Sent: Thursday, January 10, 2019 2:50 PM
> To: [email protected]
> Subject: [Non-DoD Source] Re: Things that we still doesn't have and need
> in UIBase sizing
>
> Hi Mark,
>
> thanks for joining to the discussion:
>
>
> El jue., 10 ene. 2019 a las 20:31, Kessler CTR Mark J
> (<[email protected]>) escribió:
>
> >
> > Back on topic, I was able to avoid using max size declarations by
adding
> > in CSS to utilize the flex-box CSS alignments to fill and distribute
> sizes.
>
>
> >
>
> Very interesting, could you provide some code example so I can understand
> the concept? I'm interested in that technique
>
> thanks
>
> --
> Carlos Rovira
>
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7Cbf26b57c45254489fc7c08d67950514e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636829783199266513&sdata=cuqt%2Bt%2FmIi4b1O03TkrGCsAIy098RmBUkkrrMZ2FJ%2Fo%3D&reserved=0
>
--
Carlos Rovira
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7Cbf26b57c45254489fc7c08d67950514e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636829783199266513&sdata=cuqt%2Bt%2FmIi4b1O03TkrGCsAIy098RmBUkkrrMZ2FJ%2Fo%3D&reserved=0
