IMO, you are welcome to do more, but as long as you don't break existing
functionality, or make it harder to make improvements later, doing just
what you need is completely acceptable, so I think your current set of
proposed changes is fine.
-Alex
On 12/9/13 8:02 AM, "Stephan Plath" wrote:
>Am
Am 09.12.2013 15:32, schrieb Mr. Rich:
Personally, I've always used ant to automate the wrappers.
The Flex SDK is released together with
${FLEX_HOME}/ant/lib/flexTasks.jar which provides the following ant tasks
mxmlc=flex.ant.MxmlcTask
compc=flex.ant.CompcTask
html-wrapper=flex.ant.HtmlWrapp
While you're in ant, automate your project assets also. Setup a main
workspace asset repo, pull files from there.
Another good trick, if you have multiple projects that work together, use
ant to create a main output folder and compile files there.
On Dec 9, 2013 4:17 AM, "Stephan Plath" wrote:
Personally, I've always used ant to automate the wrappers.
Just my 2 cents.
On Dec 9, 2013 4:17 AM, "Stephan Plath" wrote:
> The current version of the Ant html-wrapper task doesn't supports to use
> external files. Instead it only uses its embedded template resources
>
> - /history
> - histor
