[osflash] Know how many kb each class adds to the SWF when compiling with MTASC
David Rorex
drorex at gmail.com
Wed Aug 16 20:30:50 EDT 2006
To bring back an old topic:
Size reporting would be useful, but I own a copy of Burak's
ActionscriptViewer, which shows the size of each compiled class.
What I am more interested in, is dependancy tracking. I'd like to be
able to use Makefiles to compile my project, and if mtasc would output
class dependancy, this would greatly simplify things. For example:
$ mtasc -printdeps -swf output.swf Main.as
would output:
> output.swf: Main.as OtherClass.as ThirdClass.as
>
> Main.as: MyObj.as OtherObj.as
>
> OtherClass.as:
>
> ThirdClass.as: DebugObj.as
Showing that output.swf depends on Main.as, OtherClass.as,
ThirdClass.as, and Main.as depends on MyObj.as, OtherObj.as, etc etc
That way, I could easily build makefiles, such that when I modify a
couple classes, make will then know exactly which SWFs need to be
rebuilt (I have several in a project).
Hopefully you will consider something like this for addition to either
mainline mtasc, or hamtasc.
Thanks
-David R
On 8/4/06, Steve Webster <spjwebster at gmail.com> wrote:
> 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.
>
> Cheers,
>
> Steve
>
> --
> Steve Webster
> http://dynamicflash.com
>
> _______________________________________________
> osflash mailing list
> osflash at osflash.org
> http://osflash.org/mailman/listinfo/osflash_osflash.org
>
More information about the osflash
mailing list