On 11/1/16, 4:09 AM, "Christofer Dutz" <christofer.d...@codecentric.de>
wrote:
>Hi,
>
>
>
>so I cleaned up the MXMLFlexJSPublisher class greatly. Currently I’m
>trying to figgure out why the release output of 3 modules doesn’t seem to
>work. The thing is that I never tested the release versions of the
>original build, so I’ll probably be comparing the new to the old output
>first. But I did encounter some things I have questions about:
>
>1. I think it would be a good idea to omit this „marmotinini“
>conditional code. What needs to be done differently for a marmotini run
>should be passed in by configuration
Take it out and I'll see if checkintests still works. We might have
already bypassed the marmotinni code paths as far as checkintests is
concerned.
>
>2. The default for outputting stuff if no ouput-directory is
>specified is the directory containing the main class ... I would prefer
>it to be the current working directory
It is? I thought it was a level higher. SWF output goes in the same
directory as the main class, but JS output seems to go in the parent. If
I transpire foo/bar/MainClass.mxml, I think the output ends up in
foo/bin/js-debug.
Anyway, what if we had more intelligent defaults. If the main class is in
a "src" folder, then use the parent (IMO, that's more desirable for the
way Flash Builder sets up projects), if the main class is in a
src/main/flex folder, then use ../../../target.
>
>3. All (image) resources need to be located relative to the main
>application class. I think they should be relative to the/any source
>directories (Would like to have a separate source and a resource
>directory)
I'm not sure I want to spend time searching in lots of places, but having
one more place to look would be fine with me.
>
>4. The extern.js files seem to be dumped to the intermediate
>„debug-js“ directory. I think they should be dumped somewhere outsite
>(they should not be needed in the output)
Such as? Again, you could pick different places if you find the Main
Class is in a src/main/flex folder.
>
>
>
>There’s one part I didn’t quite understand:
>
>
>
>if (!googConfiguration.getSkipTranspile()) {
> appendEncodedCSS(projectIntermediateMainFile, projectName);
>}
>
>
>
>What does this do? Also I don’t understand the conditional of only
>requiring this if transpilation is not skipped (isn’t transpilation all
>the JS output is about ... so what’s the use of skiping transpilation?)
>Wouldn’t it be better to simply do a
The goal of -skip-transpile is to let someone generate the js-debug
version, muck with the results, then have FalconJX send the results to the
GCC without overwriting modifications with new generated code. So, first
you would run FalconJX with -debug=true to get the js-debug version, then
after you muck with the results, you would run FalconJX with -debug=false,
-skip-transpile=true and no JS or CSS files would be generated, just the
code where GCC is handed the js-debug folder and told to generate the
js-release folder should be run.
It is basically a short cut for calling GCC yourself from the command line
and lets you workaround any bugs in our code-generation.
-Alex
