>>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.
They are actually overrides of the defaults set in the Configuration class and it's super classes. Nothing special, nothing dynamic ;-) > 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? You mean: how does my main project (JS version) connect to the SWC (JS version, compiled previously/separately)? Not sure if that's possible at all, as I said in a previous thread. The GCC process ALL files together, calculating dependencies and renaming/inlining whatever it finds, from all over the files. Now, there are way to 'publish' the API of one project/SWC (export, externs) and tell another project about it, but I'm not sure we'll be able to that automagically... EdB -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
