[osflash] Know how many kb each class adds to the SWF when compiling with MTASC
spjwebster at gmail.com
Fri Aug 4 05:21:02 EDT 2006
On 8/4/06, Ralf Bokelberg <ralf.bokelberg at gmail.com> wrote:
> > How does class size really help there?
> It helps to decide if it makes sense to put the classes in different
> swfs for example.
> Also it helps to decide if it is better to divide a large class into
> two or more classes.
Such decisions should probably be based on the source code and not the
compiled byte-code size.
As a general rule of thumb, it's likely that a class whose source code
is twice the size of another will produce twice as much bytecode.
Unless, of course, once of them has an insane amount of whitespace.
> > It sounds like what you actually want is a tool that generates a
> > dependency graph
> This could be useful too, but its the second step. First you need to
> know the size of a single class to be able to calculate the size of
> your graph.
This sounds much more useful to me as full dependancies aren't
immediately obvious by looking at the code.
Just my 2p.
More information about the osflash