2

User interface for web applications in general contain various buttons for performing CRUD operations. What would be the suggested naming convention for button labels while performing the following actions..

  • User creation (Add User... or Add User or Add user)
  • Event creation (Add Event... or Add Event or Add event)
  • View users button (List All Users or List All users or List all users )

Most of the sites seem to contain the last option (e.g. Add user) where the first alphabet in the word is capitalized and rest all are lower case). What would be a better practice here?

Nick Allen
  • 11,970
  • 11
  • 45
  • 58
Sam
  • 8,387
  • 19
  • 62
  • 97
  • 1
    User interface standards and rationale for sentence versus title capitalization are answered in: http://stackoverflow.com/questions/2371226/capitalizing-texts-in-user-interface/ Standards and meaning for using the ellipsis (“…”) are answered in: http://stackoverflow.com/questions/278655/when-should-i-use-a-ellipsis-in-a-menu-item The answers apply to command buttons and menu items. – Michael Zuschlag Mar 26 '10 at 20:36

4 Answers4

2

It's a question of taste and personal preferences. The most important thing is to be consistent all over the application.

Klaus Byskov Pedersen
  • 117,245
  • 29
  • 183
  • 222
  • I agree, are there anything specific which needs to be thought out from a user interface guideline perspective – Sam Mar 26 '10 at 11:33
1

As I understood the question it's regarding the button label, not the name in the code.

"Add user…": An action ending in an ellipsis (…) (I always prefer an ellipsis over three dots) normally indicates "something more", e.g. a dialog box popping up with a form or more questions before the action is performed.

"Add User" I see as just bad writing. Unless perhaps it's in german where all nouns are capitalized. =)

I'd go for "Add user", if it's the last step in the flow/process of creating the user.

Glenn Jorde
  • 570
  • 4
  • 10
0

Well certainly in .Net Button controls I always use

BtnEventName

But this is a general convention for any control in .Net for example a TextBox would be

TxtUserName

Major benefit of this is that controls of the same type are grouped in intellisense

Nick Allen
  • 11,970
  • 11
  • 45
  • 58
0

Depends, in swing I use, :

JTextField txtUserField; // description about the inputType + description of what it actually is.!
JButton butSubmit;

For a j2ee application ,

HTML : <input type="button" name="butUserName"/>

Beans : It is HIGHLY recommended to name the input field exactly as it is named in the HTML forms. (like in struts, in the form bean String butUserName;)

in jsp/servlets: same....... String butUserName = request.getParameter("butUserName");

raj
  • 3,769
  • 4
  • 25
  • 43