flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Harui <aha...@adobe.com>
Subject Re: [FLEXJS] Overlays and SWC Refactoring
Date Mon, 18 Nov 2013 21:23:54 GMT
OK, I've moved the as code into a subfolder.  The ant build for
FlexJSUI.swc is probably broken, but I'll be working on it and a
uber-script now.  But you should be able to modify AS classes after
pulling and any further work I do should not result in a conflict.


On 11/18/13 12:30 PM, "Alex Harui" <aharui@adobe.com> wrote:

>On 11/18/13 12:19 PM, "Erik de Bruin" <erik@ixsoftware.nl> wrote:
>>I'm clear. Sounds awesome! Let me know when the ant script is done,
>>I'll work it into a Jenkins job so we get a fresh overlay for each
>>commit to either Falcon(Jx) or FlexJS. Another advantage, besides
>>being always up to date, is that this way there will be a fixed URL
>>pointing to the latest and greatest overlay.
>>By the way, did you see my commit for the defaults for the command
>>line arguments to FalconJx? Having those should make the launch files
>>a bit lighter, not having to set these arguments and all.
>No, I missed that.  How does it work?  FalconJX is also picking up the
>-library-path and main mxml file from the FB config, but having a way to
>pick up the other options would be great too.
>One thing I see coming up is that if you have a big enough project to have
>your own SWCs, once you cross-compile that SWC to a folder of JS files,
>there is no automagic mapping of the library-path to the SWC to the folder
>of JS files for that SWC.  Maybe we can guess the folder of JS files from
>certain library-path entries?

View raw message