week 10 bug fix submission: Bug 1892, Bug 1897, Bug 1319. Also 3 or 4 documents were found to contain code blocks with SFL, which has been fixed. Partial fix for broken links, links to Forum Nokia, and the 'Symbian platform' terminology issues.
--- a/Symbian3/SDK/Source/GUID-00113601-193D-5214-9DFB-1C67456B7039.dita Fri Jan 22 18:26:19 2010 +0000
+++ b/Symbian3/SDK/Source/GUID-00113601-193D-5214-9DFB-1C67456B7039.dita Thu Mar 11 15:24:26 2010 +0000
@@ -9,6 +9,6 @@
-->
<!DOCTYPE concept
PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
-<concept id="GUID-00113601-193D-5214-9DFB-1C67456B7039" xml:lang="en"><title>About the Symbian
-Developer Library</title><shortdesc>The following sections are about the Symbian Developer Library
+<concept id="GUID-00113601-193D-5214-9DFB-1C67456B7039" xml:lang="en"><title>About this
+Library</title><shortdesc>The following sections are about the Symbian Developer Library
- what it contains, who should read it, and how it is organised.</shortdesc><prolog><metadata><keywords/></metadata></prolog></concept>
\ No newline at end of file
--- a/Symbian3/SDK/Source/GUID-05931546-C3C9-4085-8D5F-6B6C3F21D24C.dita Fri Jan 22 18:26:19 2010 +0000
+++ b/Symbian3/SDK/Source/GUID-05931546-C3C9-4085-8D5F-6B6C3F21D24C.dita Thu Mar 11 15:24:26 2010 +0000
@@ -27,6 +27,8 @@
<li><p>Deleting a trigger</p></li>
<li><p>Handling a trigger firing event.</p></li>
</ul>
+<p>For detailed information about the Location Triggering API, see the Location
+Triggering API Specification document.</p>
</conbody><related-links>
<link href="GUID-D0318BB6-0B9F-5A1C-AB0B-61BA22D28661.dita"><linktext>Location
Acquisition API</linktext></link>
--- a/Symbian3/SDK/Source/GUID-0817AD1D-58CF-5108-ACBF-26DFD4BA395E.dita Fri Jan 22 18:26:19 2010 +0000
+++ b/Symbian3/SDK/Source/GUID-0817AD1D-58CF-5108-ACBF-26DFD4BA395E.dita Thu Mar 11 15:24:26 2010 +0000
@@ -71,7 +71,14 @@
data that rarely changes. </p> </li>
<li id="GUID-A15A3A8B-4B8A-58FB-A972-91242331502D"><p>Use <codeph>RBuf</codeph> for
data that changes frequently. </p> </li>
-</ul> </section>
+</ul> <p><b>Example code</b></p><p>For
+examples, see:</p><ul>
+<li><p><xref href="GUID-14FAE656-7CDE-56ED-ACB2-7853276C24E9.dita">Descriptor Example
+Code</xref></p></li>
+<li><p><xref href="http://developer.symbian.org/wiki/index.php/Descriptors_Cookbook.dita">Descriptors
+Cookbook</xref> at the Symbian Foundation.</p></li>
+<li><p><xref href="http://www.forum.nokia.com/info/sw.nokia.com/id/9c61aadd-8ae7-4c19-9484-2b165f0cb55e/S60_Platform_Descriptor_Example_v2_1_en.zip.html" scope="external">S60 Platform: Descriptor Example v2.1</xref> on Forum Nokia.</p></li>
+</ul></section>
<section id="GUID-72EDBF0F-A0EB-4D93-85D0-55D0EA4740BB"><title>See also</title> <p> <xref href="GUID-EA98D77C-743B-5BA5-B131-A327B12A099C.dita">Character Representation
Of Real Numbers Overview</xref> </p> <p> <xref href="GUID-C15F56E3-753C-55CA-B3EF-63B2D139BCE4.dita">Dynamic
Buffers Overview</xref> </p> <p> <xref href="GUID-106B5A31-012E-503D-A972-A745ECADC1E7.dita">Literals
--- a/Symbian3/SDK/Source/GUID-092C18D4-A525-5562-9BF6-41435E400290.dita Fri Jan 22 18:26:19 2010 +0000
+++ b/Symbian3/SDK/Source/GUID-092C18D4-A525-5562-9BF6-41435E400290.dita Thu Mar 11 15:24:26 2010 +0000
@@ -12,26 +12,27 @@
<concept id="GUID-092C18D4-A525-5562-9BF6-41435E400290" xml:lang="en"><title>LibpThread
Example - Using P.I.P.S OECORE </title><prolog><metadata><keywords/></metadata></prolog><conbody>
<p>This example application shows, using a P.I.P.S. (P.I.P.S. Is POSIX on
-Symbian OS) program, the use of the LibpThread library to demonstrate simple
-multi-threading and synchronisation. </p>
+the Symbian platform) program, the use of the LibpThread library to demonstrate
+simple multi-threading and synchronisation. </p>
<p>The purpose is to create a basic multithreading example showing the usage
of the LibpThread APIs. This example also shows how multi-threading is used
to achieve concurrency in tasks and sharing of resources. </p>
-<section id="GUID-026FD8D6-6C4A-5958-B289-775D4AE1E756"><title>Download</title> <p>Click
+<section id="GUID-026FD8D6-6C4A-5958-B289-775D4AE1E756-GENID-1-6-1-9-1-1-5-1-3-1-11-1-7-1-2-3"><title>Download</title> <p>Click
on the following link to download the example: <xref href="guid-6013a680-57f9-415b-8851-c4fa63356636/zips/guid-84e8baf2-57f1-4255-aeb8-a6ed0ed2145e.zip" scope="external"> LibpThreadExample.zip</xref></p><p>Click: <xref href="guid-6013a680-57f9-415b-8851-c4fa63356636/guid-84e8baf2-57f1-4255-aeb8-a6ed0ed2145e.html" scope="peer">browse</xref> to view the example code. </p> </section>
-<section><title>Description</title> <p>The following sections provide more
-information about the steps that the example performs. </p> <p><b> Thread
-Synchronisation</b> </p> <p>The example creates three threads named ThreadOne,
-ThreadTwo and ThreadThree. The threads write "One", "Two" and "Three" five
-times in a text file. The text file, located in <filepath>epoc32\winscw\c\newfile.txt</filepath>,
-is used as a shared resource for all three threads. A mutex is used to ensure
-that first ThreadOne writes in the file, then ThreadTwo and then ThreadThree.
-If the mutex is not used all the threads can simultaneously write in the file.
-This can be seen by commenting out <codeph>pthread_mutex_lock</codeph> and <codeph>pthread_mutex_unlock</codeph> in
+<section id="GUID-7E7C4564-B10E-41F9-8A9D-D8A6C5E9C51C-GENID-1-6-1-9-1-1-5-1-3-1-11-1-7-1-2-4"><title>Description</title> <p>The
+following sections provide more information about the steps that the example
+performs. </p> <p><b> Thread Synchronisation</b> </p> <p>The example creates
+three threads named ThreadOne, ThreadTwo and ThreadThree. The threads write
+"One", "Two" and "Three" five times in a text file. The text file, located
+in <filepath>epoc32\winscw\c\newfile.txt</filepath>, is used as a shared resource
+for all three threads. A mutex is used to ensure that first ThreadOne writes
+in the file, then ThreadTwo and then ThreadThree. If the mutex is not used
+all the threads can simultaneously write in the file. This can be seen by
+commenting out <codeph>pthread_mutex_lock</codeph> and <codeph>pthread_mutex_unlock</codeph> in
the code. </p> </section>
-<section><title>Related APIs</title><p><xref href="GUID-736D5209-CD86-324C-BAB0-7B15C3D1862D.dita"><apiname>pthread_mutex_lock</apiname></xref> </p><p><xref href="GUID-9D7CD10C-F958-3792-8888-B7F39B148302.dita"><apiname>pthread_mutex_unlock</apiname></xref> </p><p><xref href="GUID-3A89E849-DD7F-3381-9469-6CD89892E616.dita"><apiname>pthread_join</apiname></xref></p><p><xref href="GUID-889CB456-6980-3B92-9350-0C6C8C9AC435.dita"><apiname>pthread_mutex_t</apiname></xref></p></section>
-<section><title>Build</title> <p>The <xref href="GUID-3100800B-B2F7-50EF-BD4C-3C345ECCB2A5.dita">Symbian
-OS build process</xref> describes how to build this example application. </p> <p>The
+<section id="GUID-236CB272-E196-4A61-B627-ACFFC4B37AA1"><title>Related APIs</title><p><xref href="GUID-736D5209-CD86-324C-BAB0-7B15C3D1862D.dita"><apiname>pthread_mutex_lock</apiname></xref> </p><p><xref href="GUID-9D7CD10C-F958-3792-8888-B7F39B148302.dita"><apiname>pthread_mutex_unlock</apiname></xref> </p><p><xref href="GUID-3A89E849-DD7F-3381-9469-6CD89892E616.dita"><apiname>pthread_join</apiname></xref></p><p><xref href="GUID-889CB456-6980-3B92-9350-0C6C8C9AC435.dita"><apiname>pthread_mutex_t</apiname></xref></p></section>
+<section id="GUID-67A72761-1D92-46D1-B1C9-7455978BDE4E-GENID-1-6-1-9-1-1-5-1-3-1-11-1-7-1-2-6"><title>Build</title> <p>The <xref href="GUID-3100800B-B2F7-50EF-BD4C-3C345ECCB2A5.dita">Symbian build
+process</xref> describes how to build this example application. </p> <p>The
example builds an executable called <filepath>LibpThreadExample.exe</filepath> in
the standard locations. </p> <p>To run the example, start <filepath>LibpThreadExample.exe</filepath> from
the file system or from your IDE. After launching the executable, depending
--- a/Symbian3/SDK/Source/GUID-0A332D6E-E712-5186-8CD0-D5022FA54052.dita Fri Jan 22 18:26:19 2010 +0000
+++ b/Symbian3/SDK/Source/GUID-0A332D6E-E712-5186-8CD0-D5022FA54052.dita Thu Mar 11 15:24:26 2010 +0000
@@ -621,10 +621,10 @@
aMessage.ReadL(0,buffer); // Read data from client descriptor (param 0)
...</codeblock> <p>Because <codeph>TIpcArgs</codeph> also stores type
information about arguments, the kernel knows that argument 0 in the above
-message is an 8-bit constant descriptor. On Symbian OS platforms using the
-EKA2 kernel, this information is used to enforce correct usage of descriptor
-access methods; in this case, trying to write to <codeph>aDes</codeph>, or
-treating it as a 16-bit descriptor would fail with <codeph>KErrBadDescriptor</codeph>.
+message is an 8-bit constant descriptor. On Symbian platforms
+using the EKA2 kernel, this information is used to enforce correct usage of
+descriptor access methods; in this case, trying to write to <codeph>aDes</codeph>,
+or treating it as a 16-bit descriptor would fail with <codeph>KErrBadDescriptor</codeph>.
(The latter case would have allowed access to data beyond the length of the
8- bit descriptor. </p> <p>Note, both leaving and non-leaving versions of
the <codeph>Read()</codeph> and <codeph>Write()</codeph> functions are provided.
--- a/Symbian3/SDK/Source/GUID-176FD8C9-B4A9-5B50-B683-AB5DA7D5D6F4.dita Fri Jan 22 18:26:19 2010 +0000
+++ b/Symbian3/SDK/Source/GUID-176FD8C9-B4A9-5B50-B683-AB5DA7D5D6F4.dita Thu Mar 11 15:24:26 2010 +0000
@@ -11,16 +11,15 @@
PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
<concept id="GUID-176FD8C9-B4A9-5B50-B683-AB5DA7D5D6F4" xml:lang="en"><title>CreateStaticDLL
and UseStaticDLL: using a statically linked DLL</title><prolog><metadata><keywords/></metadata></prolog><conbody>
-<section><title>Description</title> <p>The example shows how a class implemented
+<section id="GUID-A88465CB-D776-49CD-AA0C-1BAD59D340B6"><title>Description</title> <p>The example shows how a class implemented
in a statically linked DLL is used. The DLL is built by <filepath>CreateStaticDLL</filepath> and
is used by <filepath>UseStaticDLL</filepath>. </p> </section>
-<section><title>Download</title> <p>Click on the following link to download
-the example: <xref href="guid-6013a680-57f9-415b-8851-c4fa63356636/zips/guid-2e2b4dbb-291f-428c-82bf-fe796b4f50f4.zip" scope="external">StaticDLL.zip</xref></p><p>Click on the following link to
-download additional files: <xref href="guid-6013a680-57f9-415b-8851-c4fa63356636/zips/guid-bd05bfa4-e51c-4cf7-b327-646b0b9e814d.zip" scope="external">CommonFramework.zip</xref>.</p><p>Click<xref href="guid-6013a680-57f9-415b-8851-c4fa63356636/guid-2e2b4dbb-291f-428c-82bf-fe796b4f50f4.html" scope="peer"> browse StaticDLL</xref> to view the example code. </p><p>Click <xref href="guid-6013a680-57f9-415b-8851-c4fa63356636/guid-bd05bfa4-e51c-4cf7-b327-646b0b9e814d.html" scope="peer">browse CommonFramework</xref> to view additional
-files.</p> </section>
-<section><title>Build and Usage</title> <p>It may be in the directory in which
-you installed Symbian platform, or it may be in <filepath>src\common\developerlibrary\</filepath>.
-It includes the project files needed for building: <filepath>bld.inf</filepath> and
+<section id="GUID-D201398C-0D5C-4DA5-BEE6-A85BFDDD16BE"><title>Download</title> <p>Click on the following link
+to download the example: <xref href="guid-6013a680-57f9-415b-8851-c4fa63356636/zips/guid-2e2b4dbb-291f-428c-82bf-fe796b4f50f4.zip" scope="external">StaticDLL.zip</xref></p><p>Click on the following link to
+download additional files: <xref href="guid-6013a680-57f9-415b-8851-c4fa63356636/zips/guid-bd05bfa4-e51c-4cf7-b327-646b0b9e814d.zip" scope="external">CommonFramework.zip</xref>.</p><p>Click<xref href="guid-6013a680-57f9-415b-8851-c4fa63356636/guid-2e2b4dbb-291f-428c-82bf-fe796b4f50f4.html" scope="peer"> browse StaticDLL</xref> to view the example code. </p><p>Click <xref href="guid-6013a680-57f9-415b-8851-c4fa63356636/guid-bd05bfa4-e51c-4cf7-b327-646b0b9e814d.html" scope="peer">browse CommonFramework</xref> to view additional files.</p> </section>
+<section id="GUID-98C5D73C-E983-4530-92E9-439E47B43162"><title>Build and Usage</title> <p>The example may be in the directory
+in which you installed the Symbian platform, or it may be in <filepath>src\common\developerlibrary\</filepath>.
+The example includes the project files needed for building: <filepath>bld.inf</filepath> and
two <filepath>.mmp</filepath> files. </p> <p> <xref href="GUID-3100800B-B2F7-50EF-BD4C-3C345ECCB2A5.dita">The
Symbian platform build process</xref> describes how to build Symbian programs.
To run this example: </p> <ol id="GUID-C12016AA-4582-5812-BD1B-4D36A27679EB">
--- a/Symbian3/SDK/Source/GUID-1ACD01D1-2055-581A-9478-2C0D7D1CF9E6.dita Fri Jan 22 18:26:19 2010 +0000
+++ b/Symbian3/SDK/Source/GUID-1ACD01D1-2055-581A-9478-2C0D7D1CF9E6.dita Thu Mar 11 15:24:26 2010 +0000
@@ -9,10 +9,10 @@
-->
<!DOCTYPE concept
PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
-<concept id="GUID-1ACD01D1-2055-581A-9478-2C0D7D1CF9E6" xml:lang="en"><title>Use Cases
-for Writing Standard C++ Code</title><prolog><metadata><keywords/></metadata></prolog><conbody>
+<concept id="GUID-1ACD01D1-2055-581A-9478-2C0D7D1CF9E6" xml:lang="en"><title>Use
+Cases for Writing Standard C++ Code</title><prolog><metadata><keywords/></metadata></prolog><conbody>
<p>The following topics describe the use cases based on which you can write
-Standard C++ code on Symbian platform: </p>
+Standard C++ code on the Symbian platform: </p>
<ul>
<li id="GUID-FE4675CC-A3B2-5487-8318-996810CED805"><p><xref href="GUID-1ACD01D1-2055-581A-9478-2C0D7D1CF9E6.dita#GUID-1ACD01D1-2055-581A-9478-2C0D7D1CF9E6/GUID-20DCAC0E-D335-55A7-ADDE-17245D591970">Standard C++ code using STL or Standard C</xref> </p> </li>
<li id="GUID-6AE48560-9481-511F-9165-FA9F15E36D2F"><p><xref href="GUID-1ACD01D1-2055-581A-9478-2C0D7D1CF9E6.dita#GUID-1ACD01D1-2055-581A-9478-2C0D7D1CF9E6/GUID-4024FCCD-7A54-50EE-BCDD-72BC23A34CD8">Standard C++ code calling Symbian C++ functions</xref> </p> </li>
@@ -65,7 +65,7 @@
this can cause problems illustrated in the <xref href="GUID-AF2CE612-F12E-5A18-81A5-C303992D2D46.dita#GUID-AF2CE612-F12E-5A18-81A5-C303992D2D46/GUID-6CE49D59-46BB-5145-B346-6FD3EA8BC011">Standard
C++ calling Symbian C++ functions</xref> section. </p> <p> <b>Note:</b> For
more information about the leave-idiom on Symbian C++, see the <b>Lifetimes
-in Symbian platform</b> topic under the <xref href="GUID-1FFE4ED5-7B2E-58A0-9D08-A096F53F37AB.dita">Object
+in Symbian</b> topic under the <xref href="GUID-1FFE4ED5-7B2E-58A0-9D08-A096F53F37AB.dita">Object
lifetimes and cleanup</xref> section. </p> <p>The error code <codeph>err</codeph> can
then be translated to throw a corresponding Standard C++ exception using the <codeph>TranslateSymErrorToCppException</codeph> utility
function. This function is declared in <filepath>stdcpp_support.h</filepath>. </p> <p>Alternatively,
@@ -176,7 +176,7 @@
<link href="GUID-F7FEB759-E64D-5B6D-9017-C5E982E4FC16.dita"><linktext>Standard
C++ Library Overview</linktext></link>
<link href="GUID-2CCD1748-9EDE-5383-9941-A3051E06F3E2.dita"><linktext> Standard
-C++ Support on Symbian Platform</linktext></link>
+C++ Support on the Symbian Platform</linktext></link>
<link href="GUID-E331B72B-84AF-558A-9B8F-73E5E50B58C7.dita"><linktext>Building
a Standard C++ Application or Library</linktext></link>
<link href="GUID-AF2CE612-F12E-5A18-81A5-C303992D2D46.dita"><linktext>Possible
--- a/Symbian3/SDK/Source/GUID-1F6DA049-AC03-5122-8B91-32C007A41526.dita Fri Jan 22 18:26:19 2010 +0000
+++ b/Symbian3/SDK/Source/GUID-1F6DA049-AC03-5122-8B91-32C007A41526.dita Thu Mar 11 15:24:26 2010 +0000
@@ -63,8 +63,8 @@
</ul> <p>The example application shows how you to code security policies.
It also shows you the constants and classes that you must define to use the
policy server framework. </p> </section>
-<section id="GUID-DD984CA6-90E7-4B7D-9876-356A7BBFEA26"><title>Class summary</title><p>This example demonstrates the following
-classes:<ul>
+<section id="GUID-DD984CA6-90E7-4B7D-9876-356A7BBFEA26"><title>Class summary</title><p>This
+example demonstrates the following classes:<ul>
<li><p><xref href="GUID-5BDFF5B1-DC1F-393A-879B-9D8DE080B4E2.dita"><apiname>CPolicyServer</apiname></xref></p></li>
<li><p><xref href="GUID-D5A30C75-E22C-34E8-913B-7D2CA6AD5C51.dita"><apiname>CSession2</apiname></xref></p></li>
<li><p><xref href="GUID-D82DEC7A-71C2-3004-BFC2-C82C009A2715.dita"><apiname>TVersion</apiname></xref></p></li>
@@ -77,7 +77,7 @@
<li><p><xref href="GUID-B0E661BC-4058-3256-B9C3-5A4FD52F6DE5.dita"><apiname>RThread</apiname></xref></p></li>
<li><p><xref href="GUID-1BBE1448-1DF8-33C4-BF9E-5A5F427AEE35.dita"><apiname>RSubSessionBase</apiname></xref></p></li>
</ul></p></section>
-<section id="GUID-B9CD5974-18AA-5581-8BA5-8A1F2CFBC4E7"><title>Build</title> <p><xref href="GUID-3100800B-B2F7-50EF-BD4C-3C345ECCB2A5.dita">The Symbian OS build process</xref> describes
+<section id="GUID-B9CD5974-18AA-5581-8BA5-8A1F2CFBC4E7"><title>Build</title> <p><xref href="GUID-3100800B-B2F7-50EF-BD4C-3C345ECCB2A5.dita">The Symbian build process</xref> describes
how to build this example. </p> <p>The <codeph>SecureServer</codeph> example
builds the following binaries in the standard location (<filepath>\epoc32\release\winscw\<build_variant></filepath>)
for Carbide.c++. </p> <ul>
--- a/Symbian3/SDK/Source/GUID-24EFD1EC-333C-537C-89FF-A77627D962C3.dita Fri Jan 22 18:26:19 2010 +0000
+++ b/Symbian3/SDK/Source/GUID-24EFD1EC-333C-537C-89FF-A77627D962C3.dita Thu Mar 11 15:24:26 2010 +0000
@@ -12,8 +12,8 @@
<concept id="GUID-24EFD1EC-333C-537C-89FF-A77627D962C3" xml:lang="en"><title>LocaleUpdateExample:
Using the Locale Functionality</title><shortdesc>This example demonstrates how to get different locale settings
from the locale DLLs in the system. </shortdesc><prolog><metadata><keywords/></metadata></prolog><conbody>
-<section id="GUID-DDFC3596-480B-4918-A60A-E1801BBB1BEA"><title>Download</title> <p>Click on the following link to download
-the example: <xref href="guid-6013a680-57f9-415b-8851-c4fa63356636/zips/guid-5a60c198-2dac-4ef7-883a-b282bd9a42f9.zip" scope="external">localeupdate.zip</xref>.</p> <p>Click: <xref href="guid-6013a680-57f9-415b-8851-c4fa63356636/guid-5a60c198-2dac-4ef7-883a-b282bd9a42f9.html" scope="peer">browse</xref> to view the example code.</p> </section>
+<section id="GUID-DDFC3596-480B-4918-A60A-E1801BBB1BEA"><title>Download</title> <p>Click
+on the following link to download the example: <xref href="guid-6013a680-57f9-415b-8851-c4fa63356636/zips/guid-5a60c198-2dac-4ef7-883a-b282bd9a42f9.zip" scope="external">localeupdate.zip</xref>.</p> <p>Click: <xref href="guid-6013a680-57f9-415b-8851-c4fa63356636/guid-5a60c198-2dac-4ef7-883a-b282bd9a42f9.html" scope="peer">browse</xref> to view the example code.</p> </section>
<section id="GUID-72B5059D-9D34-5383-814B-45A1DAD2FC90"><title>Description</title> <p>An
object of the <xref href="GUID-454ACAB5-1573-323C-820E-AF542B149D2A.dita"><apiname>TExtendedLocale</apiname></xref> class is used to load a number
of locale DLLs from the system. For each locale DLL, it gets the following
@@ -35,12 +35,12 @@
<li><p><xref href="GUID-FFC6932E-2FFF-315E-975B-9E9A7A8CBF2F.dita"><apiname>TDateFormat</apiname></xref> - Defines the date formats.</p></li>
<li><p><xref href="GUID-7F61AE3B-579D-32E3-8134-81BFAAD4807E.dita"><apiname>TTimeFormat</apiname></xref> - Defines the time formats as either
12 hour or 24 hour. </p></li>
-<li><p><xref href="GUID-E13F49BA-BB0F-3ECA-A1F6-158E5C80F799.dita"><apiname>TDaylightSavingZone</apiname></xref> - Defines the daylight saving
-zones.</p></li>
+<li><p><xref href="GUID-E13F49BA-BB0F-3ECA-A1F6-158E5C80F799.dita"><apiname>TDaylightSavingZone</apiname></xref> - Defines the daylight
+saving zones.</p></li>
<li><p><xref href="GUID-4B94449F-05D7-376E-94EF-D11AB200E543.dita"><apiname>TUnitsFormat</apiname></xref> - Enumerates the units of measurement
as either Imperial or Metric.</p></li>
</ul></section>
-<section id="GUID-2421D907-91C7-590C-BEE3-A84526C9FFE3"><title>Build</title> <p><xref href="GUID-3100800B-B2F7-50EF-BD4C-3C345ECCB2A5.dita">The Symbian OS build process</xref> describes
+<section id="GUID-2421D907-91C7-590C-BEE3-A84526C9FFE3"><title>Build</title> <p><xref href="GUID-3100800B-B2F7-50EF-BD4C-3C345ECCB2A5.dita">The Symbian build process</xref> describes
how to build this example. </p> <p>The <codeph>localeupdate</codeph> example
builds the <filepath>localeupdate.exe</filepath> executable file in the standard
location (<filepath>\epoc32\release\winscw\ <build_variant></filepath>)
--- a/Symbian3/SDK/Source/GUID-2C5B58F2-6BD2-5C2B-8E1B-CFB3D7EB6ED9.dita Fri Jan 22 18:26:19 2010 +0000
+++ b/Symbian3/SDK/Source/GUID-2C5B58F2-6BD2-5C2B-8E1B-CFB3D7EB6ED9.dita Thu Mar 11 15:24:26 2010 +0000
@@ -13,7 +13,8 @@
Library (STLport v5)</title><prolog><metadata><keywords/></metadata></prolog><conbody>
<p>A Standard C++ environment with IOStream and STL (Standard Template Library)
libraries enables you to develop or port Standard C++ applications or libraries
-quickly and easily on Symbian platform. The topics in this guide provide a
-brief overview of Standard C++ support on Symbian platform and also describe
-how to develop applications or libraries based on Standard C++. </p>
+quickly and easily onto the Symbian platform. The topics in this
+guide provide a brief overview of Standard C++ support on the Symbian platform
+and also describe how to develop applications or libraries based on Standard
+C++. </p>
</conbody></concept>
\ No newline at end of file
--- a/Symbian3/SDK/Source/GUID-2CCD1748-9EDE-5383-9941-A3051E06F3E2.dita Fri Jan 22 18:26:19 2010 +0000
+++ b/Symbian3/SDK/Source/GUID-2CCD1748-9EDE-5383-9941-A3051E06F3E2.dita Thu Mar 11 15:24:26 2010 +0000
@@ -10,7 +10,7 @@
<!DOCTYPE concept
PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
<concept id="GUID-2CCD1748-9EDE-5383-9941-A3051E06F3E2" xml:lang="en"><title>Standard
-C++ Support on Symbian Platform</title><prolog><metadata><keywords/></metadata></prolog><conbody>
+C++ Support on the Symbian Platform</title><prolog><metadata><keywords/></metadata></prolog><conbody>
<p>This topic describes the Standard C++ runtime features supported on Symbian^3. </p>
<ul>
<li id="GUID-F620B47D-35A9-54DF-89FC-031C3B3A50D4"><p><xref href="GUID-2CCD1748-9EDE-5383-9941-A3051E06F3E2.dita#GUID-2CCD1748-9EDE-5383-9941-A3051E06F3E2/GUID-B44FDC08-487F-589B-8355-CF6EAB3F25BC">Global operator new</xref> </p> </li>
@@ -26,7 +26,7 @@
you write Standard C++ code on Symbian C++ ensure that you either use Symbian
C++ semantics of operator new or Standard C++ semantics of operator new in
your code. You can use the global <codeph>operator new</codeph> as per the
-Standard C++ specification on Symbian platform by either: </p> <ul>
+Standard C++ specification on the Symbian platform by either: </p> <ul>
<li id="GUID-3E72A8F5-F68B-5454-8F20-67CC53FDC37F"><p>Building your application
or library using the STD target type. </p> </li>
<li id="GUID-40D77F25-4EE4-578A-B51E-451F7655CBA6"><p>Using the <codeph>MMP</codeph> keyword, <codeph>STDCPP</codeph>. </p> </li>
@@ -35,8 +35,8 @@
does not permit you to mix the Standard C++ <codeph>operator new</codeph> and
the Symbian C++ <codeph>operator new</codeph>. </p> <p><b>Example</b> </p> <p>The
following example code illustrates how to use the global <codeph>operator
-new</codeph> when you write Standard C++ code on Symbian platform and your
-target type is a non-STD target type, for example, <codeph>exe</codeph>. </p> <p>You
+new</codeph> when you write Standard C++ code on the Symbian platform and
+your target type is a non-STD target type, for example, <codeph>exe</codeph>. </p> <p>You
must add the <codeph>MMP</codeph> keyword, <codeph>STDCPP</codeph> in the <filepath>.mmp</filepath> file
as shown in the following code: </p> <codeblock id="GUID-400432AB-79A2-5F17-9F96-22209524BC84" xml:space="preserve">//operator_new_example.mmp
Target operator_new_example.exe
@@ -63,12 +63,12 @@
delete ptr;
return 0;
}</codeblock> </section>
-<section id="GUID-ED64EEBA-A52D-5008-8F5F-11019BC5B1E2"><title>new_handler</title> <p>The
-new_handler() function of Standard C++ is fully supported on Symbian platform
-(the global <codeph>operator new</codeph> restrictions are applicable). You
-can use the new_handler function to handle an out of memory scenario caused
-by the global <codeph>operator new</codeph> when dynamic memory allocation
-fails. </p> <p>The following code illustrates how to set and invoke a <codeph>new_handler</codeph>: </p> <codeblock id="GUID-E1CD4479-99AF-5547-B350-00699CD2788D" xml:space="preserve">#include <new>
+<section id="GUID-ED64EEBA-A52D-5008-8F5F-11019BC5B1E2"><title>new_handler</title> <p>The <codeph>new_handler()</codeph> function
+of Standard C++ is fully supported on the Symbian platform (the global <codeph>operator
+new</codeph> restrictions are applicable). You can use the new_handler function
+to handle an out of memory scenario caused by the global <codeph>operator
+new</codeph> when dynamic memory allocation fails. </p> <p>The following code
+illustrates how to set and invoke a <codeph>new_handler</codeph>: </p> <codeblock id="GUID-E1CD4479-99AF-5547-B350-00699CD2788D" xml:space="preserve">#include <new>
int one_huge_chunk = 0xa000;
int *last_huge_chunk=NULL;
void foo()
@@ -146,9 +146,9 @@
main
dtor</codeblock> </section>
<section id="GUID-1D9D2701-FD3E-57D1-952B-FB8C057FE055"><title>STL</title> <p>Here
-are some key facts about STL support on Symbian platform: </p> <ul>
+are some key facts about STL support on the Symbian platform: </p> <ul>
<li id="GUID-F0FCA9CA-7417-5D07-A6AA-F679B3A3A41A"><p>The Standard C++ implementation
-on Symbian platform is based on STLPort version 5.1.4. </p> </li>
+on the Symbian platform is based on STLPort version 5.1.4. </p> </li>
<li id="GUID-FB97F095-533F-582D-BD28-667D1BD6863A"><p>The Standard C++ header
files are available in the <filepath>${EPOCROOT}/epoc32/include/stdapis/stlportv5</filepath> directory. </p> </li>
<li id="GUID-F6381C75-4C30-5627-8AAA-7D8F1FF53565"><p>The Standard C++ library
--- a/Symbian3/SDK/Source/GUID-30382EFD-90D5-570C-A6CD-19D34360F329.dita Fri Jan 22 18:26:19 2010 +0000
+++ b/Symbian3/SDK/Source/GUID-30382EFD-90D5-570C-A6CD-19D34360F329.dita Thu Mar 11 15:24:26 2010 +0000
@@ -12,11 +12,11 @@
<concept id="GUID-30382EFD-90D5-570C-A6CD-19D34360F329" xml:lang="en"><title>GraphicsShell:
drawing and zooming</title><shortdesc>A TechView application that demonstrates drawing points, lines
and shapes, and zooming a bitmap and text. </shortdesc><prolog><metadata><keywords/></metadata></prolog><conbody>
-<section><title>Download</title> <p>Click on the following link to download
+<section id="GUID-A512AE19-D921-47B7-86D7-1AE293365BC9"><title>Download</title> <p>Click on the following link to download
the example: <xref href="guid-6013a680-57f9-415b-8851-c4fa63356636/zips/guid-c01568a1-21f6-4508-8de7-9733ae2737a1.zip" scope="external">GraphicsShell.zip</xref></p>Download some additional files
required by the example: <xref href="guid-6013a680-57f9-415b-8851-c4fa63356636/zips/guid-a92c7d47-fa68-49c6-9e43-c9c2e650f219.zip" scope="external">CommonGraphicsExampleFiles</xref><p>Click: <xref href="guid-6013a680-57f9-415b-8851-c4fa63356636/guid-c01568a1-21f6-4508-8de7-9733ae2737a1.html" scope="peer">browse</xref> to view the example code. </p>View the additional
files: <xref href="guid-6013a680-57f9-415b-8851-c4fa63356636/guid-a92c7d47-fa68-49c6-9e43-c9c2e650f219.html" scope="peer">browse</xref>. </section>
-<section><title>Description</title> <p> <filepath>GraphicsShell</filepath> provides
+<section id="GUID-12DAE9CC-9E18-40AA-A820-FBC86F179425"><title>Description</title> <p> <filepath>GraphicsShell</filepath> provides
an application shell, and two concrete controls. </p> <p> <codeph>CGraphicExampleControl</codeph> is
a control class, derived from <codeph>CCoeControl</codeph>, which links the
app shell to the particular controls. </p> <p> <codeph>CDrawControl</codeph> illustrates
@@ -24,16 +24,17 @@
this exercises a variety of drawing functions provided by the window graphics
context such as <codeph>MoveTo()</codeph>, <codeph>DrawLineTo()</codeph>, <codeph>DrawArc()</codeph> etc. </p> <p> <codeph>CZoomControl</codeph> illustrates
the use of zooming. </p> </section>
-<section><title>Class Summary</title><p><xref href="GUID-339EC4C5-89DC-3972-9579-6DD38D418317.dita"><apiname>TPoint</apiname></xref></p><p><xref href="GUID-CCD7C54F-C3D6-3F92-B6CC-1B6116170C6C.dita"><apiname>TRectTSize</apiname></xref></p><p><xref href="GUID-0AEE5955-C530-35F1-A904-69183331B294.dita"><apiname>CWindowGc</apiname></xref></p><p><xref href="GUID-F84C7F40-6DEB-39D1-B172-CB0CC3918E27.dita"><apiname>TRgb</apiname></xref></p><p><xref href="GUID-2A12FE3B-47F2-3016-8161-A971CA506491.dita"><apiname>CFont</apiname></xref></p><p><xref href="GUID-052E4F6B-71C5-304C-B387-07A2F6F9900B.dita"><apiname>TFontSpec</apiname></xref></p><p><xref href="GUID-0AEE5955-C530-35F1-A904-69183331B294.dita"><apiname>CWindowGc</apiname></xref></p><p><xref href="GUID-DDE4C9C0-7218-385E-B239-0DEFDE19FCCC.dita"><apiname>TZoomFactor</apiname></xref></p><p><xref href="GUID-4791F2C1-C351-3824-8784-3161F5B65DCA.dita"><apiname>MGraphicsDeviceMap</apiname></xref></p><p><xref href="GUID-683A1D42-2764-3EB7-BD19-9E12559199AB.dita"><apiname>CFbsBitmap</apiname></xref></p></section>
-<section><title>Build</title> <p>The source code for this example application
-can be found in the directory: </p> <p> <filepath>examples\Graphics\GraphicsShell</filepath> </p> <p>It
-may be in the directory in which you installed Symbian platform, or it may
-be in <filepath>src\common\developerlibrary\</filepath>. It includes the two
-project files needed for building: <filepath>bld.inf</filepath> and the <filepath>.mmp</filepath> file. </p> <p><xref href="GUID-3100800B-B2F7-50EF-BD4C-3C345ECCB2A5.dita">The Symbian platform build
-process</xref> describes how to build this application. For the emulator,
-an application called <filepath>GraphicsShell.exe</filepath> is created in <filepath>epoc32\release\winscw\<udeb
-or urel>\</filepath>. </p> </section>
-<section><title>Usage</title> <ol id="GUID-911BEED5-308F-5700-A32B-C09194AEFBA7">
+<section id="GUID-1CF95EDF-58AF-4B79-B8AA-635D456F4590"><title>Class Summary</title><p><xref href="GUID-339EC4C5-89DC-3972-9579-6DD38D418317.dita"><apiname>TPoint</apiname></xref></p><p><xref href="GUID-CCD7C54F-C3D6-3F92-B6CC-1B6116170C6C.dita"><apiname>TRectTSize</apiname></xref></p><p><xref href="GUID-0AEE5955-C530-35F1-A904-69183331B294.dita"><apiname>CWindowGc</apiname></xref></p><p><xref href="GUID-F84C7F40-6DEB-39D1-B172-CB0CC3918E27.dita"><apiname>TRgb</apiname></xref></p><p><xref href="GUID-2A12FE3B-47F2-3016-8161-A971CA506491.dita"><apiname>CFont</apiname></xref></p><p><xref href="GUID-052E4F6B-71C5-304C-B387-07A2F6F9900B.dita"><apiname>TFontSpec</apiname></xref></p><p><xref href="GUID-0AEE5955-C530-35F1-A904-69183331B294.dita"><apiname>CWindowGc</apiname></xref></p><p><xref href="GUID-DDE4C9C0-7218-385E-B239-0DEFDE19FCCC.dita"><apiname>TZoomFactor</apiname></xref></p><p><xref href="GUID-4791F2C1-C351-3824-8784-3161F5B65DCA.dita"><apiname>MGraphicsDeviceMap</apiname></xref></p><p><xref href="GUID-683A1D42-2764-3EB7-BD19-9E12559199AB.dita"><apiname>CFbsBitmap</apiname></xref></p></section>
+<section id="GUID-11F1F1BF-F1DC-4876-B47A-275B07C645E3"><title>Build</title> <p>The source code for this example
+application can be found in the directory: </p> <p> <filepath>examples\Graphics\GraphicsShell</filepath> </p> <p>This
+source code may be in the directory in which you installed the Symbian platform,
+or it may be in the <filepath>src\common\developerlibrary\</filepath> directory.
+The directory includes the two project files needed for building the example: <filepath>bld.inf</filepath> and
+the <filepath>.mmp</filepath> file. </p> <p><xref href="GUID-3100800B-B2F7-50EF-BD4C-3C345ECCB2A5.dita">The
+Symbian build process</xref> describes how to build this application. For
+the emulator, an application called <filepath>GraphicsShell.exe</filepath> is
+created in <filepath>epoc32\release\winscw\<udeb or urel>\</filepath>. </p> </section>
+<section id="GUID-0CB7BF6D-ED18-46CA-8ED1-ADB440508BBC"><title>Usage</title> <ol id="GUID-911BEED5-308F-5700-A32B-C09194AEFBA7">
<li id="GUID-2E6EB0AA-B311-53DD-B0CA-BE5E4AA04C7B"><p>Launch the emulator: </p> <p> <filepath>\epoc32\release\winscw\<udeb
or urel>\EPOC.EXE</filepath>. </p> </li>
<li id="GUID-6ECA1727-FC1E-5659-B805-1AB1EF7C9407"><p>Click on <systemoutput>GRAPHICSSHELL</systemoutput> to
--- a/Symbian3/SDK/Source/GUID-315452C2-A1E2-5888-A694-6D2DE73A3F5E.dita Fri Jan 22 18:26:19 2010 +0000
+++ b/Symbian3/SDK/Source/GUID-315452C2-A1E2-5888-A694-6D2DE73A3F5E.dita Thu Mar 11 15:24:26 2010 +0000
@@ -12,8 +12,8 @@
<concept id="GUID-315452C2-A1E2-5888-A694-6D2DE73A3F5E" xml:lang="en"><title>OS Security
Guide</title><prolog><metadata><keywords/></metadata></prolog><conbody>
<p>OS Security provides the fundamental services to make protocols and services
-in Symbian platform secure. It provides frameworks and interfaces that are
-required to fulfill the demands of Symbian OS Platform Security Architecture.
-It includes collections of components that have to be modified or redesigned
-to support Platform Security.</p>
+in the Symbian platform secure. It provides frameworks and interfaces that
+are required to fulfill the demands of Symbian Platform Security
+Architecture. It includes collections of components that have to be modified
+or redesigned to support Platform Security.</p>
</conbody></concept>
\ No newline at end of file
--- a/Symbian3/SDK/Source/GUID-32E29020-1956-461A-B79A-1492E06049E7.dita Fri Jan 22 18:26:19 2010 +0000
+++ b/Symbian3/SDK/Source/GUID-32E29020-1956-461A-B79A-1492E06049E7.dita Thu Mar 11 15:24:26 2010 +0000
@@ -1,4 +1,7 @@
<?xml version="1.0" encoding="utf-8"?>
+<!--Arbortext, Inc., 1988-2004, v.4002-->
+<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN"
+ "concept.dtd">
<!-- Copyright (c) 2007-2010 Nokia Corporation and/or its subsidiary(-ies) All rights reserved. -->
<!-- This component and the accompanying materials are made available under the terms of the License
"Eclipse Public License v1.0" which accompanies this distribution,
@@ -7,7 +10,60 @@
Nokia Corporation - initial contribution.
Contributors:
-->
-<!DOCTYPE concept
- PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
-<concept id="GUID-32E29020-1956-461A-B79A-1492E06049E7" xml:lang="en"><title>Symbian guide</title><shortdesc>The Symbian Guide describes the architecture and functionality
-of the platform, and provides guides on using its APIs. </shortdesc><prolog><metadata><keywords/></metadata></prolog></concept>
\ No newline at end of file
+<concept id="GUID-32E29020-1956-461A-B79A-1492E06049E7" xml:lang="en"><title>Symbian
+G<?Pub Caret?>uide</title>
+<shortdesc>The Symbian Guide describes the architecture and functionality
+of the platform, and provides guides on using its APIs. </shortdesc>
+<conbody>
+<ul>
+<li><p><xref href="GUID-97CCEF05-8F3D-5802-A33A-ED349084D524.dita">Application
+Framework Guide</xref></p></li>
+<li><p><xref href="GUID-0AF47934-0A16-51A2-9254-992D7C6B322B.dita">Application
+Installation Guide</xref></p></li>
+<li><p><xref href="GUID-34E7AAF2-EC62-5BF6-B9E7-C7D346BCDF93.dita">Cellular Baseband
+Services Guide</xref></p></li>
+<li><p><xref href="GUID-94005A46-B4C6-4A30-A8E8-1B9C2D583D50.dita">Classic UI Guide</xref></p></li>
+<li><p><xref href="GUID-8F2D6AC8-8357-55C7-970B-CD2684BA9B04.dita">Communications
+Framework Guide</xref></p></li>
+<li><p><xref href="GUID-F8C8CE42-E7C9-5AFC-86BC-B78F677F1B05.dita">Device Services
+Guide</xref></p></li>
+<li><p><xref href="GUID-58035B49-2EAE-5144-B226-28AF2EDD62E7.dita">Generic Application
+Support Guide</xref></p></li>
+<li><p><xref href="GUID-5072BE46-B1B4-5C3A-BF55-BEA7443E7657.dita">Generic OS Services
+Guide</xref></p></li>
+<li><p><xref href="GUID-975CBC70-81E6-5FA2-80CE-88DD2ABE9595.dita">Graphics Guide</xref></p></li>
+<li><p><xref href="GUID-C0D38954-2FC5-4E8B-BC11-229464DCF16C.dita">High Level Internet
+Protocols Guide</xref></p></li>
+<li><p><xref href="GUID-E3D2A6ED-8192-563D-8966-DD96B3AF1783.dita">Kernel and Hardware
+Services Guide</xref></p></li>
+<li><p><xref href="GUID-7F476137-5E7F-5288-9F4A-6C20F0A1AD9B.dita">Location Based
+Services (LBS) Guide</xref></p></li>
+<li><p><xref href="GUID-1A43A45B-80AE-56A0-A94C-64BA75519C67.dita">Messaging Application
+Guide</xref></p></li>
+<li><p><xref href="GUID-5DD1010C-1648-5086-BA80-BC25F3C7A2C4.dita">Messaging Middleware
+Guide</xref></p></li>
+<li><p><xref href="GUID-1DE5CDAD-8D71-5384-9E98-5665D5A4C792.dita">Multimedia Guide</xref></p></li>
+<li><p><xref href="GUID-6425B722-4095-56E3-9198-70BA3E06C617.dita">Multimedia Protocols
+Guide</xref></p></li>
+<li><p><xref href="GUID-B144EAB9-53AB-579B-9E12-B16518E4FC01.dita">Networking Services
+Guide</xref></p></li>
+<li><p><xref href="GUID-FBCBF8A0-7922-5881-A1C5-5DB41630E75A.dita">Persistent Data
+Services Guide</xref></p></li>
+<li><p><xref href="GUID-BE3B53A8-B06D-53C4-8FC0-85B3BA4F39EF.dita">PIM Application
+Engines and Services Guide</xref></p></li>
+<li><p><xref href="GUID-315452C2-A1E2-5888-A694-6D2DE73A3F5E.dita">OS Security
+Guide</xref></p></li>
+<li><p><xref href="GUID-4CF8E6BC-3E2A-5773-A296-6321573B967E.dita">Security Services
+Guide</xref></p></li>
+<li><p><xref href="GUID-DD13AA8E-BDAD-57EC-81EC-49C8D6D30A86.dita">Short Link Services
+Guide</xref></p></li>
+<li><p><xref href="GUID-629EAA30-ED77-4CA9-91ED-36C818D7B4F4.dita">SMP Guide</xref></p></li>
+<li><p><xref href="GUID-1DCA2F4D-ABE6-52A0-AC4E-5AAC1AB5909D.dita">Text and Localization
+Guide</xref></p></li>
+<li><p><xref href="GUID-F9F53050-AAFA-4685-8C62-033E585F061B.dita">Web Guide</xref></p></li>
+<li><p><xref href="GUID-82AF5F49-EE25-54C7-AEE9-D1F41BD5190F.dita">XML Services
+Guide</xref></p></li>
+</ul>
+</conbody>
+</concept>
+<?Pub *0000003619?>
--- a/Symbian3/SDK/Source/GUID-3314123F-205D-5E05-9041-DB9836B7812B.dita Fri Jan 22 18:26:19 2010 +0000
+++ b/Symbian3/SDK/Source/GUID-3314123F-205D-5E05-9041-DB9836B7812B.dita Thu Mar 11 15:24:26 2010 +0000
@@ -12,30 +12,31 @@
<concept id="GUID-3314123F-205D-5E05-9041-DB9836B7812B" xml:lang="en"><title>File
Access Example: Accessing the File System Using P.I.P.S.</title><prolog><metadata><keywords/></metadata></prolog><conbody>
<p>This example application shows, using a P.I.P.S. (P.I.P.S. Is POSIX on
-Symbian platform) program, the restrictions on file access that are imposed
+the Symbian platform) program, the restrictions on file access that are imposed
by the Symbian platform Security model. </p>
-<p>It shows that programs can access their own directories, but cannot, without
-platform security capabilities not available to ordinary programs, access
-the directories of other programs, or the system binary directory <filepath>sys/bin</filepath>. </p>
+<p>It shows that programs can access their own directories, but
+cannot, without platform security capabilities not available to ordinary programs,
+access the directories of other programs, or the system binary directory <filepath>sys/bin</filepath>. </p>
<p>This example defines an executable file with no platform security capabilities.
The program first creates its own secure directory that it can write to and
read from. It then attempts to use a file in a private directory of another
program, and then in <filepath>sys/bin</filepath>, and shows that these attempts
are denied. </p>
-<section><title>Download</title> <p>Click on the following link to download
-the example: <xref href="guid-6013a680-57f9-415b-8851-c4fa63356636/zips/guid-2dae3cca-f112-4219-8f7c-6c48682d1f28.zip" scope="external">FileAccessExample.zip</xref></p><p>Click: <xref href="guid-6013a680-57f9-415b-8851-c4fa63356636/guid-2dae3cca-f112-4219-8f7c-6c48682d1f28.html" scope="peer">browse</xref> to view the example code. </p> </section>
-<section><title>Description</title> <p>The following sections provide more
-information about the steps that the example performs. </p> <p><b> Create
-a secure directory</b> </p> <p>The example creates an empty secure directory
-for the program by using the <xref href="GUID-5EA72F64-E826-3B15-9468-902BD57F6AA7.dita"><apiname>mkdir()</apiname></xref> function. </p> <p>This
+<section id="GUID-820F9B58-8877-414B-A18B-B591F6D67158"><title>Download</title> <p>Click
+on the following link to download the example: <xref href="guid-6013a680-57f9-415b-8851-c4fa63356636/zips/guid-2dae3cca-f112-4219-8f7c-6c48682d1f28.zip" scope="external">FileAccessExample.zip</xref></p><p>Click: <xref href="guid-6013a680-57f9-415b-8851-c4fa63356636/guid-2dae3cca-f112-4219-8f7c-6c48682d1f28.html" scope="peer">browse</xref> to view the example code. </p> </section>
+<section id="GUID-3EAFEC43-CFDA-4E3D-8ACD-E3AAE48BE97D"><title>Description</title> <p>The
+following sections provide more information about the steps that the example
+performs. </p> <p><b> Create a secure directory</b> </p> <p>The example creates
+an empty secure directory for the program by using the <xref href="GUID-5EA72F64-E826-3B15-9468-902BD57F6AA7.dita"><apiname>mkdir()</apiname></xref> function. </p> <p>This
empty secure directory is created in <filepath>C:\private\E80000C9</filepath>,
as 0xE80000C9 is a unique identifier for the program (as specified by the
third UID in its project file). </p></section>
-<section> <p><b>Write and read a file in the private directory </b> </p> <p>The
-example writes and reads a file in the secure directory using the <xref href="GUID-64886CC6-072F-3542-855A-5D733FC761E8.dita"><apiname>fopen()</apiname></xref> and
-other file stream functions. </p> <p><b> Write and read a file in the private
-directory of another program </b> </p> <p>The example attempts to write and
-read a file in the secure directory of another program. </p> <p>The <xref href="GUID-64886CC6-072F-3542-855A-5D733FC761E8.dita"><apiname>fopen()</apiname></xref> function
+<section id="GUID-D9F306FF-D14E-4BCC-BAE6-55804F31CA0D"> <p><b>Write and read
+a file in the private directory </b> </p> <p>The example writes and reads
+a file in the secure directory using the <xref href="GUID-64886CC6-072F-3542-855A-5D733FC761E8.dita"><apiname>fopen()</apiname></xref> and other
+file stream functions. </p> <p><b> Write and read a file in the private directory
+of another program </b> </p> <p>The example attempts to write and read a file
+in the secure directory of another program. </p> <p>The <xref href="GUID-64886CC6-072F-3542-855A-5D733FC761E8.dita"><apiname>fopen()</apiname></xref> function
is expected to return <codeph>NULL</codeph>, indicating that access is not
possible, as the program has insufficient platform security capabilities. </p><p><b> Write
and read a file in the sys/bin directory</b> </p> <p>The example attempts
@@ -43,12 +44,12 @@
where program binaries are stored. </p> <p>Again, the <xref href="GUID-64886CC6-072F-3542-855A-5D733FC761E8.dita"><apiname>fopen()</apiname></xref> function
is expected to return <codeph>NULL</codeph>, indicating that access is not
possible, as the program has insufficient platform security capabilities. </p> </section>
-<section><title>Releated APIs</title><p><xref href="GUID-5EA72F64-E826-3B15-9468-902BD57F6AA7.dita"><apiname>mkdir()</apiname></xref></p><p><xref href="GUID-64886CC6-072F-3542-855A-5D733FC761E8.dita"><apiname>fopen()</apiname></xref></p></section>
-<section><title>Build</title> <p>The <xref href="GUID-3100800B-B2F7-50EF-BD4C-3C345ECCB2A5.dita">Symbian
-platform build process</xref> describes how to build this example application. </p> <p>The
-example builds an executable called <filepath>fileaccessexample.exe</filepath> in
-the standard locations. </p> <p>To run the example, start <filepath>fileaccessexample.exe</filepath> from
-the file system or from your IDE. After launching the executable, depending
-on the emulator you are using, you may need to navigate away from the application
+<section id="GUID-EB4F71F2-D55D-43C5-B55F-F211D170056F"><title>Related APIs</title><p><xref href="GUID-5EA72F64-E826-3B15-9468-902BD57F6AA7.dita"><apiname>mkdir()</apiname></xref></p><p><xref href="GUID-64886CC6-072F-3542-855A-5D733FC761E8.dita"><apiname>fopen()</apiname></xref></p></section>
+<section id="GUID-81AA0C7F-5D43-4EFB-9DD0-4A8A79922576"><title>Build</title> <p>The <xref href="GUID-3100800B-B2F7-50EF-BD4C-3C345ECCB2A5.dita">Symbian build process</xref> describes
+how to build this example application. </p> <p>The example builds an executable
+called <filepath>fileaccessexample.exe</filepath> in the standard locations. </p> <p>To
+run the example, start <filepath>fileaccessexample.exe</filepath> from the
+file system or from your IDE. After launching the executable, depending on
+the emulator you are using, you may need to navigate away from the application
launcher or shell screen to view the console. </p> </section>
</conbody></concept>
\ No newline at end of file
--- a/Symbian3/SDK/Source/GUID-35D49549-1F4D-583F-A45D-9B557A207DD2.dita Fri Jan 22 18:26:19 2010 +0000
+++ b/Symbian3/SDK/Source/GUID-35D49549-1F4D-583F-A45D-9B557A207DD2.dita Thu Mar 11 15:24:26 2010 +0000
@@ -11,27 +11,28 @@
PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
<concept id="GUID-35D49549-1F4D-583F-A45D-9B557A207DD2" xml:lang="en"><title>GlassTerm:
glass teletype terminal</title><prolog><metadata><keywords/></metadata></prolog><conbody>
-<section><title>Download</title> <p>Click on the following link to download
+<section id="GUID-1D23EC68-021A-43E5-8584-28D8E85C0E62"><title>Download</title> <p>Click on the following link to download
the example: <xref href="guid-6013a680-57f9-415b-8851-c4fa63356636/zips/guid-e132f025-ded6-4ae4-8a4d-dc50d344b55b.zip" scope="external">GlassTerm.zip</xref></p>Download some additional files required
by the example: <xref href="guid-6013a680-57f9-415b-8851-c4fa63356636/zips/guid-16f2a07d-2ace-4a32-b383-6f1352dfd72e.zip" scope="external">CommonFiles</xref><p>Click: <xref href="guid-6013a680-57f9-415b-8851-c4fa63356636/guid-e132f025-ded6-4ae4-8a4d-dc50d344b55b.html" scope="peer">browse</xref> to view the example code. </p>View the additional
files: <xref href="guid-6013a680-57f9-415b-8851-c4fa63356636/guid-16f2a07d-2ace-4a32-b383-6f1352dfd72e.html" scope="peer">browse</xref>. </section>
-<section><title>Description</title> <p>GlassTerm is a terminal application
+<section id="GUID-A2E5D50F-2DD3-4A5A-8433-13B8BADEB77B"><title>Description</title> <p>GlassTerm is a terminal application
with configurable handshaking that illustrates the use of the Serial Communications
API. </p> </section>
-<section><title>Class Summary</title><p><xref href="GUID-3B4E8ED5-72F7-3E51-B188-3C1045526DDF.dita"><apiname>RComm</apiname></xref>: serial port</p><p><xref href="GUID-6B3CA99B-ABF2-32EA-935D-23AE5AE2C306.dita"><apiname>RCommServ</apiname></xref>:
+<section id="GUID-5DDD6F0D-50FA-4887-A61F-2E6C8074E168"><title>Class Summary</title><p><xref href="GUID-3B4E8ED5-72F7-3E51-B188-3C1045526DDF.dita"><apiname>RComm</apiname></xref>: serial port</p><p><xref href="GUID-6B3CA99B-ABF2-32EA-935D-23AE5AE2C306.dita"><apiname>RCommServ</apiname></xref>:
Comms server</p><p><xref href="GUID-076DD315-CE3F-3640-BAB4-0FC51C906820.dita"><apiname>TCommCaps</apiname></xref>: serial port capabilities
(in package buffer) </p><p><xref href="GUID-BF099B27-4E8A-3765-A6A8-DB88DB4F4F2E.dita"><apiname>TCommConfig</apiname></xref>: serial port configuration
(in package buffer) </p><p><xref href="GUID-E0B34F3E-D4C4-3232-B8B1-7DB35B454646.dita"><apiname>TRequestStatus</apiname></xref>: asynchronous
request status </p><p><xref href="GUID-A6E4627A-A3AE-3B64-9E5C-710EE15C5595.dita"><apiname>TSerialInfo</apiname></xref>: serial protocol information </p></section>
-<section><title>Build</title> <p>The source code for this example application
-can be found in the directory: </p> <p> <filepath>examples\SerialComms\ServerClientSide\GlassTerm</filepath> </p> <p>It
-may be in the directory in which you installed Symbian OS, or it may be in <filepath>src\common\developerlibrary\</filepath>.
-It includes the two project files needed for building: <filepath>bld.inf</filepath> and
+<section id="GUID-2925258F-CF25-46F7-B6B6-761615C7526B"><title>Build</title> <p>The source code for this example application
+can be found in the directory: </p> <p> <filepath>examples\SerialComms\ServerClientSide\GlassTerm</filepath> </p> <p>The
+source code may be in the directory in which you installed the Symbian platform,
+or it may be in <filepath>src\common\developerlibrary\</filepath>. The source
+code includes the two project files needed for building the example: <filepath>bld.inf</filepath> and
the <filepath>.mmp</filepath> file. </p> <p><xref href="GUID-3100800B-B2F7-50EF-BD4C-3C345ECCB2A5.dita">The
-Symbian OS build process</xref> describes how to build this application, which
+Symbian build process</xref> describes how to build this application, which
results in an executable called <filepath>\epoc32\release\<target>\<urel
or udeb>\GLASSTERM.EXE</filepath>. </p> </section>
-<section><title>Usage</title> <ol id="GUID-1DB8E591-3818-51E6-BDE0-89FFE8B6F96A">
+<section id="GUID-13E2D7B4-19BD-4EF5-BD11-96858ED96A9C"><title>Usage</title> <ol id="GUID-1DB8E591-3818-51E6-BDE0-89FFE8B6F96A">
<li id="GUID-A399AF4D-E821-5341-9645-B7F0FA42B76A"><p>Run the executable <filepath>GLASSTERM.EXE</filepath>. </p> <p>Executables
for the emulator targets <filepath>wins</filepath> and <filepath>winscw</filepath> can
be run on your PC. Executables for ARM targets must be copied to your target
@@ -45,10 +46,10 @@
</ul> <p>It sends and receives at 19200 baud, 8 data bits, no parity, 1 stop
bit. </p> </li>
</ol> <p>In order to see the application working, you must make a suitable
-serial port connection. A simple way is to connect a PC and a Symbian OS phone,
+serial port connection. A simple way is to connect a PC and a Symbian device,
and run the application on both machines simultaneously. (Before doing this,
make sure to close down any other applications using the serial port on the
-PC, and set the phone's <systemoutput>Link To Desktop</systemoutput> option
+PC, and set the device's <systemoutput>Link To Desktop</systemoutput> option
to <systemoutput>Off</systemoutput>). Characters typed on one machine are
then echoed to the application on the other. </p> </section>
</conbody></concept>
\ No newline at end of file
--- a/Symbian3/SDK/Source/GUID-382B8A9D-9D10-54CD-91A6-B9E7A2477662.dita Fri Jan 22 18:26:19 2010 +0000
+++ b/Symbian3/SDK/Source/GUID-382B8A9D-9D10-54CD-91A6-B9E7A2477662.dita Thu Mar 11 15:24:26 2010 +0000
@@ -12,10 +12,10 @@
<concept id="GUID-382B8A9D-9D10-54CD-91A6-B9E7A2477662" xml:lang="en"><title>SendAs
v2.0</title><prolog><metadata><keywords/></metadata></prolog><conbody>
<section id="GUID-9D54D47A-37D9-5229-92D5-B80B442E8B0D"><title>Description</title> <p>The
-application establishes a session with the SendAs server, sets a message entry,
-creates a message, sets its body text, adds a recipient, sends the message
-and closes the session. The sequence of events is detailed in the following
-list: </p> <ul>
+application establishes a session with the SendAs server, sets
+a message entry, creates a message, sets its body text, adds a recipient,
+sends the message and closes the session. The sequence of events is detailed
+in the following list: </p> <ul>
<li id="GUID-ADE16BD9-7B38-5B35-8E72-77E968D1CED2"><p>Create a session with
the SendAs server using <xref href="GUID-2DA04D96-F0AD-3FDC-9E36-1C27D889AF4B.dita#GUID-2DA04D96-F0AD-3FDC-9E36-1C27D889AF4B/GUID-423E2320-FB34-3249-80D9-9AA62C9DDF60"><apiname>CMsvSession::OpenSyncL()</apiname></xref> function. </p> </li>
<li id="GUID-E1BF3D0E-C278-57F6-9359-4EDC426034BD"><p>Set the message entry
@@ -64,9 +64,9 @@
is used to end the session with SendAs server. </p> </section>
<section id="GUID-5D17C0D4-1D8E-5E85-AEFD-7083A748C728"><title>Download</title> <p>Click
on the following link to download the example: <xref href="guid-6013a680-57f9-415b-8851-c4fa63356636/zips/guid-90c56a55-33bb-4ab7-a6b8-8932ba181dc8.zip" scope="external">sendAs.zip</xref></p><p>Click: <xref href="guid-6013a680-57f9-415b-8851-c4fa63356636/guid-90c56a55-33bb-4ab7-a6b8-8932ba181dc8.html" scope="peer">browse </xref> to view the example code. </p> </section>
-<section><title>Class summary</title><p> The SendAs v2 example application
+<section id="GUID-3AE6EA98-02BC-41BD-AC4E-157A6700A12A"><title>Class summary</title><p> The SendAs v2 example application
uses the following classes:</p><p><xref href="GUID-85BBE389-81F7-3E2F-A789-446D9BE2CC49.dita"><apiname>CMsvEntry </apiname></xref><xref href="GUID-B36289AC-769F-3A83-BADB-AE0568E97581.dita"><apiname>MMsvEntryObserver </apiname></xref><xref href="GUID-2DA04D96-F0AD-3FDC-9E36-1C27D889AF4B.dita"><apiname>CMsvSession </apiname></xref><xref href="GUID-E1699CAB-423D-3AFA-BE77-3AFF38886EA3.dita"><apiname>RSendAs </apiname></xref><xref href="GUID-CB2BB982-F91D-3E06-8D66-56731AA60EB8.dita"><apiname>CSendAsMessageTypes </apiname></xref><xref href="GUID-90C4FDEE-3E4D-32B3-85E1-52C157AC4AC4.dita"><apiname>CSendAsAccounts </apiname></xref> <xref href="GUID-90C4FDEE-3E4D-32B3-85E1-52C157AC4AC4.dita"><apiname>CSendAsAccounts </apiname></xref> <xref href="GUID-1FDBA8F6-D1CC-3AE5-AF48-1256D50C5A4F.dita"><apiname>CMsvOperationWait </apiname></xref><xref href="GUID-4499491F-FA1A-38E1-BB13-1AB184A31DA6.dita"><apiname> RSendAsMessage </apiname></xref></p></section>
-<section id="GUID-13FDF5EE-00C2-54D4-AF6C-41E3DBDC2B93"><title>Build</title> <p>The <xref href="GUID-3100800B-B2F7-50EF-BD4C-3C345ECCB2A5.dita">Symbian OS build process</xref> describes
+<section id="GUID-13FDF5EE-00C2-54D4-AF6C-41E3DBDC2B93"><title>Build</title> <p>The <xref href="GUID-3100800B-B2F7-50EF-BD4C-3C345ECCB2A5.dita">Symbian build process</xref> describes
how to build an application. </p> <p>The SendAs example builds an executable
called <filepath>SendAs2Example.exe</filepath> in the standard location (<filepath>\epoc32\release\winscw\</filepath> <i><build_variant></i> for
CodeWarrior). After launching the executable, depending on the emulator you
--- a/Symbian3/SDK/Source/GUID-385BB488-5C32-58A7-8401-F3F0A0707DD9.dita Fri Jan 22 18:26:19 2010 +0000
+++ b/Symbian3/SDK/Source/GUID-385BB488-5C32-58A7-8401-F3F0A0707DD9.dita Thu Mar 11 15:24:26 2010 +0000
@@ -13,19 +13,19 @@
Interface MTM implementation</title><prolog><metadata><keywords/></metadata></prolog><conbody>
<p> <b>Note:</b> This example is designed to work with Techview and there
is no guarantee that it will work on other interfaces </p>
-<section><title>Example Code</title> <p>Click on the following link to download
-the example:<xref href="guid-6013a680-57f9-415b-8851-c4fa63356636/zips/guid-419758e4-b663-48d3-bf21-d9c4bb00da23.zip" scope="external">.TextMTM.zip</xref> </p><p>Click: <xref href="guid-6013a680-57f9-415b-8851-c4fa63356636/guid-419758e4-b663-48d3-bf21-d9c4bb00da23.html" scope="peer">browse</xref> to view the example code. </p> <p>The
-files reproduced here are the main files contained in the examples directory.
-Some extra files may be needed to run the examples, and these will be found
-in the appropriate examples directory. </p> </section>
-<section><title>Class summary</title><p> <xref href="GUID-A5982338-A057-3870-8832-F503AEAC470A.dita"><apiname>CBaseMtmUi</apiname></xref> <xref href="GUID-A4B1F874-27C0-3BB6-9D29-C35C75A5DB98.dita"><apiname> TMsvId</apiname></xref> <xref href="GUID-AF724192-6580-3DE3-9287-3A005C0AA932.dita"><apiname> CMsvOperation</apiname></xref> <xref href="GUID-ED81FC3E-2BDA-390D-A866-9651DF8CE51D.dita"><apiname> CEikFileSaveAsDialog </apiname></xref> <xref href="GUID-DC21E927-18B3-3BBF-9B67-496F2D158B03.dita"><apiname>CEikDialog</apiname></xref> </p></section>
-<section><title>Description</title> <p>The <filepath>txtu</filepath> project
+<section id="GUID-F60E6B58-C75C-4C28-954B-770EE756E397"><title>Example Code</title> <p>Click on the following link to download
+the example:<xref href="guid-6013a680-57f9-415b-8851-c4fa63356636/zips/guid-419758e4-b663-48d3-bf21-d9c4bb00da23.zip" scope="external">.TextMTM.zip</xref> </p><p>Click: <xref href="guid-6013a680-57f9-415b-8851-c4fa63356636/guid-419758e4-b663-48d3-bf21-d9c4bb00da23.html" scope="peer">browse</xref> to view the example code. </p> <p>The files reproduced
+here are the main files contained in the examples directory. Some extra files
+may be needed to run the examples, and these will be found in the appropriate
+examples directory. </p> </section>
+<section id="GUID-EC764B46-F419-46B4-B99B-96EA0935277F"><title>Class summary</title><p> <xref href="GUID-A5982338-A057-3870-8832-F503AEAC470A.dita"><apiname>CBaseMtmUi</apiname></xref> <xref href="GUID-A4B1F874-27C0-3BB6-9D29-C35C75A5DB98.dita"><apiname> TMsvId</apiname></xref> <xref href="GUID-AF724192-6580-3DE3-9287-3A005C0AA932.dita"><apiname> CMsvOperation</apiname></xref> <xref href="GUID-ED81FC3E-2BDA-390D-A866-9651DF8CE51D.dita"><apiname> CEikFileSaveAsDialog </apiname></xref> <xref href="GUID-DC21E927-18B3-3BBF-9B67-496F2D158B03.dita"><apiname>CEikDialog</apiname></xref> </p></section>
+<section id="GUID-5FB87906-A38C-4BAB-92B3-75FF497E9E24"><title>Description</title> <p>The <filepath>txtu</filepath> project
demonstrates a User Interface MTM. The central class is <codeph>CTextMtmUi</codeph>,
derived from the User Interface MTM base class <codeph>CBaseMtmUi</codeph>. </p> <p>Note
that the <filepath>txtu</filepath> project has dependencies on some GUI components
-that might not be present on all Symbian OS licensee SDKs. </p> <p> <filepath>txtu</filepath> implements
+that might not be present on all SDKs. </p> <p> <filepath>txtu</filepath> implements
the following MTM functionality: </p> </section>
-<section><title>Basic functions for messages</title> <p> <codeph>Create()</codeph>:
+<section id="GUID-8F7FD0AC-86BE-486B-B999-43EC6914A457"><title>Basic functions for messages</title> <p> <codeph>Create()</codeph>:
this creates a new local message in the <systemoutput>Draft</systemoutput> folder,
with description field set to "New Text", and then invokes edit. </p> <p> <codeph>Edit()</codeph>:
no UI for editing and viewing text messages is implemented. A simple stub
@@ -39,13 +39,13 @@
move and delete functions. These commands are passed to the Message Server,
which then passes them on to the Server-side Text MTM. </p> <p> <codeph>ReplyL()</codeph> and <codeph>ForwardL()</codeph>:
there is no UI support for message replies and forwarding. </p> </section>
-<section><title>Basic functions for services</title> <p> <codeph>Create()</codeph> and <codeph>Edit()</codeph>:
+<section id="GUID-F1566C1D-A866-46F1-AE7B-34280C7A6FBB"><title>Basic functions for services</title> <p> <codeph>Create()</codeph> and <codeph>Edit()</codeph>:
when requested to create a new Text service entry, a dialog pops up allowing
the user to specify the folder associated with the service. This is performed
by class <codeph>CTextMtmEditServiceDialog</codeph> and resource <codeph>r_dialog_service_settings</codeph>.
The service entry can then be edited later on, to change the folder. </p> <p>After
the service entry is created or changed, an automatic refresh will be triggered. </p> </section>
-<section><title>MTM-specific operations</title> <p>The following MTM-specific
+<section id="GUID-1084490D-DA56-4F06-BCA2-BD4698CE633E"><title>MTM-specific operations</title> <p>The following MTM-specific
operations are accepted: </p> <ul>
<li id="GUID-94BF89D8-80D9-53CD-B3C3-40150B16EF6A"><p>Refresh: this command
refreshes the currently highlighted service entry. It calls the MTM-specific
--- a/Symbian3/SDK/Source/GUID-43080A86-72D3-5422-953E-A5EF79961D7B.dita Fri Jan 22 18:26:19 2010 +0000
+++ b/Symbian3/SDK/Source/GUID-43080A86-72D3-5422-953E-A5EF79961D7B.dita Thu Mar 11 15:24:26 2010 +0000
@@ -11,7 +11,7 @@
PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
<concept id="GUID-43080A86-72D3-5422-953E-A5EF79961D7B" xml:lang="en"><title>Writing
a UPS Policy Evaluator</title><prolog><metadata><keywords/></metadata></prolog><conbody>
-<section><title>Introduction</title> <p>Policy Evaluators are ECOM plug-ins.
+<section id="GUID-56EDF170-1A32-4275-8799-99D13C485E1E"><title>Introduction</title> <p>Policy Evaluators are ECOM plug-ins.
They allow security decisions to be specific to the data on which the service
acts instead of simply granting full access to the service, for example "Allow
application X to send SMS messages to 01234567". This is supported through
@@ -39,7 +39,7 @@
on a usage threshold or simply as additional confirmation if the user selected
"Never". This is supported via the force prompt functionality. </p> </li>
</ul> </section>
-<section><title>Procedure</title> <p>Writing policy evaluator includes the
+<section id="GUID-CCBB139D-0F1C-4AD4-B2F2-062CF660A0DE"><title>Procedure</title> <p>Writing policy evaluator includes the
following: </p> <ol id="GUID-F50174F6-3619-545A-8844-D4DA64B1B339">
<li id="GUID-246EF2AB-23D9-5B1B-BC4C-8CCFB545C307"><p>Generating fingerprints </p> </li>
<li id="GUID-4427FF70-9461-566A-8567-FC6EEF879475"><p>Forcing prompts </p> </li>
@@ -181,7 +181,7 @@
creators do not define a policy evaluator, a default (internal) policy evaluator
is returned. The default policy evaluator returns a single, null fingerprint.
The default policy evaluator does not override the <codeph>ForcePromptL()</codeph> API. </p> </section>
-<section><title> Upgrading policy evaluators </title> <p>A policy evaluator
+<section id="GUID-987ECDA9-5728-4A7A-AB38-D58A7CC097AC"><title> Upgrading policy evaluators </title> <p>A policy evaluator
can be overwritten or eclipsed without restarting the UPS, if it is delivered
through an appropriately signed upgrade. </p> <ul>
<li id="GUID-086FABB6-13C0-5D98-8B2A-1D38BD620EB5"><p>The ECOM plug-in will
@@ -194,20 +194,8 @@
the UPS that the plug-ins may have changed whenever Software Install modifies <filepath>sys\bin</filepath> on
the system drive. There is no need to explicitly register changes to plug-ins. </p> </li>
</ul> </section>
-<section><title> Policy evaluator example</title> <p>The following code shows
-an example of a full implementation of the policy evaluator file: </p> <codeblock id="GUID-D1615A8D-334C-5718-BFD6-EC3004A09F3A" xml:space="preserve">// Copyright (c) 2006-2009 Nokia Corporation and/or its subsidiary(-ies).
-// All rights reserved.
-// This component and the accompanying materials are made available
-// under the terms of the License "Symbian Foundation License v1.0"
-// which accompanies this distribution, and is available
-// at the URL "http://www.symbianfoundation.org/legal/sfl-v10.html".
-//
-// Initial Contributors:
-// Nokia Corporation - initial contribution.
-
-// refpolicyevaluator.cpp
-
-#include "refpolicyevaluator.h"
+<section id="GUID-48624948-C1C9-4DEA-A6E1-6E4B9AC72E8E"><title> Policy evaluator example</title> <p>The following code shows
+an example of a full implementation of the policy evaluator file: </p> <codeblock id="GUID-D1615A8D-334C-5718-BFD6-EC3004A09F3A" xml:space="preserve">#include "refpolicyevaluator.h"
#include <ecom/implementationproxy.h>
#include <ups/cliententity.h>
#include <ups/fingerprint.h>
--- a/Symbian3/SDK/Source/GUID-4A4951D6-92A9-596D-B84C-B95E78CE8AA8.dita Fri Jan 22 18:26:19 2010 +0000
+++ b/Symbian3/SDK/Source/GUID-4A4951D6-92A9-596D-B84C-B95E78CE8AA8.dita Thu Mar 11 15:24:26 2010 +0000
@@ -12,8 +12,8 @@
<concept id="GUID-4A4951D6-92A9-596D-B84C-B95E78CE8AA8" xml:lang="en"><title>Copyright
Acknowledgments for P.I.P.S. Libraries</title><prolog><metadata><keywords/></metadata></prolog><conbody>
<section id="GUID-6918526A-A574-4172-A64A-216E1C04585F"><title>Overview</title> <p>The
-P.I.P.S. libraries included in Symbian platform are covered by the following
-copyright notices: </p> <ul>
+P.I.P.S. libraries included on the Symbian platform are covered
+by the following copyright notices: </p> <ul>
<li id="GUID-EAEA5FD9-2686-5B42-9B06-6D125C50D6B0"><p><xref href="GUID-4A4951D6-92A9-596D-B84C-B95E78CE8AA8.dita#GUID-4A4951D6-92A9-596D-B84C-B95E78CE8AA8/GUID-417AF001-F9D8-5D02-89CF-60D4F66E0701">Free BSD</xref> </p> </li>
<li><p><xref href="GUID-4A4951D6-92A9-596D-B84C-B95E78CE8AA8.dita#GUID-4A4951D6-92A9-596D-B84C-B95E78CE8AA8/GUID-69dd6f30-81a6-4891-87b0-ab965693a535">OpenSSL</xref></p></li>
<li><p><xref href="GUID-4A4951D6-92A9-596D-B84C-B95E78CE8AA8.dita#GUID-4A4951D6-92A9-596D-B84C-B95E78CE8AA8/GUID-d1f2b954-c042-465f-b946-caeac8bbaf9f">Zlib</xref></p></li>
@@ -1552,7 +1552,7 @@
</ol><p>Jean-loup Gailly Mark Adler</p><p>jloup@gzip.org madler@alumni.caltech.edu</p></section>
<section id="GUID-D3AAED73-A09D-55E3-88A4-B882D878102D"><title>Nokia Corporation</title> <p>Copyright
(c) 2006-2010 Nokia Corporation and/or its subsidiary(-ies). </p> <p>All rights
-reserved. </p> <p>This component and the accompanying materials are made available
-under the terms of the License "Symbian Foundation License v1.0" which accompanies
-this distribution, and is available at the URL "http://www.symbianfoundation.org/legal/sfl-v10.html". </p> </section>
+reserved. </p> <p>This component and the accompanying materials are made available under the terms of the License
+"Eclipse Public License v1.0" which accompanies this distribution,
+and is available at the URL "http://www.eclipse.org/legal/epl-v10.html".</p> </section>
</conbody></concept>
\ No newline at end of file
--- a/Symbian3/SDK/Source/GUID-57A909F3-EAEA-5FE2-B620-E21204794497.dita Fri Jan 22 18:26:19 2010 +0000
+++ b/Symbian3/SDK/Source/GUID-57A909F3-EAEA-5FE2-B620-E21204794497.dita Thu Mar 11 15:24:26 2010 +0000
@@ -13,22 +13,20 @@
to Load the Physical Device Driver and Logical Device Driver: Tutorial</title><shortdesc>When testing using the console, all drivers need to be loaded directly.
This tutorial describes how to load the drivers required for the Serial Communications
Server. </shortdesc><prolog><metadata><keywords/></metadata></prolog><taskbody>
-<context><p>Testing of communications software can be done using the Symbian
-OS console shell interface rather than a GUI interface. The console shell
-interface has advantages when testing since the console allows software to
-be tested in isolation. When testing with a GUI interface the testing can
-be difficult if other software in the GUI is attempting to access resources.
-If the device or the emulator is started with just the console, then only
-the kernel and file system are running. The tester can then load the software
-required for the test and ensure that no other software is using any resources.
-This avoids problems of other software interrupting the CPU or using and releasing
-memory or other hardware while a test is running. </p><p>Any test applications
-that have not been launched by the GUI should
- explicitly load the correct physical and logical device drivers. In most
-cases the bootloader will load the physical device driver. It is safe to load
-a
-device driver which has already been loaded, since the API will return
-<xref href="GUID-D1D25122-F2B8-3C78-8599-84905BFD47B8.dita"><apiname>KErrAlreadyExists</apiname></xref></p> </context>
+<context id="GUID-3FD29C37-082A-4B68-A955-E4B0D625BA92"><p>Testing of communications software can be done using the Symbian platform
+console shell interface rather than a GUI interface. The console shell interface
+has advantages when testing since the console allows software to be tested
+in isolation. When testing with a GUI interface the testing can be difficult
+if other software in the GUI is attempting to access resources. If the device
+or the emulator is started with just the console, then only the kernel and
+file system are running. The tester can then load the software required for
+the test and ensure that no other software is using any resources. This avoids
+problems of other software interrupting the CPU or using and releasing memory
+or other hardware while a test is running. </p><p>Any test applications that
+have not been launched by the GUI should explicitly load the correct physical
+and logical device drivers. In most cases the bootloader will load the physical
+device driver. It is safe to load a device driver which has already been loaded,
+since the API will return <xref href="GUID-D1D25122-F2B8-3C78-8599-84905BFD47B8.dita"><apiname>KErrAlreadyExists</apiname></xref></p> </context>
<steps id="GUID-8D0D239F-51F9-512A-8405-ADD01AE1660B">
<step id="GUID-21876E62-D2A9-510A-BAD2-CB3E4271A02B"><cmd>Identify the names
of the physical and logical device drivers required.</cmd>
--- a/Symbian3/SDK/Source/GUID-59230503-7E2E-505D-9BC9-C2D2DB96B3E9.dita Fri Jan 22 18:26:19 2010 +0000
+++ b/Symbian3/SDK/Source/GUID-59230503-7E2E-505D-9BC9-C2D2DB96B3E9.dita Thu Mar 11 15:24:26 2010 +0000
@@ -11,7 +11,7 @@
PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
<concept id="GUID-59230503-7E2E-505D-9BC9-C2D2DB96B3E9" xml:lang="en"><title>RTPExample:
RTP Packet Streaming Example</title><prolog><metadata><keywords/></metadata></prolog><conbody>
-<section><title>Description</title> <p>This example code demonstrates RTP
+<section id="GUID-50EDE46C-719B-4D77-8C61-666A5125C07C"><title>Description</title> <p>This example code demonstrates RTP
packet streaming. It uses <codeph>CRtpFileSender</codeph> to send RTP packets
and <codeph>CRtpFileStreamer</codeph> to receive RTP packets. The example
opens an RTP session using the pre-connected socket and initialises new send
@@ -22,9 +22,9 @@
the following functionality: </p> </section>
<section id="GUID-1A5135CC-CAF2-58D8-B37D-5C04B0454D59"><title>Download</title> <p>Click
on the following link to download the example: <xref href="guid-6013a680-57f9-415b-8851-c4fa63356636/zips/guid-a4ef24ea-0ffa-410a-a19c-e1085f64c0e2.zip" scope="external">RTPExample.zip</xref></p><p>Click <xref href="guid-6013a680-57f9-415b-8851-c4fa63356636/guid-a4ef24ea-0ffa-410a-a19c-e1085f64c0e2.html" scope="peer">browse</xref> to view the example code. </p> </section>
-<section><title>Initialising</title> <codeblock id="GUID-DD0E36D0-2CC4-52FF-8C58-2D0061A453CA" xml:space="preserve">void CRtpFileStreamer::ConstructL();</codeblock> <p>Opens an RTP session using the pre-connected socket and initialises new send
+<section id="GUID-6CB87F84-BDBB-4606-917D-3FE79FDA16C5"><title>Initialising</title> <codeblock id="GUID-DD0E36D0-2CC4-52FF-8C58-2D0061A453CA" xml:space="preserve">void CRtpFileStreamer::ConstructL();</codeblock> <p>Opens an RTP session using the pre-connected socket and initialises new send
sources on the RTP session. </p> </section>
-<section><title>Sending an RTP packet</title> <codeblock id="GUID-53DAAACD-46A9-5DAA-8B2D-A4108DA6DFA7" xml:space="preserve">void CRtpFileSender::RunL();</codeblock> <p>Sends the RTP packet. This does the following: </p> <ul>
+<section id="GUID-3F6D2D79-9639-4EAC-9EE6-BA32DC688B6F"><title>Sending an RTP packet</title> <codeblock id="GUID-53DAAACD-46A9-5DAA-8B2D-A4108DA6DFA7" xml:space="preserve">void CRtpFileSender::RunL();</codeblock> <p>Sends the RTP packet. This does the following: </p> <ul>
<li id="GUID-C279418B-B804-53F1-B18F-1FB030BC6007"><p>gets a new RTP packet
to send from the send source </p> </li>
<li id="GUID-35269B55-BD88-5CEA-A9E1-5423BB0E3AF9"><p>sets the RTP timestamp
@@ -37,19 +37,19 @@
<li id="GUID-84488760-F28D-584A-A5F1-9E5D44C8C2D4"><p>closes the source file. </p> </li>
</ul> <p> <codeph>CRtpFileSender::PacketSent()</codeph> is called to notify
that the RTP packet has been successfully sent. </p> </section>
-<section><title>Receiving an RTP packet</title> <codeblock id="GUID-0C30C58E-70B9-5E2A-946F-F349E8026454" xml:space="preserve">void CRtpFileStreamer::NewSource();</codeblock> <p>When an RTP packet with a new receive source arrives, this callback function
+<section id="GUID-72251E64-B5EF-4994-8ECF-89872AE23D2F"><title>Receiving an RTP packet</title> <codeblock id="GUID-0C30C58E-70B9-5E2A-946F-F349E8026454" xml:space="preserve">void CRtpFileStreamer::NewSource();</codeblock> <p>When an RTP packet with a new receive source arrives, this callback function
is called, which registers the packet. This can be used for different types
of RTP packets such as APP, BYE, SDES, SR and RR. </p> <codeblock id="GUID-22A41C41-613E-5DB5-BA35-1F92FEE214AF" xml:space="preserve">void CRtpFileStreamer::PacketArrived();</codeblock> <p>Whenever an RTP packet arrives, this callback function is called. The
function retrieves the payload from the packet received and writes it to the
target file. </p> </section>
-<section><title>Class summary</title><p> <xref href="GUID-D4F08503-F1EF-3531-9C3C-4AF24A6255F0.dita"><apiname>RSocket </apiname></xref> <xref href="GUID-EF29C1D7-B1E5-370F-AE37-66231A6BE449.dita"><apiname>RSocketServ </apiname></xref> <xref href="GUID-BED8A733-2ED7-31AD-A911-C1F4707C67FD.dita"><apiname>RConnection </apiname></xref> <xref href="GUID-97FC8566-E4AD-3881-8669-134798A88779.dita"><apiname> RRtpSession </apiname></xref> <xref href="GUID-EF30A0A3-612A-362D-9AC5-07FD314E5CDC.dita"><apiname>RRtpSendSource </apiname></xref> <xref href="GUID-3690BFA1-A4EA-34EA-AD63-5FCC14CB67A2.dita"><apiname>RRtpReceiveSource </apiname></xref> <xref href="GUID-0720D1BD-7F73-3EF6-80A6-17127EF17C91.dita"><apiname>RRtpSendPacket </apiname></xref> <xref href="GUID-3E4F47A8-0432-307A-B871-A2F7F3A7505F.dita"><apiname>RRtpReceivePacket </apiname></xref> <xref href="GUID-E263C747-946F-35AA-9F1D-41833BD350FC.dita"><apiname>RFs </apiname></xref> <xref href="GUID-BE0804F6-4375-3C8A-8C83-968F510466E0.dita"><apiname>RFile </apiname></xref> </p></section>
-<section><title>Usage</title> <p>The <xref href="GUID-3100800B-B2F7-50EF-BD4C-3C345ECCB2A5.dita">Symbian
-OS build process</xref> describes how to build an application. </p> <p>This
+<section id="GUID-2291AD95-0A59-4FE0-A52E-12FA0876E097"><title>Class summary</title><p> <xref href="GUID-D4F08503-F1EF-3531-9C3C-4AF24A6255F0.dita"><apiname>RSocket </apiname></xref> <xref href="GUID-EF29C1D7-B1E5-370F-AE37-66231A6BE449.dita"><apiname>RSocketServ </apiname></xref> <xref href="GUID-BED8A733-2ED7-31AD-A911-C1F4707C67FD.dita"><apiname>RConnection </apiname></xref> <xref href="GUID-97FC8566-E4AD-3881-8669-134798A88779.dita"><apiname> RRtpSession </apiname></xref> <xref href="GUID-EF30A0A3-612A-362D-9AC5-07FD314E5CDC.dita"><apiname>RRtpSendSource </apiname></xref> <xref href="GUID-3690BFA1-A4EA-34EA-AD63-5FCC14CB67A2.dita"><apiname>RRtpReceiveSource </apiname></xref> <xref href="GUID-0720D1BD-7F73-3EF6-80A6-17127EF17C91.dita"><apiname>RRtpSendPacket </apiname></xref> <xref href="GUID-3E4F47A8-0432-307A-B871-A2F7F3A7505F.dita"><apiname>RRtpReceivePacket </apiname></xref> <xref href="GUID-E263C747-946F-35AA-9F1D-41833BD350FC.dita"><apiname>RFs </apiname></xref> <xref href="GUID-BE0804F6-4375-3C8A-8C83-968F510466E0.dita"><apiname>RFile </apiname></xref> </p></section>
+<section id="GUID-8FE5D0CA-57F6-4CF2-A5AA-44C6A7534AA3"><title>Usage</title> <p>The <xref href="GUID-3100800B-B2F7-50EF-BD4C-3C345ECCB2A5.dita">Symbian
+build process</xref> describes how to build an application. </p> <p>This
is a console application, so does not have a GUI. It builds an executable
called <filepath>RTPExample.exe</filepath> in the standard location (<filepath>\epoc32\release\winscw\</filepath> <i><build_variant></i> for
CodeWarrior). After launching the executable, depending on the emulator you
are using, you may need to task away from the app launcher/shell screen to
view the console. </p> </section>
-<section><title>See also</title> <p> <xref href="GUID-993629CB-17B4-5E87-8DE1-06A4AC473FDD.dita">RTP
+<section id="GUID-467EE2A3-9D85-4909-9CB1-98C9CBCAA41D"><title>See also</title> <p> <xref href="GUID-993629CB-17B4-5E87-8DE1-06A4AC473FDD.dita">RTP
overview</xref> </p> </section>
</conbody></concept>
\ No newline at end of file
--- a/Symbian3/SDK/Source/GUID-641A276D-F618-50CE-BA5A-658DCC26BAB5.dita Fri Jan 22 18:26:19 2010 +0000
+++ b/Symbian3/SDK/Source/GUID-641A276D-F618-50CE-BA5A-658DCC26BAB5.dita Thu Mar 11 15:24:26 2010 +0000
@@ -14,11 +14,12 @@
essential elements of the implementation. The project files are used for project
development. The implementation project file contains information (source
file, build file) about the implementation that is being built.<shortdesc>The
-format of implementation project file is dependent on the version of Symbian
+format of implementation project file is dependent on the version of the Symbian
platform used. The differences basically reflect the introduction of platform
security into Symbian OS v9.0 and later versions. </shortdesc></abstract><prolog><metadata><keywords/></metadata></prolog><taskbody>
<steps-unordered id="GUID-C62C17ED-E41C-54FA-BA0A-9C10A49E159B">
-<step id="GUID-BB98ED98-0E27-4865-857D-01BC54ACB226"><cmd>For creating a plug-in project file for Symbian OS v9.1 and later: </cmd>
+<step id="GUID-BB98ED98-0E27-4865-857D-01BC54ACB226"><cmd>For creating a plug-in
+project file for Symbian OS v9.1 and later: </cmd>
<substeps id="GUID-A24F641F-EF19-46A2-8B4B-883E726AE909">
<substep id="GUID-F4AC55A1-0B66-4F17-8B24-2BE518949884"><cmd/>
<info>Set <codeph>TARGET</codeph> to the standard DLL name. <codeph>TARGET</codeph> contains
--- a/Symbian3/SDK/Source/GUID-6590B534-D976-5305-BE95-48DD05120DFB.dita Fri Jan 22 18:26:19 2010 +0000
+++ b/Symbian3/SDK/Source/GUID-6590B534-D976-5305-BE95-48DD05120DFB.dita Thu Mar 11 15:24:26 2010 +0000
@@ -18,7 +18,7 @@
<li id="GUID-245A31A4-4C38-54F4-9ACC-92285C12966E"><p><xref href="GUID-6590B534-D976-5305-BE95-48DD05120DFB.dita#GUID-6590B534-D976-5305-BE95-48DD05120DFB/GUID-7582B2CB-AAC8-5E41-ADE1-76C12B691E10">Socket IOCtl options</xref> </p> </li>
<li id="GUID-1A2BDA7D-2DE4-52AE-ACD3-12D1A6311A88"><p><xref href="GUID-6590B534-D976-5305-BE95-48DD05120DFB.dita#GUID-6590B534-D976-5305-BE95-48DD05120DFB/GUID-9BF9562E-5831-5A7F-90A1-87BDE1CFBA54">Mathematical functions</xref> </p> </li>
<li id="GUID-A6183A50-BFBA-573B-B2BC-68BE637D7DF5"><p><xref href="GUID-6590B534-D976-5305-BE95-48DD05120DFB.dita#GUID-6590B534-D976-5305-BE95-48DD05120DFB/GUID-DA65E8FA-E20B-5572-AEC9-20AB140DF33A">Error handling and cleanup</xref> </p> <ul>
-<li id="GUID-ADB0AC3E-FB59-52DC-B151-A4551467CBA0"><p><xref href="GUID-6590B534-D976-5305-BE95-48DD05120DFB.dita#GUID-6590B534-D976-5305-BE95-48DD05120DFB/GUID-D8DB43BD-9D19-5A78-8E37-6699653D047A">Mapping P.I.P.S. error codes to Symbian platform error codes</xref> </p> </li>
+<li id="GUID-ADB0AC3E-FB59-52DC-B151-A4551467CBA0"><p><xref href="GUID-6590B534-D976-5305-BE95-48DD05120DFB.dita#GUID-6590B534-D976-5305-BE95-48DD05120DFB/GUID-D8DB43BD-9D19-5A78-8E37-6699653D047A">Mapping P.I.P.S. error codes to the Symbian platform error codes</xref> </p> </li>
</ul> </li>
<li id="GUID-EA748131-29ED-5D32-B1C2-F948ABEA6584"><p><xref href="GUID-6590B534-D976-5305-BE95-48DD05120DFB.dita#GUID-6590B534-D976-5305-BE95-48DD05120DFB/GUID-CF52A59F-FD04-5043-A526-05545E11F0F5">System logger</xref> </p> </li>
<li id="GUID-1C98EDF4-C7BD-5CC8-90EB-D35B759280CD"><p><xref href="GUID-6590B534-D976-5305-BE95-48DD05120DFB.dita#GUID-6590B534-D976-5305-BE95-48DD05120DFB/GUID-8C951D9F-DE32-5201-90F2-45EB442F9FFC">Pthread barriers, rwlocks and spinlocks</xref> </p> </li>
@@ -122,9 +122,9 @@
return EXIT_SUCCESS;
}</codeblock> </section>
<section id="GUID-7582B2CB-AAC8-5E41-ADE1-76C12B691E10"><title>Socket IOCtl
-options</title> <p>The underlying implementation of sockets on Symbian platform
-imposes some restrictions on the socket options available in P.I.P.S. and
-has also resulted in some new non-standard options to be created. </p> <p>The
+options</title> <p>The underlying implementation of sockets on the Symbian
+platform imposes some restrictions on the socket options available in P.I.P.S.
+and has also resulted in some new non-standard options to be created. </p> <p>The
introduction of multi-homing (single link, multiple IP addresses) on Symbian
phones and the various methods of connecting to networks, such as Wi-Fi and
3G, with their varying degrees of cost to the user have made it important
@@ -252,27 +252,27 @@
return Sock;
}</codeblock> </section>
<section id="GUID-9BF9562E-5831-5A7F-90A1-87BDE1CFBA54"><title>Mathematical
-functions</title> <p>Symbian platform does not have any support for long doubles
-so any P.I.P.S. programs which call long double versions of APIs will actually
-invoke the double version of the API. </p> <p>Symbian platform supports the
-use of a hardware floating point co-processor, however not all phones incorporate
-an FPU (Floating Point Unit) and rely on software emulation of floating point
-operations. Phones and computers equipped with an FPU provide faster and more
-accurate floating point operations. </p> <p>Symbian platform does not support
-complex numbers so the P.I.P.S. libraries are not able to offer the POSIX
-complex number APIs. </p> <p> <b>Note:</b> The mathematical functions are
-included in the <filepath>libm.dll</filepath> file. </p> </section>
+functions</title> <p>The Symbian platform does not have any support for long
+doubles so any P.I.P.S. programs which call long double versions of APIs will
+actually invoke the double version of the API. </p> <p>The Symbian platform
+supports the use of a hardware floating point co-processor, however not all
+phones incorporate an FPU (Floating Point Unit) and rely on software emulation
+of floating point operations. Phones and computers equipped with an FPU provide
+faster and more accurate floating point operations. </p> <p>The Symbian platform
+does not support complex numbers so the P.I.P.S. libraries are not able to
+offer the POSIX complex number APIs. </p> <p> <b>Note:</b> The mathematical
+functions are included in the <filepath>libm.dll</filepath> file. </p> </section>
<section id="GUID-DA65E8FA-E20B-5572-AEC9-20AB140DF33A"><title> Error handling
-and cleanup</title> <p>It is important that Symbian platform error codes do
-not reach any ported application code. P.I.P.S. logically maps the native
+and cleanup</title> <p>It is important that the Symbian platform error codes
+do not reach any ported application code. P.I.P.S. logically maps the native
OS error codes with the corresponding POSIX <codeph>errno</codeph> values
as per the standard. So, ported programs will not usually have to alter their
error checking/handling. </p> <p id="GUID-D8DB43BD-9D19-5A78-8E37-6699653D047A"><b>Mapping
-P.I.P.S. error codes to Symbian platform error codes</b> </p> <p>Porting your
-application to Symbian platform requires 'translating' Symbian platform error
-codes to POSIX error codes. <xref href="GUID-C197C9A7-EA05-3F24-9854-542E984C612D.dita#GUID-C197C9A7-EA05-3F24-9854-542E984C612D/GUID-B00F7659-9C31-36CD-896A-40887DECEA4B"><apiname>User::Leaves()</apiname></xref> from native
-Symbian APIs are trapped in P.I.P.S.. Calls to P.I.P.S. APIs from user code
-need not be wrapped in <xref href="GUID-3AD20E0C-F364-533F-9FBC-227478CA9982.dita">TRAP</xref> s. </p> <p>Occasionally
+P.I.P.S. error codes to the Symbian platform error codes</b> </p> <p>Porting
+your application to the Symbian platform requires 'translating' the Symbian
+platform error codes to POSIX error codes. <xref href="GUID-C197C9A7-EA05-3F24-9854-542E984C612D.dita#GUID-C197C9A7-EA05-3F24-9854-542E984C612D/GUID-B00F7659-9C31-36CD-896A-40887DECEA4B"><apiname>User::Leaves()</apiname></xref> from
+native Symbian APIs are trapped in P.I.P.S.. Calls to P.I.P.S. APIs from user
+code need not be wrapped in <xref href="GUID-3AD20E0C-F364-533F-9FBC-227478CA9982.dita">TRAP</xref> s. </p> <p>Occasionally
errors may be generated by the underlying Symbian platform that cannot be
translated to POSIX error codes, in which case the error variable <codeph>errno</codeph> will
be out of the usual range of values, above the maximum value of <codeph>__EMAXERRNO</codeph> or <codeph>124</codeph>. </p> <p>The
@@ -653,7 +653,7 @@
/**</codeblock> </section>
<section id="GUID-777FDBF9-4B80-5B58-88F3-E78DBDB89021"><title>Command line
-shell</title> <p>Symbian platform phones do not have a command line shell
+shell</title> <p>The Symbian platform phones do not have a command line shell
as standard. P.I.P.S. does however support the <xref href="GUID-C0C1D22B-298F-3E8D-A1E9-6F5EFA81F9E8.dita"><apiname>stdin()</apiname></xref>, <xref href="GUID-85797574-E2A2-3C0C-9670-C178078DE199.dita"><apiname>stdout()</apiname></xref> and <xref href="GUID-4FF97B50-2C1E-37EC-888B-FB8D3F14B5B8.dita"><apiname>stderr()</apiname></xref> standard
streams, enabling parent processes to redirect a child's standard streams
for the exchange of data. Without explicitly redirecting the standard streams,
@@ -666,11 +666,11 @@
libraries such as GTK. P.I.P.S., however, does not have its own UI libraries,
so any P.I.P.S. based applications that require UI functionality must rely
on the UI from the device manufacturer. As a consequence, for any UI program
-that uses P.I.P.S., there must be an interaction between Symbian platform
+that uses P.I.P.S., there must be an interaction between the Symbian platform
native C++ and P.I.P.S. C code. </p> </section>
<section id="GUID-3CA8FF29-79B4-5D43-8A23-EDB136BF7A8F"><title>One Definition
Rule - warning</title> <p>Standard C++ states that the <keyword>One Definition
-Rule</keyword> (ODR) must be maintained within a program. </p> <p>Symbian
+Rule</keyword> (ODR) must be maintained within a program. </p> <p>The Symbian
platform can neither check (without significant modifications) that the ODR
is violated nor use the technique called symbol pre-emption to ensure that
the ODR is enforced. </p> <p>Therefore, you must take care and must not assume
--- a/Symbian3/SDK/Source/GUID-66C1493D-5B85-558A-9A39-454E6EBA307B.dita Fri Jan 22 18:26:19 2010 +0000
+++ b/Symbian3/SDK/Source/GUID-66C1493D-5B85-558A-9A39-454E6EBA307B.dita Thu Mar 11 15:24:26 2010 +0000
@@ -10,7 +10,7 @@
<!DOCTYPE concept
PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
<concept id="GUID-66C1493D-5B85-558A-9A39-454E6EBA307B" xml:lang="en"><title>Signal
-Emulation on Symbian Platform</title><prolog><metadata><keywords/></metadata></prolog><conbody>
+Emulation on the Symbian Platform</title><prolog><metadata><keywords/></metadata></prolog><conbody>
<p>The <codeph>libc</codeph> library of P.I.P.S. provides support for POSIX
signals, thereby facilitating the porting of applications that use signals
for exception handling and as control IPC. </p>
@@ -29,7 +29,7 @@
<li id="GUID-177E6544-106B-5E8B-94C6-B0AAD6437C4C"><p>There might be a considerable
amount of latency when you send or receive signals. </p> </li>
</ul>
-<section><title>Sending signals</title> <p>Signals can be sent between P.I.P.S.
+<section id="GUID-BD44C679-553C-402B-AF78-8922E15884E4"><title>Sending signals</title> <p>Signals can be sent between P.I.P.S.
processes using <xref href="GUID-16DC4A9D-44BC-36E2-AB97-5E9E7521937D.dita"><apiname>kill()</apiname></xref>, <xref href="GUID-EB7F74AE-091B-32C3-9D73-18B82F8D3D73.dita"><apiname>raise()</apiname></xref> or <xref href="GUID-3C70BF0B-CD6E-3A30-A9E6-4CCF11D47EEC.dita"><apiname>sigqueue()</apiname></xref>. </p> <p>You
can use these functions to send any of the supported signals (refer to the
following table). </p> <p>The P.I.P.S. runtime sends the following signals
@@ -44,13 +44,13 @@
</ul> <p> <b>Note:</b> Always ensure that you handle <codeph>SIGPIPE</codeph>, <codeph>SIGCHLD</codeph> or <codeph>SIGALRM</codeph> using
a signal handler to avoid the termination of the process receiving these signals.
For more information about handling signals, see the following section. </p> </section>
-<section><title>Handling signals</title> <p>A signal can be received by a
+<section id="GUID-E244317F-3B69-4B10-8156-03F4A807E663"><title>Handling signals</title> <p>A signal can be received by a
process at any time and is handled immediately, unless it is currently blocked.
You can handle a signal in the following ways: </p> <ol id="GUID-F03B299F-A527-5365-81D3-DDDC607A4094">
<li id="GUID-DF0E70C8-74C2-5ACC-B556-8D216275C554"><p> <b>Use default handling:</b> The
-default action for each signal supported on Symbian platform is listed in
-the following table. </p> <p> <b>Note:</b> The default action for all of the
-signals sent by the P.I.P.S. runtime (<codeph>SIGPIPE</codeph>, <codeph>SIGCHLD</codeph> or <codeph>SIGALRM</codeph>)
+default action for each signal supported on the Symbian platform
+is listed in the following table. </p> <p> <b>Note:</b> The default action
+for all of the signals sent by the P.I.P.S. runtime (<codeph>SIGPIPE</codeph>, <codeph>SIGCHLD</codeph> or <codeph>SIGALRM</codeph>)
is process termination. You must provide a custom handler for each of these
signals. </p> <table id="GUID-7101041B-CC50-5367-A3A2-6D15FB15C3DD">
<tgroup cols="2"><colspec colname="col0"/><colspec colname="col1"/>
@@ -230,7 +230,7 @@
return 0;
}</codeblock> </li>
</ol> </section>
-<section><title>Blocking signals</title> <p>A P.I.P.S. process can choose
+<section id="GUID-252E0621-51F1-443A-A4FC-689BD27597E3"><title>Blocking signals</title> <p>A P.I.P.S. process can choose
to block (and subsequently unblock) signals to itself using <xref href="GUID-02901E24-3615-3018-AF20-F5D5D63FD708.dita"><apiname>sighold()</apiname></xref>, <xref href="GUID-AE4CC3C8-C6D4-3F5C-A28F-C4AAB63E8992.dita"><apiname>sigset()</apiname></xref>, <xref href="GUID-68BD2914-FB73-3D91-9D81-425BF2436473.dita"><apiname>sigrelse()</apiname></xref> and <xref href="GUID-C7279C75-CB98-3F24-ABAA-76CF0009A8ED.dita"><apiname>sigprocmask()</apiname></xref>. Signals that are blocked on a P.I.P.S.
process are not be delivered for handling. Instead, they are queued to be
handled when they are unblocked. </p> <p>Non-realtime signals are queued only
--- a/Symbian3/SDK/Source/GUID-69B46D92-8D07-5B42-B603-3F725977AA4A.dita Fri Jan 22 18:26:19 2010 +0000
+++ b/Symbian3/SDK/Source/GUID-69B46D92-8D07-5B42-B603-3F725977AA4A.dita Thu Mar 11 15:24:26 2010 +0000
@@ -19,8 +19,8 @@
<li id="GUID-77B3171B-FCF4-5744-B288-AFCC81B93488"><p>DHCP States </p> </li>
<li id="GUID-460F04A8-5FF1-578F-B129-3C61264044D4"><p>DHCP Options </p> </li>
</ul>
-<section id="GUID-D83FB908-53EC-4019-A8E4-8B633FEC7F0B"><title>DHCP States </title> <p>The following are the states of the
-DHCP daemon in Symbian OS: </p> <ul>
+<section id="GUID-D83FB908-53EC-4019-A8E4-8B633FEC7F0B"><title>DHCP States </title> <p>The
+following are the states of the DHCP daemon in Symbian platform: </p> <ul>
<li id="GUID-ACD085A9-E25C-58A8-859E-1E42BC467089"><p>DHCP Discover </p> </li>
<li id="GUID-18AAC18A-9A29-5B5D-AEC1-E64B8A81A149"><p>Bind </p> </li>
<li id="GUID-04DF8A2D-4CCD-59A3-8346-CF7D5E1F176C"><p>Renew lease </p> </li>
@@ -40,9 +40,10 @@
IP address using DISCOVER message. </p> <p><b>Release lease </b> </p> <p>When
the DHCP client does not require a connection it releases the lease, so that
it can be configured to any other client requesting a connection. </p> </section>
-<section id="GUID-C5F11CA2-8880-4FDB-8065-149C5EAA7A44"><title>DHCP Options</title> <p>To obtain the network parameters from
-the DHCP server, the client uses the DHCP options. The Internet standard <xref href="http://www.ietf.org/rfc/rfc2132.txt" scope="external">RFC 2132</xref> specifies
-the various DHCP options. The client uses the <xref href="GUID-95F9FA1F-5AA5-3C2F-ADE0-34668B499C50.dita"><apiname>aOptionLevel</apiname></xref> and <xref href="GUID-DA7EBA40-EF88-3C95-9361-E3A199783CE2.dita"><apiname>aOptionName</apiname></xref> arguments
+<section id="GUID-C5F11CA2-8880-4FDB-8065-149C5EAA7A44"><title>DHCP Options</title> <p>To
+obtain the network parameters from the DHCP server, the client uses the DHCP
+options. The Internet standard <xref href="http://www.ietf.org/rfc/rfc2132.txt" scope="external">RFC 2132</xref> specifies the various DHCP options. The client
+uses the <xref href="GUID-95F9FA1F-5AA5-3C2F-ADE0-34668B499C50.dita"><apiname>aOptionLevel</apiname></xref> and <xref href="GUID-DA7EBA40-EF88-3C95-9361-E3A199783CE2.dita"><apiname>aOptionName</apiname></xref> arguments
while calling <xref href="GUID-BED8A733-2ED7-31AD-A911-C1F4707C67FD.dita#GUID-BED8A733-2ED7-31AD-A911-C1F4707C67FD/GUID-9F820CF9-1D4F-3452-983B-E0C694D6783A"><apiname>RConnection::Ioctl()</apiname></xref> function. </p> </section>
</conbody><related-links>
<link href="GUID-45E1953A-DEFB-5E48-AC96-443A3234F913.dita"><linktext>Retrieving
--- a/Symbian3/SDK/Source/GUID-7068AB77-5C96-59A3-B975-7923FD843832.dita Fri Jan 22 18:26:19 2010 +0000
+++ b/Symbian3/SDK/Source/GUID-7068AB77-5C96-59A3-B975-7923FD843832.dita Thu Mar 11 15:24:26 2010 +0000
@@ -123,11 +123,11 @@
<li><p><xref href="GUID-1851A507-A5A9-356F-88A4-494066F43499.dita"><apiname>RHashSet</apiname></xref> </p></li>
<li><p><xref href="GUID-616B71F7-B0A8-31F9-BCF1-FB736EC7E225.dita"><apiname>RPtrHashMap</apiname></xref></p></li>
</ul></section>
-<section id="GUID-167C0565-5EFF-5F8E-A4AB-2D1591A9AEFA"><title>Build</title> <p>The
-Symbian OS build process describes how to build an application. </p> <p>The
-HashTableExample builds an executable called <filepath>hashtableexample.exe</filepath> in
-the standard location (<filepath>\epoc32\release\winscw\<build_variant></filepath> for
-CodeWarrior). After launching the executable, depending on the emulator you
-are using, you may need to navigate away from the application launcher/shell
-screen to view the console. </p> </section>
+<section id="GUID-167C0565-5EFF-5F8E-A4AB-2D1591A9AEFA"><title>Build</title> <p><xref href="GUID-3100800B-B2F7-50EF-BD4C-3C345ECCB2A5.dita">The Symbian build process</xref> describes
+how to build an application. </p> <p>The HashTableExample builds an executable
+called <filepath>hashtableexample.exe</filepath> in the standard location
+(<filepath>\epoc32\release\winscw\<build_variant></filepath> for CodeWarrior).
+After launching the executable, depending on the emulator you are using, you
+may need to navigate away from the application launcher/shell screen to view
+the console. </p> </section>
</conbody></concept>
\ No newline at end of file
--- a/Symbian3/SDK/Source/GUID-70B9796F-8CF3-5DC4-93B4-0B1FED936169.dita Fri Jan 22 18:26:19 2010 +0000
+++ b/Symbian3/SDK/Source/GUID-70B9796F-8CF3-5DC4-93B4-0B1FED936169.dita Thu Mar 11 15:24:26 2010 +0000
@@ -17,21 +17,21 @@
class is <codeph>CTxtiMtmUiData</codeph>, derived from the User Interface
MTM base class <codeph>CBaseMtmUiData</codeph>. </p>
<p> <filepath>txti</filepath> implements the following MTM functionality: </p>
-<section><title>Example Code</title> <p>Click on the following link to download
-the example: <xref href="guid-6013a680-57f9-415b-8851-c4fa63356636/zips/guid-419758e4-b663-48d3-bf21-d9c4bb00da23.zip" scope="external">TextMTM.zip</xref> </p><p>Click: <xref href="guid-6013a680-57f9-415b-8851-c4fa63356636/guid-419758e4-b663-48d3-bf21-d9c4bb00da23.html" scope="peer">browse</xref> to view the example code. </p> <p>The
-files reproduced here are the main files contained in the examples directory.
-Some extra files may be needed to run the examples, and these will be found
-in the appropriate examples directory. </p> </section>
-<section><title>Class summary</title><p><xref href="GUID-899C6D87-5712-34A7-902C-EA452894700C.dita"><apiname>CBaseMtmUiData</apiname></xref></p></section>
-<section><title>Icons</title> <p>Icons are provided for messages, folders,
+<section id="GUID-D230F67C-8D31-41A6-B298-0AF0DC45A130"><title>Example Code</title> <p>Click on the following link to download
+the example: <xref href="guid-6013a680-57f9-415b-8851-c4fa63356636/zips/guid-419758e4-b663-48d3-bf21-d9c4bb00da23.zip" scope="external">TextMTM.zip</xref> </p><p>Click: <xref href="guid-6013a680-57f9-415b-8851-c4fa63356636/guid-419758e4-b663-48d3-bf21-d9c4bb00da23.html" scope="peer">browse</xref> to view the example code. </p> <p>The files reproduced
+here are the main files contained in the examples directory. Some extra files
+may be needed to run the examples, and these will be found in the appropriate
+examples directory. </p> </section>
+<section id="GUID-F62B8A55-BBFF-4B09-92AB-DB6BECAEDE7F"><title>Class summary</title><p><xref href="GUID-899C6D87-5712-34A7-902C-EA452894700C.dita"><apiname>CBaseMtmUiData</apiname></xref></p></section>
+<section id="GUID-2149EB45-BDA8-41EE-887D-69A3439DF2E1"><title>Icons</title> <p>Icons are provided for messages, folders,
and services, for use in the message browser. They are built into a Symbian
-OS multi-bitmap file <filepath>txti.mbm</filepath>. <codeph>ContextIcon()</codeph> selects
+platform multi-bitmap file <filepath>txti.mbm</filepath>. <codeph>ContextIcon()</codeph> selects
the correct icon depending on the entry context. </p> </section>
-<section><title>MTM-specific operations</title> <p>Menu specifications for
+<section id="GUID-3D7F8936-7D6B-450C-BF8F-88E8ACF356F0"><title>MTM-specific operations</title> <p>Menu specifications for
the two MTM-specific operations, Refresh and Export text to file, are provided
in the resource <codeph>r_textud_function_array</codeph>. <codeph>OperationSupportedL()</codeph> determines
whether these operations are appropriate to the entry context. </p> </section>
-<section><title>Context-specific information (Can<Operation> functions)</title> <p>Implementations
+<section id="GUID-8C741A4E-6CB9-498C-89F5-C288010444DD"><title>Context-specific information (Can<Operation> functions)</title> <p>Implementations
of these functions check that that the specific operation is available and
appropriate to the context. </p> </section>
</conbody></concept>
\ No newline at end of file
--- a/Symbian3/SDK/Source/GUID-83E4F989-0B73-5E83-8547-AB3070492CBF.dita Fri Jan 22 18:26:19 2010 +0000
+++ b/Symbian3/SDK/Source/GUID-83E4F989-0B73-5E83-8547-AB3070492CBF.dita Thu Mar 11 15:24:26 2010 +0000
@@ -12,14 +12,13 @@
<task id="GUID-83E4F989-0B73-5E83-8547-AB3070492CBF" xml:lang="en"><title>What
is the Comms Database?</title><shortdesc>The Comms Database contains the information necessary to configure
components in the comms stack. </shortdesc><prolog><metadata><keywords/></metadata></prolog><taskbody>
-<context><p>The Comms Database has a set of parameters used
-to configure communications on Symbian OS. The information stored in the Comms
-Database is used to configure components in the comms stack. Information such
-as connection preferences, account settings and some of the linkage between
-components can be set in the comms stack. The configuration data is stored
-in records in database tables. The data also has data schema to define the
-tables. For more information and a full list of the settings in the Comms Database,
-see the <xref href="GUID-58089281-9DD0-502D-8DFD-831E7BAA931E.dita">Reference</xref></p><p>The
+<context id="GUID-CA4E76D5-2505-48F7-A205-BA42A93FD92B"><p>The Comms Database has a set of parameters used to configure communications
+on Symbian platform. The information stored in the Comms Database
+is used to configure components in the comms stack. Information such as connection
+preferences, account settings and some of the linkage between components can
+be set in the comms stack. The configuration data is stored in records in
+database tables. The data also has data schema to define the tables. For more
+information and a full list of the settings in the Comms Database, see the <xref href="GUID-58089281-9DD0-502D-8DFD-831E7BAA931E.dita">Reference</xref></p><p>The
Comms Database is configured in one of the following ways: </p> <ul>
<li id="GUID-3CFE8D23-F087-54D1-A6F3-83EDD0510609"><p>It is compiled from
a definition file into a binary file to ship in the ROM of a device. For more
--- a/Symbian3/SDK/Source/GUID-85D9878E-4FEF-5E45-9F87-53634CD171E0.dita Fri Jan 22 18:26:19 2010 +0000
+++ b/Symbian3/SDK/Source/GUID-85D9878E-4FEF-5E45-9F87-53634CD171E0.dita Thu Mar 11 15:24:26 2010 +0000
@@ -11,7 +11,7 @@
PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
<concept id="GUID-85D9878E-4FEF-5E45-9F87-53634CD171E0" xml:lang="en"><title>Integrating
a System Server with UPS</title><prolog><metadata><keywords/></metadata></prolog><conbody>
-<section><title>Introduction</title> <p>User Prompt Service (UPS) functionality
+<section id="GUID-78B46051-E035-4798-9A4D-B274D4783164"><title>Introduction</title> <p>User Prompt Service (UPS) functionality
is provided by the server process <filepath>upsserver.exe</filepath>. The
process starts on demand when system servers make calls to the UPS client
library. Only applications with a capability of <codeph>ProtServ</codeph> or
@@ -22,11 +22,11 @@
a system server that invokes the UPS, if a compatible dialog creator is available
and the policies are delivered in an appropriately signed SIS file. They can
also write a policy evaluator, but a default policy evaluator is provided
-by Symbian platform. </p> <p>If the device creators do not specify any policy
-file, the UPS uses the platform security check results to decide whether to
-access requested services. Thus not supplying policy files effectively turns
-UPS off. </p> </section>
-<section><title>Required background</title><p id="GUID-9C6EBADD-175A-5122-90C4-CED8A9855BAB"><b>Configuring
+by the Symbian platform. </p> <p>If the device creators do not
+specify any policy file, the UPS uses the platform security check results
+to decide whether to access requested services. Thus not supplying policy
+files effectively turns UPS off. </p> </section>
+<section id="GUID-718CF580-05FE-4F75-A7D8-4487C35675B6"><title>Required background</title><p id="GUID-9C6EBADD-175A-5122-90C4-CED8A9855BAB"><b>Configuring
the system server</b> </p> <p>For each system server that accesses the UPS,
you need to do the following: </p> <ol id="GUID-D14BDAE1-BD62-530E-B3C4-2FA380BDBDC5">
<li id="GUID-090CE65B-44BF-54CF-8961-69059655C5F5"><p>Create one <codeph>RUpsSession</codeph> per
@@ -60,7 +60,7 @@
check fails these checks may have to be modified. </p> </li>
</ul><p> <b>Note</b>: For an example of how to include the above, see the
example code later in this document. </p></section>
-<section><title>Integration of UPS</title> <p>If the system server uses the <codeph>CPolicyServer</codeph> framework,
+<section id="GUID-3C0A43C1-1CEF-4C0F-83A6-64B3EF73E955"><title>Integration of UPS</title> <p>If the system server uses the <codeph>CPolicyServer</codeph> framework,
there are three candidates for the main integration point. </p> <table id="GUID-BBE389D8-77A0-52BA-910D-368BAC25DCC3">
<tgroup cols="2"><colspec colname="col0"/><colspec colname="col1"/>
<tbody>
--- a/Symbian3/SDK/Source/GUID-9058F379-C495-4B22-B270-FF6A80E450B8.dita Fri Jan 22 18:26:19 2010 +0000
+++ b/Symbian3/SDK/Source/GUID-9058F379-C495-4B22-B270-FF6A80E450B8.dita Thu Mar 11 15:24:26 2010 +0000
@@ -1,4 +1,7 @@
<?xml version="1.0" encoding="utf-8"?>
+<!--Arbortext, Inc., 1988-2004, v.4002-->
+<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN"
+ "concept.dtd">
<!-- Copyright (c) 2007-2010 Nokia Corporation and/or its subsidiary(-ies) All rights reserved. -->
<!-- This component and the accompanying materials are made available under the terms of the License
"Eclipse Public License v1.0" which accompanies this distribution,
@@ -7,78 +10,81 @@
Nokia Corporation - initial contribution.
Contributors:
-->
-<!DOCTYPE concept
- PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
<concept id="GUID-9058F379-C495-4B22-B270-FF6A80E450B8" xml:lang="en"><title>Device
-security mechanisms</title><prolog><metadata><keywords/></metadata></prolog><conbody>
+security mechanisms</title>
+<prolog>
+<metadata>
+<keywords></keywords>
+</metadata>
+</prolog>
+<conbody>
<p>The list below contains some common device security mechanisms.</p>
-<section id="GUID-24AD1095-E039-46B5-A39A-1D814D697DA1"><title>Device protection</title>
-<p>The Symbian platform is not well equipped to protect against a physical
-attack (that is, when an attacker has physical access to the mobile device)
-because access to a device is controlled by the device lock feature, which
-is often not used. Other external methods of protection, like a PIN code or
-Subscriber Identity Module (SIM) locking, tend to provide protection only
-when accessing a cellular network, leaving the information content vulnerable.
+<section id="GUID-24AD1095-E039-46B5-A39A-1D814D697DA1"><title>Device protection</title> <p>The
+Symbian platform is not well equipped to protect against a physical attack
+(that is, when an attacker has physical access to the mobile device) because
+access to a device is controlled by the device lock feature, which is often
+not used. Other external methods of protection, like a PIN code or Subscriber
+Identity Module (SIM) locking, tend to provide protection only when accessing
+a cellular network, leaving the <?Pub Caret?>information content vulnerable.
Without <xref href="GUID-A1ED2377-E196-423F-A5A2-1889C1CC3E05.dita">cryptographic
protection</xref>, it is possible to gain access to the device's information
storage with hardware-based methods (for example, wiretapping connectors and
-direct reading of memory chips).</p>
-</section>
-<section id="GUID-BE16A5D1-B580-4ED6-82D7-16B33B8EEADF"><title>Device authentication</title>
-<p>Sometimes, for security reasons, an application needs to identify the
-mobile device it is running on, for example, to use specific ciphering keys
-or to apply copy protection. Identification can be done by checking the device's
-International Mobile Equipment Identity (IMEI) code, which is unique in each
-device used in cellular networks. To retrieve the IMEI code, you can use,
-for example the <xref href="jar:GUID-35228542-8C95-4849-A73F-2B4F082F0C44.jar!/sdk/doc_source/reference/reference-cpp/ETel_3rd_Party_API/CTelephonyClass.html#%3a%3aCTelephony%3a%3aGetPhoneId%28TRequestStatus%20%26amp%3b%2cTDes8%20%26amp%3b%29const" format="application/java-archive"><codeph>CTelephony::GetPhoneId</codeph></xref> method. For more information,
- see <xref href="http://wiki.forum.nokia.com/index.php" scope="external">Retrieving
-Phone's Manufacturer, Model & IMEI number in Symbian</xref> in the
-Forum Nokia Developer Community Wiki. There are different APIs for retrieving
-the IMEI code in different versions of SDKs. Refer to the SDK API or Symbian
-documentation for the proper method.</p>
-<p>Another way to get information about the running platform and the mobile
-device is to use the <codeph>HAL:Get()</codeph> method defined in <codeph>hal.h</codeph> header
-file. For more information and examples, see <xref href="http://www.forum.nokia.com/info/sw.nokia.com/id/61ae01cb-3c34-47f6-843e-485d4f56409b/S60_Platform_Identification_Codes.html" scope="external">S60 Platform: Identification Codes</xref> on Forum Nokia.</p>
-<p><b>User authentication</b></p>
-<p>When powering on the device, the user is authenticated in the <i>operating
-system level</i> with standard device authentication methods, such as a PIN
-code and security code requests. However, these features can be turned off
-by the user and are easily reset with special hardware. If an application
-needs to authenticate the user, it should be done in the <i>application level</i> by
-implementing a separate user name/password authentication mechanism.</p>
-</section>
-<section id="GUID-962E0183-0CBD-457D-B24C-C0BDB30A58A4"><title>Mobile hardware</title>
-<p>The Symbian platform attempts to ensure the integrity of data even in
-the presence of unreliable communication and a shortage of resources, such
-as memory, power, and storage.</p>
-<p>The user may detach removable storage media at any time, either intentionally
-or unintentionally. The platform has a built-in detach handling mechanism,
-but applications should still be prepared for a sudden loss of storage media
-to prevent data loss or corruption. To check the type of storage media (removable/fixed),
-use the <xref href="jar:GUID-35228542-8C95-4849-A73F-2B4F082F0C44.jar!/sdk/doc_source/reference/reference-cpp/F32_EKA2/RFsClass.html#%3a%3aRFs%3a%3aDrive%28%29" format="application/java-archive"><codeph>RFs::Drive()</codeph></xref> method. </p>
-<p>The device may shut down at any time, either by accident or because
-the battery runs out. Important data stored in nonpermanent memory should
-be written to permanent memory as early as possible. To query the battery
-level, use the <codeph>HAL::Get(EPowerBatteryStatus)</codeph> method. For
-information on how to retrieve system information, see <xref href="http://www.forum.nokia.com/info/sw.nokia.com/id/1bd6bf54-7886-43a5-8335-821bcb603049/S60_Platform_System_Information_Example_v2_0_en.zip.html" scope="external">S60 Platform: System Information Example</xref> on Forum Nokia.</p>
-<p>Even though internal storage is not physically protected, you can secure
-memory cards with password protection. If the locking option is used (method <xref href="jar:GUID-35228542-8C95-4849-A73F-2B4F082F0C44.jar!/sdk/doc_source/reference/reference-cpp/F32_EKA2/RFsClass.html#%3a%3aRFs%3a%3aLockDrive%28%29" format="application/java-archive"><codeph>RFs::LockDrive</codeph></xref>), memory card contents are protected
+direct reading of memory chips).</p> </section>
+<section id="GUID-BE16A5D1-B580-4ED6-82D7-16B33B8EEADF"><title>Device authentication</title> <p>Sometimes,
+for security reasons, an application needs to identify the mobile device it
+is running on, for example, to use specific ciphering keys or to apply copy
+protection. Identification can be done by checking the device's International
+Mobile Equipment Identity (IMEI) code, which is unique in each device used
+in cellular networks. To retrieve the IMEI code, you can use, for example
+the <xref format="application/java-archive" href="jar:GUID-35228542-8C95-4849-A73F-2B4F082F0C44.jar!/sdk/doc_source/reference/reference-cpp/ETel_3rd_Party_API/CTelephonyClass.html#%3a%3aCTelephony%3a%3aGetPhoneId%28TRequestStatus%20%26amp%3b%2cTDes8%20%26amp%3b%29const"
+><codeph>CTelephony::GetPhoneId</codeph></xref> method. There are different
+APIs for retrieving the IMEI code in different versions of SDKs. Refer to
+the SDK API or Symbian documentation for the proper method.</p> <p>Another
+way to get information about the running platform and the mobile device is
+to use the <codeph>HAL:Get()</codeph> method defined in <codeph>hal.h</codeph> header
+file. For more information and examples, see <xref href="http://developer.symbian.org/wiki/index.php/Device_Product_ID,_Platform_ID_and_HAL_information"
+scope="external">Device Product ID, Platform ID and HAL information</xref> at
+the Symbian Foundation.</p> <p><b>User authentication</b></p> <p>When powering
+on the device, the user is authenticated in the <i>operating system level</i> with
+standard device authentication methods, such as a PIN code and security code
+requests. However, these features can be turned off by the user and are easily
+reset with special hardware. If an application needs to authenticate the user,
+it should be done in the <i>application level</i> by implementing a separate
+user name/password authentication mechanism.</p> </section>
+<section id="GUID-962E0183-0CBD-457D-B24C-C0BDB30A58A4"><title>Mobile hardware</title> <p>The
+Symbian platform attempts to ensure the integrity of data even in the presence
+of unreliable communication and a shortage of resources, such as memory, power,
+and storage.</p> <p>The user may detach removable storage media at any time,
+either intentionally or unintentionally. The platform has a built-in detach
+handling mechanism, but applications should still be prepared for a sudden
+loss of storage media to prevent data loss or corruption. To check the type
+of storage media (removable/fixed), use the <xref format="application/java-archive"
+href="jar:GUID-35228542-8C95-4849-A73F-2B4F082F0C44.jar!/sdk/doc_source/reference/reference-cpp/F32_EKA2/RFsClass.html#%3a%3aRFs%3a%3aDrive%28%29"
+><codeph>RFs::Drive()</codeph></xref> method. </p> <p>The device may shut
+down at any time, either by accident or because the battery runs out. Important
+data stored in nonpermanent memory should be written to permanent memory as
+early as possible. To query the battery level, use the <codeph>HAL::Get(EPowerBatteryStatus)</codeph> method.
+For information on how to retrieve system information, see the <xref href="GUID-54042C84-6216-5930-9CBF-BAF635CECD4D.dita">Power
+HAL Handler Tutorial</xref>.</p> <p>Even though internal storage is not physically
+protected, you can secure memory cards with password protection. If the locking
+option is used (method <xref format="application/java-archive" href="jar:GUID-35228542-8C95-4849-A73F-2B4F082F0C44.jar!/sdk/doc_source/reference/reference-cpp/F32_EKA2/RFsClass.html#%3a%3aRFs%3a%3aLockDrive%28%29"
+><codeph>RFs::LockDrive</codeph></xref>), memory card contents are protected
with a password and cannot be read in any other device without it. Password
locking is an extended functionality of the Multimedia card (MMC), and may
-not be compatible with all hardware and software configurations.</p>
-</section>
-<section id="GUID-9058F379-C495-4B22-B270-FF6A80E450B9"><title>Third-party solutions</title>
-<p>A mobile device can be protected with third-party security applications. <i>Antivirus
-software</i> can detect and quarantine any viruses that try to access the
-device, as well as restore infected files. Antivirus software is usually used
-together with <i>firewalls</i> to observe and protect both incoming and outgoing
-data connections. This enables monitoring of important data and prevents it
-from being sent out of the device. Firewall and antivirus software can also
-be part of an <i>intrusion detection system</i> that notifies the user whenever
-a malicious attempt is detected.</p>
-<p>Furthermore, there are applications you can use to encrypt existing
-files, manage passwords, and store information and data securely (in vaults).
-You can even cipher information in applications and connection methods which
-do not initially support ciphering (for example, short message service [SMS]).</p>
-</section>
-</conbody></concept>
\ No newline at end of file
+not be compatible with all hardware and software configurations.</p> </section>
+<section id="GUID-9058F379-C495-4B22-B270-FF6A80E450B9"><title>Third-party
+solutions</title> <p>A mobile device can be protected with third-party security
+applications. <i>Antivirus software</i> can detect and quarantine any viruses
+that try to access the device, as well as restore infected files. Antivirus
+software is usually used together with <i>firewalls</i> to observe and protect
+both incoming and outgoing data connections. This enables monitoring of important
+data and prevents it from being sent out of the device. Firewall and antivirus
+software can also be part of an <i>intrusion detection system</i> that notifies
+the user whenever a malicious attempt is detected.</p> <p>Furthermore, there
+are applications you can use to encrypt existing files, manage passwords,
+and store information and data securely (in vaults). You can even cipher information
+in applications and connection methods which do not initially support ciphering
+(for example, short message service [SMS]).</p> </section>
+</conbody>
+</concept>
+<?Pub *0000006870?>
--- a/Symbian3/SDK/Source/GUID-92966ADC-17CF-5411-A829-1201C182B59F.dita Fri Jan 22 18:26:19 2010 +0000
+++ b/Symbian3/SDK/Source/GUID-92966ADC-17CF-5411-A829-1201C182B59F.dita Thu Mar 11 15:24:26 2010 +0000
@@ -19,7 +19,7 @@
<p>Each example demonstrates a different set of mobile telephony services,
and is stored in a subdirectory of <filepath>ETel3rdPartyExample</filepath>.
These subdirectories are explained in the description section. </p>
-<section><title>Download</title> <p>Click on the following link to download
+<section id="GUID-CD1C71CD-AB0C-4C39-93CA-50E57E4A80FE"><title>Download</title> <p>Click on the following link to download
the example: <xref href="guid-6013a680-57f9-415b-8851-c4fa63356636/zips/guid-7bdecae0-8d0b-407e-b387-2543550d99e7.zip" scope="external"> ETel3rdParty.zip</xref></p><p>Click <xref href="guid-6013a680-57f9-415b-8851-c4fa63356636/guid-7bdecae0-8d0b-407e-b387-2543550d99e7.html" scope="peer">browse</xref> to view the example code. </p> </section>
<section id="GUID-BF0DBC82-2432-54B9-9A5F-78900F3FDA6C"><title>Description</title> <p><b>AutoDTMFDialler</b> </p> <p>This
example performs the following operations: </p> <ul>
@@ -94,7 +94,7 @@
<li id="GUID-D2A45950-D676-54F8-A365-AAC53160CE86"><p>call identity services
using the <xref href="GUID-97D402C8-B4B7-385A-92B3-D3FCC0CA575A.dita#GUID-97D402C8-B4B7-385A-92B3-D3FCC0CA575A/GUID-768817E6-D985-3C18-AD12-448D192B460F"><apiname>CTelephony::GetIdentityServiceStatus()</apiname></xref> function. </p> </li>
</ul> </section>
-<section><title>Class summary</title> <p>The principal class used in this
+<section id="GUID-A4801049-45DC-4705-B43B-9F2CD37E130E"><title>Class summary</title> <p>The principal class used in this
example is <xref href="GUID-97D402C8-B4B7-385A-92B3-D3FCC0CA575A.dita"><apiname>CTelephony</apiname></xref>. </p> </section>
<section id="GUID-F065BEFB-810D-5C25-97FD-8D953515D249"><title>Configuring
the simulator TSY</title> <p>To run the application you must configure the
@@ -112,7 +112,7 @@
</ol> </section>
<section id="GUID-67006F52-C18C-576E-B645-20AE6CCD61C4"><title>Building and
running</title> <p> <xref href="GUID-3100800B-B2F7-50EF-BD4C-3C345ECCB2A5.dita">The
-Symbian OS build process</xref> describes how to build an application. </p> <p>The <codeph>ETel3rdPartyExample</codeph> builds
+Symbian build process</xref> describes how to build an application. </p> <p>The <codeph>ETel3rdPartyExample</codeph> builds
the following executables in the standard location (<filepath>\epoc32\release\winscw\<build_variant></filepath> for
CodeWarrior): </p> <ul>
<li id="GUID-443AF336-E3B4-507E-9A13-A6AB7912B79F"><p> <filepath> phoneid.exe</filepath> </p> </li>
--- a/Symbian3/SDK/Source/GUID-95E557D0-9A84-514C-B51E-0556F26B3C98.dita Fri Jan 22 18:26:19 2010 +0000
+++ b/Symbian3/SDK/Source/GUID-95E557D0-9A84-514C-B51E-0556F26B3C98.dita Thu Mar 11 15:24:26 2010 +0000
@@ -37,9 +37,9 @@
the application compresses the <filepath>error.wav</filepath> file to a <filepath>.gz</filepath> file.
The GZip file being created is represented by an object of the <xref href="GUID-417AB4E0-FF07-34CB-A4A8-CEF31C48A162.dita"><apiname>CEZFileToGZip</apiname></xref> class
and the <filepath>.wav</filepath> file is compressed using the <xref href="GUID-417AB4E0-FF07-34CB-A4A8-CEF31C48A162.dita#GUID-417AB4E0-FF07-34CB-A4A8-CEF31C48A162/GUID-4E51D7C5-C624-3F27-A5CD-01E92F96F72B"><apiname>CEZFileToGZip::DeflateL()</apiname></xref> method. </p> </section>
-<section><title>Class Summary</title><p><xref href="GUID-79C613E8-35F8-319B-BE8B-1411CBE5AF00.dita"><apiname>CZipFile</apiname></xref></p><p><xref href="GUID-02A8BC62-D653-39A3-BE0C-92A5F3F43E85.dita"><apiname>CZipFileMember</apiname></xref></p><p><xref href="GUID-D458AE6A-EC64-3882-BCEA-A44A43DAA99A.dita"><apiname>CZipFileMemberIterator</apiname></xref></p><p><xref href="GUID-62F9728B-9C39-3496-BAEB-6E1456E6F197.dita"><apiname>RZipFileMemberReaderStream</apiname></xref></p><p><xref href="GUID-8DE05785-D058-3855-A11F-7132EB4DE078.dita"><apiname>CEZGZipToFile</apiname></xref></p><p><xref href="GUID-417AB4E0-FF07-34CB-A4A8-CEF31C48A162.dita"><apiname>CEZFileToGZip</apiname></xref></p></section>
-<section id="GUID-986B5547-0C87-57E1-893C-21444F82BE45"><title>Build</title> <p>The <xref href="GUID-3100800B-B2F7-50EF-BD4C-3C345ECCB2A5.dita">Symbian OS build process</xref> describes
-how to build an application. </p> <p>The <codeph>EzlibExample</codeph> builds
+<section id="GUID-922B4740-7F7D-4A12-B92A-FE9720E2C7CD"><title>Class Summary</title><p><xref href="GUID-79C613E8-35F8-319B-BE8B-1411CBE5AF00.dita"><apiname>CZipFile</apiname></xref></p><p><xref href="GUID-02A8BC62-D653-39A3-BE0C-92A5F3F43E85.dita"><apiname>CZipFileMember</apiname></xref></p><p><xref href="GUID-D458AE6A-EC64-3882-BCEA-A44A43DAA99A.dita"><apiname>CZipFileMemberIterator</apiname></xref></p><p><xref href="GUID-62F9728B-9C39-3496-BAEB-6E1456E6F197.dita"><apiname>RZipFileMemberReaderStream</apiname></xref></p><p><xref href="GUID-8DE05785-D058-3855-A11F-7132EB4DE078.dita"><apiname>CEZGZipToFile</apiname></xref></p><p><xref href="GUID-417AB4E0-FF07-34CB-A4A8-CEF31C48A162.dita"><apiname>CEZFileToGZip</apiname></xref></p></section>
+<section id="GUID-986B5547-0C87-57E1-893C-21444F82BE45"><title>Build</title> <p>The <xref href="GUID-3100800B-B2F7-50EF-BD4C-3C345ECCB2A5.dita">Symbian build
+process</xref> describes how to build an application. </p> <p>The <codeph>EzlibExample</codeph> builds
an executable file called <filepath>ezlibexample.exe</filepath> in the standard
location (<filepath>\epoc32\release\winscw\</filepath> <<varname>build_variant</varname> >
for CodeWarrior). After launching the executable, depending on the emulator
--- a/Symbian3/SDK/Source/GUID-9D278187-8B5E-581D-9869-EE8861048F93.dita Fri Jan 22 18:26:19 2010 +0000
+++ b/Symbian3/SDK/Source/GUID-9D278187-8B5E-581D-9869-EE8861048F93.dita Thu Mar 11 15:24:26 2010 +0000
@@ -19,16 +19,16 @@
ascertain the address within the DLL of the functions or variables. </p> <p>Alternatively
a program can dynamically load a DLL into memory during execution, locate
the address of a symbol, use it and then unload the DLL. Traditionally and
-for greater memory efficiency, Symbian platform links by ordinal, whereas
-Unix-like operating systems link by name. The following sections provide example
-code to illustrate how the DLL loader works with each operating system. </p><p>The
-Symbian platform v9.3 kernel supports all functionalities of P.I.P.S. libraries
-- referred to as "P.I.P.S.- ready". Pre v9.3 the kernel only supports the
-Symbian platform- standard ordinal lookup in DLLs; it does not support symbolic
-lookup. Thus the function <codeph>dlsym()</codeph> cannot be used with a symbolic
-name. To overcome this restriction, pass the function's ordinal number as
-symbol parameter refer the library's list of exports (the DEF file) for the
-function's ordinal number. For example, instead of: <codeph>dlsym(&handle,
+for greater memory efficiency, the Symbian platform links by
+ordinal, whereas Unix-like operating systems link by name. The following sections
+provide example code to illustrate how the DLL loader works with each operating
+system. </p><p>The Symbian platform v9.3 kernel supports all functionalities
+of P.I.P.S. libraries - referred to as "P.I.P.S.- ready". Pre v9.3 the kernel
+only supports the Symbian platform- standard ordinal lookup in DLLs; it does
+not support symbolic lookup. Thus the function <codeph>dlsym()</codeph> cannot
+be used with a symbolic name. To overcome this restriction, pass the function's
+ordinal number as symbol parameter refer the library's list of exports (the
+DEF file) for the function's ordinal number. For example, instead of: <codeph>dlsym(&handle,
"foo")</codeph> use <codeph>dlsym (&handle, "3")</codeph> where the function <codeph>foo()</codeph> has
ordinal 3.</p> </section>
<section id="GUID-CCE3F3DC-307A-41F2-BAB4-523834C12E93"><title>Using shared
@@ -80,10 +80,11 @@
{
printf("Result is : %d\n", a + b);
}</codeblock></section>
-<section id="GUID-7C649A95-3F73-454B-AAD4-80889D6B34E3"><title>DLLs on Symbian
-platform(prior to v9.3)</title><p>Symbian platform programs uses the function
-or variable's ordinal position within a DLL to link with DLLs. For example,
-implementing a shared DLL on Symbian platform could look like this:</p><codeblock xml:space="preserve">EXPORT_C void printSum(int a, int b)
+<section id="GUID-7C649A95-3F73-454B-AAD4-80889D6B34E3"><title>DLLs on the
+Symbian platform(prior to v9.3)</title><p>Symbian platform programs uses the
+function or variable's ordinal position within a DLL to link with DLLs. For
+example, implementing a shared DLL on the Symbian platform could look like
+this:</p><codeblock xml:space="preserve">EXPORT_C void printSum(int a, int b)
{
printf("Result is : %d\n", a + b);
}</codeblock><p>Compiling this will generate a <filepath>.def</filepath> file,
@@ -138,11 +139,11 @@
mode parameter in the example, it will behave just as <codeph>RTLD_NOW</codeph>.
Also note that there is no facility to call any library constructor and destructor
functions using <codeph>__attribute((constructor))</codeph> or <codeph>__attribute((destructor))</codeph>. </p></section>
-<section id="GUID-DEF804DF-CECC-4739-9ACD-24F46A945F6E"><title>DLLs on Symbian
-platform (v9.3 onwards)</title><p>P.I.P.S. provides APIs from libdl to support
-dynamic lookup by name, which is used in Unix-like platforms, instead of the
-native Symbian platform lookup by ordinal mechanism. Lookup by name is possible
-thanks to the new libdl, which in turn uses the existing <ph>RLibrary</ph> functions
+<section id="GUID-DEF804DF-CECC-4739-9ACD-24F46A945F6E"><title>DLLs on the
+Symbian platform (v9.3 onwards)</title><p>P.I.P.S. provides APIs from libdl
+to support dynamic lookup by name, which is used in Unix-like platforms, instead
+of the native Symbian platform lookup by ordinal mechanism. Lookup by name
+is possible thanks to the new libdl, which in turn uses the existing <ph>RLibrary</ph> functions
to load and unload DLLs. </p><p>A symbol name lookup version of the dlsym()
function is provided, similar to UNIX®, which does not need any special treatment
(the example shown in the <b>Using Shared libraries in a Unix-like environment</b> section
--- a/Symbian3/SDK/Source/GUID-A80ED7B2-4A58-570A-A671-4F4B1BB9FDAF.dita Fri Jan 22 18:26:19 2010 +0000
+++ b/Symbian3/SDK/Source/GUID-A80ED7B2-4A58-570A-A671-4F4B1BB9FDAF.dita Thu Mar 11 15:24:26 2010 +0000
@@ -9,4 +9,9 @@
-->
<!DOCTYPE concept
PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
-<concept id="GUID-A80ED7B2-4A58-570A-A671-4F4B1BB9FDAF" xml:lang="en"><title>Concepts</title><prolog><metadata><keywords/></metadata></prolog><conbody><p>This section describes the concepts that Symbian OS uses in its implementation of sockets. The section includes a description of the architecture and the Sockets Server API. </p> <p> </p> </conbody></concept>
\ No newline at end of file
+<concept id="GUID-A80ED7B2-4A58-570A-A671-4F4B1BB9FDAF" xml:lang="en"><title>Concepts</title><prolog><metadata><keywords/></metadata></prolog><conbody>
+<p>This section describes the concepts that Symbian platform
+uses in its implementation of sockets. The section includes a description
+of the architecture and the Sockets Server API. </p>
+<p> </p>
+</conbody></concept>
\ No newline at end of file
--- a/Symbian3/SDK/Source/GUID-A8130D83-E684-5B6C-BDFE-EB6EE3CD49E8.dita Fri Jan 22 18:26:19 2010 +0000
+++ b/Symbian3/SDK/Source/GUID-A8130D83-E684-5B6C-BDFE-EB6EE3CD49E8.dita Thu Mar 11 15:24:26 2010 +0000
@@ -1,4 +1,7 @@
<?xml version="1.0" encoding="utf-8"?>
+<!--Arbortext, Inc., 1988-2004, v.4002-->
+<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN"
+ "concept.dtd">
<!-- Copyright (c) 2007-2010 Nokia Corporation and/or its subsidiary(-ies) All rights reserved. -->
<!-- This component and the accompanying materials are made available under the terms of the License
"Eclipse Public License v1.0" which accompanies this distribution,
@@ -7,13 +10,18 @@
Nokia Corporation - initial contribution.
Contributors:
-->
-<!DOCTYPE concept
- PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
<concept id="GUID-A8130D83-E684-5B6C-BDFE-EB6EE3CD49E8" xml:lang="en"><title>Writing
-a UPS Dialog Creator</title><prolog><metadata><keywords/></metadata></prolog><conbody>
-<section><title>Introduction</title> <p>Dialog creators are EComplug-ins that
-device creators can write to generate the dialogs containing prompts for phone
-users. </p> <p>The plug-in has an API that consists of two asynchronous functions: </p> <ul>
+a UPS Dialog Creator</title>
+<prolog>
+<metadata>
+<keywords></keywords>
+</metadata>
+</prolog>
+<conbody>
+<section><title>Introduction</title> <p>Dialog creators are ECom <?Pub Caret?>plug-ins
+that device creators can write to generate the dialogs containing prompts
+for phone users. </p> <p>The plug-in has an API that consists of two asynchronous
+functions: </p> <ul>
<li id="GUID-96CBCE79-4F5D-5F87-AC6B-C366346447AB"><p>The <codeph>PrepareDialog()</codeph> function.
This function is called first by the UPS server. It enables the dialog creator
to query other system servers such as AppArc or the SIS registry to retrieve
@@ -27,7 +35,8 @@
</ul> <p>The UPS displays only one prompt at a time so it is possible for
there to be a delay between calling the function to prepare the dialog and
the function to display the dialog. It is also possible for other dialogs
-to be displayed between the dialog being prepared and its being displayed. </p> <p>Both <codeph>PrepareDialog()</codeph> and <codeph>DisplayDialog()</codeph> are asynchronous and must support cancellation through <codeph>CActive::Cancel</codeph>.
+to be displayed between the dialog being prepared and its being displayed. </p> <p>Both <codeph>PrepareDialog()</codeph> and <codeph>DisplayDialog()</codeph
+> are asynchronous and must support cancellation through <codeph>CActive::Cancel</codeph>.
If either function is cancelled, the dialog creator instance is destroyed
without calling further methods. </p> <p>The work split between <codeph>PrepareDialog()</codeph> and <codeph>DisplayDialog()</codeph> described
above is a recommendation, and some of the functionality could be implemented
@@ -48,7 +57,8 @@
the dialog</b> </p> <p>The parameters to <codeph>PrepareDialog()</codeph> are
mostly <codeph>const</codeph> pointers and references to the data that has
already been generated by the UPS or policy evaluator. </p> <p>The following
-table describes the parameters for the <codeph>PrepareDialog()</codeph> function: </p> <table id="GUID-6D139216-B6A8-55A1-8D9B-C15134198198">
+table describes the parameters for the <codeph>PrepareDialog()</codeph> function: </p> <table
+id="GUID-6D139216-B6A8-55A1-8D9B-C15134198198">
<tgroup cols="2"><colspec colname="col0"/><colspec colname="col1"/>
<thead>
<row>
@@ -89,7 +99,7 @@
</row>
</tbody>
</tgroup>
-</table> <p><note/> The UPS does not allow any responses to be returned
+</table> <p><note></note> The UPS does not allow any responses to be returned
to the system server except those defined in the UPS policy file. If the dialog
creator returns an option that was not specified in the policy, the request
is rejected and <codeph>EUpsDecNo</codeph> is returned. </p><p>Your implementation
@@ -118,28 +128,16 @@
is called through a <codeph>switch</codeph> statement, which can be seen in
the full code sample at the end of this section: </p> </section>
<section><title>Example</title> <p>The following code shows an example of
-a full implementation of the dialog creator file: </p> <codeblock id="GUID-314673F2-BBA0-56C0-A76D-07862BB4592F" xml:space="preserve">// Copyright (c) 2006-2009 Nokia Corporation and/or its subsidiary(-ies).
-// All rights reserved.
-// This component and the accompanying materials are made available
-// under the terms of the License "Symbian Foundation License v1.0"
-// which accompanies this distribution, and is available
-// at the URL "http://www.symbianfoundation.org/legal/sfl-v10.html".
-//
-// Initial Contributors:
-// Nokia Corporation - initial contribution.
-
-// refdialogcreator.cpp
-
-
-#include "refdialogcreator.h"
-#include <ecom/implementationproxy.h>
-#include <apaid.h>
-#include <apgcli.h>
-#include <ups/promptrequest.h>
-#include <swi/sisregistrypackage.h>
-#include <swi/sisregistrysession.h>
-#include <scs/nullstream.h>
-#include <s32mem.h>
+a full implementation of the dialog creator file: </p> <codeblock id="GUID-314673F2-BBA0-56C0-A76D-07862BB4592F"
+xml:space="preserve">#include "refdialogcreator.h"
+#include <ecom/implementationproxy.h>
+#include <apaid.h>
+#include <apgcli.h>
+#include <ups/promptrequest.h>
+#include <swi/sisregistrypackage.h>
+#include <swi/sisregistrysession.h>
+#include <scs/nullstream.h>
+#include <s32mem.h>
static const TUint KRefDialogCreatorImplementationId = 0x10283694;
@@ -154,7 +152,7 @@
{
CRefDialogCreator* self = new (ELeave)CRefDialogCreator();
CleanupStack::PushL(self);
- self->ConstructL();
+ self->ConstructL();
CleanupStack::Pop(self);
return self;
}
@@ -249,31 +247,31 @@
// Only one state at the moment but more should be
// added for long running operators e.g. querying the SIS registry
// or resolving the client entity.
- ResolveClientNameL(iRequest->ClientSid());
+ ResolveClientNameL(iRequest->ClientSid());
// Get the vendor name for the client process
- ResolveVendorNameL(iRequest->ClientVid());
+ ResolveVendorNameL(iRequest->ClientVid());
// Server / Service localized names generated in notifier plug-in.
- iPromptData->iServerSid = iRequest->ServerSid();
- iPromptData->iServiceId = iRequest->ServiceId();
+ iPromptData->iServerSid = iRequest->ServerSid();
+ iPromptData->iServiceId = iRequest->ServiceId();
// Different dialog text is displayed depending on whether the client application
// is signed.
// N.B. Protected SID is assumed to be signed or included at ROM build.
- if (iRequest->IsClientSidProtected()) iPromptData->iFlags |= ETrustedClient;
+ if (iRequest->IsClientSidProtected()) iPromptData->iFlags |= ETrustedClient;
// Use the options specified by the policy
- iPromptData->iOptions = iPolicy->Options();
+ iPromptData->iOptions = iPolicy->Options();
// Add the descriptions of the fingerprints. This could be used
// to allow the user to grant access to all destinations
// or a single destination.
- TInt count = iFingerprints->Count();
+ TInt count = iFingerprints->Count();
for (TInt i = 0; i < count; ++i)
{
- HBufC* description = (*iFingerprints)[i]->Description().AllocLC();
- iPromptData->iDescriptions.AppendL(description);
+ HBufC* description = (*iFingerprints)[i]->Description().AllocLC();
+ iPromptData->iDescriptions.AppendL(description);
CleanupStack::Pop(description);
}
@@ -316,7 +314,7 @@
//
// In this implementation a copy of the original fingerprint is returned. However,
// it is permitted to return a different fingerprint e.g. a modifier description.
- if (iPromptResult.iDestination >= 0 && iPromptResult.iDestination < iFingerprints->Count())
+ if (iPromptResult.iDestination >= 0 && iPromptResult.iDestination < iFingerprints->Count())
{
*iFingerprint = (*iFingerprints)[iPromptResult.iDestination];
}
@@ -333,14 +331,14 @@
void CRefDialogCreator::ResolveVendorNameL(const TVendorId& aVid)
/**
Looks up the localized vendor name for the client process and writes
-this to iPromptData->iVendorName.
+this to iPromptData->iVendorName.
Typically, this would be resolved from the SIS registry or a lookup table.
@param aVid The vendor id of the client process.
*/
{
- if (iPromptData->iVendorName.Length() != 0)
+ if (iPromptData->iVendorName.Length() != 0)
{
// already obtained vendor name from SIS registry
return;
@@ -349,12 +347,12 @@
if (aVid.iId == 0x70000001)
{
_LIT(KSymbian, "Symbian Foundation");
- iPromptData->iVendorName.Create(KSymbian);
+ iPromptData->iVendorName.Create(KSymbian);
}
else
{
_LIT(KUnknown, "Unknown vendor");
- iPromptData->iVendorName.Create(KUnknown);
+ iPromptData->iVendorName.Create(KUnknown);
}
}
@@ -389,9 +387,9 @@
if (! found)
{
RProcess clientProcess;
- User::LeaveIfError(clientProcess.Open(iRequest->ClientProcessId()));
+ User::LeaveIfError(clientProcess.Open(iRequest->ClientProcessId()));
CleanupClosePushL(clientProcess);
- iPromptData->iClientName.Create(clientProcess.FileName());
+ iPromptData->iClientName.Create(clientProcess.FileName());
CleanupStack::PopAndDestroy(&clientProcess);
}
}
@@ -417,8 +415,8 @@
err = apa.GetAppInfo(*info, TUid::Uid(aSid));
if (err == KErrNone)
{
- iPromptData->iClientName.Close();
- iPromptData->iClientName.Create(info->iCaption);
+ iPromptData->iClientName.Close();
+ iPromptData->iClientName.Create(info->iCaption);
found = ETrue;
}
else if (err != KErrNotFound)
@@ -454,8 +452,8 @@
TRAPD(err, p = r.SidToPackageL(TUid::Uid(aSid.iId)));
if (err == KErrNone)
{
- iPromptData->iClientName.Create(p->Name());
- iPromptData->iVendorName.Create(p->Vendor());
+ iPromptData->iClientName.Create(p->Name());
+ iPromptData->iVendorName.Create(p->Vendor());
found = ETrue;
delete p;
}
@@ -466,7 +464,7 @@
// From CDialogCreator
void CRefDialogCreator::PrepareDialog(
const UserPromptService::CPromptRequest& aRequest, const CPolicy& aPolicy,
- const RPointerArray<CFingerprint>& aFingerprints, const CClientEntity* aClientEntity,
+ const RPointerArray<CFingerprint>& aFingerprints, const CClientEntity* aClientEntity,
const TAny* aEvalPrivateData, TRequestStatus& aStatus)
{
aStatus = KRequestPending;
@@ -506,4 +504,6 @@
User::RequestComplete(status, KErrNone);
}
</codeblock> </section>
-</conbody></concept>
\ No newline at end of file
+</conbody>
+</concept>
+<?Pub *0000019622?>
--- a/Symbian3/SDK/Source/GUID-A837D8F6-B9D3-5119-8C63-51772B388999.dita Fri Jan 22 18:26:19 2010 +0000
+++ b/Symbian3/SDK/Source/GUID-A837D8F6-B9D3-5119-8C63-51772B388999.dita Thu Mar 11 15:24:26 2010 +0000
@@ -9,7 +9,7 @@
-->
<!DOCTYPE concept
PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
-<concept id="GUID-A837D8F6-B9D3-5119-8C63-51772B388999" xml:lang="en"><title>Symbian Platform
-Tools And Utilities</title><prolog><metadata><keywords/></metadata></prolog><conbody>
+<concept id="GUID-A837D8F6-B9D3-5119-8C63-51772B388999" xml:lang="en"><title>Tools and
+Utilities</title><prolog><metadata><keywords/></metadata></prolog><conbody>
<p>The guide describe the tools for developing and building programs. </p>
</conbody></concept>
\ No newline at end of file
--- a/Symbian3/SDK/Source/GUID-ACDED56F-38FE-491D-B019-BE2C53A75D28.dita Fri Jan 22 18:26:19 2010 +0000
+++ b/Symbian3/SDK/Source/GUID-ACDED56F-38FE-491D-B019-BE2C53A75D28.dita Thu Mar 11 15:24:26 2010 +0000
@@ -45,6 +45,6 @@
registration resource files should be installed in the <parmname>\resource\plugins</parmname> subfolder.</p>
</li>
</ul>
-<p>For more information, see <xref href="jar:GUID-35228542-8C95-4849-A73F-2B4F082F0C44.jar!/sdk/doc_source/guide/Base-subsystem-guide/f32/FileServerClientSide/FileServerClientSideGuide5/ApplicationArchitecture.guide.html" format="application/java-archive">File
+<p>For more information, see <xref href="GUID-54E62386-E4DB-55C3-BA9A-FFB7BFE6703E.dita">File
locations</xref>.</p>
</conbody></concept>
\ No newline at end of file
--- a/Symbian3/SDK/Source/GUID-AED57265-6106-4217-ADE6-1327CA3FDE7E.dita Fri Jan 22 18:26:19 2010 +0000
+++ b/Symbian3/SDK/Source/GUID-AED57265-6106-4217-ADE6-1327CA3FDE7E.dita Thu Mar 11 15:24:26 2010 +0000
@@ -12,8 +12,8 @@
<concept id="GUID-AED57265-6106-4217-ADE6-1327CA3FDE7E" xml:lang="en"><title>PKG
file format to support simple installation</title><abstract><p>The simplest installation file supports a single language version
only and requires no special capabilities. It installs a fixed list of files
-to the Symbian device and is self-signed. The PKG file must contain the following
-elements: </p> <ul>
+to the Symbian device and is self-signed. The PKG file must contain
+the following elements: </p> <ul>
<li id="GUID-9B77CB46-60E1-56CE-8232-BD279E17335F"><p><xref href="GUID-0BE71FC3-4759-50FC-A74F-C3DD42C9FCED.dita">Languages</xref> </p> </li>
<li id="GUID-D049FACA-2B95-5705-893F-A4E048112815"><p><xref href="GUID-7664A4D4-C24B-5225-9E0B-7A021DA6A3AF.dita">Vendor
Names</xref> </p> </li>
@@ -21,7 +21,7 @@
<li id="GUID-28A5B022-61FF-59A2-B003-4F67E8A5D6E7"><p><xref href="GUID-FF39192E-9C93-593F-8F47-DB18DB876F6F.dita">Installation
Files</xref> </p> </li>
</ul> </abstract><prolog><metadata><keywords/></metadata></prolog><conbody>
-<section><title>Example</title><p>The following PKG file is provided in <filepath>examples\HelloWorld\</filepath>.
+<section id="GUID-072DCCAD-86E8-491C-B29C-3F776AEF9456"><title>Example</title><p>The following PKG file is provided in <filepath>examples\HelloWorld\</filepath>.
The associated files are built from the source code located in the same directory.
See <xref href="GUID-F64B88E0-49DA-5563-896E-29BAB8A244C9.dita">here</xref> for
information. </p> <codeblock id="GUID-2541A514-BAA9-54E6-8927-2F0044F28D5B" xml:space="preserve">; List of languages supported
@@ -35,7 +35,7 @@
; Package header format: Package Name, UID, Major version, Minor Version, Build Number
#{"Minimal application"},(0xE8000091),1,0,0
-; Files to install for the minimal application: "Files located on PC" - "Target location on Symbian device"
+; Files to install for the minimal application: "Files located on PC" - "Target location on the Symbian device"
"HelloWorld.exe"-"!:\sys\bin\HelloWorld.exe"
"HelloWorld.rsc"-"!:\resource\apps\HelloWorld.rsc"
"HelloWorld.mbm" - "!:\resource\apps\HelloWorld.mbm"
--- a/Symbian3/SDK/Source/GUID-AF07AD54-86F1-5DB7-80FF-633A559DA4BD.dita Fri Jan 22 18:26:19 2010 +0000
+++ b/Symbian3/SDK/Source/GUID-AF07AD54-86F1-5DB7-80FF-633A559DA4BD.dita Thu Mar 11 15:24:26 2010 +0000
@@ -29,10 +29,10 @@
<li><p><xref href="GUID-545DA961-217E-49CA-A90E-7A41E2C03A99.dita">Forking without <codeph>exec()</codeph></xref></p></li>
<li><p><xref href="GUID-B58D282E-E6EC-4AE1-96DB-30A5FB850563.dita"><codeph>exec()</codeph> without
forking using <apiname>posix_spawn()</apiname></xref></p></li>
-</ul> <p><b>Omission of fork()</b> </p> <p>A Unix-like kernel
-is designed with the two stage process creation in mind. On Symbian platform
-(and Microsoft Windows®) the kernel was designed to create a process, which
-runs a single executable, in a single step. </p> <p>P.I.P.S. does not implement
+</ul> <p><b>Omission of fork()</b> </p> <p>A Unix-like kernel is designed
+with the two stage process creation in mind. On the Symbian platform (and
+Microsoft Windows®), the kernel was designed to create a process, which runs
+a single executable, in a single step. </p> <p>P.I.P.S. does not implement
the <codeph>fork()</codeph> operation because this would require an entirely
new way of dealing with processes in the kernel and memory model. For example,
duplicating the address space of an existing process was not something that
@@ -44,13 +44,13 @@
the standard way to load a process image into memory. Only the initialisation
process is loaded directly into a new address space (special case code in
the kernel), all other processes are loaded into an existing address space
-which was initially created by forking. </p> <p>On Symbian platform, the only
-way to load a process image into memory is using the loader. It assumes that
-the image is being loaded as a new process - one that owns no resources, has
-no open handles and so on. The change to the loader and any associated kernel
-changes, to support the <codeph>exec()</codeph> function were deemed to be
-too risky. </p> <p><b>Generic IPC</b> </p> <p>P.I.P.S. supports two types
-of Inter-Process Communication (IPC) between processes or threads: </p> <ul>
+which was initially created by forking. </p> <p>On the Symbian
+platform, the only way to load a process image into memory is using the loader.
+It assumes that the image is being loaded as a new process - one that owns
+no resources, has no open handles and so on. The change to the loader and
+any associated kernel changes, to support the <codeph>exec()</codeph> function
+were deemed to be too risky. </p> <p><b>Generic IPC</b> </p> <p>P.I.P.S. supports
+two types of Inter-Process Communication (IPC) between processes or threads: </p> <ul>
<li><p> <b>Pipes (named and unnamed):</b> Unnamed pipes are created using <xref href="GUID-EC7F85FF-FD4E-324C-8D01-EF6F7E7A79FE.dita"><apiname>pipe()</apiname></xref> and
named pipes are created using <xref href="GUID-F4749DAA-1B29-3D1D-A3AA-0D52B851E501.dita"><apiname>mkfifo()</apiname></xref>. Pipe-based communication
is also possible between a parent and a child process when the child is created
--- a/Symbian3/SDK/Source/GUID-AF2CE612-F12E-5A18-81A5-C303992D2D46.dita Fri Jan 22 18:26:19 2010 +0000
+++ b/Symbian3/SDK/Source/GUID-AF2CE612-F12E-5A18-81A5-C303992D2D46.dita Thu Mar 11 15:24:26 2010 +0000
@@ -12,8 +12,8 @@
<concept id="GUID-AF2CE612-F12E-5A18-81A5-C303992D2D46" xml:lang="en"><title>Possible
Problems</title><prolog><metadata><keywords/></metadata></prolog><conbody>
<p>This section describes the possible problems that you may encounter when
-you develop applications or libraries on Symbian platform based on Standard
-C++. These problems can occur in the following scenarios: </p>
+you develop applications or libraries on the Symbian platform
+based on Standard C++. These problems can occur in the following scenarios: </p>
<ul>
<li id="GUID-A3F0DCD7-CA38-5405-B01D-1E3B3F75B67D"><p><xref href="GUID-AF2CE612-F12E-5A18-81A5-C303992D2D46.dita#GUID-AF2CE612-F12E-5A18-81A5-C303992D2D46/GUID-39350E32-26C2-5440-B221-10EE693CCF18">Use of operator new</xref> </p> </li>
<li id="GUID-9B185254-36B9-58F7-888D-8198EAD77769"><p><xref href="GUID-AF2CE612-F12E-5A18-81A5-C303992D2D46.dita#GUID-AF2CE612-F12E-5A18-81A5-C303992D2D46/GUID-A85386B3-3E37-5303-8FBF-211551D5CB71">Use of one definition rule</xref> </p> </li>
@@ -44,8 +44,8 @@
says that there must be only one definition of a symbol in a program. But
to be able to maintain a single definition in a program, symbol pre-emption
must be possible. This functionality is not supported on the DLL model of
-Symbian platform. </p> <p><b>Example</b> </p> <p>The following example illustrates
-the problem with the use of one definition rule: </p> <codeblock id="GUID-FB9FBAAD-8CB8-5EAB-BA25-18A92822CF8E" xml:space="preserve">//MySingleton.h
+the Symbian platform. </p> <p><b>Example</b> </p> <p>The following example
+illustrates the problem with the use of one definition rule: </p> <codeblock id="GUID-FB9FBAAD-8CB8-5EAB-BA25-18A92822CF8E" xml:space="preserve">//MySingleton.h
template <class T>
class MySingleton
{
@@ -85,11 +85,11 @@
{
printf("%d\n", Baz());
}</codeblock> <p>This example must have displayed the output as <b>1,
-2</b>. But on Symbian platform, it displays <b>1,1</b>. </p> <p>The problem
-here is Symbian platform's DLL model. In particular Symbian platform does
-not support symbol pre-emption. In Symbian platform <codeph>static T * aT</codeph> gets
-allocated in each DLL in which <codeph>X::GetInstance</codeph> is invoked.
-Here the problem arises because Symbian platform cannot redirect the references
+2</b>. But on the Symbian platform, it displays <b>1,1</b>. </p> <p>The problem
+here is, the Symbian platform's DLL model. In particular, the Symbian platform
+does not support symbol pre-emption. <codeph>static T * aT</codeph> gets allocated
+in each DLL in which <codeph>X::GetInstance</codeph> is invoked. Here the
+problem arises because the Symbian platform cannot redirect the references
in distinct DLLs to a single unique location as required by the ODR. </p> </section>
<section id="GUID-6CE49D59-46BB-5145-B346-6FD3EA8BC011"><title>Standard C++
calling Symbian C++ functions</title> <p>The following example illustrates
@@ -100,7 +100,7 @@
<li id="GUID-CC89E765-AF86-5300-BB76-F84DCF9E3910"><p>one which expects standard
C++ semantics (<codeph>CppCallee</codeph>), and </p> </li>
<li id="GUID-2E9D21A4-8FD3-5DC9-A264-7E7FEA05F4A9"><p>another which expects
-Symbian platform semantics (<codeph>GetAK1LC</codeph>). </p> </li>
+the Symbian platform semantics (<codeph>GetAK1LC</codeph>). </p> </li>
</ul> <p> <codeph>SymbianCallerLC</codeph> itself belongs to the Symbian C++
world since it participates in the LC convention (it imposes a contract on
its caller with respect to the object that it returns). </p> <codeblock id="GUID-D88FA0A6-1107-570D-B79A-30EA10E4AB0C" xml:space="preserve">K1 * SymbianCallerLC()
@@ -156,7 +156,7 @@
<link href="GUID-F7FEB759-E64D-5B6D-9017-C5E982E4FC16.dita"><linktext>Standard
C++ Library Overview</linktext></link>
<link href="GUID-2CCD1748-9EDE-5383-9941-A3051E06F3E2.dita"><linktext>Standard
-C++ Support on Symbian Platform</linktext></link>
+C++ Support on the Symbian Platform</linktext></link>
<link href="GUID-1ACD01D1-2055-581A-9478-2C0D7D1CF9E6.dita"><linktext>Use Cases
for Writing Standard C++ Code</linktext></link>
<link href="GUID-E331B72B-84AF-558A-9B8F-73E5E50B58C7.dita"><linktext>Building
--- a/Symbian3/SDK/Source/GUID-B51A9A1F-8E80-4DF6-904A-7BD1A8976BBB.dita Fri Jan 22 18:26:19 2010 +0000
+++ b/Symbian3/SDK/Source/GUID-B51A9A1F-8E80-4DF6-904A-7BD1A8976BBB.dita Thu Mar 11 15:24:26 2010 +0000
@@ -25,7 +25,7 @@
<row>
<entry><p>These sections provide some starting points for using the library
and the platform.</p><p><xref href="GUID-00113601-193D-5214-9DFB-1C67456B7039.dita">About
-the Symbian Developer Library</xref></p> <p><xref href="GUID-35D7EEFC-B2E4-5444-8875-2A24790E08C2.dita">Essential
+this Library</xref></p> <p><xref href="GUID-35D7EEFC-B2E4-5444-8875-2A24790E08C2.dita">Essential
idioms</xref></p> <p><xref href="GUID-270C96B0-4BDF-5A18-A8FE-FA4F78BB34EE.dita">Example
programs</xref></p><p/><p>These pages on the Symbian Foundation wiki provide
useful information for developers new to the Symbian platform. </p><p><xref href="http://developer.symbian.org/wiki/index.php/Symbian_C++_Quick_Start" scope="external">Symbian C++ Quick Start</xref></p><p><xref href="http://developer.symbian.org/wiki/index.php/Going_Beyond_Hello:_A_Tutorial_for_Symbian_C++_Applications" scope="external">Going Beyond Hello: A Tutorial for Symbian C++ Applications</xref></p></entry>
@@ -79,8 +79,8 @@
<entry><p>These documents help you write better and safer programs.</p> <p><xref href="GUID-AB3D07E6-83C9-4948-A13F-75A65498F444.dita">Security</xref></p></entry>
<entry><p>These links take you to full lists of packages and tools described
in the library.</p><p><xref href="GUID-32E29020-1956-461A-B79A-1492E06049E7.dita">Symbian
-guide</xref></p><p><xref href="GUID-A837D8F6-B9D3-5119-8C63-51772B388999.dita">Tools
-and utilities</xref></p></entry>
+Guide</xref></p><p><xref href="GUID-A837D8F6-B9D3-5119-8C63-51772B388999.dita">Tools
+and Utilities</xref></p></entry>
</row>
</tbody>
</tgroup>
--- a/Symbian3/SDK/Source/GUID-B5F98445-3CFF-5067-B89A-AC80F56C40C3.dita Fri Jan 22 18:26:19 2010 +0000
+++ b/Symbian3/SDK/Source/GUID-B5F98445-3CFF-5067-B89A-AC80F56C40C3.dita Thu Mar 11 15:24:26 2010 +0000
@@ -11,8 +11,8 @@
PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
<concept id="GUID-B5F98445-3CFF-5067-B89A-AC80F56C40C3" xml:lang="en"><title>Porting
Data Recognizers to Secure Platform</title><shortdesc>This page describes how to migrate data recognizers to the secure
-version of Symbian platform. </shortdesc><prolog><metadata><keywords/></metadata></prolog><conbody>
-<section><title>Procedure</title> <p id="GUID-37D4A6C5-1A14-5CE3-A852-1AAD412C57DA"><b>Converting
+version of the Symbian platform. </shortdesc><prolog><metadata><keywords/></metadata></prolog><conbody>
+<section id="GUID-322F3E8C-2835-4B73-88AD-C537A20E0329"><title>Procedure</title> <p id="GUID-37D4A6C5-1A14-5CE3-A852-1AAD412C57DA"><b>Converting
data recognizers into ECOM plugins</b> </p> <ol id="GUID-56EF676C-103E-5B68-85A1-D6A66B9EC046">
<li id="GUID-18ED65F4-B508-5DC7-8869-A5035C7922B3"><b>Changing the project
specification (.mmp) file</b> - Change the project specification (<filepath>.mmp</filepath>)
@@ -111,6 +111,6 @@
return thing; // null if new failed
}</codeblock></li>
</ol> </section>
-<section><title>See also</title> <p><xref href="GUID-1AAA88BB-19AD-5B8E-993C-11F4B7CD90EB.dita">Writing
+<section id="GUID-C7BCBCEB-5135-4F9D-BC22-69922CE4F776"><title>See also</title> <p><xref href="GUID-1AAA88BB-19AD-5B8E-993C-11F4B7CD90EB.dita">Writing
a MIME Recognizer</xref>. </p> </section>
</conbody></concept>
\ No newline at end of file
--- a/Symbian3/SDK/Source/GUID-B7482AEB-9E7E-5F9C-A69D-60E1FE82CCE1.dita Fri Jan 22 18:26:19 2010 +0000
+++ b/Symbian3/SDK/Source/GUID-B7482AEB-9E7E-5F9C-A69D-60E1FE82CCE1.dita Thu Mar 11 15:24:26 2010 +0000
@@ -26,14 +26,15 @@
<li id="GUID-6ADD8D2B-9B4E-52C5-838E-DA0F3D646390"><p>Sorts array </p> </li>
<li id="GUID-BF05324F-470C-5DE6-8BAD-E842D7C2BBC8"><p>Destroys the array </p> </li>
</ul>
-<section id="GUID-C469AD45-C916-48B9-A621-944D8FE0B625"><title>Download</title> <p>Click on the following link to download
-the example: <xref href="guid-6013a680-57f9-415b-8851-c4fa63356636/zips/guid-a0e27f39-b574-424f-af5c-8e764d4e3aa0.zip" scope="external">DynamicArrays.zip</xref></p><p>Download some additional files
+<section id="GUID-C469AD45-C916-48B9-A621-944D8FE0B625"><title>Download</title> <p>Click
+on the following link to download the example: <xref href="guid-6013a680-57f9-415b-8851-c4fa63356636/zips/guid-a0e27f39-b574-424f-af5c-8e764d4e3aa0.zip" scope="external">DynamicArrays.zip</xref></p><p>Download some additional files
required by the example: <xref href="guid-6013a680-57f9-415b-8851-c4fa63356636/zips/guid-4184e6d4-8dbe-4267-b1a3-8737c8bf64ce.zip" scope="external">CommonFramework.zip</xref></p><p>View the source code: <xref href="guid-6013a680-57f9-415b-8851-c4fa63356636/guid-a0e27f39-b574-424f-af5c-8e764d4e3aa0.html" scope="peer">browse </xref> . View the additional files:<xref href="guid-6013a680-57f9-415b-8851-c4fa63356636/guid-4184e6d4-8dbe-4267-b1a3-8737c8bf64ce.html" scope="peer">browse</xref>.</p> </section>
-<section id="GUID-B7551573-B14D-45A9-9F29-39033C2058EC"><title>Description</title> <p>This example demonstrates how to construct
-and use the following types of dynamic arrays: </p> <p><b>CArrayFixFlat</b> </p> <p>This
-example uses the <xref href="GUID-12C65B99-553E-35CA-B36F-2F77BFC972B3.dita"><apiname>CArrayFixFlat</apiname></xref> array class to create an
-array of objects. These objects are of fixed length and are stored in a flat
-buffer. </p> <p>The following operations are performed on this array: </p> <ul>
+<section id="GUID-B7551573-B14D-45A9-9F29-39033C2058EC"><title>Description</title> <p>This
+example demonstrates how to construct and use the following types of dynamic
+arrays: </p> <p><b>CArrayFixFlat</b> </p> <p>This example uses the <xref href="GUID-12C65B99-553E-35CA-B36F-2F77BFC972B3.dita"><apiname>CArrayFixFlat</apiname></xref> array
+class to create an array of objects. These objects are of fixed length and
+are stored in a flat buffer. </p> <p>The following operations are performed
+on this array: </p> <ul>
<li id="GUID-98A1051E-C6A9-5A4D-9AC0-6421E7D2B972"><p> <b>Append elements:</b> The
example uses the <xref href="GUID-79EFD210-2C4F-31E5-83CD-DC9FE54FD585.dita#GUID-79EFD210-2C4F-31E5-83CD-DC9FE54FD585/GUID-B4C14DDC-78BF-3A11-9A7C-6B7F948CE162"><apiname>CArrayFix::AppendL()</apiname></xref> function to append
objects to the array. </p> </li>
@@ -201,10 +202,10 @@
</ul> </li>
</ul> </section>
<section id="GUID-232031B9-5964-45FC-A497-1FBC6FB068B1"><title>Class summary</title><p> <xref href="GUID-12C65B99-553E-35CA-B36F-2F77BFC972B3.dita"><apiname>CArrayFixFlat </apiname></xref> <xref href="GUID-FCE7D958-96AA-346D-8D22-0EF24B9DB7CC.dita"><apiname>CArrayPtrFlat </apiname></xref> <xref href="GUID-5BC7EAFE-FC9C-3E86-BFDC-FDE9FE086D53.dita"><apiname>CArrayVarFlat </apiname></xref> <xref href="GUID-4D6E6B46-32B5-34AD-BD8A-84BF6B2B7C81.dita"><apiname>CArrayPakFlat </apiname></xref> <xref href="GUID-04117018-A42A-3D49-9EA3-D1D7A7785B0A.dita"><apiname>TSwap </apiname></xref> <xref href="GUID-5BC09594-7D9F-3B3F-95B0-7828A756537B.dita"><apiname>TKeyArrayFix </apiname></xref> <xref href="GUID-03CE0E0B-3731-338A-87E4-49B669AD4EBC.dita"><apiname>TKeyArrayVar </apiname></xref> <xref href="GUID-F3BF9485-BA32-36A4-9B39-FC51E28F5A24.dita"><apiname>TKeyArrayPak </apiname></xref> <xref href="GUID-0756A649-486C-3CE5-9F1E-467E008A63C7.dita"><apiname>TKey </apiname></xref> <xref href="GUID-FAEBF321-6B08-3041-A01F-B1E7282D0707.dita"><apiname>RArray </apiname></xref> <xref href="GUID-C028C373-CE25-3832-855E-17FB738721CF.dita"><apiname>TLinearOrder </apiname></xref> <xref href="GUID-AAA13D1F-1BD7-3331-BB8C-11FA2795B53F.dita"><apiname>RPointerArray</apiname></xref> </p></section>
-<section id="GUID-7F5416FD-580C-4CD5-8167-DB6C546B75A4"><title>Build</title> <p> <xref href="GUID-3100800B-B2F7-50EF-BD4C-3C345ECCB2A5.dita">The
-Symbian OS build process</xref> describes how to build this example. </p> <p>For
-the emulator, the example builds an executable file called <filepath>DynamicArrays.exe</filepath> in
-the standard location (<filepath>\epoc32\release\winscw\<build_variant></filepath> for
+<section id="GUID-7F5416FD-580C-4CD5-8167-DB6C546B75A4"><title>Build</title> <p> <xref href="GUID-3100800B-B2F7-50EF-BD4C-3C345ECCB2A5.dita">The Symbian build process</xref> describes
+how to build this example. </p> <p>For the emulator, the example builds an
+executable file called <filepath>DynamicArrays.exe</filepath> in the standard
+location (<filepath>\epoc32\release\winscw\<build_variant></filepath> for
CodeWarrior) directory. After launching the executable file, depending on
the emulator you are using, you can task away from the application launcher
or shell screen to view the console. </p> </section>
--- a/Symbian3/SDK/Source/GUID-B79B6DD2-40C5-591B-AF56-5ACD167C66F5.dita Fri Jan 22 18:26:19 2010 +0000
+++ b/Symbian3/SDK/Source/GUID-B79B6DD2-40C5-591B-AF56-5ACD167C66F5.dita Thu Mar 11 15:24:26 2010 +0000
@@ -23,21 +23,6 @@
this manually or use the mmp file syntax to export it to the <filepath>\resource\messaging\mtm</filepath> directory
automatically at build time.</note> </li>
</ol> <p><b>Example</b> </p> <codeblock id="GUID-90D8E09C-7F3D-5D07-8056-083A0EAC1486" xml:space="preserve">// mtm.mmp
-//
-// Copyright 2006-2009 Nokia Corporation and/or its subsidiary(-ies).
-// All rights reserved.
-// This component and the accompanying materials are made available
-// under the terms of the License "Symbian Foundation License v1.0"
-// which accompanies this distribution, and is available
-// at the URL "http://www.symbianfoundation.org/legal/sfl-v10.html".
-//
-// Initial Contributors:
-// Nokia Corporation - initial contribution.
-//
-// Contributors:
-//
-// Description:
-//
/**
@file
--- a/Symbian3/SDK/Source/GUID-B9414AE8-820E-4CA5-A9C4-29560CD6F2EF.dita Fri Jan 22 18:26:19 2010 +0000
+++ b/Symbian3/SDK/Source/GUID-B9414AE8-820E-4CA5-A9C4-29560CD6F2EF.dita Thu Mar 11 15:24:26 2010 +0000
@@ -31,8 +31,8 @@
applications to install.</p>
</note>
<p>Sign the <codeph>sis</codeph> <xref href="GUID-61EE2BE0-7B86-42CD-A03F-857DD8FAC246.dita">installation
-file</xref> file with any private key. You can use the <xref href="jar:GUID-35228542-8C95-4849-A73F-2B4F082F0C44.jar!/sdk/doc_source/ToolsAndUtilities94/Installing/IntroductionToSecurity.guide.html" format="application/java-archive">MakeKeys</xref> application
-to create the needed private key and, for example, <xref href="jar:GUID-35228542-8C95-4849-A73F-2B4F082F0C44.jar!/sdk/doc_source/ToolsAndUtilities94/Installing/IntroductionToSignSIS.guide.html" format="application/java-archive">SignSIS</xref> to
+file</xref> with any private key. You can use the <xref href="GUID-557BF1DA-B6E8-521B-89F0-15C84E3BCB1A.dita">MakeKeys</xref> application
+to create the needed private key and, for example, <xref href="GUID-B20EE8A3-D7B2-5872-AF43-001A88C1A46E.dita">SignSIS</xref> to
sign the application. Both applications are delivered with the SDK. For more
information, see <xref href="http://wiki.forum.nokia.com/index.php/How_to_sign_a_.Sis_file_with_Self-Sign_Certificate" scope="external">How
to sign a .Sis file with Self-Sign Certificate</xref> in the Forum Nokia
@@ -44,7 +44,7 @@
<section id="GUID-44AC868B-484A-4B84-8A3A-0351E70F1141"><title>Additional information
on signing</title>
<p>The UID value you need to use for your application depends on whether
-your application is signed or self-signed. For more information, see <xref href="GUID-EA05F9B6-52C7-4BD9-8B9A-4BA3456E70B5.dita">UID</xref> and <xref href="jar:GUID-35228542-8C95-4849-A73F-2B4F082F0C44.jar!/sdk/doc_source/ToolsAndUtilities94/BuildTools/UsingUids.guide.html" format="application/java-archive">How
+your application is signed or self-signed. For more information, see <xref href="GUID-EA05F9B6-52C7-4BD9-8B9A-4BA3456E70B5.dita">UID</xref> and <xref href="GUID-380A8C4F-3EB6-5E1C-BCFB-ED5B866136D9.dita">How
to use UIDs</xref>.</p>
</section>
</conbody></concept>
\ No newline at end of file
--- a/Symbian3/SDK/Source/GUID-BC191AA8-696F-51A2-801F-B3F952037F54.dita Fri Jan 22 18:26:19 2010 +0000
+++ b/Symbian3/SDK/Source/GUID-BC191AA8-696F-51A2-801F-B3F952037F54.dita Thu Mar 11 15:24:26 2010 +0000
@@ -10,12 +10,12 @@
<!DOCTYPE concept
PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
<concept id="GUID-BC191AA8-696F-51A2-801F-B3F952037F54" xml:lang="en"><title>OS
-Security Quick Start</title><shortdesc>OS Security on Symbian platform enables data confidentiality, integrity
-and authentication. It provides high-level services, such as key and certificate
-management, authentication, secure user prompting, and Digital Rights Management
-(DRM) framework. </shortdesc><prolog><metadata><keywords/></metadata></prolog><conbody>
-<section id="GUID-3925A78F-68F0-4D92-BE2D-4AA7A2071C38"><title>Getting started with OS Security </title> <p>OS Security is
-intended to support: </p> <ul>
+Security Quick Start</title><shortdesc>OS Security on the Symbian platform enables data confidentiality,
+integrity and authentication. It provides high-level services, such as key
+and certificate management, authentication, secure user prompting, and Digital
+Rights Management (DRM) framework. </shortdesc><prolog><metadata><keywords/></metadata></prolog><conbody>
+<section id="GUID-3925A78F-68F0-4D92-BE2D-4AA7A2071C38"><title>Getting started
+with OS Security </title> <p>OS Security is intended to support: </p> <ul>
<li id="GUID-29D6A956-E19D-5015-8AF7-08C2AC607100"><p>Secure communication
protocols that provide data confidentiality and integrity </p> </li>
<li id="GUID-250B6FC2-44CB-5C3E-824C-AFFDA315421E"><p>Authentication of installable
@@ -23,8 +23,8 @@
<li id="GUID-521A3365-8C88-559C-92D5-E487047BFC4D"><p>Protection of device
integrity </p> </li>
</ul> </section>
-<section id="GUID-9337A628-41D8-4450-8EDB-8D89AB6FA3A1"><title>Architecture</title> <p>OS Security includes the following
-collections: </p> <ul>
+<section id="GUID-9337A628-41D8-4450-8EDB-8D89AB6FA3A1"><title>Architecture</title> <p>OS
+Security includes the following collections: </p> <ul>
<li id="GUID-5A81451B-7E7F-55D9-8FF5-1AD439A237AD"><p><xref href="GUID-BA362536-C9C9-5BA4-BEE3-0E1AD7FA45F1.dita">Authorisation</xref> contains <xref href="GUID-5329AE68-39E0-55E7-9878-2D8FF9E29B21.dita">User Prompt Service</xref> (UPS)
component that provides standard interfaces for the device creators to set
policies that determine if requests made by applications to access system
@@ -62,8 +62,8 @@
OpenSSL components. </p> </li>
</ul> <p>The following diagram shows the OS Security's components grouped
into collections, which are shown as white boxes: </p> </section>
-<section id="GUID-37CD3D25-4861-4277-AF70-C8A3038C85C4"><title>Technologies</title> <p> <b>DRM</b> </p> <p>DRM refers to
-an access control technology that prevents unauthorised use of copyrighted
+<section id="GUID-37CD3D25-4861-4277-AF70-C8A3038C85C4"><title>Technologies</title> <p> <b>DRM</b> </p> <p>DRM
+refers to an access control technology that prevents unauthorised use of copyrighted
content. </p> <p>To know more about the key concepts used in OS
Security, see <xref href="GUID-6F73ED8C-E259-5717-AB84-0C2933A866DA.dita">OS Security
Concepts</xref>. </p> </section>
--- a/Symbian3/SDK/Source/GUID-BD971173-E009-58DA-AF9C-F4AAFF77B138.dita Fri Jan 22 18:26:19 2010 +0000
+++ b/Symbian3/SDK/Source/GUID-BD971173-E009-58DA-AF9C-F4AAFF77B138.dita Thu Mar 11 15:24:26 2010 +0000
@@ -9,4 +9,14 @@
-->
<!DOCTYPE concept
PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
-<concept id="GUID-BD971173-E009-58DA-AF9C-F4AAFF77B138" xml:lang="en"><title>Comms Database</title><prolog><metadata><keywords/></metadata></prolog><conbody><p>The Comms Database provides system wide storage for communications related settings. </p> <p>Comunications related settings specify the available connections. The settings can also enable connections. Information is arranged into a number of different tables. For example, tables of Internet Access Providers (IAPs) and tables of Internet Service Providers (ISPs). </p> <p>The Comms Database provides an abstract data storage API to tools and applications. This API allows future versions of Symbian OS to change the implementation of the data store. </p> </conbody></concept>
\ No newline at end of file
+<concept id="GUID-BD971173-E009-58DA-AF9C-F4AAFF77B138" xml:lang="en"><title>Comms Database</title><prolog><metadata><keywords/></metadata></prolog><conbody>
+<p>The Comms Database provides system wide storage for communications related
+settings. </p>
+<p>Comunications related settings specify the available connections. The settings
+can also enable connections. Information is arranged into a number of different
+tables. For example, tables of Internet Access Providers (IAPs) and tables
+of Internet Service Providers (ISPs). </p>
+<p>The Comms Database provides an abstract data storage API to tools and applications.
+This API allows future versions of Symbian platform to change
+the implementation of the data store. </p>
+</conbody></concept>
\ No newline at end of file
--- a/Symbian3/SDK/Source/GUID-C1612638-4C5A-5C37-AF1A-16F9EBEF09FD.dita Fri Jan 22 18:26:19 2010 +0000
+++ b/Symbian3/SDK/Source/GUID-C1612638-4C5A-5C37-AF1A-16F9EBEF09FD.dita Thu Mar 11 15:24:26 2010 +0000
@@ -23,13 +23,14 @@
<li><p><xref href="GUID-D5A30C75-E22C-34E8-913B-7D2CA6AD5C51.dita"><apiname>CSession2</apiname></xref> - Represents a session (version 2) for
a client thread on the server-side.</p></li>
</ul></section>
-<section id="GUID-E688F8C0-0A4A-4D25-B7B4-779CB6A08157"><title>Download</title> <p>Click on the following link to download
-the example: <xref href="guid-6013a680-57f9-415b-8851-c4fa63356636/zips/guid-cbf7e18e-3788-4ec1-a225-268ce1a22c51.zip" scope="external">transient.zip</xref></p><p>click: <xref href="guid-6013a680-57f9-415b-8851-c4fa63356636/guid-cbf7e18e-3788-4ec1-a225-268ce1a22c51.html" scope="peer">browse</xref> to view the example code.</p> </section>
-<section id="GUID-87B18963-ACE8-464B-9863-A37ADA57379C"><title>Background</title> <p>The client-server framework is an important
-part of Symbian platform. There is a level of complexity in implementing a
-server for an application, but this example provides client interface code
-and server code that can be re-used in your own implementations. </p> <p>Symbian
-platform servers are of three basic types: </p> <ul>
+<section id="GUID-E688F8C0-0A4A-4D25-B7B4-779CB6A08157"><title>Download</title> <p>Click
+on the following link to download the example: <xref href="guid-6013a680-57f9-415b-8851-c4fa63356636/zips/guid-cbf7e18e-3788-4ec1-a225-268ce1a22c51.zip" scope="external">transient.zip</xref></p><p>click: <xref href="guid-6013a680-57f9-415b-8851-c4fa63356636/guid-cbf7e18e-3788-4ec1-a225-268ce1a22c51.html" scope="peer">browse</xref> to view the example code.</p> </section>
+<section id="GUID-87B18963-ACE8-464B-9863-A37ADA57379C"><title>Background</title> <p>The
+client-server framework is an important part of the Symbian platform. There
+is a level of complexity in implementing a server for an application, but
+this example provides client interface code and server code that can be re-used
+in your own implementations. </p> <p>Symbian platform servers are of three
+basic types: </p> <ul>
<li id="GUID-6D0F8C69-CFEA-5BB1-A0CB-C4D178DFAE25"><p> <b>Transient servers:</b> these
are started on demand when a client needs the server, and exit after the last
client has disconnected - sometimes after a short delay, for example, the
@@ -41,12 +42,13 @@
are "local" to a process to provide multi-threaded access to thread-specific
resources, for example, the posix server (in the C Standard Library). </p> </li>
</ul> </section>
-<section id="GUID-EEA0A38B-F8A6-4308-A50D-B3E74B12420A"><title>Description</title> <p>The transient server supplied here
-runs in a thread in its own process. This gives the server independence from
-its clients. This is important because if the client were to create the server
-as a separate thread within its own process, then the server would exit, i.e.
-terminate, if its owning process terminated. This would be true even if clients
-in other processes were still connected to it. </p> <p>Equally as important: </p> <ul>
+<section id="GUID-EEA0A38B-F8A6-4308-A50D-B3E74B12420A"><title>Description</title> <p>The
+transient server supplied here runs in a thread in its own process. This gives
+the server independence from its clients. This is important because if the
+client were to create the server as a separate thread within its own process,
+then the server would exit, i.e. terminate, if its owning process terminated.
+This would be true even if clients in other processes were still connected
+to it. </p> <p>Equally as important: </p> <ul>
<li id="GUID-432FCF7B-2393-5E59-BDE5-0A5B4BAFD155"><p>a client does not explicitly
need to start the server prior to connecting; this is done by the client interface. </p> </li>
<li id="GUID-D89C8F48-2CA2-5769-8DB9-42FD8FFA5879"><p>the server terminates
@@ -154,7 +156,8 @@
<li><p><xref href="GUID-E0B34F3E-D4C4-3232-B8B1-7DB35B454646.dita"><apiname>TRequestStatus</apiname></xref> - Indicates the completion status
of a request made to a service provider.</p></li>
</ul> </section>
-<section id="GUID-86D3479E-216B-4D5D-AF57-C4C9963CD9F0"><title>Building and configuring</title> <p>To build the example: </p> <ul>
+<section id="GUID-86D3479E-216B-4D5D-AF57-C4C9963CD9F0"><title>Building and
+configuring</title> <p>To build the example: </p> <ul>
<li id="GUID-FDC690A6-D68B-58E5-A10D-89220DB9B89E"><p>You can build the example
from your IDE or the command line. </p> <p>If you use an IDE, import the <filepath>bld.inf</filepath> file
of the example into your IDE, and use the build command of the IDE. </p> <p>If
--- a/Symbian3/SDK/Source/GUID-C4CC3CA3-8C02-5F73-A482-4F849DD08111.dita Fri Jan 22 18:26:19 2010 +0000
+++ b/Symbian3/SDK/Source/GUID-C4CC3CA3-8C02-5F73-A482-4F849DD08111.dita Thu Mar 11 15:24:26 2010 +0000
@@ -9,4 +9,9 @@
-->
<!DOCTYPE concept
PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
-<concept id="GUID-C4CC3CA3-8C02-5F73-A482-4F849DD08111" xml:lang="en"><title>Porting Tutorial</title><prolog><metadata><keywords/></metadata></prolog><conbody><p>This section describes changes and the instructions required to migrate from apps to exes, control panel plug-ins to Symbian OS v9.1 and later, exe-apps to a data caged directory structure, data recognizers to the secure version of Symbian platform and notifiers to Symbian OS v9.1.</p> </conbody></concept>
\ No newline at end of file
+<concept id="GUID-C4CC3CA3-8C02-5F73-A482-4F849DD08111" xml:lang="en"><title>Porting Tutorial</title><prolog><metadata><keywords/></metadata></prolog><conbody>
+<p>This section describes changes and the instructions required to migrate
+from apps to exes, control panel plug-ins to Symbian OS v9.1 and later, exe-apps
+to a data caged directory structure, data recognizers to the secure version
+of the Symbian platform and notifiers to Symbian OS v9.1.</p>
+</conbody></concept>
\ No newline at end of file
--- a/Symbian3/SDK/Source/GUID-CAD36EEF-42CF-52AE-A619-64F988FF342D.dita Fri Jan 22 18:26:19 2010 +0000
+++ b/Symbian3/SDK/Source/GUID-CAD36EEF-42CF-52AE-A619-64F988FF342D.dita Thu Mar 11 15:24:26 2010 +0000
@@ -12,10 +12,12 @@
<concept id="GUID-CAD36EEF-42CF-52AE-A619-64F988FF342D" xml:lang="en"><title>Legal
Notices</title><prolog><metadata><keywords/></metadata></prolog><conbody>
<p>This page provides copyright and acknowledgement information. </p>
-<section id="GUID-AF837579-4E73-45CC-AB57-600CF171BB22"><title>Copyright</title> <p>Copyright © 2009 Nokia Corporation and/or
-its subsidiary(-ies). All rights reserved. This component and the accompanying
-materials are made available under the terms of "Eclipse Public License v1.0"
-which accompanies this distribution, and is available at the URL <xref href="http://www.eclipse.org/legal/epl-v10.html.dita">http://www.eclipse.org/legal/epl-v10.html</xref>. </p> <p>Initial Contributors: </p> <p>Nokia Corporation - initial contribution </p> </section>
+<section id="GUID-AF837579-4E73-45CC-AB57-600CF171BB22"><title>Copyright</title> <p>Copyright
+© 2007-2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. This
+component and the accompanying materials are made available under the terms
+of "Eclipse Public License v1.0" which accompanies this distribution, and
+is available at the URL <xref href="http://www.eclipse.org/legal/epl-v10.html.dita">http://www.eclipse.org/legal/epl-v10.html</xref>. </p> <p>Initial
+Contributors: </p> <p>Nokia Corporation - initial contribution </p> </section>
<section id="GUID-F0030E9A-8035-5EDF-A80E-52418F88F3CC"><title>Trademarks</title> <p>These
trademarks, and others, are acknowledged. Conventional abbreviations of these
trademarks are used throughout this documentation. </p> <p>Nokia and Nokia
--- a/Symbian3/SDK/Source/GUID-CC8EA664-FF2E-40FB-BC1C-89FB1255A9C9.dita Fri Jan 22 18:26:19 2010 +0000
+++ b/Symbian3/SDK/Source/GUID-CC8EA664-FF2E-40FB-BC1C-89FB1255A9C9.dita Thu Mar 11 15:24:26 2010 +0000
@@ -35,11 +35,10 @@
traffic between units, and by limiting access rights of unidentified parties.
These techniques can be applied from a single software component to an entire
business system.</p>
-<p>From Symbian OS v9.1 onwards, <xref href="jar:GUID-35228542-8C95-4849-A73F-2B4F082F0C44.jar!/sdk/doc_source/guide/platsecsdk/index.html" format="application/java-archive">platform security</xref> implements
-control of events inside the operating system and creates borders for different
-security areas (for example, by means of <xref href="GUID-ACDED56F-38FE-491D-B019-BE2C53A75D28.dita">data
-caging</xref> and server protection). Platform security also implements the
-minimum rights principle.</p>
+<p>From Symbian OS v9.1 onwards, <xref href="GUID-4BFEDD79-9502-526A-BA7B-97550A6F0601.dita">platform
+security</xref> implements control of events inside the operating system and
+creates borders for different security areas (for example, by means of <xref href="GUID-ACDED56F-38FE-491D-B019-BE2C53A75D28.dita">data caging</xref> and server
+protection). Platform security also implements the minimum rights principle.</p>
<p>Additionally, there are <xref href="GUID-9058F379-C495-4B22-B270-FF6A80E450B8.dita#GUID-9058F379-C495-4B22-B270-FF6A80E450B8/GUID-9058F379-C495-4B22-B270-FF6A80E450B9">third-party
security applications</xref> such as <i>antivirus software</i>, <i>firewalls,</i> and <i>intrusion
detection systems</i> that provide good protection against hostile attacks
--- a/Symbian3/SDK/Source/GUID-D32E52C9-F05C-5F1E-8B49-243D555C353C.dita Fri Jan 22 18:26:19 2010 +0000
+++ b/Symbian3/SDK/Source/GUID-D32E52C9-F05C-5F1E-8B49-243D555C353C.dita Thu Mar 11 15:24:26 2010 +0000
@@ -12,12 +12,12 @@
<concept id="GUID-D32E52C9-F05C-5F1E-8B49-243D555C353C" xml:lang="en"><title>Known
Issues</title><prolog><metadata><keywords/></metadata></prolog><conbody>
<p>This topic describes the known issues associated with developing Standard
-C++ applications or libraries on Symbian platform. </p>
+C++ applications or libraries on the Symbian platform. </p>
<p>The following functionalities of Standard C++ have certain limitations
-on Symbian platform: </p>
+on the Symbian platform: </p>
<ul>
<li id="GUID-8A496C80-74F0-559D-84B3-34EF8BA15A39"><p> <b>dynamic_cast:</b> The <codeph>dynamic_cast</codeph> operator
-is not fully supported on Symbian platform. </p> </li>
+is not fully supported on the Symbian platform. </p> </li>
<li id="GUID-012F6B22-4A66-5B54-B981-01A252F10147"><p> <b>unexpected_handler:</b> The
CodeWarrior runtime does not support the invocation of <codeph>unexpected_handler</codeph> upon
an exception specification violation. </p> </li>
@@ -44,11 +44,11 @@
compiler.</note></li>
</ol></section>
<section id="GUID-6008A836-2454-49E5-BE25-29EB9074CF88"><title>Using the id
-member variable of facet classes</title> <p>Symbian platform does not support
-exporting static data. Hence, the <codeph>id</codeph> member variable of facet
-classes (<codeph>static locale::id id</codeph>) cannot be used directly
-on Symbian platform. When you use these classes you must use the <codeph>GetFacetLocaleId()</codeph> function
-to access the data member <codeph>id</codeph> instead. </p> <p> <b>Examples</b> </p> <ol id="GUID-96B64FD3-382E-56E1-BAD6-90DFBDA0969F">
+member variable of facet classes</title> <p>The Symbian platform does not
+support exporting static data. Hence, the <codeph>id</codeph> member variable
+of facet classes (<codeph>static locale::id id</codeph>) cannot
+be used directly on the Symbian platform. When you use these classes you must
+use the <codeph>GetFacetLocaleId()</codeph> function to access the data member <codeph>id</codeph> instead. </p> <p> <b>Examples</b> </p> <ol id="GUID-96B64FD3-382E-56E1-BAD6-90DFBDA0969F">
<li id="GUID-20337C94-A194-5BD7-9974-490C1EBB543F"><p> <b>Using the id member
of standard facets:</b> For example, you can change <codeph>locale::id Id1
= numpunct<char>::id;</codeph> to <codeph>locale::id Id1
@@ -119,7 +119,7 @@
<link href="GUID-F7FEB759-E64D-5B6D-9017-C5E982E4FC16.dita"><linktext>Standard
C++ Library Overview</linktext></link>
<link href="GUID-2CCD1748-9EDE-5383-9941-A3051E06F3E2.dita"><linktext>Standard
-C++ Support on Symbian Platform</linktext></link>
+C++ Support on the Symbian platform</linktext></link>
<link href="GUID-CDE8CD85-8467-5B36-A0AC-41D1D98151CA.dita"><linktext>Developing
Applications or Libraries Using Standard C++</linktext></link>
<link href="GUID-E331B72B-84AF-558A-9B8F-73E5E50B58C7.dita"><linktext>Building
--- a/Symbian3/SDK/Source/GUID-D60B55FA-D8C1-559A-9D99-48845BE32A6C.dita Fri Jan 22 18:26:19 2010 +0000
+++ b/Symbian3/SDK/Source/GUID-D60B55FA-D8C1-559A-9D99-48845BE32A6C.dita Thu Mar 11 15:24:26 2010 +0000
@@ -12,6 +12,6 @@
<concept id="GUID-D60B55FA-D8C1-559A-9D99-48845BE32A6C" xml:lang="en"><title>EUser High
Level Library</title><shortdesc>The EUser High Level (EUserHL) library is a general purpose user
library that provides a usability layer to hide away some of the complexities
-of Symbian platform. This section lists the concepts, the overview and the
-tutorials that helps the Symbian Developers understand the importance of the
-EUserHL library. </shortdesc><prolog><metadata><keywords/></metadata></prolog><conbody/></concept>
\ No newline at end of file
+of the Symbian platform. This section lists the concepts, the
+overview and the tutorials that helps the Symbian Developers understand the
+importance of the EUserHL library. </shortdesc><prolog><metadata><keywords/></metadata></prolog><conbody/></concept>
\ No newline at end of file
--- a/Symbian3/SDK/Source/GUID-DB827750-6057-537E-8FE1-8F68BF2E9F99.dita Fri Jan 22 18:26:19 2010 +0000
+++ b/Symbian3/SDK/Source/GUID-DB827750-6057-537E-8FE1-8F68BF2E9F99.dita Thu Mar 11 15:24:26 2010 +0000
@@ -15,9 +15,9 @@
to access services are silently accepted or denied or whether they require
the user to be prompted. Each service has a policy file. The policy file lists
policies for various applications. </p>
-<section><title>Required Background</title> <p>Before you start writing a
+<section id="GUID-F3D62C3E-D570-4DE2-ACED-0577D3923965"><title>Required Background</title> <p>Before you start writing a
UPS policy file, you must configure the UPS. For more information, see <xref href="GUID-6849E256-6719-5788-BCB2-7557F09AAAD0.dita">Configuring UPS</xref>. </p> </section>
-<section><title>Introduction</title> <p>The resource header file, <filepath>ups/policies.rh</filepath>,
+<section id="GUID-10A7A574-4E57-45E3-8198-CD6D15EAC455"><title>Introduction</title> <p>The resource header file, <filepath>ups/policies.rh</filepath>,
defines the structures and constants required by User Prompt Service policy
files. </p> <p>Device creators can customise the circumstances under which
prompts are generated by configuring policies. Policies are made up of details
@@ -27,7 +27,7 @@
cases where the policy specifies that a user prompt is required, ECOM plug-ins
called <xref href="GUID-43080A86-72D3-5422-953E-A5EF79961D7B.dita">Policy Evaluators</xref> and <xref href="GUID-A8130D83-E684-5B6C-BDFE-EB6EE3CD49E8.dita">Dialog Creators</xref>, written
by device creators. </p> </section>
-<section><title>Writing policy files</title> <p>Writing policy files include
+<section id="GUID-7DFB9572-0E28-4D7A-9EF1-8A4DADFAA0B3"><title>Writing policy files</title> <p>Writing policy files include
the following: </p> <ul>
<li id="GUID-9FE188FC-A512-595A-848B-DA5A82F143AF"><p>Naming and location
of policy files </p> </li>
@@ -78,19 +78,8 @@
policyevaluator = 0x10283698;
};
</codeblock> </section>
-<section><title>Example of a policy file </title> <p>The following is an example
-of a policy file: </p> <codeblock id="GUID-F5378D3D-02A5-536E-96D1-6BD240B3852E" xml:space="preserve">// Copyright (c) 2006-2009 Nokia Corporation and/or its subsidiary(-ies).
-// All rights reserved.
-// This component and the accompanying materials are made available
-// under the terms of the License "Symbian Foundation License v1.0"
-// which accompanies this distribution, and is available
-// at the URL "http://www.symbianfoundation.org/legal/sfl-v10.html".
-//
-// Initial Contributors:
-// Nokia Corporation - initial contribution.
-
-
-#include <ups/policies.rh>
+<section id="GUID-7A571B93-A2B9-4B97-ACE9-8C70AABBB389"><title>Example of a policy file </title> <p>The following is an example
+of a policy file: </p> <codeblock id="GUID-F5378D3D-02A5-536E-96D1-6BD240B3852E" xml:space="preserve">#include <ups/policies.rh>
// Identifies this as a UPS policy file
UID2 KUidUpsPolicyResourceFile
// Uniquely defines this policy file. The UID should be reserved using the Symbian Signed protected UID allocator.
@@ -146,6 +135,6 @@
}
</codeblock> </section>
-<section><title>See also</title> <p><xref href="GUID-4E838A77-C7B5-5B1F-93F5-F3577901914B.dita">Policy
+<section id="GUID-C069700D-FABD-4C84-AD71-B292F3B26E04"><title>See also</title><p><xref href="GUID-4E838A77-C7B5-5B1F-93F5-F3577901914B.dita">Policy
Resource</xref> </p> </section>
</conbody></concept>
\ No newline at end of file
--- a/Symbian3/SDK/Source/GUID-DCA2880E-7DF9-5E60-8F87-241711935389.dita Fri Jan 22 18:26:19 2010 +0000
+++ b/Symbian3/SDK/Source/GUID-DCA2880E-7DF9-5E60-8F87-241711935389.dita Thu Mar 11 15:24:26 2010 +0000
@@ -13,16 +13,16 @@
dynamic feature management example</title><shortdesc>This example demonstrates the use of Feature Manager APIs for dynamic
feature management. It also demonstrates how to receive notification about
changes to a feature. </shortdesc><prolog><metadata><keywords/></metadata></prolog><conbody>
-<section><title>Download</title> <p>Click on the following link to download
+<section id="GUID-716F1987-F1F1-4E20-8390-BBD9AE592C2A"><title>Download</title> <p>Click on the following link to download
the example: <xref href="guid-6013a680-57f9-415b-8851-c4fa63356636/zips/guid-3bc38b8f-c8bf-4af9-969b-a0bc4dd4dcad.zip" scope="external">FeatMngrExample.zip</xref></p><p>Click: <xref href="guid-6013a680-57f9-415b-8851-c4fa63356636/guid-3bc38b8f-c8bf-4af9-969b-a0bc4dd4dcad.html" scope="peer">browse</xref> to view the example code.</p> </section>
-<section><title>Purpose</title> <p>The example shows how to use the <xref href="GUID-0CA63AEB-9A80-51C6-AE7F-E747D6B3B789.dita">Feature Manager</xref> API.
+<section id="GUID-CA323EF2-3A8A-4363-AC6E-A21B3C2648D7"><title>Purpose</title> <p>The example shows how to use the <xref href="GUID-0CA63AEB-9A80-51C6-AE7F-E747D6B3B789.dita">Feature Manager</xref> API.
UI vendors and device manufacturers can use this API to declare features (such
as DRM agents, codecs, vibra) as available or not. The feature set can be
adjusted dynamically as software services are installed and uninstalled or
as platform capabilities are discovered dynamically. </p> <p>This example
shows how Feature Manager APIs allow applications and system software to establish
-which features are present on or absent from a Symbian OS device. </p> </section>
-<section><title>Design and implementation</title> <p>The example consists
+which features are present on or absent from a Symbian device. </p> </section>
+<section id="GUID-1C59222F-2F39-4599-8052-AE7C83854AC8"><title>Design and implementation</title> <p>The example consists
of two processes: </p> <ul>
<li id="GUID-0DA213CD-55C2-5ADD-A872-20D008EE5D46"><p> <filepath>featmngrexample.exe</filepath>:
this is the main process which provides the list of available features. It
@@ -48,7 +48,7 @@
infoprint message (<xref href="GUID-C197C9A7-EA05-3F24-9854-542E984C612D.dita#GUID-C197C9A7-EA05-3F24-9854-542E984C612D/GUID-EEF84AA0-A277-390D-BFAB-CF50C94DF18D"><apiname>User::InfoPrint()</apiname></xref>). <codeph>HandleNotifyChange()</codeph> is
called to handle changes for those features which are subscribed to for notification
(in the <codeph>NotifyFeatureL</codeph> () method). </p> </section>
-<section><title>Building and configuring</title> <p>To build the example: </p> <ul>
+<section id="GUID-7A7C9409-D701-4C64-B0B2-AE0F89C396FA"><title>Building and configuring</title> <p>To build the example: </p> <ul>
<li id="GUID-A8030260-4FEF-55E1-A50C-65BEE3F08E21"><p>The example builds two
executables called <filepath>featmngrexample.exe</filepath> and <filepath>featurechecker.exe</filepath> in
the standard locations. The second executable is run by the first. </p> </li>
@@ -61,7 +61,7 @@
bldfiles</userinput> </p> <p><userinput>abld build</userinput> </p> <p><xref href="GUID-793A5EF9-CC16-5EEB-9011-6431EA76EB15.dita">How to use bldmake</xref> and <xref href="GUID-B6B54E07-3B34-5D5C-8815-93383FA8FB4B.dita">How to use abld</xref> describe
how to use the SBSv1 build tools. </p> </li>
</ul> </section>
-<section><title>Running the example</title> <p>When running the example, the
+<section id="GUID-8B18A01A-44D4-400E-9CEC-3E75F55D7F7F"><title>Running the example</title> <p>When running the example, the
user is presented with various menu options that are self-explanatory. Press
any other key to exit. </p> </section>
<section id="GUID-433F7103-5372-5971-85A6-0FBF88ECE5C1"><title>See also:</title><p><xref href="GUID-7495B1C8-38B5-5A09-8231-25B3BBC09F51.dita">Feature Management</xref></p></section>
--- a/Symbian3/SDK/Source/GUID-E21287EF-7211-590B-A1E3-E0B37069FCB2.dita Fri Jan 22 18:26:19 2010 +0000
+++ b/Symbian3/SDK/Source/GUID-E21287EF-7211-590B-A1E3-E0B37069FCB2.dita Thu Mar 11 15:24:26 2010 +0000
@@ -9,4 +9,13 @@
-->
<!DOCTYPE concept
PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
-<concept id="GUID-E21287EF-7211-590B-A1E3-E0B37069FCB2" xml:lang="en"><title>POSIX Realtime Extensions</title><prolog><metadata><keywords/></metadata></prolog><conbody><p>POSIX real-time extensions (based on <xref scope="external" href="http://en.wikipedia.org/wiki/POSIX">POSIX 1003.1b</xref>) define extensions such as timers, priority scheduling, real-time signals, semaphores, memory queues, shared memory and memory locking that are useful for development of real-time systems. Extensions such as, timers and shared memory are supported by the <xref scope="external" href="http://refspecs.freestandards.org/LSB_3.1.0/LSB-Core-generic/LSB-Core-generic/librt.html">Librt library</xref>, which conforms to the Linux Standard Base (LSB) 3.1 Specification. Symbian platform supports the Librt library, which enables Symbian Developers to port Librt-based applications to Symbian platform quickly and easily.</p> </conbody></concept>
\ No newline at end of file
+<concept id="GUID-E21287EF-7211-590B-A1E3-E0B37069FCB2" xml:lang="en"><title>POSIX Realtime
+Extensions</title><prolog><metadata><keywords/></metadata></prolog><conbody>
+<p>POSIX real-time extensions (based on <xref href="http://en.wikipedia.org/wiki/POSIX" scope="external">POSIX 1003.1b</xref>) define extensions such as timers, priority
+scheduling, real-time signals, semaphores, memory queues, shared memory and
+memory locking that are useful for development of real-time systems. Extensions
+such as, timers and shared memory are supported by the <xref href="http://refspecs.freestandards.org/LSB_3.1.0/LSB-Core-generic/LSB-Core-generic/librt.html" scope="external">Librt library</xref>, which conforms to the Linux Standard
+Base (LSB) 3.1 Specification. The Symbian platform supports the Librt library,
+which enables Symbian Developers to port Librt-based applications onto the
+Symbian platform quickly and easily.</p>
+</conbody></concept>
\ No newline at end of file
--- a/Symbian3/SDK/Source/GUID-E23CC708-1DD1-5DFC-992A-997AA107A616.dita Fri Jan 22 18:26:19 2010 +0000
+++ b/Symbian3/SDK/Source/GUID-E23CC708-1DD1-5DFC-992A-997AA107A616.dita Thu Mar 11 15:24:26 2010 +0000
@@ -9,4 +9,9 @@
-->
<!DOCTYPE concept
PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
-<concept id="GUID-E23CC708-1DD1-5DFC-992A-997AA107A616" xml:lang="en"><title>File server plugins</title><prolog><metadata><keywords/></metadata></prolog><conbody><p>The File Server Plugin Framework provides a way for developers to extend the functionality of the Symbian OS File Server. Developers can produce plugins that intercept file and directory IO. </p> <p>The interception and processing of requests by plugins is transparent to the application making the request. </p> </conbody></concept>
\ No newline at end of file
+<concept id="GUID-E23CC708-1DD1-5DFC-992A-997AA107A616" xml:lang="en"><title>File Server
+Plug-ins</title><shortdesc>The File Server Plug-in Framework provides a way for developers
+to extend the functionality of the Symbian platform File Server. Developers
+can produce plug-ins that intercept file and directory IO. The interception
+and processing of requests by plug-ins is transparent to the application making
+the request.</shortdesc><prolog><metadata><keywords/></metadata></prolog></concept>
\ No newline at end of file
--- a/Symbian3/SDK/Source/GUID-E331B72B-84AF-558A-9B8F-73E5E50B58C7.dita Fri Jan 22 18:26:19 2010 +0000
+++ b/Symbian3/SDK/Source/GUID-E331B72B-84AF-558A-9B8F-73E5E50B58C7.dita Thu Mar 11 15:24:26 2010 +0000
@@ -80,7 +80,7 @@
<link href="GUID-F7FEB759-E64D-5B6D-9017-C5E982E4FC16.dita"><linktext>Standard
C++ Library Overview</linktext></link>
<link href="GUID-2CCD1748-9EDE-5383-9941-A3051E06F3E2.dita"><linktext>Standard
-C++ Support on Symbian Platform</linktext></link>
+C++ Support on the Symbian Platform</linktext></link>
<link href="GUID-CDE8CD85-8467-5B36-A0AC-41D1D98151CA.dita"><linktext>Developing
Applications or Libraries Using Standard C++</linktext></link>
<link href="GUID-5B3F5296-D6D0-5D25-8362-141DF5927E52.dita"><linktext>Troubleshooting</linktext>
--- a/Symbian3/SDK/Source/GUID-E3E4E9A1-359E-5475-A355-1DA446FE7170.dita Fri Jan 22 18:26:19 2010 +0000
+++ b/Symbian3/SDK/Source/GUID-E3E4E9A1-359E-5475-A355-1DA446FE7170.dita Thu Mar 11 15:24:26 2010 +0000
@@ -9,4 +9,10 @@
-->
<!DOCTYPE concept
PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
-<concept id="GUID-E3E4E9A1-359E-5475-A355-1DA446FE7170" xml:lang="en"><title>What are Nodes</title><shortdesc>This section describes the concept of <i>Nodes</i> in Symbian OS and in the Communications Framework. </shortdesc><prolog><metadata><keywords/></metadata></prolog><conbody><p>The section first describes the base concept of a Node. The section continues with a description of the more specialised Nodes provided by the Communications Framework. </p> </conbody></concept>
\ No newline at end of file
+<concept id="GUID-E3E4E9A1-359E-5475-A355-1DA446FE7170" xml:lang="en"><title>What are Nodes</title><shortdesc>This section describes the concept of <i>Nodes</i> in Symbian platform
+and in the Communications Framework. </shortdesc><prolog><metadata><keywords/></metadata></prolog><conbody>
+
+<p>The section first describes the base concept of a Node. The section continues
+with a description of the more specialised Nodes provided by the Communications
+Framework. </p>
+</conbody></concept>
\ No newline at end of file
--- a/Symbian3/SDK/Source/GUID-E9B97347-D703-4758-A5CE-423A6CB4E474.dita Fri Jan 22 18:26:19 2010 +0000
+++ b/Symbian3/SDK/Source/GUID-E9B97347-D703-4758-A5CE-423A6CB4E474.dita Thu Mar 11 15:24:26 2010 +0000
@@ -15,8 +15,7 @@
such as image capture and voice recording. For example, a multimedia messaging
service (MMS) editor could embed the camera application to capture images
and insert them in multimedia messages.</p>
-<p>Use the New File Service Client API to create a service client. You can
-download the API from the <xref href="http://wiki.forum.nokia.com/index.php/SDK_API_Plug-in" scope="external">SDK API plug-in page</xref> on Forum Nokia.</p>
+<p>Use the New File Service Client API to create a service client.</p>
<note><p>The binary compatibility of the API plug-ins is not guaranteed either
between platform versions or within a platform version. Test your application
on each device model that the application can be installed on to ensure the
@@ -24,7 +23,8 @@
than tested devices, define the product IDs (also called manufacturer IDs)
in the <xref href="GUID-7F1B2577-2FEF-45F9-B32F-745DFE0F0D95.dita">package file</xref>.
For more information, see <xref href="jar:GUID-35228542-8C95-4849-A73F-2B4F082F0C44.jar!/sdk/doc_source/ToolsAndUtilities94/Installing-ref/PKG_format/PKG_dependency.html" format="application/java-archive">Hardware/UI platform dependency</xref>.</p></note>
-<section id="GUID-A7CFB0D3-0F64-4BCA-93F1-28D7F2F892A0"><title>To embed camera applications</title><ol>
+<section id="GUID-A7CFB0D3-0F64-4BCA-93F1-28D7F2F892A0"><title>To embed camera
+applications</title><ol>
<li id="GUID-B945513D-1DBA-46A5-BE66-20F36EF8E4B4"><p>Use the <codeph>CNewFileServiceClient</codeph> method
to create a new file service client. </p><codeblock xml:space="preserve">CNewFileServiceClient* fileClient = NewFileServiceFactory::NewClientL();
CleanupStack::PushL( fileClient );
--- a/Symbian3/SDK/Source/GUID-E9E5556C-101B-48F2-B9AA-9DBEF5D85D5E.dita Fri Jan 22 18:26:19 2010 +0000
+++ b/Symbian3/SDK/Source/GUID-E9E5556C-101B-48F2-B9AA-9DBEF5D85D5E.dita Thu Mar 11 15:24:26 2010 +0000
@@ -9,7 +9,14 @@
-->
<!DOCTYPE concept
PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
-<concept id="GUID-E9E5556C-101B-48F2-B9AA-9DBEF5D85D5E" xml:lang="en"><title>Backup and restore</title><prolog><metadata><keywords/></metadata></prolog><conbody>
-<p>The <xref href="jar:GUID-35228542-8C95-4849-A73F-2B4F082F0C44.jar!/sdk/doc_source/guide/platsecsdk/index.html" format="application/java-archive">platform security</xref> architecture introduced a new secure backup and restore method that is compatible with the <xref href="GUID-6971B0A2-F79B-4E05-8AF3-BB1FC1932A22.dita">capability</xref> model, <xref href="GUID-ACDED56F-38FE-491D-B019-BE2C53A75D28.dita">data caging</xref>, and data storage features. It offers both active and passive methods to backup and restore data:</p>
-<p>For more information about backup and restore, see <xref href="jar:GUID-35228542-8C95-4849-A73F-2B4F082F0C44.jar!/sdk/doc_source/guide/Connectivity-subsystem-guide/Connectivity/PC_Connectivity_How-To_Write_Backup_Aware_Software.html" format="application/java-archive">How-To Write Backup-aware Software</xref> and <xref href="http://wiki.forum.nokia.com/index.php/TSS000750_-_Enabling_backup_and_restore_for_installed_C%2B%2B_applications" scope="external">Enabling backup and restore for installed C++ applications</xref> at Forum Nokia.</p>
+<concept id="GUID-E9E5556C-101B-48F2-B9AA-9DBEF5D85D5E" xml:lang="en"><title>Backup
+and restore</title><prolog><metadata><keywords/></metadata></prolog><conbody>
+<p>The <xref href="GUID-4BFEDD79-9502-526A-BA7B-97550A6F0601.dita">platform
+security</xref> architecture introduced a new secure backup and restore method
+that is compatible with the <xref href="GUID-6971B0A2-F79B-4E05-8AF3-BB1FC1932A22.dita">capability</xref> model, <xref href="GUID-ACDED56F-38FE-491D-B019-BE2C53A75D28.dita">data caging</xref>, and data
+storage features. It offers both active and passive methods to backup and
+restore data. </p>
+
+<p>In addition, you can refer to <xref href="http://developer.symbian.org/wiki/index.php/PC_Connectivity:_How_To_Write_Backup_Aware_Software_for_Symbian" scope="external">PC Connectivity: How To Write Backup Aware Software for Symbian</xref> at
+the Symbian Foundation.</p>
</conbody></concept>
\ No newline at end of file
--- a/Symbian3/SDK/Source/GUID-EEC50FC0-46D5-4ED7-AD95-67430D5EC651.dita Fri Jan 22 18:26:19 2010 +0000
+++ b/Symbian3/SDK/Source/GUID-EEC50FC0-46D5-4ED7-AD95-67430D5EC651.dita Thu Mar 11 15:24:26 2010 +0000
@@ -9,16 +9,16 @@
-->
<!DOCTYPE concept
PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
-<concept id="GUID-EEC50FC0-46D5-4ED7-AD95-67430D5EC651" xml:lang="en"><title>Application security</title><prolog><metadata><keywords/></metadata></prolog><conbody>
-<p>Native C++ applications have broad access to the mobile device functionality. They can access, for example, network and mobile device interfaces, storage memory and messaging framework. This provides many features for application developers to use, but can be exploited in the wrong hands.</p>
-<p>The Symbian OS v9 <xref href="jar:GUID-35228542-8C95-4849-A73F-2B4F082F0C44.jar!/sdk/doc_source/guide/platsecsdk/index.html" format="application/java-archive">platform security</xref> architecture allows an application server to determine whether installed software using the server can be trusted. This section covers the most critical components in the security system, the components that first encounter problems and form the front line of defense when a system is attacked.</p>
+<concept id="GUID-EEC50FC0-46D5-4ED7-AD95-67430D5EC651" xml:lang="en"><title>Application
+security</title><prolog><metadata><keywords/></metadata></prolog><conbody>
+<p>Native C++ applications have broad access to the mobile device functionality.
+They can access, for example, network and mobile device interfaces, storage
+memory and messaging framework. This provides many features for application
+developers to use, but can be exploited in the wrong hands.</p>
+<p>The Symbian <xref href="GUID-4BFEDD79-9502-526A-BA7B-97550A6F0601.dita">platform
+security</xref> architecture allows an application server to determine whether
+installed software using the server can be trusted. This section covers the
+most critical components in the security system, the components that first
+encounter problems and form the front line of defense when a system is attacked.</p>
<p>The following aspects of application security are covered in this section:</p>
-<ul>
-<li><p><xref href="GUID-50BE8F1A-513A-433C-B045-66658FC226D7.dita">Client/server communication</xref></p></li>
-<li><p><xref href="GUID-C23196E8-FDD3-4A10-9DA2-DA83A2AD49D9.dita">Applications with an user interface</xref></p></li>
-<li><p><xref href="GUID-2E986A81-F094-4F1D-9ECB-6A325CFA5BB4.dita">Plug-ins</xref></p></li>
-<li><p><xref href="GUID-1293DE8C-E803-4ADF-9FA8-862519337331.dita">Software installer</xref></p></li>
-<li><p><xref href="GUID-8255A186-C1AC-44DA-844C-1FEA029C73BC.dita">Publish and Subscribe</xref></p></li>
-<li><p><xref href="GUID-261ADCEC-C8C8-46E3-A7DC-804AC868C233.dita">Descriptors</xref></p></li>
-</ul>
</conbody></concept>
\ No newline at end of file
--- a/Symbian3/SDK/Source/GUID-F51062B0-90BB-5659-9F23-2FF25116D78A.dita Fri Jan 22 18:26:19 2010 +0000
+++ b/Symbian3/SDK/Source/GUID-F51062B0-90BB-5659-9F23-2FF25116D78A.dita Thu Mar 11 15:24:26 2010 +0000
@@ -9,4 +9,17 @@
-->
<!DOCTYPE concept
PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
-<concept id="GUID-F51062B0-90BB-5659-9F23-2FF25116D78A" xml:lang="en"><title>Porting Tutorials</title><prolog><metadata><keywords/></metadata></prolog><conbody><p>This topic describes how to port some C applications to Symbian platform. </p> <p>It uses <filepath>Hello</filepath>, <filepath>ConsoleApp</filepath> and <filepath>GUIApp</filepath> examples . The first two are simple console-based examples. The third is a command-line driven program which has been converted into a standard Symbian application. It also describes typical problems which may be encountered when porting C code to Symbian platform, including the restriction on writeable data in DLLs. These example codes can be found in directory <filepath>examples\stdlib\</filepath>. </p> <p> <b>NOTE</b>: These examples may not be present on all Symbian platform SDKs. </p> <p>Some of the code for the second two examples was taken from the FreeBSD source code. For information on FreeBSD, see <xref scope="external" href="http://www.freebsd.org">http://www.freebsd.org</xref>. </p> </conbody></concept>
\ No newline at end of file
+<concept id="GUID-F51062B0-90BB-5659-9F23-2FF25116D78A" xml:lang="en"><title>Porting Tutorials</title><prolog><metadata><keywords/></metadata></prolog><conbody>
+<p>This topic describes how to port some C applications to the Symbian
+platform. </p>
+<p>It uses <filepath>Hello</filepath>, <filepath>ConsoleApp</filepath> and <filepath>GUIApp</filepath> examples
+. The first two are simple console-based examples. The third is a command-line
+driven program which has been converted into a standard Symbian application.
+It also describes typical problems which may be encountered when porting C
+code to the Symbian platform, including the restriction on writeable data
+in DLLs. These example codes can be found in directory <filepath>examples\stdlib\</filepath>. </p>
+<p> <b>NOTE</b>: These examples may not be present on all Symbian platform
+SDKs. </p>
+<p>Some of the code for the second two examples was taken from the FreeBSD
+source code. For information on FreeBSD, see <xref href="http://www.freebsd.org" scope="external">http://www.freebsd.org</xref>. </p>
+</conbody></concept>
\ No newline at end of file
--- a/Symbian3/SDK/Source/GUID-F8A26275-883A-5299-9C37-9DDCC2F62108.dita Fri Jan 22 18:26:19 2010 +0000
+++ b/Symbian3/SDK/Source/GUID-F8A26275-883A-5299-9C37-9DDCC2F62108.dita Thu Mar 11 15:24:26 2010 +0000
@@ -21,8 +21,8 @@
SIS file. The eclipsing fails if there is no associated Stub SIS file present
in ROM. </p> <p>The following are important considerations for eclipsing
ROM files: </p> <ul>
-<li id="GUID-B854DA2E-A125-5E42-8B97-7DD9E5D30FFE"><p>In Symbian platform,
-drives are are scanned in the order <filepath>Y</filepath> to <filepath>A</filepath> and
+<li id="GUID-B854DA2E-A125-5E42-8B97-7DD9E5D30FFE"><p>Drives are
+scanned in the order <filepath>Y</filepath> to <filepath>A</filepath> and
lastly the <filepath>Z</filepath> drive. Therefore a file in <filepath>Z</filepath> drive
can be eclipsed by the newer version of the file placed on any drive between <filepath>Y</filepath> to <filepath>A</filepath>. </p> </li>
<li id="GUID-4ECA6004-CE36-5EC7-A523-03EC3B9FC171"><p>The upgrading package