Scopes…

Hi guys…

Let’s put on the table flex-mojos scopes.

Library dependencies can be add on SWC or SWF projects.

For SWC, 3 scopes make sense:

    merged: this is the default value, when not defined will assume merged. That means SWC file will be bigger and self sufficient.
    internal: all dependency content will be included on target SWC. Biggest SWC
    external: no dependency content will be included on target SWC. Smaller SWC

And for SWF we have 2 more:

    rsl: no dependency content will be included on target SWC. Smaller SWF and will load library content at runtime.
    caching: same as rsl. But will ask at runtime for Adobe’s signed library.

Is possible to use RSL and CACHING when compiling SWC files. But I strongly recommend you don’t. Why? Well, make no sense on library loading content at runtime because we don’t run libraries. (Or I’m miss informed =p)

I like to external dependencies for libraries (SWC projects). That’s how I did it, that’s how Adobe does it, and it’s worked out pretty well so far ;)

On SWF project I use caching, rsl and merged. On modules only use external. Again, that is me. On my projects that values showed less memory usage. I did some tests at work, will ask my boss to release on internet, let’s see…

If someone can explain better each scope, please post it on comment and I will update this.

VELO

2 Responses to “Scopes…”

  1. Flex-Mojos » Adding libraries to compilation… Says:

    […] To read more about flex-mojos scopes click here. […]

  2. how to run swf file Says:

    […] […]

Leave a Reply