----- Original Message -----
From: "Paul Andrews" <[EMAIL PROTECTED]>
To: "Flash Coders List" <[email protected]>
Sent: Friday, September 19, 2008 4:34 PM
Subject: Re: [Flashcoders] RE: Optimising file size - stripping down
----- Original Message -----
From: "SJF" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Friday, September 19, 2008 4:10 PM
Subject: [Flashcoders] RE: Optimising file size - stripping down
Yes he was building components at the time, so maybe I have my wires
crossed.
Anyway, ignore the thread so far, what I would like to know is whether
it's
possible to strip out methods/capabilities from flash classes - for
example,
and to name a few, I don't need any of the following methods in any of my
classes that extend Sprite:
getObjectsUnderPoint
propertyIsEnumerable
areInaccessibleObjectsUnderPoint
So does anyone know if it's worth stripping down classes to the bare
minimum
- for optimization and player performance.
It's not something I have ever done. I can't imagine why it would give you
much (if anything). WHat it would do is make your classes less flexible
for the future and focussing on things that give you such small gains
takes attention away from the bigger picture.
My understanding is that if you have 50,000 instances of ClassA, stripping
out 3 methods from ClassA doesn't save you 50,000 x memory used by those
methods (if you never call them). You'll just save a bit of memory in the
class description, that's all.
Paul
I should add that I really had in mind stripping down classes generally. As
has been said elsewhere (and caused me a Doh! moment) standard classes are
built into the player so there's absolutely nothing to be gained at all.
Paul
Cheers. SJF.
_______________________________________________
Flashcoders mailing list
[email protected]
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
_______________________________________________
Flashcoders mailing list
[email protected]
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
