Legacy Maemo 5 Documentation/Human Interface Guidelines - Revision history

amigadave: {{Legacy documentation}}

2010-02-12T09:24:10Z

← Older revision		Revision as of 09:24, 12 February 2010
Line 1:		Line 1:
		+	{{Legacy documentation}}
		+
	*[[{{PAGENAME}}/Introduction\| Introduction]]		*[[{{PAGENAME}}/Introduction\| Introduction]]
	*[[{{PAGENAME}}/Usability Principles\|Usability Principles]]		*[[{{PAGENAME}}/Usability Principles\|Usability Principles]]

msoini at 09:20, 14 October 2009

2009-10-14T09:20:14Z

← Older revision		Revision as of 09:20, 14 October 2009
Line 11:		Line 11:
	*[[{{PAGENAME}}/Icons\|Icons]]		*[[{{PAGENAME}}/Icons\|Icons]]
	*[[{{PAGENAME}}/Reality Checks\|Reality Checks]]		*[[{{PAGENAME}}/Reality Checks\|Reality Checks]]
-	*[[{{PAGENAME}}/GUI Design Template\|GUI Design Template]]
-	*[[{{PAGENAME}}/Desktop Widget UI Guidelines\|Desktop Widget UI Guidelines]]
-
-	*[[Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines/Introduction\| Introduction]]
-	*[[Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines/Usability Principles\|Usability Principles]]
-	*[[Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines/Device Orientation\| Device Orientation]]
-	*[[Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines/Windows\|Windows]]
-	*[[Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines/Notes and Banners\|Notes and Banners]]
-	*[[Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines/Dialogs\|Dialogs]]
-	*[[Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines/View Menu\|View Menu]]
-	*[[Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines/Hildonizing an Interface\|Hildonizing an Interface]]
-	*[[Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines/Controls\|Controls]]
-	*[[Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines/User Input\|User Input]]
-	*[[Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines/Icons\|Icons]]
-	*[[Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines/Reality Checks\|Reality Checks]]
-	*[[Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines/GUI Design Template\|GUI Design Template]]
-	*[[Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines/Desktop Widget UI Guidelines\|Desktop Widget UI Guidelines]]

msoini at 08:58, 14 October 2009

2009-10-14T08:58:49Z

← Older revision		Revision as of 08:58, 14 October 2009
Line 13:		Line 13:
	*[[{{PAGENAME}}/GUI Design Template\|GUI Design Template]]		*[[{{PAGENAME}}/GUI Design Template\|GUI Design Template]]
	*[[{{PAGENAME}}/Desktop Widget UI Guidelines\|Desktop Widget UI Guidelines]]		*[[{{PAGENAME}}/Desktop Widget UI Guidelines\|Desktop Widget UI Guidelines]]
		+
		+	*[[Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines/Introduction\| Introduction]]
		+	*[[Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines/Usability Principles\|Usability Principles]]
		+	*[[Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines/Device Orientation\| Device Orientation]]
		+	*[[Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines/Windows\|Windows]]
		+	*[[Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines/Notes and Banners\|Notes and Banners]]
		+	*[[Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines/Dialogs\|Dialogs]]
		+	*[[Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines/View Menu\|View Menu]]
		+	*[[Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines/Hildonizing an Interface\|Hildonizing an Interface]]
		+	*[[Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines/Controls\|Controls]]
		+	*[[Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines/User Input\|User Input]]
		+	*[[Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines/Icons\|Icons]]
		+	*[[Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines/Reality Checks\|Reality Checks]]
		+	*[[Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines/GUI Design Template\|GUI Design Template]]
		+	*[[Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines/Desktop Widget UI Guidelines\|Desktop Widget UI Guidelines]]

msoini: Documentation/Maemo 5 Developer Guide/Human Interface Guidelines moved to Legacy Maemo 5 Documentation/Human Interface Guidelines: This part of documentation is phased out, in favor of official Nokia forum documentation

2009-10-14T08:52:55Z

Documentation/Maemo 5 Developer Guide/Human Interface Guidelines moved to Legacy Maemo 5 Documentation/Human Interface Guidelines: This part of documentation is phased out, in favor of official Nokia forum documentation

← Older revision

Revision as of 08:52, 14 October 2009

msoini at 14:26, 14 September 2009

2009-09-14T14:26:18Z

← Older revision		Revision as of 14:26, 14 September 2009
Line 11:		Line 11:
	*[[{{PAGENAME}}/Icons\|Icons]]		*[[{{PAGENAME}}/Icons\|Icons]]
	*[[{{PAGENAME}}/Reality Checks\|Reality Checks]]		*[[{{PAGENAME}}/Reality Checks\|Reality Checks]]
		+	*[[{{PAGENAME}}/GUI Design Template\|GUI Design Template]]
	*[[{{PAGENAME}}/Desktop Widget UI Guidelines\|Desktop Widget UI Guidelines]]		*[[{{PAGENAME}}/Desktop Widget UI Guidelines\|Desktop Widget UI Guidelines]]

msoini at 13:56, 2 September 2009

2009-09-02T13:56:04Z

← Older revision		Revision as of 13:56, 2 September 2009
Line 11:		Line 11:
	*[[{{PAGENAME}}/Icons\|Icons]]		*[[{{PAGENAME}}/Icons\|Icons]]
	*[[{{PAGENAME}}/Reality Checks\|Reality Checks]]		*[[{{PAGENAME}}/Reality Checks\|Reality Checks]]
		+	*[[{{PAGENAME}}/Desktop Widget UI Guidelines\|Desktop Widget UI Guidelines]]

bijjal: /* Hildon Human Interface Guidelines */

2009-07-13T20:14:00Z

Hildon Human Interface Guidelines

← Older revision		Revision as of 20:14, 13 July 2009
Line 1:		Line 1:
-	~~=Hildon Human Interface Guidelines=~~
-
	*[[{{PAGENAME}}/Introduction\| Introduction]]		*[[{{PAGENAME}}/Introduction\| Introduction]]
	*[[{{PAGENAME}}/Usability Principles\|Usability Principles]]		*[[{{PAGENAME}}/Usability Principles\|Usability Principles]]

bijjal at 20:10, 13 July 2009

2009-07-13T20:10:15Z

Show changes

bijjal: /* Soft Keys and Touch Types */

2009-07-13T19:58:06Z

Soft Keys and Touch Types

← Older revision		Revision as of 19:58, 13 July 2009
Line 455:		Line 455:
	* ''Tap release:'' This state occurs when users lift up their finger after a tap down. This will activate the element that was tapped, such as a button or task launcher.		* ''Tap release:'' This state occurs when users lift up their finger after a tap down. This will activate the element that was tapped, such as a button or task launcher.
	* ''Tap and cancel:'' If a fixed position element (such as a button) is tapped, but loses its focus (e.g., a user slides their finger out of the element's area), it will not activate that element.		* ''Tap and cancel:'' If a fixed position element (such as a button) is tapped, but loses its focus (e.g., a user slides their finger out of the element's area), it will not activate that element.
-

	====Two-Touch====		====Two-Touch====
	Two-Touch occurs when users tap an onscreen element and, without lifting their initial tapping finger, touch the screen with another finger. The Two-Touch can be used to activate element-specific context sensitive menus (similar to right-clicking an application icon in a traditional desktop scenario).		Two-Touch occurs when users tap an onscreen element and, without lifting their initial tapping finger, touch the screen with another finger. The Two-Touch can be used to activate element-specific context sensitive menus (similar to right-clicking an application icon in a traditional desktop scenario).
-

	====Long-Tap====		====Long-Tap====

bijjal: /* User Input */

2009-07-13T19:57:33Z

User Input

← Older revision		Revision as of 19:57, 13 July 2009
Line 410:		Line 410:


-	==User Input==	+	=User Input=
-		+
	There are several methods of using and manipulating applications on a Hildon-powered device. First, there are two viewable orientations: landscape and portrait. Second, users can control what is happening on the device with either a finger (or fingers) or by using a stylus. Because of this, developers must carefully weigh the various use-cases and input methods when planning an application.		There are several methods of using and manipulating applications on a Hildon-powered device. First, there are two viewable orientations: landscape and portrait. Second, users can control what is happening on the device with either a finger (or fingers) or by using a stylus. Because of this, developers must carefully weigh the various use-cases and input methods when planning an application.

	This section covers these various types of usage in an attempt to advise developers and interface designers how to utilize best practices in order to provide a smooth, intuitive experience for end-users.		This section covers these various types of usage in an attempt to advise developers and interface designers how to utilize best practices in order to provide a smooth, intuitive experience for end-users.

-	===Input Hardware===	+
		+	==Input Hardware==
	Input Hardware is the hardware that allows users to interact with a Hildon device. When users interact with any component of the Input Hardware, the device should respond with some sort of feedback.		Input Hardware is the hardware that allows users to interact with a Hildon device. When users interact with any component of the Input Hardware, the device should respond with some sort of feedback.

-	====Hard Keys====	+	===Hard Keys===
	Hard Keys are the keys on the device that can be physically touched. The set of Hard Keys available on various devices will vary according to the make and model of the device. These differences must be taken into account when developing a Hildon application. Nonetheless, there are sets of keys that are fairly standard on most hand-held devices.		Hard Keys are the keys on the device that can be physically touched. The set of Hard Keys available on various devices will vary according to the make and model of the device. These differences must be taken into account when developing a Hildon application. Nonetheless, there are sets of keys that are fairly standard on most hand-held devices.

-	~~'''~~Common Hard Keys~~'''~~	+	====Common Hard Keys====
-		+
	* ''Power Key:'' This key common to most devices, as it is a basic, but vital function.		* ''Power Key:'' This key common to most devices, as it is a basic, but vital function.
	* ''Lock/Unlock Key:'' This key can also be found on many devices. It is the key that "locks" and "unlocks" a device for use. Note that although this key is common, some devices handle this function via "soft keys."		* ''Lock/Unlock Key:'' This key can also be found on many devices. It is the key that "locks" and "unlocks" a device for use. Note that although this key is common, some devices handle this function via "soft keys."
	* ''Increase/Decrease Key:'' Normally these keys are used to adjust the sound volume of a device, or to zoom in and out of a device's viewable area.		* ''Increase/Decrease Key:'' Normally these keys are used to adjust the sound volume of a device, or to zoom in and out of a device's viewable area.

-	~~'''~~Optional Hard Keys~~'''~~	+	====Optional Hard Keys====
-		+
	* ''Capture Key:'' The "Capture Key," if available is primarily used to take a photo with the device's built-in camera.		* ''Capture Key:'' The "Capture Key," if available is primarily used to take a photo with the device's built-in camera.
	* ''Keyboard:'' Many devices feature a hardware keyboard that is either always present or can be slid or flipped out. Hildon supports two types of text input: hardware keyboard and touch screen text input methods. Touch screen input methods should never be activated if a hardware keyboard is available (i.e., open for use).		* ''Keyboard:'' Many devices feature a hardware keyboard that is either always present or can be slid or flipped out. Hildon supports two types of text input: hardware keyboard and touch screen text input methods. Touch screen input methods should never be activated if a hardware keyboard is available (i.e., open for use).


-	===Finger Interaction===	+	==Finger Interaction==
	Hildon can be manipulated by users' fingertips, without the need of a stylus pointer. But, as described in the Principles section, keep in mind that using the finger input method may result in obscuring parts of the application. Placing important information in a position that can be hidden by finger/hand interaction is never desirable. Because of this, it is extremely important to choose proper placement of all onscreen widgets. Likewise, try to offer a way to let users choose their preferred widget placement.		Hildon can be manipulated by users' fingertips, without the need of a stylus pointer. But, as described in the Principles section, keep in mind that using the finger input method may result in obscuring parts of the application. Placing important information in a position that can be hidden by finger/hand interaction is never desirable. Because of this, it is extremely important to choose proper placement of all onscreen widgets. Likewise, try to offer a way to let users choose their preferred widget placement.

-	====Two Hand Usage====	+	===Two Hand Usage===
	Two Hand usage occurs when users hold the device with both hands, using their fingers to interact with the device and/or application. In this case, the application should be designed to work in landscape mode. For example, if both thumbs are required to interact with the device, the obscured area will be greater than if it was a function controlled with just one finger. Because of this, deciding on the placement of onscreen elements becomes bigger challenge for interface designers. Great care must be taken when designing a usable interface where important items are always visible when they need to be.		Two Hand usage occurs when users hold the device with both hands, using their fingers to interact with the device and/or application. In this case, the application should be designed to work in landscape mode. For example, if both thumbs are required to interact with the device, the obscured area will be greater than if it was a function controlled with just one finger. Because of this, deciding on the placement of onscreen elements becomes bigger challenge for interface designers. Great care must be taken when designing a usable interface where important items are always visible when they need to be.

-	====Two Hand Usage with Keyboard====	+	===Two Hand Usage with Keyboard===
	Some devices will also have hardware keyboards that either slide or flip out. Again, special attention must be paid to how users will interact with onscreen elements, as well as the physical keyboard.		Some devices will also have hardware keyboards that either slide or flip out. Again, special attention must be paid to how users will interact with onscreen elements, as well as the physical keyboard.

	In some cases, certain onscreen elements items may be hard to reach if a physical keyboard is present. Specifically, any widget placed at the top-most area of the screen can be difficult to reach while users are holding a device when the keyboard is slid out.		In some cases, certain onscreen elements items may be hard to reach if a physical keyboard is present. Specifically, any widget placed at the top-most area of the screen can be difficult to reach while users are holding a device when the keyboard is slid out.

-	====One Hand Usage====	+	===One Hand Usage===
	If you are planning an application that can be used with only one hand, consider making it run in portrait mode. This is because devices are typically easier to hold with one hand when positioned vertically (i.e., holding a device that is positioned in landscape mode with one hand can be very difficult). Remember that creating static designs (e.g., elements that fit only in one orientation) is not a best practice. Take care to design interfaces that can adapt easily to both horizontal and vertical orientations, as one cannot anticipate various users' preferences.		If you are planning an application that can be used with only one hand, consider making it run in portrait mode. This is because devices are typically easier to hold with one hand when positioned vertically (i.e., holding a device that is positioned in landscape mode with one hand can be very difficult). Remember that creating static designs (e.g., elements that fit only in one orientation) is not a best practice. Take care to design interfaces that can adapt easily to both horizontal and vertical orientations, as one cannot anticipate various users' preferences.

-	====Soft Keys and Touch Types====	+	===Soft Keys and Touch Types===
	Hildon, like other touch-screen frameworks, can accommodate a variety of different types of taps.		Hildon, like other touch-screen frameworks, can accommodate a variety of different types of taps.

-	~~'''~~Single Tap~~'''~~	+	====Single Tap====
-		+
	Any interactive elements like controls, buttons, links, et cetera, can be activated by tapping and releasing on top of the element's control area. The process of performing a Single-Tap is divided into three separate states. The following list describes those states and what users can accomplish with Single-Taps.		Any interactive elements like controls, buttons, links, et cetera, can be activated by tapping and releasing on top of the element's control area. The process of performing a Single-Tap is divided into three separate states. The following list describes those states and what users can accomplish with Single-Taps.

Line 460:		Line 457:


-	~~'''~~Two-Touch~~'''~~	+	====Two-Touch====
-		+
	Two-Touch occurs when users tap an onscreen element and, without lifting their initial tapping finger, touch the screen with another finger. The Two-Touch can be used to activate element-specific context sensitive menus (similar to right-clicking an application icon in a traditional desktop scenario).		Two-Touch occurs when users tap an onscreen element and, without lifting their initial tapping finger, touch the screen with another finger. The Two-Touch can be used to activate element-specific context sensitive menus (similar to right-clicking an application icon in a traditional desktop scenario).


-	~~'''~~Long-Tap~~'''~~	+	====Long-Tap====
-		+
	Whenever a user taps and element, but keeps their finger pressed down, it produces a "Long-Tap." Long-Taps should only be used as a shortcut method of accessing a function that can otherwise be accessed another way. For instance, users can Long-Tap a contact in the Contact List to trigger a menu with additional options.		Whenever a user taps and element, but keeps their finger pressed down, it produces a "Long-Tap." Long-Taps should only be used as a shortcut method of accessing a function that can otherwise be accessed another way. For instance, users can Long-Tap a contact in the Contact List to trigger a menu with additional options.

-	===Stylus Interaction===	+	==Stylus Interaction==
	Even though Hildon widgets are designed for finger use, certain devices may still include a stylus. However, designing stylus usage into an application is inadvisable unless a specific task requires extremely high precision: clicking links within a website (typically, websites are designed to be navigated via a small mouse cursor), imaging applications that features drawing or painting operations, and applications that require more widgets than can be viewed at one time (leaving no space for fingers).		Even though Hildon widgets are designed for finger use, certain devices may still include a stylus. However, designing stylus usage into an application is inadvisable unless a specific task requires extremely high precision: clicking links within a website (typically, websites are designed to be navigated via a small mouse cursor), imaging applications that features drawing or painting operations, and applications that require more widgets than can be viewed at one time (leaving no space for fingers).


-	===Dimensions===	+	==Dimensions==
	Buttons that are designed to be clicked by a mouse or a stylus are not always very easy to be pressed by a finger or thumb because of their smaller sizes. The placement of widgets can also impact usability when considering finger usage (e.g., buttons that are placed right next each other require higher precision and may make them difficult to be pressed by fingers).		Buttons that are designed to be clicked by a mouse or a stylus are not always very easy to be pressed by a finger or thumb because of their smaller sizes. The placement of widgets can also impact usability when considering finger usage (e.g., buttons that are placed right next each other require higher precision and may make them difficult to be pressed by fingers).

Line 480:		Line 475:
	The Hildon API provides several defined values in order to make creating variable control sizes easier:		The Hildon API provides several defined values in order to make creating variable control sizes easier:

-	~~'''~~Hildon control size types~~'''~~	+	===Hildon control size types===

	*''HILDON_SIZE_AUTO_WIDTH'' Automatic width		*''HILDON_SIZE_AUTO_WIDTH'' Automatic width
Line 491:		Line 486:
	Use the variable sizes above when choosing the size of widgets based on certain use-cases. For example, if you place a button on a bottom corner of the screen, it is likely that that users will use their thumbs to press it. In this case, choose ''HILDON_SIZE_THUMB_HEIGHT'' for this button.		Use the variable sizes above when choosing the size of widgets based on certain use-cases. For example, if you place a button on a bottom corner of the screen, it is likely that that users will use their thumbs to press it. In this case, choose ''HILDON_SIZE_THUMB_HEIGHT'' for this button.

-	===Interaction Actions===	+	==Interaction Actions==
	While many of the actions that can be performed with a Hildon-based device are similar to those found within a traditional desktop environment, several additional methods of interacting within Hildon are rather unique. The following sections describe these actions or interactions.		While many of the actions that can be performed with a Hildon-based device are similar to those found within a traditional desktop environment, several additional methods of interacting within Hildon are rather unique. The following sections describe these actions or interactions.

	The following sections describe these actions or interactions.		The following sections describe these actions or interactions.

-	====Copy, paste, cut====	+	===Copy, paste, cut===
	The text input fields support the common actions of copying, pasting, and cutting. To perform these actions, users can use the standard hardware keyboard (if available) shortcuts Ctrl+c, Ctrl+v, and Ctrl+x, respectively.		The text input fields support the common actions of copying, pasting, and cutting. To perform these actions, users can use the standard hardware keyboard (if available) shortcuts Ctrl+c, Ctrl+v, and Ctrl+x, respectively.

-	====Panning====	+	===Panning===
	The use of scrollbars within Hildon is discouraged, as the interface is intended to be manipulated with fingers. The concept of Panning refers to navigation of onscreen content by tapping and ''dragging'' a finger over the content. When users enter a view that contains content that cannot be fully viewed within the physical screen area, scroll indicators will appear on the right and bottom sides of the screen. These indicators tell users that the content can be Panned in order to navigate through the content.		The use of scrollbars within Hildon is discouraged, as the interface is intended to be manipulated with fingers. The concept of Panning refers to navigation of onscreen content by tapping and ''dragging'' a finger over the content. When users enter a view that contains content that cannot be fully viewed within the physical screen area, scroll indicators will appear on the right and bottom sides of the screen. These indicators tell users that the content can be Panned in order to navigate through the content.

← Older revision		Revision as of 09:20, 14 October 2009
Line 11:		Line 11:
	*[[{{PAGENAME}}/Icons\|Icons]]		*[[{{PAGENAME}}/Icons\|Icons]]
	*[[{{PAGENAME}}/Reality Checks\|Reality Checks]]		*[[{{PAGENAME}}/Reality Checks\|Reality Checks]]
-	*[[{{PAGENAME}}/GUI Design Template\|GUI Design Template]]
-	*[[{{PAGENAME}}/Desktop Widget UI Guidelines\|Desktop Widget UI Guidelines]]
-
-	*[[Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines/Introduction\| Introduction]]
-	*[[Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines/Usability Principles\|Usability Principles]]
-	*[[Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines/Device Orientation\| Device Orientation]]
-	*[[Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines/Windows\|Windows]]
-	*[[Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines/Notes and Banners\|Notes and Banners]]
-	*[[Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines/Dialogs\|Dialogs]]
-	*[[Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines/View Menu\|View Menu]]
-	*[[Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines/Hildonizing an Interface\|Hildonizing an Interface]]
-	*[[Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines/Controls\|Controls]]
-	*[[Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines/User Input\|User Input]]
-	*[[Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines/Icons\|Icons]]
-	*[[Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines/Reality Checks\|Reality Checks]]
-	*[[Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines/GUI Design Template\|GUI Design Template]]
-	*[[Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines/Desktop Widget UI Guidelines\|Desktop Widget UI Guidelines]]

← Older revision		Revision as of 08:58, 14 October 2009
Line 13:		Line 13:
	*[[{{PAGENAME}}/GUI Design Template\|GUI Design Template]]		*[[{{PAGENAME}}/GUI Design Template\|GUI Design Template]]
	*[[{{PAGENAME}}/Desktop Widget UI Guidelines\|Desktop Widget UI Guidelines]]		*[[{{PAGENAME}}/Desktop Widget UI Guidelines\|Desktop Widget UI Guidelines]]
		+
		+	*[[Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines/Introduction\| Introduction]]
		+	*[[Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines/Usability Principles\|Usability Principles]]
		+	*[[Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines/Device Orientation\| Device Orientation]]
		+	*[[Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines/Windows\|Windows]]
		+	*[[Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines/Notes and Banners\|Notes and Banners]]
		+	*[[Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines/Dialogs\|Dialogs]]
		+	*[[Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines/View Menu\|View Menu]]
		+	*[[Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines/Hildonizing an Interface\|Hildonizing an Interface]]
		+	*[[Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines/Controls\|Controls]]
		+	*[[Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines/User Input\|User Input]]
		+	*[[Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines/Icons\|Icons]]
		+	*[[Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines/Reality Checks\|Reality Checks]]
		+	*[[Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines/GUI Design Template\|GUI Design Template]]
		+	*[[Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines/Desktop Widget UI Guidelines\|Desktop Widget UI Guidelines]]

← Older revision		Revision as of 14:26, 14 September 2009
Line 11:		Line 11:
	*[[{{PAGENAME}}/Icons\|Icons]]		*[[{{PAGENAME}}/Icons\|Icons]]
	*[[{{PAGENAME}}/Reality Checks\|Reality Checks]]		*[[{{PAGENAME}}/Reality Checks\|Reality Checks]]
		+	*[[{{PAGENAME}}/GUI Design Template\|GUI Design Template]]
	*[[{{PAGENAME}}/Desktop Widget UI Guidelines\|Desktop Widget UI Guidelines]]		*[[{{PAGENAME}}/Desktop Widget UI Guidelines\|Desktop Widget UI Guidelines]]

← Older revision		Revision as of 13:56, 2 September 2009
Line 11:		Line 11:
	*[[{{PAGENAME}}/Icons\|Icons]]		*[[{{PAGENAME}}/Icons\|Icons]]
	*[[{{PAGENAME}}/Reality Checks\|Reality Checks]]		*[[{{PAGENAME}}/Reality Checks\|Reality Checks]]
		+	*[[{{PAGENAME}}/Desktop Widget UI Guidelines\|Desktop Widget UI Guidelines]]