Hi Piotr and others about this point :
* Card: Added default 100% w/h so Card know knows about it I reverted it since I saw people should do as in Flex. If they want w o h to be 100% just set in the instance in mxml (width="100%" height="100%"), if not that could be strange for users to see Cards taking 100% of space on its own. El mié., 18 mar. 2020 a las 11:11, Carlos Rovira (<[email protected]>) escribió: > Hi Alex, > > I'm experimenting for this concrete case with a calc(% - px) formula that > could work. don't like it so much since it means is something very "JS" > coupled but it should maintain responsiveness. Crossing fingers :) > > El mié., 18 mar. 2020 a las 3:44, Alex Harui (<[email protected]>) > escribió: > >> >> >> On 3/17/20, 5:14 PM, "Carlos Rovira" <[email protected]> wrote: >> >> Hi Alex, >> >> I'll try to see how things are done in MXRoyale's ADG for columns. >> Really >> the problem right now is in that concrete case. I'm sure there's some >> way >> to do it but while I'm using flex box already as you suggest for many >> things, in this case I need to do calculations, since all is based on >> how >> users will configure the columns via mxml with a mix (or not) of >> pixels and >> percentages. >> >> And because you are using display="flex", not having the child columns >> also be CSS compliant with the width is probably causing the pain. That's >> what I saw with MXRoyale. >> You may be able to calculate the numbers, but then the columns will not >> be responsive as the "flex" container changes size. You will have to >> detect that and recompute. >> >> If you instead using the weighting system that "flex" children use, I >> think you will have less pain and more responsive-ness. Users might gladly >> give up on the old Flex percentWidth overloading in favor of the weighting >> system to get that responsiveness. >> >> My 2 cents, >> -Alex >> >> >> > > -- > Carlos Rovira > http://about.me/carlosrovira > > -- Carlos Rovira http://about.me/carlosrovira
