I think I get it.
I thought that the source code for js.swc was in
$FLEX_HOME/frameworks/js/FlexJS/src.
I guess that is not true?
The original problem was that asjsc does not create the index.html file. I
was asked to use mxmlc for that. (Refer to the npm install flexjs thread)
When I used the script in {installed_flexjs}/js/bin/mxmlc, it blew up
because it could not find the definitions for HTMLElement, SVGElement etc.
because they are in js.swc. I don't think it blew up because of the
missing /frameworks/js/FlexJS/src folder. Adding the external library path
to js.swc fixed this issue.
The way I did this was to create a new mxmlcnpm script and add this js.swc
library path in that. Is that okay?
I guess another question is: what would be the best way to add ability to
create index.html capability to asjsc?
Thanks,
Om
On Mon, Jan 4, 2016 at 4:16 PM, Alex Harui <[email protected]> wrote:
>
>
> On 1/4/16, 4:09 PM, "[email protected] on behalf of OmPrakash Muppirala"
> <[email protected] on behalf of [email protected]> wrote:
>
> >In the flexjs/js/bin/mxmlc script, I see that we are referencing the '
> >*/frameworks/js/FlexJS/src*' folder.
>
> This folder is intended as the place for folks to put monkey-patched JS
> files so they can override the JS in the SWCs if they need to workaround a
> bug.
>
> What code blew up? Maybe we should create an empty folder there or make
> the compiler tolerant of it not being there.
>
> Trying to use js.swc with MXMLC is not currently the common configuration
> for FlexJS. Most folks who are using MXML and AS to build a FlexJS app
> shouldn't need to write directly the the JS API especially if they want to
> use a SWF version for testing and/or deployment.
>
> If you want to build out a different script for folks to use to build
> native apps, feel free to do that.
>
> -Aleex
>
>
