I also find that, if you keep your classes appropriately succinct then all of your variables (and their types) are usually defined within close proximation to where you use them. Local variables are a lot more common, and your class properties should be intuitively descriptive of what they do in that context.
Properties of the class should also be handled internally, even if they're accessable externally. For example, the skin property of a component is probably a MovieClip, but someone using the component class should use a styles object to manipulate its appearance. This of course isn't always necessary, especially if you want to allow the greatest amount of flexibility, but if you follow some basic OOP principles it makes special naming conventions unnescessary. Good luck with AS2.0, it's a new world even if it's the syntax isn't that different. Tyler _______________________________________________ Flashcoders mailing list [email protected] http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
