On 12/3/13 2:38 PM, "David Coleman" <david_coleman_...@hotmail.com> wrote:
>Actually Alex, what is the biggest culprit in our file is Greensock, and >after that, a whole mess of engine logic needed to handle the interface >with the games. Also some of our legacy animations use Tweener, so for >now I'm cursed with having to include BOTH libs in the main app. > >I also think that 500K is too much and like I said, each version I >whittle it down a little more. > >I've often thought of loading the engine container as a module to remove >another 100K or so from the main app. > >How would i create a custom RSL? Can I automate it via ant to generate >it via the link-reports? I'd like to keep one RSL for ALL files, app, >and modules to increase cache hits, and not hit a different file each >time. > >I'm really curious to experiment with this. It's ok if the browser cache >expires, that's beyond my control, but 99% of the time it will be a >benefit - I'm ok with those numbers. I asked this in the other reply, but how will that save you over a single monolithic SWF? If you're not in the cache, then instead of loading two things, one of which may contain classes you don't need until later, you only load what you need when you need it. -Alex
