I agree that building everything in one command should be the goal. I do not think that HTML should be part of the compiler. Isn't there a way to wrap both the compile step and the HTML generation into one script, like I did in ant with the publisher, but maybe in an extended version of MXMLC?
EdB On Tue, Jan 29, 2013 at 6:58 PM, Alex Harui <aha...@adobe.com> wrote: > Any objections to adding a feature to Falcon/FalconJS/FalconJX to take > additional arguments and fix up the HTML wrapper (or –app.xml for AIR)? I > know compilers really should just compile, but the compiler knows much of the > information that needs to be substituted into those files. > > For Falcon, I would add an option like –html.template=<path to html template> > and –air.template=<path to –app.xml template> > > FalconJS/FalconJX would also support –js.source-path=<path to more JS source> > to point to the framework (and goog if we use that) files. > > Thoughts? > > -- > Alex Harui > Flex SDK Team > Adobe Systems, Inc. > http://blogs.adobe.com/aharui -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
