Thanks Alex for your answer,
I don't count too much on FalconJS, but as Michael Chaize told us, it
gives a good starting point of a research to identify which points have
to be solved to get a full trans compilation to HTLM5.
So i'm couting on the background research of what is needed, more than
what has already been done.
By the way, with FalconJS donation, will you also give some documentions
regarding this reasearch?
"I don't have one, but it would be great to construct such a list. I
don't know HTML/JS well enough to help too much."
I was talking about a generic list of what makes Flex linked to Adobe
runtime, everything that is used directly from the runtime, like
DisplayList, events, e4x, and would need to be dropped or emulated if we
need to target other runtimes. Again such list must have been done in a
way or another to start flaconJS i think.
But i was not talking about any specific target runtime, so there's no
need to know HTML/JS to get this list, but it needs to know well the
flex SDK.
Regards
On 10/19/12 8:35 AM, "sébastien Paturel" <sebpatu.f...@gmail.com> wrote:
Questions are:
- Do we have a clear view of what tie the Flex SDK to the Adobe's
runtime, and need to be handled for a multi target strategy? in the
rendering layer but also everything else?
If we identify clearly what are the difficult points, it would be more
easy to take decisions, of what can be dropped (like e4x) and what need
a solution.
It seems that the work on FalconJS has already given a good start on
such information.
Don't count too much on FalconJS having all the answers. It was just a
prototype.
Can we have a clear list of such issues?
I don't have one, but it would be great to construct such a list. I don't
know HTML/JS well enough to help too much.
