If you have multiple modules in the compile, am I right to think the
link report only shows the info for the last module built?
That's how it seems, but perhaps I'm just missing something...
Guy
On 01/04/2009, at 4:32 PM, Alex Harui wrote:
Yeah, you can specify a more sophisticated path to get it to show up
elsewhere. There are some third-party link-report viewing tools
available as well. I don’t recall the names.
One final tip: Don’t link in Donuts.SWC ;-)
Alex Harui
Flex SDK Developer
Adobe Systems Inc.
Blog: http://blogs.adobe.com/aharui
From: [email protected] [mailto:[email protected]]
On Behalf Of dorkie dork from dorktown
Sent: Tuesday, March 31, 2009 10:17 PM
To: [email protected]
Subject: Re: [flexcoders]Where does my SWF gain it's weight?
Hi Alex,
Thanks,
FFR - "–link-report outputfile.xml", shows up in bin-debug.
On Sat, Mar 28, 2009 at 11:15 AM, Alex Harui <[email protected]> wrote:
Use –link-report. The sizes aren’t accurate as absolute, but are as
relative sizes
Alex Harui
Flex SDK Developer
Adobe Systems Inc.
Blog: http://blogs.adobe.com/aharui
From: [email protected]
[mailto:[email protected]]on Behalf Of Nicolas Noben
Sent: Friday, March 27, 2009 5:23 PM
To: [email protected]
Subject: Re: [flexcoders]Where does my SWF gain it's weight?
Yeah make a search through all the files for 'Embed' and make sure
that everything that is embedded really needs to be. That's the
biggest hog.
Also make sure your final build is published using 'Export release
build'. You will save a fair bit at release time.
But it's mostly assets' fault. Unless you've added plenty of custom
components who extend default ones..
HTH
--
Nicolas Noben
P http://noben.org
B http://idletogether.com
T http://twitter.com/keyle
--- In [email protected], dorkie dork from dorktown
<dorkiedorkfromdorkt...@...> wrote:
>
> Is there a tool or a way to find out what classes are making my
SWF fat?
>
> It's been a few months since I last checked my SWF file size and
it's 1.2mb.
> It used to be 600kb and I've made so many changes since then I
don't know
> where the weight is coming in.
>