Standard Terminology for Application Elements

[jbean]

Does anyone know of an on-line resource that defines standard terms for various application elements, such as a window, a pane, a a panel, a dialog, etc.

Many thanks

[LTinker68]

I don't know of one, but I'd be curious if there was. Personally, I use "screen" instead of "dialog" (programmers love that term). I don't use "windows" because I don't want to confuse computer newbies with the difference between Microsoft Windows and Windows Explorer and non-Microsoft program windows.

[helen]

I find both the MS Manual of Style and the Chicago Manual of Style to be useful resources:

Microsoft Manual of Style: http://www.microsoft.com/MSPress/books/6074.aspx
Chicago Manual of Style: http://www.chicagomanualofstyle.org/home.html

[lacastle]

I second the Microsoft Manual of Style. There are free PDF versions of it online too.

[RamonS]

The list from Microsoft is commonly used as reference, but I recommend to ask industry experts (support, sales with several years of experience) if there are particular terms that are well understood by the targeted audience. I know that many developers refer to a window or screen as "form", because that is how the IDEs name them. I also found it interesting to see the term "menu command" in the Microsoft list (I think that is where I saw it). Until then I always found that "menu entry" is well understood.
Also, some call drop-down list "pull downs" (makes me think of pull up baby diapers) and drag & drop "click & drag" or "click & drop" (I also saw it once referenced as drag&click!!). Those are just a few examples where several terms exist for the same thing. Some of them may be better understood although they do not appear in any of the lists.
In any case I recommend to create a glossary of terms for this. I wouldn't necessarily add these terms to the main glossary, but craft a simple help topic that gives definitions and definitely pictures. It is like the "Help on Help" topic, once done right it will be ready for use in many projects to come.

[lacastle]

I also meant to say the the MMoS is good if your users are familiar with other Microsoft applications. If your users know Mac or Linux or Unix or something else, you'd want to use those terms.

And when you're seeing a GUI that isn't "normal" or intuitive, at least you have a big name like Microsoft to back up your suggestions for changes.

[BL_N]

Thirded on the Microsoft Manual of Style, but also agree to some extent with Ramon. User terminology or industry specific references trump style guides in every case. On the other hand, references that incorporate both are usually best for educating and ramping up technological concept knowledge for a non-technical audience (e.g., using Ramon's example - "The X menu (form) consists of the following elements...").

[KevinDAmery]

In addition to the MMoS, Sun used to publish a styleguide as well (maybe they still do...) That may be of help if you document products for the Linux / Unix world. HTH.

[forfear]

Fourthded...

I'd go with MMoS..there used to be a CHM version of it online..i guess if you google hard enough you might find the rare copy of it..

When you have it, search for the keywords such as 'user interface' or 'dialog boxes' ...its pretty much THE reference guide. A lot of the other alternatives i find are usually a wee bit dated.

[QBF]

I find both the MS Manual of Style and the Chicago Manual of Style to be useful resources:

Microsoft Manual of Style: http://www.microsoft.com/MSPress/books/6074.aspx
Chicago Manual of Style: http://www.chicagomanualofstyle.org/home.html

The Chicago Manual of Style is also available as an "online" reference by annual subscription. The cost for an Individual rate is $30.00 US/yr, there are group rates and these vary per number of users.
http://www.chicagomanualofstyle.org/sub ... _opts.html