On Wed, Mar 26, 2008 at 1:38 PM, Jack Doyle <[EMAIL PROTECTED]> wrote:
> When you're driving around town, there ain't much difference between a > Hummer and a Porche. They both get you from point A to B. If you're gonna > do > some off-roading, better warm up the Hummer. If you need speed and > agility, > get your racing gloves on and hop into the Porsche. :-) > We are programmers, we can't afford Porsches! Better change that to bike and skate... Anyway, I really think that most size optimizations should be made in your asset library, not in your code. So, you have a 80Kb filesize limit. Will 8Kb really make that much a difference? And if it does, well maybe your images could be encoded differently, or maybe you have a whole huge font embedded, which could be stripped down to a subset of characters that you really need. There's plenty of room to do size optimizations in your graphics, so you don't have to give up on code features. On the other hand, if a smaller code library fits you well enough, then just forget about all that ;) In the company I work, we use Tweener. Not actually by my own choice, but because the animation guys know how to use it well, so the tweens are already programmed when I touch the code. So much the better for me, will not complain ;) Still, I've never had any problems with filesize, not even on banners, which could only be solved by stripping some code out of it. Wagner Amaral _______________________________________________ Flashcoders mailing list Flashcoders@chattyfig.figleaf.com http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
