Home → Questions →

Can swf project add modules as flashbuilder project do?

• Edit

cwocwo

15 Jun, 2012 07:38 AM

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<actionScriptProperties analytics="false" mainApplicationPath="rhin.mxml" projectUUID="18fbebb5-899e-48e8-bdf3-db6326990839" version="10">
  <compiler additionalCompilerArguments="-locale zh_CN,en_US" autoRSLOrdering="true" copyDependentFiles="true" fteInMXComponents="false" generateAccessible="true" htmlExpressInstall="true" htmlGenerate="true" htmlHistoryManagement="true" htmlPlayerVersionCheck="true" includeNetmonSwc="false" outputFolderPath="bin-debug" removeUnusedRSL="true" sourceFolderPath="src" strict="true" targetPlayerVersion="0.0.0" useApolloConfig="false" useDebugRSLSwfs="true" verifyDigests="true" warn="true">
    <compilerSourcePath/>
    <libraryPath defaultLinkType="0">
      <libraryPathEntry kind="4" path="">
        <excludedEntries>
          <libraryPathEntry kind="3" linkType="1" path="${PROJECT_FRAMEWORKS}/libs/flex.swc" useDefaultLinkType="false"/>
          <libraryPathEntry kind="3" linkType="1" path="${PROJECT_FRAMEWORKS}/libs/core.swc" useDefaultLinkType="false"/>
        </excludedEntries>
      </libraryPathEntry>
      <libraryPathEntry kind="1" linkType="1" path="libs"/>
    </libraryPath>
    <sourceAttachmentPath/>
  </compiler>
  <applications>
    <application path="Main.mxml"/>
  </applications>
  <modules>
    <module application="src/Main.mxml" destPath="modules/admin/AnalyzeLogModule.swf" optimize="true" sourcePath="src/modules/admin/AnalyzeLogModule.mxml"/>
  </modules>
  <buildCSSFiles/>
  <flashCatalyst validateFlashCatalystCompatibility="false"/>
</actionScriptProperties>

like this:

 <modules>
    <module application="src/Main.mxml" destPath="modules/admin/AnalyzeLogModule.swf" optimize="true" sourcePath="src/modules/admin/AnalyzeLogModule.mxml"/>
  </modules>

1. Support Staff 1 Posted by Maxime Cowez on 15 Jun, 2012 08:18 AM

   

   You raise a good question. I must admit I haven't thought of modules when creating the 'flashbuilder' plugin. So those 'module' tags will definitely not be generated there.

   As for the core gradlefx functionality: Yennick will have to confirm this, but I don't think there is a convention property to support this. Of course you can do anything you want with the additionalCompilerOptions.

   At first glance, this seems to be related to optimizing modules for the main application. More information on that topic can be found here: http://help.adobe.com/en_US/flex/using/WS2db454920e96a9e51e63e3d11c...

   • Edit

2. Support Staff 2 Posted by Maxime Cowez on 15 Jun, 2012 08:34 AM

   

   I've given it some thought. I think we'll have to introduce a module dependency scope. But if we want to be able to do the optimization, this can only be done with project dependencies, not precompiled artifacts.

   I've created an issue to put it on the wishlist: https://github.com/GradleFx/GradleFx/issues/46

   It's worth investigating how FlexMojos handles this, if it does.

   • Edit

3. 3 Posted by cwocwo on 15 Jun, 2012 09:52 AM

   

   I have tried -link-report and -load-externs, but the result was not I ecpected.

   • Edit

4. Support Staff 4 Posted by Maxime Cowez on 15 Jun, 2012 11:18 AM

   

   Can you elaborate on what you've tried? And what the results or possible errors were?

   • Edit

5. Support Staff 5 Posted by Yennick Trevels on 17 Jun, 2012 06:21 PM

   

   I have to be honest that I haven't used flex modules yet, so I don't know whether it's possible with GradleFx. So I'll see whether I can put a sample project together. I'll probably look at how it's done in FlexMojos, so I'm going to follow this post http://www.adobe.com/es/devnet/flex/articles/flex-maven-flexmojos-p... :)

   • Edit

6. Support Staff 6 Posted by Maxime Cowez on 18 Jun, 2012 12:32 PM

   

   Basically, the trick seems to consist of publishing the module's generated link-report as an artifact and then using that as an additional dependency in the main application build script.

   • Edit