Open GoogleCodeExporter opened 9 years ago
I don't know how this is accomplished in other IDE's. Flash Builder can do
this, and I think the Flash IDE has some connection going to Flash Builder too.
If you could provide technical details on how it's done I'm sure it's a fast
thing to implement.
Original comment by petterson.erik@gmail.com
on 23 Aug 2010 at 7:43
Original comment by petterson.erik@gmail.com
on 25 Aug 2010 at 10:44
http://help.adobe.com/en_US/flash/cs/extend/WSb03e830bd6f770ee-370b396312677c9b3
56-8000.html
SNIP
Description
Method; publishes a FLA file without opening it. This API opens the FLA in a
headless mode and publishes the SWF (or whatever the profile is set to). The
second parameter (publishProfile) is optional. The return value is a boolean
indicating if the profile was found or not. In the case where the second
parameter is not supplied, the return value is always true.
Example
The following example prompts the user to select a FLA file and silently
publishes it using the “Default” publish profile:
var uri = fl.browseForFileURL("select", "select a FLA file to publish");
var publishProfileName = "Default";
fl.publishDocument(uri, publishProfileName);
Original comment by petterson.erik@gmail.com
on 22 Sep 2010 at 9:35
There is a bug filed in Adobe JIRA (login required) around this issue, which
basically adds command line support to compile FLA files:
http://bugs.adobe.com/jira/browse/FB-13217
There is also Fluant, an Ant task, which seems to work for some people but I
could not get to work reliably initially (and have rewritten large chunks).
But, the author seems to have updated it since I first used it:
http://fluant.riaforge.org/
Fluant uses a basic structure which I'd use, which is to do the following:
1. Write a generalized JSFL file to the disk
2. Command to open Flash.exe, opening the JSFL file
2. Open the FLA with the JSFL file
3. Attach publish settings to the FLA with JSFL
4. Have the JSFL call the publish routine
5. Have the JSFL close out Flash when complete
If the core code is correctly written, the Ant task would be a thin wrapper to
the core code, allowing the ability to have another thin wrapper which is a
command line java program to do the same routine.
Original comment by EpochofE...@gmail.com
on 22 Sep 2010 at 10:18
I've now added basic support for this (compiling).
It parses the errors yielded, if any, but it's not 100% solid that code.
The method is close to what you describe, it writes out a JSFL file & does
file.openWithDefaultApplication() on it
Path-handing is a bit mac-only now, but that's easily fixed (if one has a
windows machine at least).
Original comment by petterson.erik@gmail.com
on 30 May 2011 at 10:58
Original issue reported on code.google.com by
adrian.s...@gmail.com
on 16 Aug 2010 at 9:03