Hi Carlos,
As you noted, there is code-size/PAYG impact to adding more and more
sizing/measurement properties. After you add min-width/max-width someone will
then want explicitMinWidth and so-on. Flex has quite a few of these properties.
I know Flex users are used to having these properties, and the emulation
components have them for backward compatibility (plus emulation isn't focused
on code-size) but I was thinking that in almost all other cases, properties
like min-width/max-width are going to be passed straight to CSS since in most
other Royale layouts we are trying to let the browser's CSS do the layout. And
if that's true, then I wonder if non-Flex users won't expect these properties
on the component and will expect to set them in CSS. UIBase supports the same
inline style syntax as HTML does or you can specify those styles in <fx:Style>
or .css files. So if these values get passed to CSS, you can specify those
values in an MXML file without changing UIBase and it might be a more
expected/familiar way for non-Flex users. Or are you working with a layout
that doesn't pass these values to CSS?
I'm not sure what you mean by the width = NaN issue. The width getter makes
some attempt to compute a size, but others say that if that computation is
running then you might be asking for width too soon/often since that
computation might force the browser to run its layout.
Thoughts?
-Alex
On 1/10/19, 8:28 AM, "Carlos Rovira" <carlosrov...@apache.org> wrote:
Hi,
while working with Royale I'm finding that we need some things for in
UIBase for sizing from AS3/MXML:
- Set min-width
- Set max-width
- Manage width = NaN (in CSS this is set style to "initial")
(same for height)
I can create a CSS selector and apply it to the component. But this seems
more like a Hack and HTML/CSS platform oriented, so I don't like it at all.
For NaN is easy, I think we only need to handle it in set width, and since
is something basic I don't think it will be go against PAYG.
min and max in the other hand seems tricky since is basic UIBase
functionality, but could not PAYG depending on our thinking. My opinion is
that this getter/setter are needed and I would put it in UIBase.
Doing this as a bead seems to me a bit unnatural , but again, if all of you
think it should be bead instead something baked in UIBase, we can implement
in that way.
Thoughts?
--
Carlos Rovira
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C889cf10b160246617be308d67718a5d1%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636827345088557941&sdata=9XNx5tbbIrevwSbX87fD0sHnyGngccJs8OkmrDb8gBc%3D&reserved=0
