Geek asks and answers

Flex / Flash Builder: The right way to link to another project?

I have a rather large Flex / Flash Builder project using Flash Builder 4.5. I want to create another project that uses some components from this original project. In a new project, I associate resources with the original project, and it works fine, but the size of the new project file is quite large. It is close to the size of the project source file, although it uses only a fraction of the components and assets. Is there a better way to do this in order to minimize the file size of a new project?

+5
source share
2 answers

You should definitely see what compilation with the flag does -link-report. This prints a dependency map and shows you why you are using a lot of resources.

If you do not know how to do this: where you can add compiler arguments to the project parameters - usually FB adds -locale = en_US (which you really do not need), add -link -report = report.xml and compile. It will generate an xml file in the root directory of your project. Open it and check.

http://www.kahunaburger.com/2008/03/08/air-link-report-visualizer/ I did not use this program, but it seemed to give a nice visual representation of the dependencies - it can also be useful.

+3
source

, . FlashBuilder , , .

:

Flex app project A (swf) \
                           Flex library project (swc)
Flex app project B (swf) /

, , "" > " Flex", " ..." , .

add library project

, , . ( " " .)

choose link type

FB, -, A B. , . ( ):

  • : , , . , ClassA lib , ClassB - B .
  • RSL: , ; , , . , . , "" .

, . , ( , ).

, external, - , . , RSL .

+10

More articles:


All Articles