I see enough crazy stuff done on Canvas here:
http://net.tutsplus.com/articles/web-roundups/21-ridiculously-impressive-html
5-canvas-experiments/ to conjecture that it's performant enough to render
any Flex layout; which would normally be computed outside of the object
representing the Canvas (in my view).
Yvon
-----Original message-----
From: Roland Zwaga <rol...@stackandheap.com>
To: flex-dev@incubator.apache.org
Sent: Thu, Aug 30, 2012 11:46:24 GMT+00:00
Subject: Re: Cross-compiling Flex to HTML5/Javascript (Was : Update on
Falcon donation)
I was talking about this canvas:
http://en.wikipedia.org/wiki/Canvas_element
I haven't seen FalconJS but from what I read, it looks like it plays with
the DOM. That's what GWT does. It's good for Google because they had
nothing
to start with. For Flex, I say "forget about the DOM". Draw everything
directly into one single HTML Canvas element. So, the whole application is
in one canvas. I think this would simplify the mapping of the AS UI
constructs into HTML5, since it would entirely ignore the HTML constructs
(except for Canvas, but even that could be shielded from the coder).
Of course it would be nice to be able to interact with the rest of the
HTML
page. But this could be done with ExternalInterface, or an enhanced
version
of it.
From what I understand most implementations of Canvas are not
performant enough yet to
actually handle a sufficiently complex Flex layout. Is Canvas at all
supported in all major
browsers?
cheers,
Roland
