I see your point. I think it depends mainly of the name of the variable, and the documentation.
in my opinion, includeAirLibs or useAirDependencies (probably there´s something better), don´t have such a connotation, and it´s way better then having to put the airglobal before playerglobal, which may be hard to accomplish in a project with a lot of dependencies. Is there any other way, besides de airglobal/playerglobal order? On 2 fev, 13:32, Marvin Froeder <[email protected]> wrote: > I'm always against that. From the project characteristics flexmojos should > be able to tell if it is flex or air project. Otherwise people will make a > plain SWF project and complain that flexmojos didn't force it into a AIR > because the said is air == true > > On Wed, Feb 2, 2011 at 1:26 PM, Luiz Rolim > <[email protected]>wrote: > > > > > > > > > Velo, > > about the playerglobal/airglobal problem,what do u think about > > including a boolean property for distinguishing between AIR/FLEX > > projects (perhaps, "includeAirLibs" or "isAirProject"). > > > I think it would simplify the code a lot. -- You received this message because you are subscribed to the Google Groups "Flex Mojos" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/flex-mojos http://flexmojos.sonatype.org/
