You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: java/android/README.md
+8-3Lines changed: 8 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -42,8 +42,8 @@ The following structure should be followed when naming resoures.
42
42
***Group**: Application area or screen. If the resource is used in different parts of applications 'common' should be used instead. e.g. actionbar, menu, media, popup, footer, audio, etc.
43
43
***Type**: Resource Type. e.g. background, icon, button, textfield, list, menuitem, radiobutton, checkbox, tab, dialog, title, etc.
44
44
***Name**: Descriptive name as to what the resource is about. e.g. play, stop.
45
-
***State** (Optional): The optional state of a parent resource. e.g. A button could be in 'normal', 'pressed', 'disabled' and 'selected'. A checkbox could be 'on' or 'off'. These resources should NEVER be used directly in layout but rather as state selectors.
46
-
***Suffix** (Optional): An arbitrary suffix that helps to further identify a property of the resource. Ex: bright, dark, opaque, layer, etc.
45
+
***State**: (Optional): The optional state of a parent resource. e.g. A button could be in 'normal', 'pressed', 'disabled' and 'selected'. A checkbox could be 'on' or 'off'. These resources should NEVER be used directly in layout but rather as state selectors.
46
+
***Suffix**: (Optional): An arbitrary suffix that helps to further identify a property of the resource. e.g. bright, dark, opaque, layer.
47
47
48
48
Below are some examples of properly named resources.
49
49
@@ -71,7 +71,12 @@ Below are some examples of properly named string identifiers.
71
71
String resources placed in styles.xml are named in CamelCase.
72
72
The following structure should be followed when naming style resoures.
73
73
74
-
**Group**|**Type**|**Name**|*[Suffix]*
74
+
**[Group]TypeName[Suffix]**
75
+
76
+
***Group** (Optional): Application area or screen. e.g. actionbar, menu, media, popup, footer, audio.
0 commit comments