|Home · All Classes · Main Classes · Deprecated|
A "common component" is a reusable element of the MeeGo Handset user interface. Typical components include the standard UI controls such as buttons, sliders, and lists, as well as the more complex dialogs and menus.
Components are also widgets (specifically QGraphicsWidgets) and can be used anywhere a widget can, but common components also have some unique features that means not every widget is a component:
While applications are seldom created out of only common components, by using the common components where applicable instead of creating custom controls, your application will fit in with the rest of the MeeGo user experience. This will also help your users transfer what they have learned from other MeeGo applications to yours.
Buttons come in many form and sizes, but can fundamentally be divided into two main use cases: buttons that execute an action when pressed and buttons that maintain a toggle state (on/off).
The following button types are available:
A list is a container of objects displayed vertically. The list should be used when the number of items is very large or dynamic, otherwise consider using a layout instead.
A text edit is used for user input of text. The edit can be a single or multiple lines, or it can expand as necessary. When a hardware keyboard is not available, the text edit interacts with the virtual on-screen input methods.
A label displays a piece of text in the UI. The MeeGo Touch label supports both markup and links in labels.
The image represents a single picture in the UI.
The video widget supports flexible playback of video in the UI. The widget can for example be rotated along with the rest of the UI and have transparent controls overlaid.
The application page is one view of an application, navigation inside the application typically happens by switching between multiple pages.
The application menu is typically not directly accessed, instead actions are added to an MApplicationPage. This allows the menu to be reconfigured automatically as the user switches between pages in the application.
The application menu consists of a list of commands related to the current application view, or application wide commands.
Use dialogs when you want a response from the user while blocking access to the rest of the application. Unlike notifications, dialogs do not disappear from the UI without user interaction.
An object menu is a list of contextual actions that can be performed on a certain object. The object menu is automatically constructed by the MeeGo Touch framework when the tap and hold gesture is used on a widget. The contents of the menu are the QActions and MActions added to the widget.
Toolbar in landscape
Toolbar in portrait
The toolbar holds a list of the most important actions relevant to the current application page/view. The toolbar is reconfigured automatically based on the actions added to the currently active page.
The tab bar is an alternative way of providing navigation inside an application, where the most commonly used UI views are directly accessible from where the toolbar would normally reside.
Use a slider for a selecting a value from a range.
The seekbar is a specialization of the slider. Unlike the slider, it supports visualizing the amount of currently loaded content in the set value range.
A combobox allows the user to select a value from a pop-up selection list.
The progress indicator is used to show that an action is taking place and the expected duration thereof. If the duration is not known, the indicator can show this as well.
There are two types of progress indicators types:
Progress indicator, bar
Progress indicator, spinner
The banner provides a drop-in notification to the user on the screen that automatically disappears after a while. A banner created by an application is only visible in that single application. To create a system wide notification, use the MNotification API.
|Copyright © 2010 Nokia Corporation||Generated on Thu Nov 4 2010 18:14:23 (PDT)