On Apr 15, 2006, at 8:19 AM, Jim Kremens wrote:
IMHO, the code is very procedural, not object oriented. The cues for this are the endless conditional statements. A good, encapsulated architecture can greatly minimize these...
I can see part of your point, but to me Javascript (and Actionscript) is a prototype language, not a class-based language and I don't really find his code very difficult (it looks like the AS 1 that I have been writing for years). I would have a hard time understanding how to write a detection script that was any less "procedural", and I would love to see an example.
More specifically, what is that you want to do that you are not able? I am just wondering on a practical level, because sometimes people stress over "OOP" in a dogmatic way, but lose the forest through the trees. OOP just for the sake of OOP creates a lot of overhead sometimes that is not necessary - especially when scripting.
What did you want to do with it that you couldn't? Do you think the runtime performance/speed of the script is adversely affected? Are you talking theoretically, or are there really methods that you wanted to add to FlashObject but couldn't do it?
Did you want to build a class that inherits from FlashObject, but was prevented?
I am really just curious - I have no vested interest one way or another, just trying to understand other people's point of view.
blue skies, bryan _______________________________________________ Flashcoders@chattyfig.figleaf.com To change your subscription options or search the archive: http://chattyfig.figleaf.com/mailman/listinfo/flashcoders Brought to you by Fig Leaf Software Premier Authorized Adobe Consulting and Training http://www.figleaf.com http://training.figleaf.com
