Gebruiksaanwijzing /service van het product Series 60 van de fabrikant Nokia
Ga naar pagina of 84
NOKIA SERIES 60 UI STYLE GUIDE Copyright © Nokia Corp oration | ver. 1. 4 1.
Editorial notes A style guide should give an overview and provide enough guidelines for designing good applications, but not all the information to write the software. This is intended to be a compact and easy to read guide, w hich means skipping many details that ca n be found in other documen ts.
Contents ABOUT TH IS DOC UMENT ............................................................................................................ .................................... 7 PURPOSE ................................................................
NAVIGATION USIN G LINKS......................................................................................................... ............................ 25 5. UI COMPON ENTS ........................................................................
CONFIRMATIO N QUERY ............................................................................................................. .............................. 60 LIST QUER Y ...........................................................................
SELECT ING TEXT ................................................................................................................. ....................................... 80 DOCUMENT HANDLIN G ...........................................................
About this docu ment Purpose The Nokia Series 60 UI Style Guide gives an overview of the Series 60 user interfac e and describes the essenti al parts of it, giving examples of how to use the inte rface elements. The Nokia Series 60 UI Style Guide can be used as an introduction to the style or as reference m aterial.
1. WHERE N OKIA SERI ES 60 UI BELONGS Nokia Series 60 UI is intend ed for use in high er end mo bile phones featuring person al information management (PIM) and mul timedia applications such as: Calen.
2. HARDW ARE REQUIREME NTS Nokia Series 60 UI has cer tain requirements concerning the hardware. This section lists the assumed hardware for the first implementation; it is possible to extend and modify the hardw are to some ex tent for s ubsequent product gene rations.
Keys The following keys are required for Seri es 60 UI: navigation keys Scroll up Scroll down Scroll left Scroll right Select key softkeys Left softkey Right softkey call handling Send key End key oth.
3. GRAPHICAL COMPONENTS Wind ows an d pa nes The display layouts are hierarchically organised. The layo uts are built using components called windows and pane s . screen Screen is the topmost display component, corresponding to the entire pixel area of the physical screen.
- status pane - main pane - softkey pane See the dedicated sections for more detailed descriptions on each of these pan es. pop-up window A pop-up window does not fill the e ntire screen; the pop-up window has a frame, and typically the underlying application is partly visible around the pop-up window.
Applications can also use the main pane ar ea to freely draw w hatever is needed. In that case, however, the resp onsibility of the look and feel is entirely on the application's designer. General guidelines for designing application specific main pane layouts can be found e lsewhere in this documen t.
Context pane Context pane displays the current application's icon. Figure 3-4. Context pane. The user can r ecognize the a pplication by the con text p ane whe never th e title pane contains a context - s pecific text.
design guideline, the number of tabs should b e kept low (max 6 recommended), and the number should not be dynamic. (See Tabs in section Int eraction sty le for a description of their effec t on navigation within an application.) Navigation text Figure 3-7.
Battery pane Battery indicator is only visible in the idle state. It displays the remaining energy level of the battery, using a g raphic al in dicator .
backstepping from one state to the previous state never leads into a temporary state; they are skipped. More information on these components c an be found in section U I compon ents . Options menu The commands and options tha t are avail able in the current context can be accessed via the options menu .
Prese ntat ion of t ext Justification Default text justification is left. There are only a few exc eptions to this, in specific cases, for example: Soft indicators in idle state.
Edit key - the interaction is different, causing the action on th e key release event. Certain keys, possibly in cert ain contexts only, m ay perform key repeat .
there is no item to open and no option to selec t (see section Sele ction list ). The Select key must not directly ac tivate any such function the user wo uld not expec t in the give n situation. Therefore, the con text specific options menu is offered in states wh ere no selectable i tems exist.
During calls: - Puts an active call on hold; makes a held c all active; swap s activ e and h eld calls if both exi st. - Answer a waiting call (if o nly one call exists already ). (See section Ca ll handling for more detailed descriptions.) In idle: - Brings up Last dialed calls list for redialing.
navigation keys t o select (hig hlight) text, which then enables the copy and cut functions. - In markable lists, using Edi t key together with navigation keys allows the u ser to mark several items of the list, then a func tion can be executed on all the marked items as one operation.
1 1-1 1-2 1-3 1-1-1 1-1-2 1-2-1 1-3-1 1-3-2 1-3-3 Figure 4-1. An example of a basic st ate hierarchy in an application . Solid lin es indicate moving forward from a state into a s ub-state .
Tab-controlled views apply the following rules: Moving from one tab view to another has no effec t on the function of the Ba ck softkey in these views : from all of them the back functi on lead s to the s ame place – the previous level in the application.
This additional navigation feature can be in terpreted as a shortcut b etween sibling folders. For folder navig ati on, the basic navigation rules are applied, noticing the following: Moving from one .
a. b. Figure 5-1 List highlightin g (a) and grid hi ghlighting (b). Empty lists and grids If there are no items to be displayed in a list or grid, the pane contains a text informing the user about the empty list. Figure 5-2. Empty list. Depending on the case, i t may be justified to prompt th e user to create the first item for an empty list.
If the new choice i tem is no t visible, all items are moved in the view to the appropriate direction so that the new item becomes full y visible. For example, if focus is moving down and the new item is currently b elow the bottom edge of the view, the i tems are moved up.
The indicator is situated in the control p ane, and it consists of two arrow images, on e pointing up and the other one down. The colours of the arrows dep end on the position of the focus, so that to.
The browsing in grids that scroll vertically resembles tr aditional scrolling in text editors, based on the ide a that the user ca n always move to t he correct ro w first and then move within the row to the correct item . The following rules are applied: Empty cells are skipped: the focus is never on an empty cell.
Horizontally scrolling grids may be used when the application design requir es it. For them, the browsing rules are applied by exchanging the horizontal and vertic al browsing rules. The example figures pre sented above are correct if turned 90 degre es counter-clockwise.
Left softkey (Select) select the item, do associated function Right softkey (Ca ncel) dismiss the menu; re turn to the state preceding the opening of menu Se nd key, Edit key ignored numeric keypad ignored other keys dismiss the menu and do th e default action of the key Examples of components usi ng menu lists are options m enu and list query.
Open a context-specific opti ons menu. This should only happen w hen the user cannot be assumed to know what happens if the Select key is pressed. The m enu should contain only high-priority options associated with the item in focus , not general items like Se ttings or Help.
Select 4 Figure 5-9. Context-specific Options menu opened from Select key. Keypad functions for sel ectio n lists: Scroll up / down move focus in the list Scroll le ft / right may be ignored, or may h.
Figure 5-10. Selection lists. Markable list A markable list is a selection list with the added marking feature . The user c an mark any number of i tems on the list while browsing it, and then e xecute a single command, which is applied to all the marked items.
The mark and unmark func tions are available in the Opti ons menu of the m arkable list. Alternatively, o r as a sh ortcut, th e user can keep the Edit key pr essed while usi ng the navigation and Select keys in the following w ay: Pressing the Select key while holding Edit marks the cur rent item.
For other keypad actions th an the ones described above, refer to the Select ion list section. Multiselection list Multiselection list is used when we want to emph asize t hat it is possible to s elect several items from a list at the same tim e. Typically, there is an operation going on that expects one or more i tems as input.
other keys cancel the list, and then do the default action of the key Setting lists Setting li st is a specific ki nd of selection list con taining setting items which the user can adjust. Setting lists are displayed in the m ain pane. Figure 5-13. A setting list.
values. Then the last option is named Ot her , and selecting it opens a data query for e ntering the new value. multiselection l ist setting Multiselection list setting allows the user to choose several simultaneous values from a pre–defined list. The setting editor displays the available values as a multi-selection list.
During a setting editor state, th e keypad func tions are: Scroll up / down pop-up, multiselection: bro wse the list text: move cursor slider: ignored Scroll le ft / right pop-up: ignored multiselecti.
If pop-up setting has only two available values (like On and Off) and no special procedure is needed when switching fro m one v alue to the o ther, th en the setting editor (list) need not be displaye d when the user presses the Select k ey; the item's value is ch anged immediately.
Forms without the Options softkey In case the form does no t need any context-specific fun ctions in the Options menu , the softkey interface can b e the same as in queries: left softkey is Done and the right softkey is Cancel. Done acce pts the contents and returns, wher ea the C ancel func tion discards all changes in the form and returns.
Left softkey (Opt ions) Options menu. (In a form without options menu, left softkey is Done .) Right softkey (Do ne) Accept the conten ts and ret urn to previous sta te.
Figure 5-20. Pop-up field. A pop-up field may also allow the user to enter a textual value in addition to the pre-defined values. Then the last option is name d for example Other , and selecting it opens a d ata query.
Partial items are not visible: when the list/grid pane area does no t exactly correspond to an integer number of items, the remaining area ou tside the last fully visible item appears em pty, displaying the background of the particular pane.
Standard elements in list items, associ ated with columns, ar e: column A - small graphic (icon) - item number ( see section Numbered it ems ) column B - heading (title or attribute of the item ) column AB - heading (title or attribute of the item ) - large graphic (e.
single-lin e item with gr aphic and heading Figure 5-26. small g raphic (A), h eadi ng t ext (B), main text (C) usage: - menu lists - selection lists, markable lists - multiselection lists There is a corresponding component for pop-up windows. single-lin e item with large graphic Figure 5-27.
primary text, secondary text (ABC) usage: - menu lists - selection lists double it em with large graphic Figure 5-31. large graphic (AB), primary text, secondary t ext (C ) usage: - menu lists - selection lists Like a double item, but with the g raphic added on the left side.
setting item Figure 5-34. attribute te xt (ABC ), valu e text (C ) usage: - setting lists A two-line layout: attribute text is on top line, value text (or graphic) on bottom line in a box. The valu e box may be omitted in order to create a regular selection item within a s etting list.
Figure 5-36. A setting list conta ining a non-setting item (Ca ll waiting) to acce ss another view. Grid types Grids are in many ways anal ogous to lists.
Figure 5-37. A find pane within a selection list of names in Phonebook . The standard functionality is as follows: Characters typed from the n umeric keypad appear in th e end of the string in the find pane. · · · · There is no cursor, so the us er can only add and remove characters in the end.
The options menu is a menu list displayed in a pop-up window. Selecting an item is done pressing either th e left softkey (OK) or the Select k ey. The user mus t either select an i tem from the list or cancel th e menu ; it can't be left pending during another action.
The number of items should be low, so th at the user does not n eed to scroll in order to see all of them. · · · · · Functions should not sometimes occur in m ain level and at other times in a submenu. Item s that ar e in a submenu should always b e found in the same submenu.
Delete operation should not be listed in the OK options menu. (The Clear ke y is a shortcut to th at function.) In case there are marked items in a list, the OK options menu should include th e mark/unmark functions.
Write 4 Submenu for message writing SMS Start writing a new short mess age. MMS Start writing a n ew multimedia message. email Start writing a new email. Create new Initiate creation of a new item . When more tha n one type of item can be created, a submenu may be used to select the type.
Mark / Unmark Mark or unmark the curr ent it em, depending on the current state. Mark all Unmark all Rename Rename the item in focus. + + + Add to contacts 4 Submenu fo r functions used to ad d contact informati on into the Phonebook. Create new Creates a new contac t item.
Notes A note is a feedb ack component that in forms the user about th e current situation. A note contains a text and possibly a graphic al element. The softkey labels are typically empty (a wait no te is an exception to this.) · Figure 5-40. An informat ion note.
operation. For this a softkey labeled, for example, “Cancel’ is provided. Figure 5-41. A wait note with a Cancel function in the right softkey. Some guidelines concerning note usage: Use a confirmation note when: The effect of the operation c an't be seen directly by some other me ans.
Soft notification s Soft Notifications ar e reminders th at inform the user of events that hav e occurred in the user’s absence, or while the user w as bu sy with som e application. Text, and also graphics, can be used to communicate t he message to the user.
Figure 5-43: A grouped soft notification. Th e heig ht of the window is dynamic and depends on the number of lines in th e list. Discarding soft notifications The application that launched a soft no tification can discard it without user intervention when the notification becomes obsolete.
Figure 5-44. Several stacked soft not ificatio ns. No te the graphic indicating multiple windows. Queries A query is a sta te where th e software waits for user inp ut.
proceed is possible, and the response text (for example ‘OK’) is placed on th e left softkey. The Selection key always causes the s ame action as the left softkey. Figure 5-45. A confirmation query. Guidelines for designing confirmation queries : When designing the promp t text, make sure the ‘positive’ answer is also the safe one.
Figure 5-46. A list query. The number of items in the list should be kept low, so that all items c an be seen without scrolling. Instead of a list, a grid c an be used in a q uery. The grid query func tion is otherwise identical to a list query. Figure 5-47.
Figure 5-48. Multiselection list query. Data query A data query requests the us er to type in some alphanumeric or num eric information, like a name or a phone num ber.
Figure 5-50. A password query window. Data queries with multi ple fields It is possible to have two in put fields in a data query. An ex ample of this is a user name and password query: one field is then a normal al phanumeric editor and the other a password editor.
The signal indicator is part of the status pa ne, and it is displayed in all states where the status p ane exi sts. The in dicator cons ists o f an an tenna i con and a b ar graph t hat indicates the current signal level. The antenna icon may be replac ed by another icon indicating the GPRS connection status.
Arrow icons on the left and right ends of navi pane indicate the possibility to move in the corresponding directions. (With tabs, the arrows are only displayed when all tabs are not visible.
Operator indicator In idle, the title pane con tains the operator indicator. I t is either a text or a graphic al image. Figure 5-58. A graphical operator indicator in the title pane. Scrolling indicators Arrowhead-shaped icons that indicate th e scrolling status in lists ar e situated between softkey labels in the softkey pane.
The softkeys can be configured by th e user to access vari ous applications. · · · · · · · Scroll up, scroll down: open the Phon ebook. Scroll left, scroll right: unassigned by def ault, may be assigned by th e user.
Shortcuts When the Application shell has been open ed and no navigation has taken place, the numeric keys 1-9 ca n be used as shor tcuts to selecting an application. The keys are mapped directly to the 9 ico ns in the shell’s initi al view, so that key 1 corr esponds to the top-left application and key 9 to th e bottom-right one.
However, software modules that several applications can use (such as editors) may run simultaneously in more th an one application. The user m ay thus see the same feature being run in s everal different applic ations at the same time.
It is also possible to go to Idle state of t he phone and le ave an application running. This can be done by pressing the End key, or by selec ting the Phone application from the Application shell. (The Phone application and Idl e state are mutually exclusive states in th e phone: when t here is a voice ca ll going on, ther e is no Idle s tate.
saves it automatically into a default plac e, and if there’s a pending dialog it will be canceled. The u ser is not asked questions; all the operations needed to bring the application to th e target s t a te are d one automati cally. After switching applications in this way, the Back function does not lead to the previous state.
In simple one-call cases, the Phone application looks like this: a. b. Figure 6-6. Phone application examples: a. Creating an outgoing c all; b. A ctiv e call going on. More complex cases, whe re more than one c all is involved, may also happen. The locations and sizes of individual call win dows change according to the situation: a.
Figure 6-8. Call status window, used when Phone a pplication does not reside on sc reen. Call handling Calls are handled using the Send and End k eys as follows: Send - Answers the incoming call when the phone rings or there is a waiting c all. - Creates an outgoing call when there is a number entry window ac tive.
Figure 6-9. Volume indicator in the Na vi pane. Viewers and players Viewers are used for displaying read-only da t a. Examples of viewers ar e SMS, e-mail, and image view ers. To edit or create new data , the user sta rts an editor ; the viewer may offer a n option for starting an editor.
Multimedia viewers For viewers that support sev eral forms of data, the c apabilities should be extended, while still keeping the core functions consis tent with text viewers. For example, the viewed data may contain graphical still images that are displayed among text.
Forward / Rewind Fast playing of the piece, using short audio clips, forwar d or reverse. · · Faster / Slower Changes the speed of playin g the audio, without changing the pitch. Can b e useful with voice m emos, for example. Playing functions shall be av ailable in the player’s menu of options.
Selects characters when pressed simultaneously with navigation keys (see section Selecting text below). Edit menu Editing-specific functions can be acc essed using the Edit menu .
Figure 6-10. Special charact er win dow. Editing indicators The status of the editor is di splayed using graphic indicators. They inform the user about things such as: Editing mode (numeric/alphanumer.
Selecting text A chunk of text c an be selected in an editor by keeping the Edi t key pressed and using the navigation keys (s croll left/right/up/down). The selected text is shown using a highlight. The Cut and Copy functions are available wh en text is selected.
Saving edited data Various kinds of documents may have diff er ent requir ements conc erning the b ehavior of keeping or discarding the edited data. Typically one enters data, or modifies i t, in an editor, and then closes t he editor accep ting the new data.
Folders When there are a lot of data items to be man aged, it makes sens e to divide them into smaller sets. A folder is a place where a s et of ite ms can be collected. A folder can be present among single items in a direc tory, but it can be opened in order to view its contents.
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 addre ss from the Phonebook. This is called fe tching . It is a read-only operation: the user cannot edit the data, only browsing and s electing are possible.
84.
Een belangrijk punt na aankoop van elk apparaat Nokia Series 60 (of zelfs voordat je het koopt) is om de handleiding te lezen. Dit moeten wij doen vanwege een paar simpele redenen:
Als u nog geen Nokia Series 60 heb gekocht dan nu is een goed moment om kennis te maken met de basisgegevens van het product. Eerst kijk dan naar de eerste pagina\'s van de handleiding, die je hierboven vindt. Je moet daar de belangrijkste technische gegevens Nokia Series 60 vinden. Op dit manier kan je controleren of het apparaat aan jouw behoeften voldoet. Op de volgende pagina's van de handleiding Nokia Series 60 leer je over alle kenmerken van het product en krijg je informatie over de werking. De informatie die je over Nokia Series 60 krijgt, zal je zeker helpen om een besluit over de aankoop te nemen.
In een situatie waarin je al een beziter van Nokia Series 60 bent, maar toch heb je de instructies niet gelezen, moet je het doen voor de hierboven beschreven redenen. Je zult dan weten of je goed de alle beschikbare functies heb gebruikt, en of je fouten heb gemaakt die het leven van de Nokia Series 60 kunnen verkorten.
Maar de belangrijkste taak van de handleiding is om de gebruiker bij het oplossen van problemen te helpen met Nokia Series 60 . Bijna altijd, zal je daar het vinden Troubleshooting met de meest voorkomende storingen en defecten #MANUAl# samen met de instructies over hun opplosinge. Zelfs als je zelf niet kan om het probleem op te lossen, zal de instructie je de weg wijzen naar verdere andere procedure, bijv. door contact met de klantenservice of het dichtstbijzijnde servicecentrum.
