--- a/Symbian3/PDK/Source/GUID-A5756C5F-9C93-4949-8B60-03DCA1BAF683.dita Tue Mar 30 11:42:04 2010 +0100
+++ b/Symbian3/PDK/Source/GUID-A5756C5F-9C93-4949-8B60-03DCA1BAF683.dita Tue Mar 30 11:56:28 2010 +0100
@@ -4,10 +4,13 @@
"Eclipse Public License v1.0" which accompanies this distribution,
and is available at the URL "http://www.eclipse.org/legal/epl-v10.html". -->
<!-- Initial Contributors:
- Nokia Corporation - initial contribution.
+ Nokia Corporation - initial contribution.
Contributors:
---> <!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"><concept id="GUID-A5756C5F-9C93-4949-8B60-03DCA1BAF683" xml:lang="en"><title>Form
-items</title><prolog><metadata><keywords></keywords></metadata></prolog><conbody>
+-->
+<!DOCTYPE concept
+ PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
+<concept id="GUID-A5756C5F-9C93-4949-8B60-03DCA1BAF683" xml:lang="en"><title>Form
+items</title><prolog><metadata><keywords/></metadata></prolog><conbody>
<p>Empty items (that contain no data) can be hidden in a form's View state.
However, this is not a requirement; forms can be designed either way, whichever
is better for the given application.</p>
@@ -20,13 +23,58 @@
<p>Form items always have a label. The label has a text part, or a text and
a graphical part; however, all items in one form must have the same column
layout (see <xref href="GUID-CB548959-A1D6-4585-B8E3-B09E37E0CB43.dita">List layouts</xref> for
-detailed information about layouts).</p>
-<p>The following item types can be used in a form:</p>
-<ul>
-<li><p>Text field (alphanumeric or numeric content) </p></li>
-<li><p>Pop-up field </p></li>
-<li><p>Slider</p></li>
-</ul>
+detailed information about layouts). Field label cannot be directly edited
+even if the form is in Edit state. However, it is possible to let the user
+edit the label text when the form is in edit state. User can choose to edit
+the label with an option, which can be found in the <b>Options</b> menu.</p>
+<p>The form field types that can be used are described in the following table:</p>
+<table id="GUID-A22394D3-9C39-4DC2-8A65-255F985F97E9"><title> Form field types</title>
+<tgroup cols="2"><colspec colname="col1" colwidth="0.30*"/><colspec colname="col2" colwidth="1.70*"/>
+<thead>
+<row>
+<entry>Field</entry>
+<entry>Description</entry>
+</row>
+</thead>
+<tbody>
+<row>
+<entry><p>Text field (alphanumeric or numeric content)</p></entry>
+<entry><p>A text field contains some type of numeric or alphanumeric data.
+It can be edited directly using the usual editing functions when the form
+is in the Edit state. The text field can expand to more than one lines if
+necessary.</p><p>In the View state, a text field looks identical to a corresponding
+list item.</p></entry>
+</row>
+<row>
+<entry><p>Pop-up field</p></entry>
+<entry><p>A pop-up field offers the possibility to choose one value from a
+pre-defined list. In the View state, a pop-up field looks identical to a list
+item; the text is the current value of the field. In the Edit state, it has
+a distinct look that identifies the field as a pop-up list.</p><p>To edit
+an item in the Edit state, the user can press the Selection key or with single
+click (in tap enabled devices), which opens a menu list that contains the
+available values. The highlight is on the current value. When the list is
+open, the softkeys are <b>OK</b> and <b>Cancel</b>, as usual with a menu list.
+Both the softkeys return to the Edit state in the form.</p><p>A pop-up field
+may also allow the user to enter a textual value in addition to the pre-defined
+values. In this case, the last option is named for example <b>Other</b>, and
+selecting it opens a Data query.</p><p>See figure below.</p></entry>
+</row>
+<row>
+<entry><p>Slider</p></entry>
+<entry><p>With a slider, the user can adjust a numeric value (although it
+is not necessary to present the actual value to the user as a number). In
+the View state, the item is presented as a textual item. In the Edit state,
+the value of the slider is immediately adjustable using the Arrow left and
+Arrow right keys.</p></entry>
+</row>
+</tbody>
+</tgroup>
+</table>
+<fig id="GUID-AA0170E3-BBB2-478A-A9A1-24C48BCF917F">
+<title>Pop-up field</title>
+<image href="GUID-DC4E42CA-2A65-44D7-8DBE-386F60F998A0_d0e91827_href.png" scale="40" placement="inline"/>
+</fig>
<p>Any combination of these types is possible within one form.</p>
<p>When a form is in the Edit state, the user can move the focus up and down
like in a list. The highlight in the Edit state is different from the highlight
@@ -35,9 +83,10 @@
can browse and modify the fields in any order and then accept all modifications.
During the browsing of a form in the Edit state, the keypad functions are
as follows:</p>
+<p>The field types are described in the following table:</p>
<table id="GUID-437191CE-D3E0-4CFB-875C-9C308B18F7E9"><title>Default key events
in editing state of a form</title>
-<tgroup cols="2"><colspec colname="col1"></colspec><colspec colname="col2"></colspec>
+<tgroup cols="2"><colspec colname="col1" colwidth="0.30*"/><colspec colname="col2" colwidth="1.70*"/>
<thead>
<row>
<entry>Key</entry>
@@ -107,56 +156,7 @@
</tbody>
</tgroup>
</table>
-<p>The field types are described in the following table:</p>
-<table id="GUID-A22394D3-9C39-4DC2-8A65-255F985F97E9"><title> Form field types</title>
-<tgroup cols="2"><colspec colname="col1"></colspec><colspec colname="col2"></colspec>
-<thead>
-<row>
-<entry>Field</entry>
-<entry>Description</entry>
-</row>
-</thead>
-<tbody>
-<row>
-<entry><p>Text field</p></entry>
-<entry><p>A text field contains some type of numeric or alphanumeric data.
-It can be edited directly using the usual editing functions when the form
-is in the Edit state. The text field can expand to more than one lines if
-necessary.</p><p>In the View state, a text field looks identical to a corresponding
-list item.</p></entry>
-</row>
-<row>
-<entry><p>Pop-up field</p></entry>
-<entry><p>A pop-up field offers the possibility to choose one value from a
-pre-defined list. In the View state, a pop-up field looks identical to a list
-item; the text is the current value of the field. In the Edit state, it has
-a distinct look that identifies the field as a pop-up list.</p><p>To edit
-an item in the Edit state, the user can press the Selection key, which opens
-a menu list that contains the available values. The highlight is on the current
-value. When the list is open, the softkeys are <b>OK</b> and <b>Cancel</b>,
-as usual with a menu list. Both the softkeys return to the Edit state in the
-form.</p><p>A pop-up field may also allow the user to enter a textual value
-in addition to the pre-defined values. In this case, the last option is named
-for example <b>Other</b>, and selecting it opens a Data query.</p><p>See figure
-below.</p></entry>
-</row>
-<row>
-<entry><p>Slider</p></entry>
-<entry><p>With a slider, the user can adjust a numeric value (although it
-is not necessary to present the actual value to the user as a number). In
-the View state, the item is presented as a textual item. In the Edit state,
-the value of the slider is immediately adjustable using the Arrow left and
-Arrow right keys.</p></entry>
-</row>
-</tbody>
-</tgroup>
-</table>
-<fig id="GUID-AA0170E3-BBB2-478A-A9A1-24C48BCF917F">
-<title>Pop-up field</title>
-<image href="GUID-DC4E42CA-2A65-44D7-8DBE-386F60F998A0_d0e81272_href.png" scale="40" placement="inline"></image>
-</fig>
-<section><title>Using forms in C++ applications</title><p>The
-API to use for creating forms is the Form
-API. For implementation information, see Using
-the Form API.</p></section>
+<section id="GUID-E6A426E6-FC7E-4620-9CAE-BA9214AC17F8"><title>Using
+forms in C++ applications</title><p>The API to use for creating forms is the <xref format="html" href="specs/guides/Form_API_Specification/Form_API_Specification.html" scope="peer">Form API</xref>. For implementation information,
+see <xref format="html" href="specs/guides/Form_API_Specification/Form_API_Specification.html#Form_API_Specification.topic3" scope="peer">Using the Form API</xref>.</p></section>
</conbody></concept>
\ No newline at end of file