I didn’t try MXML, just AS. On 6/12/15, 8:42 AM, "Michael Schmalle" <teotigraphix...@gmail.com> wrote:
>Alex, so did the initial jsc require an MXML file for the main? So the way >it is now, we can pass an mxml or as main file and it will basically treat >them the same but, JS.swc is added to the library path for DOM features, >correct? > >Mike > >On Fri, Jun 12, 2015 at 11:28 AM, Alex Harui <aha...@adobe.com> wrote: > >> >> >> On 6/12/15, 7:39 AM, "Michael Schmalle" <teotigraphix...@gmail.com> >>wrote: >> >> > >> >Ah yeah ok I get that but it was more about the "refactoring the >>Installer >> >source for the Git-Split", I wasn't explicit about that. >> >> The Installer is in the flex-utilities repo along with many other >> “products” like Squiggly and Tour De Flex and Mavenizer and really, they >> should each have their own repo. But we have to put all code destined >>for >> a new repo under a single top-level folder. >> >> > >> >So do you have it automatically adding JS.swc to any build in FlexJS? >>Or >> >is >> >the 'jsc' to including the JS.swc, I am not good at understanding this >> >stuff yet. >> >> JS.swc is in the FalconJX Nightly, and I hope the next time the Falcon >> build passes the additional scripts will be in the right place and run >> correctly when Falcon gets installed as part of the FlexJS install. >> >> -Alex >> >>
