symbols with no linkage and no class attached: mc:movieclip_name btn:button_name gf:graphic_name
Since the library defaults to sorting items by name, items of the same type are then grouped. Everything else (components) starts with an uppercase (and camelcase) ComboBox MyCoolComponent Application etc.. And those end up in folders (and their assets in subfolders) with folder names indicating what they are Forms Controls Containers etc.. regards, Muzak ----- Original Message ----- From: "Steven Sacks" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Thursday, May 10, 2007 8:40 PM Subject: Re: [Flashcoders] looking for library naming conventions >I use the following naming conventions for both library and instance. > > MC_Foo for movieclips > > BTN_Foo for buttons or movieclips that behave as buttons > > GR_Foo for Graphic Symbols > > FONT_Foo for font symbols and their linkage IDs > > VID_Foo for Video symbols, not for instances, though > > > I use the following instance names for items that have no library item > associated with them. > > TXT_Foo for dynamic text fields > > INP_Foo for input text fields > > CMB_Foo for combo boxes > > RB_Foo for radio buttons > RBG_Foo for radio button groups > > SP_ for scrollpanes > > FLV_Foo for FLV players > > etc. You get the idea. > > My naming convention is 100% dedicated to code readability. At a glance, I > can identify movieclips, textfields, components, etc. > apart from eachother and from variables. It makes them stand out very well > and makes debugging so much faster when I don't have > to go hunting for anything. > _______________________________________________ [email protected] 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
