I'm currently working on a project for which the customer requires the SWF to
be very small, so I've been investigating how to reduce SWF sizes.
Flash Builder's compiler is smart enough to not include code for unreferenced
classes, but it seems to miss some other seemingly obvious opportunities
The issue here is that the compiler does not know that they will remain
unused and can not assume they will.
Why? Because if another swf file accesses the first file at runtime then
the second file may need the features.
___
Flashcoders mailing list
Thanks for the quick feedback. Is there any way to tell the compiler that the
SWF won't be loaded by another SWF, and that it's therefore safe to strip out
unreferenced features?
On 2011-09-17 , at 17:28 , Henrik Andersson wrote:
The issue here is that the compiler does not know that they
On 17/09/2011 10:48, Gerry Beauregard wrote:
Thanks for the quick feedback. Is there any way to tell the compiler that the
SWF won't be loaded by another SWF, and that it's therefore safe to strip out
unreferenced features?
I think you're flogging a dead horse, on this one..
Maybe put certain functions in their own swf and call at runtime?
Then the main swf will get smaller and you will control when and where
those functions get loaded and removed.
Just a thought.
Best,
Karl
On Sep 17, 2011, at 4:15 AM, Gerry Beauregard wrote:
It seems to me that a good
5 matches
Mail list logo
