Filter
Top Products
Fetching data
Often it is necessary to be able to pick up a piece of data from an application, such
as a phone number or address from the Phonebook. This is called fetching. It is a
read-only operation: the user cannot edit the data, only browsing and selecting are
possible.
Browsing data during a fetch operation should resemble the application’s normal
use: the data should be arranged the same way so that it is easy to find. Only the
available functions are different: the data can’t be edited.
The left softkey during a fetch operation is labeled Select, and it activates the same
function as the Select key: it selects the data currently in focus. The right softkey is
Cancel, and returns to the previous state without bringing back any data.
Sometimes it is feasible to use a multiselection list for fetching data. This should be
done when it is probable that the user wants to select more than one item for
fetching. An example of this is creating a group in the Phonebook to be used as a
distribution list: a list of names is offered to the user, and since the probable
intention is to have more than one name in the group, a multiselection list is a good
tool to use. (See section Multiselection list in the UI components chapter.)
Settings
Global settings – the ones that affect several applications or general issues within
the device, are collected into the General Settings application.
Application-specific settings are handled within the application UI. They should be
collected into a settings view that can be accessed via the Options menu. The
Settings option exists at least in the application’s initial or basic state, and possibly
also in other states where it would be beneficial to have easy access to settings –
especially to some context-dependent settings. The settings view is a list of setting
items (see the list item type description in the List types section).
Sometimes a general setting may be duplicated as an application-specific setting.
The order of priorities for duplicate settings must be specified case by case. For
example, a general predictive text setting could be overridden by an application-
specific setting, but a general ‘silent mode’ setting within a profile should be
effective regardless of any other tone settings.
If the number of setting items (within an application) is large, it may be necessary to
divide them into groups. The grouping can be done in the following ways:
Use tabs to access different setting groups ·
· Design a hierarchical setting tree, use 'setting folders' in the top level (there may
be individual settings and folders in one list; this is an exception to the rule that
only setting items should exist in one list).
83