×
Namespaces

Variants
Actions
(Difference between revisions)

Queries

From Nokia Developer Wiki
Jump to: navigation, search
Rahulsingh1m (Talk | contribs)
hamishwillee (Talk | contribs)
m (Text replace - "Category:Mobile Design" to "")
 
(13 intermediate revisions by 4 users not shown)
Line 1: Line 1:
[[Category:Usability]][[Category:Mobile_Design]]
+
[[Category:Usability]]
 +
{{ArticleMetaData <!-- v1.2 -->
 +
|sourcecode= <!-- Link to example source code e.g. [[Media:The Code Example ZIP.zip]] -->
 +
|installfile= <!-- Link to installation file (e.g. [[Media:The Installation File.sis]]) -->
 +
|devices= <!-- Devices tested against - e.g. ''devices=Nokia 6131 NFC, Nokia C7-00'') -->
 +
|sdk= <!-- SDK(s) built and tested against (e.g. [http://linktosdkdownload/ Qt SDK 1.1.4]) -->
 +
|platform= <!-- Compatible platforms - e.g. Symbian^1 and later, Qt 4.6 and later -->
 +
|devicecompatability= <!-- Compatible devices e.g.: All* (must have internal GPS) -->
 +
|dependencies= <!-- Any other/external dependencies e.g.: Google Maps Api v1.0 -->
 +
|signing= <!-- Signing requirements - empty or one of: Self-Signed, DevCert, Manufacturer -->
 +
|capabilities= <!-- Capabilities required by the article/code example (e.g. Location, NetworkServices. -->
 +
|keywords= <!-- APIs, classes and methods (e.g. QSystemScreenSaver, QList, CBase -->
 +
|language= <!-- Language category code for non-English topics - e.g. Lang-Chinese -->
 +
|translated-by= <!-- [[User:XXXX]] -->
 +
|translated-from-title= <!-- Title only -->
 +
|translated-from-id= <!-- Id of translated revision -->
 +
|review-by= <!-- After re-review: [[User:username]] -->
 +
|review-timestamp= <!-- After re-review: YYYYMMDD -->
 +
|update-by= <!-- After significant update: [[User:username]]-->
 +
|update-timestamp= <!-- After significant update: YYYYMMDD -->
 +
|creationdate= 20090621
 +
|author= [[User:Rahulsingh1m]]
 +
}}
 +
 
  
 
Queries are used in situations with more than one ways to proceed, when the application needs data from the user, or
 
Queries are used in situations with more than one ways to proceed, when the application needs data from the user, or
 
when it is necessary to make sure the user knows what is happening. A query must be exited before the application can proceed.
 
when it is necessary to make sure the user knows what is happening. A query must be exited before the application can proceed.
  
Queries are displayed in pop-up windows. The following query types can be used:<br/>
+
Queries are displayed in pop-up windows. The following query types can be used:
1. '''Confirmation query:''' a question or notice with one or two possible responses.
+
 
[[Image:query11.jpg]]<br/>
+
# '''Confirmation query:''' a question or notice with one or two possible responses.<br/>
2. '''List query:''' a question with a selection of more than two possible (predefined) responses.<br/>
+
#: [[File:query11.jpg]]
3. '''Multi-selection List query:''' presents a list of items; the user can select any number of them.<br/>
+
# '''List query:''' a question with a selection of more than two possible (predefined) responses.<br/>
4. '''Data query:''' used for numeric or textual input.<br/>
+
#: [[File:query12.jpg]]
5. '''Message query:''' used for various purposes in queries that are longer than one screen.<br/>
+
# '''Multi-selection List query:''' presents a list of items; the user can select any number of them.<br/>
 +
#: [[File:query13.jpg]]
 +
# '''Data query:''' used for numeric or textual input.<br/>
 +
#: [[File:query14.jpg]]
 +
# '''Message query:''' used for various purposes in queries that are longer than one screen.<br/>
 +
#: [[File:query15.jpg]]
 +
 
 +
== Some usability guidelines ==
 +
 
 +
* Queries should be displayed in pop-up windows.
 +
* Queries should consist of a prompt and some kind of an input component.
 +
* Make sure the prompt text for the Confirmation query should be giving a positive sign. Users tend to press the Selection key without thinking too much.
 +
* For the Data query, the input field should be able to extend automatically in case the input text is more than one line.
 +
* Activate text prediction (T9) for text input.
 +
* The query text should be meaningful and localized.
 +
* The user should be given help in case of a query which might be complicated to understand from user perspective.

Latest revision as of 06:42, 9 May 2012

Article Metadata
Article
Created: User:Rahulsingh1m (21 Jun 2009)
Last edited: hamishwillee (09 May 2012)


Queries are used in situations with more than one ways to proceed, when the application needs data from the user, or when it is necessary to make sure the user knows what is happening. A query must be exited before the application can proceed.

Queries are displayed in pop-up windows. The following query types can be used:

  1. Confirmation query: a question or notice with one or two possible responses.
    Query11.jpg
  2. List query: a question with a selection of more than two possible (predefined) responses.
    Query12.jpg
  3. Multi-selection List query: presents a list of items; the user can select any number of them.
    Query13.jpg
  4. Data query: used for numeric or textual input.
    Query14.jpg
  5. Message query: used for various purposes in queries that are longer than one screen.
    Query15.jpg

[edit] Some usability guidelines

  • Queries should be displayed in pop-up windows.
  • Queries should consist of a prompt and some kind of an input component.
  • Make sure the prompt text for the Confirmation query should be giving a positive sign. Users tend to press the Selection key without thinking too much.
  • For the Data query, the input field should be able to extend automatically in case the input text is more than one line.
  • Activate text prediction (T9) for text input.
  • The query text should be meaningful and localized.
  • The user should be given help in case of a query which might be complicated to understand from user perspective.
This page was last modified on 9 May 2012, at 06:42.
122 page views in the last 30 days.
×