author | Matti Hagman <ext-matti.hagman@nokia.com> |
Wed, 15 Sep 2010 17:28:26 +0300 | |
changeset 25 | eb17a7f7f320 |
parent 0 | 61163b28edca |
permissions | -rw-r--r-- |
0 | 1 |
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> |
2 |
<html> |
|
3 |
<head> |
|
4 |
<meta http-equiv="content-type" content="text/html; charset=iso-8859-1"> |
|
5 |
<title>Contact components</title> |
|
6 |
<link href="../../book.css" type="text/css" rel="stylesheet"> |
|
7 |
</head> |
|
8 |
<body> |
|
9 |
||
10 |
<h2>Contact components</h2> |
|
11 |
<p>The Contact component types are: </p> |
|
12 |
<ul> |
|
13 |
<li>Contact</li> |
|
14 |
<li>Contact group</li> |
|
15 |
<li>Contact set.</li> |
|
16 |
</ul> |
|
17 |
<p>These describe the contact items that should be created into the device’s database. You can either type in the needed values directly into the fields or select the <b>Random</b> options to let the S60 Creator tool generate contact items randomly. </p><p><b>Tip:</b> Instead of creating these items separately, you can also use the contact data that already exist in the Phonebook of your device. </p><p>Note the following specifics about contacts and contact sets:</p> |
|
18 |
<table width="500" border="1" cellspacing="1" cellpadding="2"> |
|
19 |
<colgroup> |
|
20 |
<col width="48*"> |
|
21 |
<col width="150*"></colgroup> |
|
22 |
<tbody> |
|
23 |
<tr> |
|
24 |
<td><b>Contact</b></td> |
|
25 |
<td><ul> |
|
26 |
<li><b>Contact set ID:</b> links this contact to a specific Contact set ID. |
|
27 |
</li> |
|
28 |
<li>A contact can have several fields of the same type, for example, multiple <b>Email</b> fields.</li> |
|
29 |
</ul></td> |
|
30 |
</tr> |
|
31 |
<tr> |
|
32 |
<td><b>Contact Group</b></td> |
|
33 |
<td><ul> |
|
34 |
<li><b>Contact set ID:</b> members of the group are taken from the defined |
|
35 |
contact set ID.</li> |
|
36 |
</ul></td> |
|
37 |
</tr> |
|
38 |
<tr> |
|
39 |
<td><b>Contact set</b></td> |
|
40 |
<td><p><b>Note:</b> The Contact set concept is a technical term that is only used to link contacts with messages and calendar items. It has no equivalent on the device.</p><ul> |
|
41 |
<li><b>Number of existing contacts:</b> uses contacts that already exist in the device's Phonebook. For example, value 5 here will include the first five Phonebook entries in the test data. </li> |
|
42 |
<li>ID numbers for contact sets are assigned automatically. </li> |
|
43 |
<li>On the Creator Script Editor view, each contact set is on a row of its own and does not contain other data except for the ID and Number of existing contacts.</li> |
|
44 |
</ul> |
|
45 |
<p>You can add new contact sets by clicking the <b>Add new Contact-set </b> button in the Creator Script Editor.</p></td> |
|
46 |
</tr> |
|
47 |
</tbody> |
|
48 |
</table> |
|
49 |
||
50 |
<h5>Related concepts</h5> |
|
51 |
<ul> |
|
52 |
<li><a href="../concepts/contact_set.htm">Contact set</a></li> |
|
53 |
</ul> |
|
54 |
||
55 |
<h5>Related references</h5> |
|
56 |
<ul> |
|
57 |
<li><a href="generic_items.htm">Generic component reference</a></li> |
|
58 |
</ul> |
|
59 |
||
25
eb17a7f7f320
Creator Carbide Extension 1.3.0
Matti Hagman <ext-matti.hagman@nokia.com>
parents:
0
diff
changeset
|
60 |
<div id="footer">Copyright © 2007-2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. |
0 | 61 |
License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a>.</div> |
62 |
</body> |
|
63 |
</html> |