Legacy Maemo 5 Documentation/Human Interface Guidelines/Icons - Revision history

imported_>amigadave: cut toplevel heading

2010-10-18T13:39:21Z

cut toplevel heading

← Older revision		Revision as of 13:39, 18 October 2010
Line 1:		Line 1:
	{{Legacy documentation}}		{{Legacy documentation}}

	~~=Icons=~~
	Many applications share similar tasks that can can be represented by a generally known icon. For example, several applications have "Previous", "Next", "Back" or "Forward" actions that can represented by arrow icons. For these kind of actions applications must not ship their own icons, they must use the system icons instead (known as stock icons). An alternative is to ship any desired icons but using the common task ones only when there is no equivalence in the system.		Many applications share similar tasks that can can be represented by a generally known icon. For example, several applications have "Previous", "Next", "Back" or "Forward" actions that can represented by arrow icons. For these kind of actions applications must not ship their own icons, they must use the system icons instead (known as stock icons). An alternative is to ship any desired icons but using the common task ones only when there is no equivalence in the system.

imported_>amigadave: {{Legacy documentation}}

2010-02-12T09:27:58Z

← Older revision		Revision as of 09:27, 12 February 2010
Line 1:		Line 1:
			{{Legacy documentation}}

	=Icons=		=Icons=
	Many applications share similar tasks that can can be represented by a generally known icon. For example, several applications have "Previous", "Next", "Back" or "Forward" actions that can represented by arrow icons. For these kind of actions applications must not ship their own icons, they must use the system icons instead (known as stock icons). An alternative is to ship any desired icons but using the common task ones only when there is no equivalence in the system.		Many applications share similar tasks that can can be represented by a generally known icon. For example, several applications have "Previous", "Next", "Back" or "Forward" actions that can represented by arrow icons. For these kind of actions applications must not ship their own icons, they must use the system icons instead (known as stock icons). An alternative is to ship any desired icons but using the common task ones only when there is no equivalence in the system.

imported_>msoini: Documentation/Maemo 5 Developer Guide/Human Interface Guidelines/Icons moved to Legacy Maemo 5 Documentation/Human Interface Guidelines/Icons: Phase out from Maemo Developer Guide, superceded by Official Nokia Forum documentation

2009-10-14T09:12:04Z

Documentation/Maemo 5 Developer Guide/Human Interface Guidelines/Icons moved to Legacy Maemo 5 Documentation/Human Interface Guidelines/Icons: Phase out from Maemo Developer Guide, superceded by Official Nokia Forum documentation

← Older revision	Revision as of 09:12, 14 October 2009
(No difference)

imported_>liox_lang_valid: /* Icons */

2009-09-22T10:31:47Z

Icons

← Older revision		Revision as of 10:31, 22 September 2009
Line 1:		Line 1:
	=Icons=		=Icons=
	Many applications share similar tasks that can can be represented by a generally known icon. For example, several applications have "Previous", "Next" or "Back", "Forward" actions that can represented by arrow icons. For these kind of actions applications ~~should~~ not ship their own icons, they ~~should~~ use the system icons instead (known as stock icons). An alternative is to ship any desired icons but using the common task ones only when there is no equivalence in the system.		Many applications share similar tasks that can can be represented by a generally known icon. For example, several applications have "Previous", "Next", "Back" or "Forward" actions that can represented by arrow icons. For these kind of actions applications must not ship their own icons, they must use the system icons instead (known as stock icons). An alternative is to ship any desired icons but using the common task ones only when there is no equivalence in the system.

	Because there is no mouse on ~~a device with~~ a touch screen, there ~~will be~~ no tooltips. ~~Therefor~~ choosing an icon when there is no text label in the widget involves an more important decision than on a desktop computer. If ~~the user doesn't~~ understand what action is assigned to a button with only an icon, ~~he or she will~~ need to read any help document about the application but is likely to press that button ~~in order~~ to check ~~what's~~ its function (which might not result in what the user wants). If an icon ~~isn't~~ clear enough for the task it represents, ~~don't~~ use it, use a text label instead. Text labels generally give a better explanation to the user. Apart from the mentioned common tasks, the only way where an icon might be preferable to a text label is when there's no space for the text.		Because there is no mouse on a touch screen device, there are no tooltips. Therefore, choosing an icon when there is no text label in the widget involves a more important decision than on a desktop computer. If users do not understand what action is assigned to a button with only an icon, they need to read any help document about the application but are likely to press that button to check its function (which might not result in what the user wants). If an icon is not clear enough for the task it represents, do not use it, use a text label instead. Text labels generally give a better explanation to the user. Apart from the mentioned common tasks, the only way where an icon might be preferable to a text label is when there is no space for the text.

	For general guidelines on the design of good icons, ~~please read~~ the GNOME HIG [http://library.gnome.org/devel/hig-book/2.26/icons.html.en Icons section].		For general guidelines on the design of good icons, see the GNOME HIG [http://library.gnome.org/devel/hig-book/2.26/icons.html.en Icons section].

imported_>jeremiah: /* Icons */

2009-09-18T16:24:45Z

Icons

← Older revision		Revision as of 16:24, 18 September 2009
Line 2:		Line 2:
	Many applications share similar tasks that can can be represented by a generally known icon. For example, several applications have "Previous", "Next" or "Back", "Forward" actions that can represented by arrow icons. For these kind of actions applications should not ship their own icons, they should use the system icons instead (known as stock icons). An alternative is to ship any desired icons but using the common task ones only when there is no equivalence in the system.		Many applications share similar tasks that can can be represented by a generally known icon. For example, several applications have "Previous", "Next" or "Back", "Forward" actions that can represented by arrow icons. For these kind of actions applications should not ship their own icons, they should use the system icons instead (known as stock icons). An alternative is to ship any desired icons but using the common task ones only when there is no equivalence in the system.

	In a device with a touch screen~~, since there is no mouse~~, there will be no tooltips~~, hence~~ choosing an icon when there is no text label in the widget involves an ~~even~~ more important decision than in a desktop computer. If the user doesn't ~~readily~~ understand what~~'s the~~ action assigned to a button with only an icon, he or she will need to read any help document about the application but is likely to press that button in order to check what's its function (which might not result in what the user wants). If an icon ~~doesn~~'t ~~seem~~ clear enough for the task it represents, ~~then~~ don't use it, use a text label instead. Text labels generally give a better explanation to a user. Apart from the mentioned common tasks, the only way where an icon might be preferable to a text label is when there's no space for the text.		Because there is no mouse on a device with a touch screen, there will be no tooltips. Therefor choosing an icon when there is no text label in the widget involves an more important decision than on a desktop computer. If the user doesn't understand what action is assigned to a button with only an icon, he or she will need to read any help document about the application but is likely to press that button in order to check what's its function (which might not result in what the user wants). If an icon isn't clear enough for the task it represents, don't use it, use a text label instead. Text labels generally give a better explanation to the user. Apart from the mentioned common tasks, the only way where an icon might be preferable to a text label is when there's no space for the text.

	For general guidelines on the design of good icons, please read the GNOME HIG [http://library.gnome.org/devel/hig-book/2.26/icons.html.en Icons section].		For general guidelines on the design of good icons, please read the GNOME HIG [http://library.gnome.org/devel/hig-book/2.26/icons.html.en Icons section].

imported_>bijjal: New page: =Icons= Many applications share similar tasks that can can be represented by a generally known icon. For example, several applications have "Previous", "Next" or "Back", "Forward" actions ...

2009-07-13T20:02:42Z

New page: =Icons= Many applications share similar tasks that can can be represented by a generally known icon. For example, several applications have "Previous", "Next" or "Back", "Forward" actions ...

New page

=Icons=
Many applications share similar tasks that can can be represented by a generally known icon. For example, several applications have "Previous", "Next" or "Back", "Forward" actions that can represented by arrow icons. For these kind of actions applications should not ship their own icons, they should use the system icons instead (known as stock icons). An alternative is to ship any desired icons but using the common task ones only when there is no equivalence in the system.

In a device with a touch screen, since there is no mouse, there will be no tooltips, hence choosing an icon when there is no text label in the widget involves an even more important decision than in a desktop computer. If the user doesn't readily understand what's the action assigned to a button with only an icon, he or she will need to read any help document about the application but is likely to press that button in order to check what's its function (which might not result in what the user wants). If an icon doesn't seem clear enough for the task it represents, then don't use it, use a text label instead. Text labels generally give a better explanation to a user. Apart from the mentioned common tasks, the only way where an icon might be preferable to a text label is when there's no space for the text.

For general guidelines on the design of good icons, please read the GNOME HIG [http://library.gnome.org/devel/hig-book/2.26/icons.html.en Icons section].