Re: [royale-asjs] branch develop updated: isHeightSizedToContent is a method, not a prop

I'm sorry in Flex you will get an warning and in that case it could also be the same. In the opposite situation Flex is throwing an error. Piotr 2017-11-22 18:27 GMT+01:00 Piotr Zarzycki : > Hi Yishay, > > I think it could be even an error throwing by the compiler. If

Re: [royale-asjs] branch develop updated: isHeightSizedToContent is a method, not a prop

Hi Yishay, I think it could be even an error throwing by the compiler. If Flex you would got an error. Piotr 2017-11-21 12:29 GMT+01:00 Yishay Weiss : > Should there be a compiler warning when methods are implicitly converted > to Booleans? > > > >

Re: How to improve the Royale developer experience ("Smart HTML" component set)

Hi Olaf, Welcome back. Can you elaborate on how Royale MXML is different from Flex MXML? Is it just the component and attribute names? Or something else? When you first learned Flex, you didn't know Flex MXML and somehow still found it easy to use. Regarding re-use of HTML/CSS snippets, I'm

Re: How to improve the Royale developer experience ("Smart HTML" component set)

I'd completely agree. It'd allow developer to solve his/her own problems (by re-using existing css/html snippets), instead of using the Royale forum to walk up the learning curve. New converts to Flex/Royale would find this more natural as well. > On November 22, 2017 at 3:28 AM Olaf Krueger

Re: [website] Getting started page

On Nov 22, 2017 7:02 AM, "Carlos Rovira" wrote: Hi, all you're completely right, I was a bit blind in this content and maybe we could move that content to other website page and create new one with the ideas you suggest here. So for the content could be more of a hello

Re: [website] Getting started page

Hi, all you're completely right, I was a bit blind in this content and maybe we could move that content to other website page and create new one with the ideas you suggest here. So for the content could be more of a hello world with steroids. The first instructions to use Royale should be from

Re: [website] list of things to finish

Awesome Olaf! :)) Waiting anxiously about your progress in that front. I'll be sending you a wp account so you can have website access. As I said to others, use it to edit website content post and pages, but try not to change configurations, since it could break things inside WP, and somethings

Re: How to improve the Royale developer experience ("Smart HTML" component set)

>Can you maybe create a little MXML and AS3 project... Yes, good idea, I will do this... maybe while thinking about such an example it turns out that it doesn't make sense at the end ;-) Olaf -- Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: How to improve the Royale developer experience ("Smart HTML" component set)

I like your reasoning. Can you maybe create a little MXML and AS3 project (pseudo code, obviously) that shows what you think a 'HTML friendly MXML/AS' file would look like? Thanks, EdB On Wed, Nov 22, 2017 at 12:28 PM, Olaf Krueger wrote: > Hi, > I guess you all are

Re: [Understanding Royale] Why MXML->JS->HTML instead of MXML->HTML

> I’m 99.9% sure that browsers mark the structure as dirty when something is > written, but none of the actual calculations and rendering happen until > something is read or the next rendering cycle in the browser happens. > > I’m not sure if we’re disagreeing here. > We are not, just finding

Re: [Understanding Royale] Why MXML->JS->HTML instead of MXML->HTML

I’m 99.9% sure that browsers mark the structure as dirty when something is written, but none of the actual calculations and rendering happen until something is read or the next rendering cycle in the browser happens. I’m not sure if we’re disagreeing here. One question I have is what the

Re: [Understanding Royale] Why MXML->JS->HTML instead of MXML->HTML

> > I would say that the addition of each element triggers the browser to do > a > > full DOM parse and reflow of the CSS. > > I don’t think this is true. Reflow only happens when attributes of the DOM > is *read*. Writing to the DOM does not trigger a reflow. > I'm not sure I agree. An addition

Re: [Understanding Royale] Why MXML->JS->HTML instead of MXML->HTML

> > I have no idea how the browser works internally but I thought that if we > add > > an HTML element to the DOM by using JS the browser has to parse it > > afterward? > > I might be wrong, but I don’t think so. AFAIU, if you add elements to the > DOM via JS, it simply gets added to the DOM tree

Re: [Understanding Royale] Why MXML->JS->HTML instead of MXML->HTML

Hi, > 2. No need for the browser to parse HTML markup. > I would say that the addition of each element triggers the browser to do a full DOM parse and reflow of the CSS. From that perspective, it might be cheaper if the backbone HTML is defined when the page loads, instead of being built from

Re: [Understanding Royale] Why MXML->JS->HTML instead of MXML->HTML

> On Nov 22, 2017, at 11:25 AM, Olaf Krueger wrote: > >> No need for the browser to parse HTML markup. > Could you explain this a bit more? > I have no idea how the browser works internally but I thought that if we add > an HTML element to the DOM by using JS the browser

Re: [Understanding Royale] Why MXML->JS->HTML instead of MXML->HTML

Forgot something: I remember that I've read sometimes here about problems to apply standard CSS3 to MXML (HTML) elements. Is the JS/DOM stuff one reason for this because it is maybe harder to provide full CSS3 support? Thanks, Olaf -- Sent from: