flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Harui <aha...@adobe.com>
Subject [FLEXJS] Named Configs for JS, JQuery, Node, and CreateJS
Date Wed, 08 Jun 2016 16:34:15 GMT

I just pushed changes to create more named configs for FlexJS.  I don't
know how many folks were aware, but named configs can be used to more
easily switch defaults at compile time.  If you've ever built both Web and
AIR/Mobile apps, you were using named configs whether you knew it or not.

The compiler supports a +configname option.  The default configname is
"flex" which is why, when building Web apps, the compiler uses
flex-config.xml.  But when you compile an AIR app, especially if you use
command-line launchers like amxmlc instead of mxmlc, your compile settings
either specifically said to use air-config.xml, or used +configname=air to
tell the compiler to use air-config.xml instead of flex-config.xml.

The changes I just pushed add more named configs, so you can use
+configname=js to get the default compiler options for JS-only projects,
or +configname=node to get default compiler options for NodeJS projects,
and similar for JQuery and CreateJS projects.

By packaging defaults into named config files, it will hopefully make it
easier for IDE vendors to keep up with changes to FlexJS.  Instead of each
IDE vendor needing to know the full set of SWCs and other options for the
various project types, they should now be able to tell the compiler to
load one of these -config.xml files instead.  I'm hopeful, for example,
that FDT will do such a thing.  We've been discussing it in this JIRA
issue: http://bugs.powerflasher.com/jira/browse/FDT-3661


View raw message