Module structure/limitation on single allocation of folder with Flash

I have posted this once on the forum and once on the youtrack. Here is a concrete manifestation of the problem of limiting allocation of a folder to one module in a project.

Flash modules are not capable of being dependant on other modules. Therefore it is impossible to have a shared src folder library. Very big problem.

Fundamentally, this limit holds no purpose whatsoever as far as I can tell. Please change it.

5 comments
Comment actions Permalink

So the workflow becomes having a single module for all flash modules and impossible to create swcs with a shared src folder.

0
Comment actions Permalink

Flash modules are certainly capable of being dependant on other modules. The dependencies are set up in the "Dependencies" tab of a build configuration.

The module settings include the module dependencies and libraries, which define how references from the source code are resolved. If it was possible to add the same directory to multiple modules, there would be no way to uniquely resolve references from files in that directory.

0
Comment actions Permalink

How does one add another flash module as a dependency? Clicking on add Build Configuration... results in "No applicable build configurations found". Clicking on "Shared library" is a similar message. One can add a folder dependency. Forgot about that when posting this thread. Is that what you mean?

0
Comment actions Permalink

Well, strictly speaking since IntelliJ IDEA 11.1 there's no such thing as Flash module-on-module dependency. Each Flash module may contain one or more build configurations (BCs), which can depend on each other. So if you have library BC in Module1 (i.e. it produces *.swc) and any other type of build configuration in Module2, you can setup dependency of BC from Module2 on BC from Module1. You have seen "No applicable build configurations found" because you didn't have any SWC build configuration in the project (and there's no sense in app-on-app dependency).
One other type of BC-opn-BC dependency is 'loads it runtime'. That means that you may have one BC producing 'Runtime loaded module' (SWF) and the other BC (producing app) may depend on runtime-loaded module.
Shared library (i.e. project or global level library) stands for 3rd party library like flexunit, robotlegs or whatever. It can be an uncompiled raw ActionScript library, but in any case it should not contain your own sources that you edit yourself.
See more here http://blogs.jetbrains.com/idea/2012/02/new-flex-project-setup/

0
Comment actions Permalink

You definitely shouldn't create a single module for a large project, and it IS possible (and recommended) to create swc for shared code. See my second answer in this thread for details.

0

Please sign in to leave a comment.