Well as soon as I have the FlexToolApi in place I think it should be possible for me to sort of write a Tool adapter mechanism for Flexmojos that adds arguments to the commandline, depending on the selected tool-group.
So I guess it's not that bad. But it will be nessecary to implement the API otherwise doing all by hand is a hack I'm not willing to implement. After all I don't want to create a beast that will be a curse for me to maintain. Chris. -----Ursprüngliche Nachricht----- Von: Alex Harui [mailto:aha...@adobe.com] Gesendet: Mittwoch, 5. November 2014 16:53 An: dev@flex.apache.org Betreff: Re: AW: [FALCONJX] Added maven artifact generation for falcon.jx ... what now? Well, that’s the way it works today. We can certainly change things if needed. I haven’t tried it, but in theory you could have these additional parameter specified in a -config.xml file. The problem is that normally you have one config file per-project not per-target. We could teach Falcon to ignore every option in -compiler.js.XXX I haven’t looked at any other cross-compiling or porting tools, especially in Maven, but I would think any time you can have multiple output formats you might need to specify additional options. If there is a Maven convention for doing that, I’m open to doing that for FalconJX. -Alex On 11/5/14, 2:57 AM, "Christofer Dutz" <christofer.d...@c-ware.de> wrote: >Oh gee ... this looks like a lot of work :-( Why do we need an explicit >reference to the closure lib? I added this as dependency to the pom of >falcon.jx so it should be available out of the box. Same with the path >to playerglobal as this is usually a dependency of the flex project and >hereby passed in to the compiler via command-line arguments. > >So assuming I have a module and I want to compile it the usual way with >Flacon, I don't need the js-output-type and sdk-js-lib options but >compile it normally with Falcon ... the output would be a SWF/SWC as >usual. But if I want some JS output, I have to use the other COMPJSC >and MXMLJSC and provide these additional arguments? > >Chris > > >________________________________________ >Von: Erik de Bruin <e...@ixsoftware.nl> >Gesendet: Mittwoch, 5. November 2014 11:33 >An: dev@flex.apache.org >Betreff: Re: [FALCONJX] Added maven artifact generation for falcon.jx ... >what now? > >> >> Now If I add a "compilerClass"property to Flexmojos and point that to >>COMPJSC, I should be able to use FalconJX in Flexmojos. But could you >>please explain what else needs to be done in order to use FlexJS and >>VF2JS? >> As far as I understood in order to use FlexJS I would need to >>reference the flex-asjs library instead of the normal flex framework >>libraries (Hope that's correct), but what would I need to do to use >>VF2JS? I am expecting to be able to continue to use the normal Flex >>Framework libraries. >> > >In order to use either of the 2 JS implementations, you need to add >several command line arguments: > >-js-output-type=FlexJS (or VF2JS) >-sdk-js-lib="[pathToJSLib]" >-closure-lib="[pathToGoogleClosureLibrary]" > >in addition to the 'regular' command line arguments: > >+env.PLAYERGLOBAL_HOME="[pathToPlayerGlobal]" >+playerglobal.version=15.0 >-load-config="[pathToFlexSDK]/frameworks/flex-config.xml" >-output="[pathToOutputDir]" >"[pathToProjectFile]" > >EdB > > > >-- >Ix Multimedia Software > >Jan Luykenstraat 27 >3521 VB Utrecht > >T. 06-51952295 >I. www.ixsoftware.nl
