Although the numbers are not correct in absolute terms (generally they are inflated by a factor of 6 or so), they are quite useful as a proportional measure of where the code size lies in the app. In typical Flex apps, shared constants do not seem to take up a very large portion of the code.

ItDepends does in fact have the same diff capability built into it — if you create a child module window from the main app window, and drag app classes into the module, all the dependencies removed from the main app will travel into the module.

In the meantime ItDepends does have a crude ability to read the output dumps from the SwfxPrinter tool and map the printed function names back into the classes they come from. Those code sizes are super accurate but of course there is no dependency info there.

For one, they are unoptimized (I forget if I committed an update to the link report which spits out a slightly optimized value as well). The biggest issue is that they don’t take into account the constant pool — if 100 strings are shared between two classes, each class will report that they take up the space of 100 strings, and the size changes between compiles depending on other factors.

I find the link report most useful to track new and removed dependencies. I should probably open-source my diff tool.

One of the issues I occasionally run into when porting code is a dependency on a class that may only be referenced in a string. For example, a dataTipRenderer for a chart. Does your application locate those dependencies as well?