incubator-flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sathyamoorthi <>
Subject Re: [OT] HTML and Flex layouts
Date Tue, 26 Jun 2012 05:06:49 GMT
Thanks to clarify my doubts Jude.

On 6/25/2012 11:29 PM, jude wrote:
>>> 1.But why they didn't propose these things (HGrop etc) to W3C for better
>> layout.
> The browsers already have something like this. It's called the table
> element. It works great for vertical, horiztonal and grid layout. There are
> some disadvantages to it compared to other layout approaches. For example,
> if you wanted to do your complete layout in CSS.
> Adobe have been proposing things like this recently but they have some
> major obstacles. This is from Ted's blog post in 2006 [1]:
> *HTML and its success has always been tightly bound to a browser
> HTML/JavaScript version. Each browser embeds its logic for interpreting
> HTML and JS within each 5MB-30MB Download of Internet Explorer and Firefox.
> The only way to upgrade this logic today is to download a new browser.
> With Flash Player, the browser and os are completely independent resulting
> in the ability to run new Flash Players and applications (Flex, Flash,
> Breeze) in older browsers and operating systems. *
>> 3.Is it tough to replace Flex UIComponent with HTML5 Canvas and create a
>> new JavaScript framework?
> There is a project called ASCanvas that is worth looking at,
> From the site:
> *ASCanvas is an implementation of the HTML 5 Canvas element for the Flash
> environment, written in ActionScript.*
> I was able to work on the project for a short time. AS and JS are both
> implementations of ECMAScript. This project is structured or makes sure
> that your ActionScript code runs in the browser as raw JavaScript as well
> as a SWF. Or another way to put it, the JavaScript is compiled to a SWF. It
> uses Adobe's asc.jar ActionScript compiler to do syntax checking. You can
> even use Flash Builder to debug it. The project uses stubs for the HTML
> document, body and other methods. Using this you could map the display list
> methods to the browser document object model.
> [1]

View raw message