Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
0

Looking for best practice on naming conventions

Guest
Apr 12, 2013 Apr 12, 2013

Does anyone out there have a best practice on naming conventions that they could share.

I'm starting to find the need to create objects and associated variables and actions.

I can see this getting very messy, very quickly and would love to learn if someone has come up with a good set of guidelines that are both easy to follow and make perfect sense. (I know....what a balance to ask for!)

Thanks

Alan

1.8K
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Apr 15, 2013 Apr 15, 2013

Hi Alan,

Welcome to Adobe Community.

There are couple of things that you can keep in mind while naming objects.

When creating custom text caption styles, be sure to follow the correct naming conventions. Each caption style has a unique name, and you must

use this name at the beginning of each associated bitmap filename. For example, if you create a text caption style named “Brightblue,” the five

bitmap images that constitute the new style should be named as follows:

Brightblue1.bmp, an image with no callouts

Brightblue2.bmp, an image with a callout to the right or upper-right

Brightblue3.bmp, an image with a callout to the left or upper-left

Brightblue4.bmp, an image with a callout to the lower right

Brightblue5.bmp, an image with a callout to the lower left

Flash button-naming conventions

Each SWF button contains three layers: a button, an icon, and an action layer.

The SWF filename consists of the following elements:

Acronym for playback control (“pbc”)

Playback element identifier (“Btn” for button, “Bar” for bar, and so on)

Name of the button (“play”).

Hope this helps!

Thanks!

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Advocate ,
Apr 15, 2013 Apr 15, 2013

When I name my objects, actions, and variables, I always try to name them so someone else can understand what they are.  That said, the names are pretty logical.

scene1_bg, background image for scenario 1

scene1_actor1 for the picture of an actor in scenario 1

if they're more generic objects I leave the 'scene1' part off.

green_arrow_dwn

green_arrow_up

variables, because of the way they sort I try to start with the same prefix 'v' or 'var'

v_progress1 (a variable to track progress)

var_ques1_response1 (response to a question)

hope that helps.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Apr 25, 2013 Apr 25, 2013
LATEST

I find this useful when dealing with a lot of objects and advanced actions

"slidename_objecttype_excercise/scenario_objectnumber"

e.g.

  • f_btn_excercise1_1
  • f_txt_ex5_4
  • b_img_ex7_2

I name the slides a, b, c etc because it helps when writing advanced actions. I can hit the corresponding letter on the keyboard and the object dropdown list jumps to all that slides objects, these objects are also grouped by type.

If  something goes wrong I can usually immediately see where I've gone wrong.

In the example below I can quickly see I've used a button instead of text. Numbering them 1,2,3 etc also helps for the same reason.

Capture.JPG

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Resources
Help resources