Re: Should we change width/height to use EM instead PX?? (was: Re: Using em vs px)

There are tons of discussions on the web about the pros and cons of pixels vs em/rem. Some examples:[1][2][3][4][5] My takeaway is that there’s no one right answer. For predictable layout, pixels is safer, but for better reading with accessibility, em/rem might work better. Simply changing

Re: Using em vs px (was. Re: Things that we still doesn't have and need in UIBase sizing)

Hi Mark, just created a new thread for this. thanks! El lun., 14 ene. 2019 a las 13:39, Mark Kessler (< kesslerconsult...@gmail.com>) escribió: > Carlos, > I can give it a shot when I'm at home. However, what about the > direct width/height assignments. Should they do EM assignment too or

Re: [Non-DoD Source] Re: Things that we still doesn't have and need in UIBase sizing

Hi Alex, El lun., 14 ene. 2019 a las 5:37, Alex Harui () escribió: > > NaN may not be a legal value on some runtimes/platforms. mmm...but, right now, since property is actually NaN, you can pass NaN value in Royale, so is a valid value actually, and I think Flex as well can accept NaN right?

Should we change width/height to use EM instead PX?? (was: Re: Using em vs px)

Hi Mark, very good question. And I don't know what would be the best... Hope others (Alex, Harbs, Piotr, etc...) could give some thoughts about this since I'm not sure. To put people on track; Mark states that using font size (only) browser increase/decrease (notice that Firefox has a built-in

Re: [Non-DoD Source] Re: Things that we still doesn't have and need in UIBase sizing

I've run into the "unset width/height" issue myself. IMO, unsetting width/height is platform-specific and shouldn't be in the API surfaces of the components. For me, I just had to pick the right place in the platform implementation to set the values. Right now there are some places where we

Re: Should we change width/height to use EM instead PX?? (was: Re: Using em vs px)

> On Jan 14, 2019, at 8:04 PM, Alex Harui wrote: > > Harbs, > > What did you learn about constants and in-lining regarding Closure Compiler? > Could we put "px" in a variable/constant and have the option to replace it > with "em”? I can’t think of a way to do that off-hand. > That said,

Re: Should we change width/height to use EM instead PX?? (was: Re: Using em vs px)

Harbs, What did you learn about constants and in-lining regarding Closure Compiler? Could we put "px" in a variable/constant and have the option to replace it with "em"? That said, are we sure that you can just switch to "em" and all other computations will "do the right thing"? My first

Re: Should we change width/height to use EM instead PX?? (was: Re: Using em vs px)

IIRC, in Flash, a string lookup is actually faster than a string literal. I was wondering if Closure would in-line it or look it up so we could hack that string. Or maybe if we define it as a "var" instead of "const" it will always look it up, but not sure. I think that for swf bytecode output

Re: Should we change width/height to use EM instead PX?? (was: Re: Using em vs px)

As a comment on the helper functions, we could also just have something that does on the fly conversion. In other words if I say 300 pixels, I want it to translate that into EM / other unit in the background. The reason I bring that up is to allow exact PX still be used for the Flex / Air side

Re: Should we change width/height to use EM instead PX?? (was: Re: Using em vs px)

Thinking about this a bit more, it reminds me a bit of a similar issue with mobile devices and pixel resolution. I think it may also be an issue with Retina displays on Macs and probably some equivalents in Windows. The most Basic applications shouldn't care about that stuff and if you ask for

Re: Should we change width/height to use EM instead PX?? (was: Re: Using em vs px)

The string literal "px" is scattered throughout our code. For example: UIBase.as this.positioner.style.height = value.toString() + 'px'; This could be changed to: public static const CSSUnits:String = "px"; this.positioner.style.height =

Issues with the first-app tutorial

Hi, all: I have run into some issues and questions related the code and the instructions for the tutorial to show users how to build their first app [1]. How do I get them resolved? Just report them here in this conversation? Thanks. a [1]

Re: Issues with the first-app tutorial

Hi Andrew, Either here or as a GH issue. GH might be better if you need to attach files or images/screenshots. -Alex On 1/14/19, 3:33 PM, "Andrew Wetmore" wrote: Hi, all: I have run into some issues and questions related the code and the instructions for the tutorial to

Re: Should we change width/height to use EM instead PX?? (was: Re: Using em vs px)

Yes, that might be possible as well. We don't really have to pick one strategy. Different component sets can have different strategies. We could have an "all em" set if we wanted. It would be nice to share code in UIBase, but not a requirement. Hopefully, IUIBase doesn't really presume

Jenkins build is back to normal : royale-asjs_jsonly #2214

See

Build failed in Jenkins: royale-asjs_MXTests #347

See -- [...truncated 2.00 MB...] [mxmlc] using source file:

Jenkins build is back to normal : royale-asjs_MXTests #348

See

Re: [royale-asjs.wiki] branch master updated: added change of chair

I just filed the report. I did not have any data on social networks. If someone wants to add that, I’ll modify the report. Thanks, Harbs > On Jan 14, 2019, at 10:02 AM, ha...@apache.org wrote: > > This is an automated email from the ASF dual-hosted git repository. > > harbs pushed a commit

Jenkins build is back to normal : royale-asjs_MXTests #342

See

Jenkins build is back to normal : royale-asjs_MXTests #344

See

Jenkins build is back to normal : TourDeFlexMigration #359

See

Build failed in Jenkins: royale-asjs_MXTests #343

See -- [...truncated 2.00 MB...] [mxmlc] using source file:

Re: Using em vs px (was. Re: Things that we still doesn't have and need in UIBase sizing)

Carlos, I can give it a shot when I'm at home. However, what about the direct width/height assignments. Should they do EM assignment too or should there be a new widthEM heightEM property added? -Mark K On Sun, Jan 13, 2019 at 6:58 AM Carlos Rovira wrote: > > Hi Mark, > > thanks for the