flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Harui <aha...@adobe.com>
Subject Re: FlexJS metadata / reflection
Date Sun, 17 Jan 2016 07:07:48 GMT

On 1/16/16, 10:55 PM, "jude" <flexcapacitor@gmail.com> wrote:

>I'm talking about a live preview that's created from the MXML markup. It
>doesn't pay attention to any of the AS. The components are created on the
>fly from the XML. There would be no interaction.
>With your live coding example, you start coding and when you save you
>create a new swf. That swf is watched (or would be watched) and it's then
>reloaded when the date has changed. Now you reload it and you have a fully
>debug swf you can interact with.

No, the SWF is not reloaded in my POC.  A LocalConnection (and in the
future, a socket) is used to communicate changes detected in the file
directly to the already running SWF.  No compiler is involved there
either, only to create the initial SWF, although we could rely on it to
prove that your changes compiled correctly.

>If you only need to preview one MXML page at a time and it doesn't have to
>be interactive, it might be much faster to parse the MXML of that page on
>the fly.

In theory, this POC could watch multiple MXML files.

>Let me be clear, creating a compiled fully interactive SWF is preferable
>and what I'm talking about has clear disadvantages, but if we want to have
>something that someone can try in the browser, that doesn't require access
>to a compiler, it's possible to parse the FlexJS markup and create the
>layout. If someone can setup the FlexJS compiler on the server then you
>wouldn't need what I'm suggesting.

Om suggested a JSFiddle like compiler-on-the-server.  It should be


View raw message