RE: [flexcoders] class signature convention

[Gordon Smith]

Best practice is to use fully qualified class names only when necessary for disambiguation (when the same class name has been imported from more than one package). So the generated code should really be       import mx.containers.TabNavigator;       public class TEOTabNavigator extends TabNavigator     {         ...     }   - Gordon   From: flexcoders@yahoogroups.com [mailto:flexcoders@yahoogroups.com] On Behalf Of Teoti Graphix Sent: Tuesday, February 14, 2006 3:48 AM To: flexcoders@yahoogroups.com Subject: [flexcoders] class signature convention   Hello, I have noticed from alpha to beta when the class is created, Flex builder now inserts public class TEOTabNavigator extends mx.containers.TabNavigator uses the fully qualified pacakge for the super class. The question is; is this a new convention, should we do this or is the import being fully qualified enough of a hint as to where the superclass originates.? To me, it seems redundent. Peace, Mike -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com SPONSORED LINKS Web site design development Computer software development Software design and development Macromedia flex Software development best practice YAHOO! GROUPS LINKS  Visit your group "flexcoders" on the web.    To unsubscribe from this group, send an email to:  [EMAIL PROTECTED]    Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.