Naming Convention for creating an ID:
- The first 2 letters of the Object's name should be the initial of creater's full-name in capital, for e.g., AK for Abhishek Kumar.
- The third letter place of the Object's name should consist the alloted project-id, for e.g., MercedesAMG's project-id is 1.
- The next letter place of the Object's name should be 'P' that means Project, and it acts as a separater (from further id's) in the Object's name.
- The next letter place of the Object's name should consist the alloted module-id, for e.g., module-id of MercedesAMG's minisite is 1 and it's form is 2.
- The next letter place of the Object's name should be 'M' that means Module, and it is a separater in the Object's name.
Below are some sample ID's that is created by following the above naming convention,
AK1P1M, AK1P2M, ..., AK27P15M, etc.
Similarly, Vijay Bisht's ID will be
VB1P1M, VB1P2M, ..., VB27P15M, etc.
And, Dulani Chandni's ID will be
DC1P1M, DC1P2M, ..., DC27P15M, etc.
Naming Convention for *.fla file:
- The first portion of the name should be the ID (as per the above naming convention).
- After that there should be an underscore '_'.
- Then there should be the relevent-name or description of the module, say, Leaderboard, Minisite, Skyscrapper, etc.
Below are some sample names for *.fla file using above mentioned naming convention,
AK27P15M_Form, AK1P2M_Leaderboard, AK5P2M_BudwiserMinisite, etc.
Naming Convention for Object-name in flash file:
- The first portion of the name should be the ID (as per the naming convention of ID).
- After that there should be an underscore '_'.
- Then there should be the relevent-name or description of the Object (that include MovieClip, Button, Graphics, or any custom made object). In absence of relevent-name or description put an incrementing-counter over their. Also to handle clashing relevent-name, precede it with incrementing-counter.
Below are some sample object-names in flash file using above mentioned naming convention,
AK27P15M_HeaderTwin, AK1P2M_CarMovingEffect, AK2P4M_015, AK5P2M_Twin3, AK4P12M_BlurEffect21, etc.
Update:
ReplyDeleteNaming Conventions for common Team's File
[http://akzcool.blogspot.com/2010/10/naming-conventions-for-common-teams.html]