|
1 <?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> |
|
2 <html lang="en" xml:lang="en"> |
|
3 <head> |
|
4 <meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> |
|
5 <meta name="copyright" content="(C) Copyright 2005" /> |
|
6 <meta name="DC.rights.owner" content="(C) Copyright 2005" /> |
|
7 <meta content="concept" name="DC.Type" /> |
|
8 <meta name="DC.Title" content="Terminology" /> |
|
9 <meta scheme="URI" name="DC.Relation" content="WRTKit_Overview_of_the_WRTKit-GUID-14c414f6-a220-40b6-8614-df13141495ab.html" /> |
|
10 <meta content="XHTML" name="DC.Format" /> |
|
11 <meta content="GUID-EBD8D7C4-03F6-498D-BECC-EB8D4081ED8B" name="DC.Identifier" /> |
|
12 <meta content="en" name="DC.Language" /> |
|
13 <link href="commonltr.css" type="text/css" rel="stylesheet" /> |
|
14 <title> |
|
15 Terminology</title> |
|
16 </head> |
|
17 <body id="GUID-EBD8D7C4-03F6-498D-BECC-EB8D4081ED8B"><a name="GUID-EBD8D7C4-03F6-498D-BECC-EB8D4081ED8B"><!-- --></a> |
|
18 |
|
19 |
|
20 |
|
21 <h1 class="topictitle1"> |
|
22 Terminology</h1> |
|
23 |
|
24 <div> |
|
25 |
|
26 <div class="section"><h2 class="sectiontitle"> |
|
27 Control</h2> |
|
28 |
|
29 |
|
30 <p> |
|
31 |
|
32 A control is a user interface element that the user can interact with. Controls |
|
33 are used in PC applications, in web pages and in mobile device applications. In |
|
34 web pages controls are often known as "form controls". Common controls include |
|
35 textfields, textareas, buttons, checkboxes, radio buttons, scrollbars, labels |
|
36 and progress bars, among others. Not all controls are interactive, e.g. labels |
|
37 simply display a value. Controls are contained within some kind of user |
|
38 interface container such as a view or window. |
|
39 </p> |
|
40 |
|
41 <p> |
|
42 |
|
43 In the WRTKit, controls are JavaScript objects that contain the state and |
|
44 implement the behavior of the control. Controls take care of drawing themselves, |
|
45 including changing their appearence as a result of various state changes. |
|
46 </p> |
|
47 |
|
48 </div> |
|
49 |
|
50 <div class="section"><h2 class="sectiontitle"> |
|
51 View</h2> |
|
52 |
|
53 |
|
54 <p> |
|
55 |
|
56 A container for user interface elements such as controls. On a mobile device |
|
57 user interface views typically fill the entire screen and thus only one view can |
|
58 be shown at a time. Views in a mobile device tend to lay out the elements it |
|
59 contains in a vertical list that can be scrolled up and down if there is more |
|
60 content in the view than what fits on the screen at a time. |
|
61 </p> |
|
62 |
|
63 <p> |
|
64 |
|
65 In the WRTKit, views are responsible for laying out controls. Custom views can |
|
66 be created to support advanced layouts but in the vast majority of cases the |
|
67 default ListView is sufficient. WRTKit views are JavaScript objects. |
|
68 </p> |
|
69 |
|
70 </div> |
|
71 |
|
72 <div class="section"><h2 class="sectiontitle"> |
|
73 Event</h2> |
|
74 |
|
75 |
|
76 <p> |
|
77 |
|
78 An event is a notification of some occurrence in a user interface element, such |
|
79 as a view or control. Events are typically propagated to application code as |
|
80 messages or function calls or a combination of the two. |
|
81 </p> |
|
82 |
|
83 <p> |
|
84 |
|
85 The WRTKit uses a model known as the "observer pattern" to deliver event |
|
86 messages, which are JavaScript objects, to event listeners, which are JavaScript |
|
87 callback functions. WRTKit events have a type name that can be used to |
|
88 distinguish between different types of events. E.g. a button press produces an |
|
89 "ActionPerformed" event. |
|
90 </p> |
|
91 |
|
92 </div> |
|
93 |
|
94 <div class="section"><h2 class="sectiontitle"> |
|
95 Focus</h2> |
|
96 |
|
97 |
|
98 <p> |
|
99 |
|
100 The control that is currently selected to receive input is said to be focused. |
|
101 Controls can be focused in both the tab and pointer navigation modes. In the tab |
|
102 mode the focus is moved between controls using the 4-way controller. In |
|
103 the pointer mode the focus is moved between controls by moving the pointer to |
|
104 "hover" above a control and then pressing a selection button to select that |
|
105 control. Focused controls are displayed in a distinct way from other controls to |
|
106 indicate that they are ready to be interacted with. |
|
107 </p> |
|
108 |
|
109 </div> |
|
110 |
|
111 <div class="section"><h2 class="sectiontitle"> |
|
112 Hovering</h2> |
|
113 |
|
114 |
|
115 <p> |
|
116 |
|
117 In pointer navigation mode, the pointer is said to be "hovering" above a control |
|
118 if the pointer is located inside the control's area on the screen. Hovering is |
|
119 similar to focus, but differs because hovering in itself does not select a |
|
120 control for interaction. Rather a selection key must be pressed in order to |
|
121 focus the control that the pointer is currently hovering over. Hover is |
|
122 indicated by displaying a control in a distinct way from other controls. |
|
123 </p> |
|
124 |
|
125 </div> |
|
126 |
|
127 <div class="section"><h2 class="sectiontitle"> |
|
128 Navigation mode</h2> |
|
129 |
|
130 |
|
131 <p> |
|
132 |
|
133 A navigation mode refers to a method of selecting what user interface element to |
|
134 interact with. The S60 Web Runtime supports two navigation modes: "tab" and |
|
135 "pointer". In the tab mode, focus is moved between controls using the 4-way |
|
136 controller. In pointer mode there is a pointer arrow on the screen that can be |
|
137 moved freely using the 4-way controller. A control is focused by moving the |
|
138 pointer arrow so that it hovers above a control, and then pressing a selection |
|
139 key to select that control. In tab mode a control can be either in normal or |
|
140 focused state, whereas in the pointer mode a control can be in normal, hover or |
|
141 focused state. |
|
142 </p> |
|
143 |
|
144 </div> |
|
145 |
|
146 </div> |
|
147 |
|
148 <div> |
|
149 <div class="familylinks"> |
|
150 <div class="parentlink"><strong>Parent topic:</strong> <a href="WRTKit_Overview_of_the_WRTKit-GUID-14c414f6-a220-40b6-8614-df13141495ab.html">Overview of the WRTKit</a></div> |
|
151 </div> |
|
152 </div> |
|
153 |
|
154 </body> |
|
155 </html> |