<li><a href="native/ui/efl/accessibility_n.htm" target="content">Accessibility</a>
<ul>
<li><a href="native/ui/efl/accessibility_architecture_n.htm" target="content">Accessibility Architecture</a></li>
- <li><a href="native/ui/efl/accessibility_config_n.htm" target="content">Configuring Accessibility in a Device</a></li>
+ <li><a href="native/ui/efl/accessibility_config_n.htm" target="content">Configuring Accessibility on a Device</a></li>
<li><a href="native/ui/efl/accessibility_implementation_n.htm" target="content">Implementing Accessible Applications</a></li>
</ul>
</li>
<ul>
<li><a href="alarms_n.htm">Alarms</a>
-<p>You can define individual or recurring alarms and store them in the device. The alarm can trigger at specific times or on a specific date. When the alarm is triggered, it launches a specified application using the application control mechanism.</p></li>
+<p>You can define individual or recurring alarms and store them on the device. The alarm can trigger at specific times or on a specific date. When the alarm is triggered, it launches a specified application using the application control mechanism.</p></li>
<li><a href="trigger_n.htm">Contextual System Event Trigger</a> <strong>in mobile applications only</strong>
<div class="note">
<strong>Note</strong>
- Be careful when using the explicit launch, because if the target application does not exist in the device, you need to handle the <code>APP_CONTROL_ERROR_APP_NOT_FOUND</code> error. If you want to launch any application that supports a certain operation, use the implicit launch.
+ Be careful when using the explicit launch, because if the target application does not exist on the device, you need to handle the <code>APP_CONTROL_ERROR_APP_NOT_FOUND</code> error. If you want to launch any application that supports a certain operation, use the implicit launch.
</div>
</li>
<li>Implicit launch
<p>The application life-cycle consists of various states the application moves through based on system events and user actions. You can manage the application life-cycle through various state change and system events, enabling the application to transition smoothly through its event loop.</p>
-<p>Tizen provides various application models to allow you to create applications targeted for specific tasks. You can create UI applications to run on the foreground, and service applications to run on the background. You can also create specific applications to function as the watch face for the device clock, or as a widget available on the home screen.</p></li>
+<p>Tizen provides various application models to allow you to create applications targeted for specific tasks. You can create UI applications to run on the foreground, and service applications to run in the background. You can also create specific applications to function as the watch face for the device clock, or as a widget available on the home screen.</p></li>
<li><a href="app_resources_n.htm">Application Resources</a>
-<p>You can define different resources for the application to be used based on the device in which the application is run. Efficient resource management allows you to create an application that can be run in various devices with different configurations, such as screen sizes.</p></li>
+<p>You can define different resources for the application to be used based on the device on which the application is run. Efficient resource management allows you to create an application that can be run on various devices with different configurations, such as different screen sizes.</p></li>
<li><a href="app_preferences_n.htm">Application Preferences</a>
<ul>
<li>Setting resources
-<p>You can <a href="#set">set resources</a> for your application in the <strong>Resource Manager</strong> view in the Tizen Studio. By setting specific resources for specific languages and screen resolutions, you ensure that the application works flawlessly in multiple devices.</p>
+<p>You can <a href="#set">set resources</a> for your application in the <strong>Resource Manager</strong> view in the Tizen Studio. By setting specific resources for specific languages and screen resolutions, you ensure that the application works flawlessly on multiple devices.</p>
<div class="note">
<h2 id="check_resource" name="check_resource">Checking Resources with the Emulator Manager</h2>
-<p>To check how the resources are shown
in different device configurations, create emulator instances with different resolutions with the <a href="../../../../org.tizen.studio/html/common_tools/emulator_manager.htm">Emulator Manager</a> and run the application on the instances using different language settings:</p>
+<p>To check how the resources are shown
on different device configurations, create emulator instances with different resolutions with the <a href="../../../../org.tizen.studio/html/common_tools/emulator_manager.htm">Emulator Manager</a> and run the application on the instances using different language settings:</p>
<ol>
<li>Open the Emulator Manager from the <strong>Connection Explorer</strong> view in the Tizen Studio.
<h2 id="state_change">Native Application State Change Callbacks</h2>
<p>A Tizen native application can be in one of several different states. Typically, the application is launched by the user from the Launcher, or by another application. When the application is starting, the <code>app_create_cb()</code> function is executed and the main event loop starts. The application is normally at the top of the window, with focus.</p>
-<p>When the application loses the focus status, the <code>app_pause_cb()</code> callback is invoked. The application can go into the pause state, which means that your application is not terminated but continues to run on the background, when:</p>
+<p>When the application loses the focus status, the <code>app_pause_cb()</code> callback is invoked. The application can go into the pause state, which means that your application is not terminated but continues to run in the background, when:</p>
<ul>
<li>A new application is launched from the request of your application.</li>
<li>An alarm is triggered for another application, which becomes the top-most window and hides your application.</li>
</ul>
-<p>Since Tizen 2.4,
the application on the background goes into a suspended state. In the suspended state, the application process is executed with limited CPU resources. In other words, the platform does not allow the running of the background applications, except for some exceptional applications (such as Media and Download) that necessarily work on the background. In this case, the application can <a href="efl_ui_app_n.htm#allow_bg">designate their background category as an allowed category</a> to avoid going into the suspended state.</p>
+<p>Since Tizen 2.4,
an application in the background goes into a suspended state. In the suspended state, the application process is executed with limited CPU resources. In other words, the platform does not allow the running of the background applications, except for some exceptional applications (such as Media and Download) that necessarily work in the background. In this case, the application can <a href="efl_ui_app_n.htm#allow_bg">designate their background category as an allowed category</a> to avoid going into the suspended state.</p>
<p>When your application becomes visible again, the <code>app_resume_cb()</code> callback is invoked. The visibility returns, when:</p>
<ul>
<p align="center"><strong>Figure: UI and service application states</strong></p>
<p align="center"><img src="../../images/multiple_apps.png" alt="UI and service application life-cycle" style="display: block; text-align: center; margin-left: auto; margin-right: auto" /></p>
-<p>Because the service application has no UI, it neither has a pause state. Since Tizen 2.4, the service application can go into the suspended state. Basically, the service application is running on the background by its nature; so the platform does not allow the running of the service application unless it is designated as a background category application. However, when the UI application that is packaged with the service application is running in the foreground, the service application is also regarded as a foreground application and it can be run without a designated background category.</p>
+<p>Because the service application has no UI, it neither has a pause state. Since Tizen 2.4, the service application can go into the suspended state. Basically, the service application is running in the background by its nature; so the platform does not allow the running of the service application unless it is designated as a background category application. However, when the UI application that is packaged with the service application is running on the foreground, the service application is also regarded as a foreground application and it can be run without a designated background category.</p>
<p>Application state changes are managed by the underlying framework. For more information on application state transitions, see <a href="efl_ui_app_n.htm#state_trans">Application States and Transitions</a>.</p>
<li>Define the <a href="#fundamentals">the application fundamentals</a>, mainly the entry point and life-cycle callbacks.
<p>The entry point starts the event loop, which is mandatory for every Tizen native application. Within the event loop, the application can receive both basic system events and application state change events. You can register <a href="#callback">callbacks for these events</a> to react to them.</p></li>
<li>Manage <a href="#state_trans">application states and transitions</a> during its life-cycle.</li>
- <li>Define a <a href="#allow_bg">background category</a> for your application, if you want it to run on the background.</li>
+ <li>Define a <a href="#allow_bg">background category</a> for your application, if you want it to run in the background.</li>
</ul>
<h2 id="callback" name="callback">Event Callbacks</h2>
<h2 id="allow_bg" name="allow_bg">Background Categories</h2>
-<p>Since Tizen 2.4, the application is not allowed to run on the background except when it is explicitly declared to do so. The following table lists the background categories that allow the application to run on the background.</p>
+<p>Since Tizen 2.4, an application is not allowed to run in the background except when it is explicitly declared to do so. The following table lists the background categories that allow an application to run in the background.</p>
<p align="center" class="Table"><strong>Table: Allowed background application policy</strong></p>
<table id="allow_bg_table">
</tr>
<tr>
<td>Media</td>
- <td>Playing audio, recording, and outputting streaming video on the background</td>
+ <td>Playing audio, recording, and outputting streaming video in the background</td>
<td>Multimedia API (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__MEDIA__FRAMEWORK.html">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__MEDIA__FRAMEWORK.html">wearable</a> applications)</td>
<td><code>media</code></td>
</tr>
</tr>
<tr>
<td>Background network</td>
- <td>Processing general network operations on the background (such as sync-manager, IM, and VOIP)</td>
+ <td>Processing general network operations in the background (such as sync-manager, IM, and VOIP)</td>
<td>Sync Manager API (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__SYNC__MANAGER__MODULE.html">mobile</a> applications), Socket, and Curl API (in <a href="../../../../org.tizen.native.mobile.apireference/group__OPENSRC__CURL__FRAMEWORK.html">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__OPENSRC__CURL__FRAMEWORK.html">wearable</a> applications)</td>
<td><code>background-network</code></td>
</tr>
<tr>
<td>Location</td>
- <td>Processing location data on the background</td>
+ <td>Processing location data in the background</td>
<td>Location API (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__LOCATION__FRAMEWORK.html">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__LOCATION__FRAMEWORK.html">wearable</a> applications)</td>
<td><code>location</code></td>
</tr>
</tr>
<tr>
<td>IoT Communication/Connectivity</td>
- <td>Communicating between external devices on the background (such as Wi-Fi and Bluetooth)</td>
+ <td>Communicating between external devices in the background (such as Wi-Fi and Bluetooth)</td>
<td>Wi-Fi (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__NETWORK__WIFI__MODULE.html">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__NETWORK__WIFI__MODULE.html">wearable</a> applications) and Bluetooth API (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__NETWORK__BLUETOOTH__MODULE.html">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__NETWORK__BLUETOOTH__MODULE.html">wearable</a> applications)</td>
<td><code>iot-communication</code></td>
</tr>
</service-application>
</manifest>
</pre>
-<p>The <code><metadata key="http://tizen.org/metadata/bacgkround-category/<value>"/></code> element has no effect on Tizen 2.3 devices, but, in Tizen 2.4 and higher devices, it has the same effect as the <code><background-category></code> element.</p>
+<p>The <code><metadata key="http://tizen.org/metadata/bacgkround-category/<value>"/></code> element has no effect on Tizen 2.3 devices, but on Tizen 2.4 and higher devices, it has the same effect as the <code><background-category></code> element.</p>
</div>
<p>The background category of your application can be specified in the
</tbody>
</table>
-<p>Because the service application has no UI, it neither has a pause state. Since Tizen 2.4, the service application can go into the suspended state. Basically, the service application is running
on the background by its nature; so the platform does not allow the running of the service application unless it is designated as a background category application. However, when the UI application that is packaged with the service application is running in the foreground, the service application is also regarded as a foreground application and it can be run without a designated background category. For more information on using and defining a background category, see <a href="efl_ui_app_n.htm#allow_bg">Background Categories</a>.</p>
+<p>Because the service application has no UI, it neither has a pause state. Since Tizen 2.4, the service application can go into the suspended state. Basically, the service application is running
in the background by its nature; so the platform does not allow the running of the service application unless it is designated as a background category application. However, when the UI application that is packaged with the service application is running on the foreground, the service application is also regarded as a foreground application and it can be run without a designated background category. For more information on using and defining a background category, see <a href="efl_ui_app_n.htm#allow_bg">Background Categories</a>.</p>
<h2 id="register" name="register">Event Callbacks</h2>
<div class="note">
<strong>Note</strong>
- This attribute is not supported in Tizen wearable devices. Since Tizen 2.4, this attribute is not supported in all Tizen devices. Because of this, the <code>auto-restart</code> attribute used in a lower API version package than 2.4 is ignored in the devices with the Tizen platform version 2.4 and higher.
+ This attribute is not supported on Tizen wearable devices. Since Tizen 2.4, this attribute is not supported on all Tizen devices. Because of this, the <code>auto-restart</code> attribute used in a lower API version package than 2.4 is ignored on devices with the Tizen platform version 2.4 and higher.
</div>
</li>
<li><code>on-boot</code>
<div class="note">
<strong>Note</strong>
- This attribute is not supported in Tizen wearable devices. Since Tizen 2.4, this attribute is not supported in all Tizen devices. Because of this, the <code>on-boot</code> attribute used in a lower API version package than 2.4 is ignored in the devices with the Tizen platform version 2.4 and higher.
+ This attribute is not supported on Tizen wearable devices. Since Tizen 2.4, this attribute is not supported on all Tizen devices. Because of this, the <code>on-boot</code> attribute used in a lower API version package than 2.4 is ignored on devices with the Tizen platform version 2.4 and higher.
</div>
</li></ul>
<div id="container"><div id="contents"><div class="content">
<h1>UI Applications</h1>
-<p>UI applications are Tizen native applications with a graphical user interface that run in the foreground. Since they have a UI, they allow the user to easily interact with them.</p>
+<p>UI applications are Tizen native applications with a graphical user interface that run on the foreground. Since they have a UI, they allow the user to easily interact with them.</p>
<p>A Tizen native UI application is similar to a conventional Linux application, with some additional features optimized for mobile and wearable devices. The additional features have constraints, such as a relatively small screen size and lack of system resources compared to a larger system. For example, for power management reasons, the application can take actions to reduce usage when it finds out that it has its display window covered over by another application window. State change events are delivered to make it possible to detect these situations.</p>
<li>Managing the time handle and displaying the time
<p>You can manage the time handle and retrieve the window object for the watch UI. With the time handle, you can <a href="#timehandle">draw the UI</a> for your watch application.</p></li>
<li>Managing the ambient mode
-<p>In a low-powered wearable device, an ambient mode is available. In this mode, the watch application shows a limited UI and receives only the ambient tick event every minute to reduce power consumption.</p>
+<p>On a low-powered wearable device, an ambient mode is available. In this mode, the watch application shows a limited UI and receives only the ambient tick event every minute to reduce power consumption.</p>
<p>To use the ambient mode, the user must enable it in the device settings. You can <a href="#ambient">define callbacks to monitor when the application enters and exits the ambient mode</a>.</p>
</li>
</ul>
<p>To use the ambient mode:</p>
<ol>
<li>Define the ambient mode callbacks.
-<ul><li><p>The <code>ambient_changed</code> event is triggered when the ambient mode is enabled or disabled in the device. You can use the callback to initialize your ambient mode UI.</p></li>
+<ul><li><p>The <code>ambient_changed</code> event is triggered when the ambient mode is enabled or disabled on the device. You can use the callback to initialize your ambient mode UI.</p></li>
<li><p>The <code>ambient_tick</code> event is triggered every minute while the device is in the ambient mode. You can use the callback to update the time on your watch application in the ambient mode. In this callback, do not perform time-consuming task and always update the UI as fast as possible. The platform can put the device to sleep shortly after the ambient tick expires.</p></li></ul>
<pre class="prettyprint">
void
<p>The following figure illustrates the widget application states during the application life-cycle:</p>
<ul>
<li>When the application is launched, it is in the Ready state.</li>
-<li>When the application is running on the background, it is in the Running state.</li>
+<li>When the application is running in the background, it is in the Running state.</li>
<li>When the application exits, it is in the Terminated state.</li>
</ul>
<p align="center"><strong>Figure: Widget application life-cycle</strong></p>
<p>You can <a href="#discovery">discover nearby devices</a> and get information about them. After discovering a device that provides a service you need, you can <a href="#connect_service">connect to the device service</a>.</p></li>
<li>Communicating with remote devices
<p>You can use the <a href="#app_communication">app communication service</a> to connect to remote services and communicate with remote applications by sending a payload.</p></li>
-<li>Launching applications in remote devices
-<p>You can use the <a href="#remote_app_control">remote app control service</a> to launch applications
in a remote device. The access to the remote device is <a href="#access_control">controlled using passcodes</a>.</p></li>
+<li>Launching applications on remote devices
+<p>You can use the <a href="#remote_app_control">remote app control service</a> to launch applications
on a remote device. The access to the remote device is <a href="#access_control">controlled using passcodes</a>.</p></li>
</ul>
<div class="note">
<strong>Note</strong>
- Currently, the remote server can only be implemented in a TV device based on Tizen 3.0, which means that you can remotely launch applications on TV devices only. You can develop a mobile or wearable client for the app communication service, if a server exists.
+ Currently, the remote server can only be implemented on a TV device based on Tizen 3.0, which means that you can remotely launch applications on TV devices only. You can develop a mobile or wearable client for the app communication service, if a server exists.
</div>
<p>A typical app communication service work flow starts with the discovery step, in which the mobile or wearable device discovers the service provided by the TV. When the service is found, the mobile or wearable device launches an application in the TV remotely and communicates with it. The app-to-app communication is bidirectional, so both local and remote applications usually play the roles of sender and listener.</p>
<h3 id="access_control">Access Control</h3>
-<p>The remote app control service can attempt to launch an application in a remote device without user permission. To prevent this, an access control module is implemented inside the D2D connectivity framework.</p>
-<p>The access control setup is similar to the pairing of Bluetooth devices. When a device tries to access a remote device with the <code>conv_service_start()</code> function, a passcode pops up in the remote device screen and the user must enter that passcode in the original device. Once the passcode is entered correctly, the remote device is managed as an allowed device and the passcode is not asked again.</p>
+<p>The remote app control service can attempt to launch an application on a remote device without user permission. To prevent this, an access control module is implemented within the D2D connectivity framework.</p>
+<p>The access control setup is similar to the pairing of Bluetooth devices. When a device tries to access a remote device with the <code>conv_service_start()</code> function, a passcode pops up on the remote device screen and the user must enter that passcode on the original device. Once the passcode is entered correctly, the remote device is managed as an allowed device and a passcode is not asked for again.</p>
<p>The following figure shows the device on the left trying to access the device on the right.</p>
</pre>
<p>The structure of the listener is the same for both server and client sides.</p>
</li>
-<li>If the application sends a payload using the <code>conv_service_publish()</code> function, the listener callback in the receiver side gets the following packet:
+<li>If the application sends a payload using the <code>conv_service_publish()</code> function, the listener callback on the receiver side gets the following packet:
<pre class="prettyprint">
"result_type": "onMessage"
"from": unique ID of a client which sends the message
<p>To start the remote app control service, publish a message, and stop the service:</p>
<ol>
<li>Register a listener callback.
-<p>In the remote app control service, the application control, delivered to a remote device, is directly processed just like a local application control. It means that there is no need for a receiver to implement a special receiving routine in the remote device, and no need to register a listener callback on the receiver side. Instead, the listener callback is useful in the sender side to check whether the function is delivered to the remote device and processed correctly.</p>
+<p>In the remote app control service, the application control, delivered to a remote device, is directly processed just like a local application control. It means that there is no need for a receiver to implement a special receiving routine on the remote device, and no need to register a listener callback on the receiver side. Instead, the listener callback is useful on the sender side to check whether the function is delivered to the remote device and processed correctly.</p>
<p>The following example shows a listener callback, which handled the result of the access control process related to the remote app control service. After the user of the remote device has decided to allow or deny access with the passcode, the user choice is delivered to the remote device with the <code>"onStart"</code> result type and predefined error types:</p>
<ul><li>If the passcode is entered correctly, the <code>"onStart"</code> returns with the <code>CONV_ERROR_NONE</code> value.</li>
</pre>
</li>
<li>Start the remote app control service.
-<p>After registering the listener callback, start the service with the service handle, obtained from the near-by device discovery previously. Build an application control handle in a payload to launch an application in a remote device.</p>
+<p>After registering the listener callback, start the service with the service handle, obtained from the near-by device discovery previously. Build an application control handle in a payload to launch an application on a remote device.</p>
<p>The following example launches the <code>"org.example.d2d_test"</code> application:</p>
<pre class="prettyprint">
int
conv_service_publish(service_handle, NULL, payload_handle);
}
</pre>
-<p>The application control handle can be built <a href="../app_management/app_controls_n.htm">using the App Control functions</a>. In the payload, there is a special <code>"reply"</code> string field, which indicates if an application control reply is returned after the sent application control is processed remotely. In other words, if <code>"reply"</code> is <code>"1"</code>, the remote device processes the application control and sends the resulting application control to the original device. In this case, the listener callback in the original device waits for an application control reply. This can be useful in designing interactive applications, such as chatting applications, in which bi-directional interplay service is required. If <code>"reply"</code> is <code>"0"</code> or this field is omitted, no response is received in the listener.</p>
+<p>The application control handle can be built <a href="../app_management/app_controls_n.htm">using the App Control functions</a>. In the payload, there is a special <code>"reply"</code> string field, which indicates if an application control reply is returned after the sent application control is processed remotely. In other words, if <code>"reply"</code> is <code>"1"</code>, the remote device processes the application control and sends the resulting application control to the original device. In this case, the listener callback on the original device waits for an application control reply. This can be useful in designing interactive applications, such as chatting applications, in which bi-directional interplay service is required. If <code>"reply"</code> is <code>"0"</code> or this field is omitted, no response is received in the listener.</p>
</li>
</ol>
<p>If the client wants to access a resource whose information it already knows, it can make a proxy using the <code>iotcon_remote_resource_create()</code> function of the Remote Resource API (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__IOT__CONNECTIVITY__CLIENT__REMOTE__RESOURCE__MODULE.html">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__IOT__CONNECTIVITY__CLIENT__REMOTE__RESOURCE__MODULE.html">wearable</a> applications) and access the resource through that proxy.</p>
-<p>You can use the client to get various information about the resource through the <code>iotcon_remote_resource_h</code> handle and the <code>iotcon_remote_resource_get_XXX()</code> functions. You can retrieve, for example, the resource URI path, host address, type, and interfaces. You can also retrieve the device ID, which defines the device to which the resource belongs. Different resources in the same device have the same device ID.</p>
+<p>You can use the client to get various information about the resource through the <code>iotcon_remote_resource_h</code> handle and the <code>iotcon_remote_resource_get_XXX()</code> functions. You can retrieve, for example, the resource URI path, host address, type, and interfaces. You can also retrieve the device ID, which defines the device to which the resource belongs. Different resources on the same device have the same device ID.</p>
</li>
<li>CRUDN request and response
<ul>
<li>MTP device is a device that supports MTP. It has an MTP responder role and 1 or more MTP storages.</li>
-<li>MTP storage is the storage in the MTP device. It has zero or more MTP objects.</li>
-<li>MTP object is the actual file. Each file in the device has a unique handle called "object handle". (The handle is not unique in each storage.)
+<li>MTP storage is the storage on the MTP device. It has zero or more MTP objects.</li>
+<li>MTP object is the actual file. Each file on the device has a unique handle called "object handle". (The handle is not unique in each storage.)
<p>The MTP object has a parent object, so it can indicate a file hierarchy. If the parent object is 0, the object is in the root of the storage.</p></li>
</ul>
#include <mtp.h>
</pre>
</li>
-<li><p>Make sure that MTP is supported in your target device.</p></li>
+<li><p>Make sure that MTP is supported on your target device.</p></li>
<li>
<p>To initialize the MTP connection, call the <code>mtp_initialize()</code> function. If the function does not return an error, the MTP is ready for use.</p>
<pre class="prettyprint">
<h2 id="storages" name="storages">Getting the MTP Storages</h2>
-<p>To obtain a list of MTP storages in an MTP device, use the <code>mtp_get_storages()</code> function. To avoid memory leaks, free the storage array variable with the <code>free()</code> function when no longer needed.</p>
+<p>To obtain a list of MTP storages on an MTP device, use the <code>mtp_get_storages()</code> function. To avoid memory leaks, free the storage array variable with the <code>free()</code> function when no longer needed.</p>
<div class="note">
<strong>Note</strong>
<pre class="prettyprint">
#include <nfc.h>
</pre>
-<p>To enable and disable NFC in the device, the <code><app_control.h></code> and <code><dlog.h></code> header files have to be included.</p>
+<p>To enable and disable NFC on the device, the <code><app_control.h></code> and <code><dlog.h></code> header files have to be included.</p>
</li>
<li><p>Check whether the device you want to work with supports NFC. This can be done by calling the <code>nfc_manager_is_supported()</code> function. It takes no parameters and returns <code>true</code> if NFC is supported on the device.</p>
<div id="container"><div id="contents"><div class="content">
<h1>Smart Card</h1>
-<p>Tizen enables you to use smart card functionalities, such as accessing a secure element (SE). Before using the Smartcard API, make sure you have a secure element on the device. The smart card service allow you to open a session on an SE, open a channel to the applet in the SE, send a command to the channel, and finally receive a response to the command.</p>
+<p>Tizen enables you to use smart card functionalities, such as accessing a secure element (SE). Before using the Smartcard API, make sure you have a secure element in the device. The smart card service allows you to open a session on an SE, open a channel to the applet in the SE, send a command to the channel, and finally receive a response to the command.</p>
<p>The main components of the Smartcard API include:</p>
<div class="note">
<strong>Note</strong>
- In some Tizen devices, after a specified time, the screen is automatically switched off and the CPU goes to the resting state. If this occurs during communication with the SE using the Smartcard API, the API may not function normally.
+ On some Tizen devices, after a specified time, the screen is automatically switched off and the CPU goes to the resting state. If this occurs during communication with the SE using the Smartcard API, the API may not function normally.
<p>To avoid the screen switching off and the CPU going to the resting state, use the <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__SYSTEM__DEVICE__MODULE.html">Device</a> API to lock the device CPU (not the display):</p>
<pre class="prettyprint">
<p>The main features of the Storage API include:</p>
<ul>
- <li>Storage management <p>You can manage different storages on the device with the Storage APIs.</p> <p>You can <a href="#storage">retrieve additional information about the storages</a>, including which storage is supported
in the device using the <code>storage_foreach_device_supported()</code> function. The callback function returns the storage type, mount state, and virtual root path. You can also <a href="#memory">retrieve memory sizes</a> and <a href="#state">monitor storage state changes</a>.</p>
+ <li>Storage management <p>You can manage different storages on the device with the Storage APIs.</p> <p>You can <a href="#storage">retrieve additional information about the storages</a>, including which storage is supported
on the device using the <code>storage_foreach_device_supported()</code> function. The callback function returns the storage type, mount state, and virtual root path. You can also <a href="#memory">retrieve memory sizes</a> and <a href="#state">monitor storage state changes</a>.</p>
</li>
<li>Storage space management
<p>You can <a href="#space">get the available and total space</a> size of the storage.</p></li></ul>
<p>To retrieve storage information:</p>
<ul>
-<li>Retrieve all storages in a device using the <code>storage_foreach_device_supported()</code> function.
+<li>Retrieve all storages on a device using the <code>storage_foreach_device_supported()</code> function.
<p>The function triggers a separate callback for each storage. As long as the callback returns <code>true</code>, the foreach function continues to loop over the storages.</p>
<p>Within the callback, you can get information about the individual storage type, state, location, and ID.</p>
<ul><li>Battery information
<p>You can <a href="#battery">get battery details</a>, such as the current percentage, the charging state, and the current level state, using the Battery API (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__SYSTEM__DEVICE__BATTERY__MODULE.html">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__SYSTEM__DEVICE__BATTERY__MODULE.html">wearable</a> applications).</p></li>
<li>Device control
- <p>You can manage various components and elements in the device:</p>
+ <p>You can manage various components and elements on the device:</p>
<ul>
<li>Display
<p>You can <a href="#display">get and set display details</a>, such as the number of displays, the maximum brightness of the display, the current brightness, and the display state, using the Display API (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__SYSTEM__DEVICE__DISPLAY__MODULE.html">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__SYSTEM__DEVICE__DISPLAY__MODULE.html">wearable</a> applications).</p></li>
<p>To control an IR device:</p>
<ol>
-<li>Determine whether IR is available in the device using the <code>device_ir_is_available()</code> function:
+<li>Determine whether IR is available on the device using the <code>device_ir_is_available()</code> function:
<pre class="prettyprint">
bool avail;
int error;
<div id="container"><div id="contents"><div class="content">
<h1>Device Settings and Systems</h1>
-<p>The device settings and systems features introduce how you can set and get information about the system. You can also access information about attached devices, and display the application output in an external device screen.</p>
+<p>The device settings and systems features introduce how you can set and get information about the system. You can also access information about attached devices, and display the application output on an external device screen.</p>
<p>You can use the following device settings and systems features in your native applications:</p>
<p align="center"><img alt="Mirror mode" src="../../images/eom_mirror_mode.png" /></p>
</li>
- <li>The presentation mode can be set by an application. If the application wants to display an image or video only in an external output device, the presentation mode must be used.
+ <li>The presentation mode can be set by an application. If the application wants to display an image or video only on an external output device, the presentation mode must be used.
<p align="center"><strong>Figure: Presentation mode</strong></p>
<p align="center"><img alt="Presentation mode" src="../../images/eom_presentation_mode.png" /></p>
<li><code>eom_get_output_physical_size()</code>: Get the physical size of the external output device.</li>
</ul>
</li>
-<li>You can receive notifications about state changes in the external output device:
+<li>You can receive notifications about state changes on the external output device:
<ol>
<li>Define the callbacks for various state changes:
<pre class="prettyprint">
<li>Try to avoid writing a heavy fragment shader. If the same data apply to all fragments, do not compute the data in the fragment shader but compute them at the CPU side and provide them as uniforms. On the other hand, whenever the data can be computed at the vertex shader, use it.</li>
<li>In general, the <code>glReadPixels()</code> function is quite slow, because it reinforces CPU-GPU synchronization, drastically decreasing the overall performance. In most cases, it is possible to obtain the desired result with the framebuffer object (FBO), avoiding the use of <code>glReadPixels()</code>. With FBO, you can access the pixels of the framebuffer (the output of GPU processing) through a texture object (render-to-texture). Since it uses texture data from a GPU stage to another GPU stage, CPU does not have to be synchronized. If the application must use the <code>glReadPixels()</code>function, use another thread to avoid blocking the main thread.</li>
<li>With FBO, various effects can be made. Consider an application requiring a number of rendering chains for making a complex effect: A framebuffer is mapped to a texture, the texture is used to render another framebuffer, the framebuffer is mapped to another texture, and so on. This enables you to create a very complex scene, but unfortunately the rendering chain cannot be parallelized. Make the rendering chains as small as possible.</li>
-<li>According to the <a href="../app_management/efl_ui_app_n.htm#state_trans">application life-cycle</a>, the application gets the <code>app_pause()</code> callback when the application runs at the background. Then, you must stop calling drawcalls during the pause state.
+<li>According to the <a href="../app_management/efl_ui_app_n.htm#state_trans">application life-cycle</a>, the application gets the <code>app_pause()</code> callback when the application runs in the background. Then, you must stop calling drawcalls during the pause state.
<p>As presented in <a href="interactive_ui_n.htm">Interactive UI</a>, the application can control the rendering loop by using an animator internally and then stop the animator in the <code>app_pause()</code> callback.</p></li>
</ol>
</table>
-<p>Typically, the application is launched by the user from the Launcher, or by another application. The application is normally launched as the top window, with focus. When the application loses the focus status, the <code>SDL_APP_WILLENTERBACKGROUND</code> and <code>SDL_APP_DIDENTERBACKGROUND</code> events are invoked. The application can go into the pause state, which means that it is not terminated but continues to run on the background. The pause state can happen when:</p>
+<p>Typically, the application is launched by the user from the Launcher, or by another application. The application is normally launched as the top window, with focus. When the application loses the focus status, the <code>SDL_APP_WILLENTERBACKGROUND</code> and <code>SDL_APP_DIDENTERBACKGROUND</code> events are invoked. The application can go into the pause state, which means that it is not terminated but continues to run in the background. The pause state can happen when:</p>
<ul>
<li>A new application is launched based on a request from your application.</li>
<li>The user requests to go to the home screen.</li>
<li><a href="personal/personal_cover_n.htm">Personal Data</a>
-<p>The personal data features cover the handling of secure data related to the user. You can manage and sync user accounts, and authenticate the user to allow them to access services. You can also manage various user data in the device, such as their contact and calendar information.</p></li>
+<p>The personal data features cover the handling of secure data related to the user. You can manage and sync user accounts, and authenticate the user to allow them to access services. You can also manage various user data on the device, such as their contact and calendar information.</p></li>
<li><a href="data/data_cover_n.htm">Data Storage and Management</a>
<li><a href="device/device_cover_n.htm">Device Settings and Systems</a>
-<p>The device settings and systems features introduce how you can set and get information about the system. You can also access information about attached devices, and display the application output in an external device screen.</p></li>
+<p>The device settings and systems features introduce how you can set and get information about the system. You can also access information about attached devices, and display the application output on an external device screen.</p></li>
<li><a href="security/security_cover_n.htm">Security</a>
<li><a href="resource_localization_n.htm">Resource Localization</a>
-<p>You can load different language resources for different locales in your application. With locale-specific resources, you ensure that the user has the best possible experience regardless of the language settings selected in the device.</p></li>
+<p>You can load different language resources for different locales in your application. With locale-specific resources, you ensure that the user has the best possible experience regardless of the language settings selected on the device.</p></li>
<li><a href="phonenumber_n.htm">Phone Number Management</a>
sensor_is_supported(SENSOR_ACCELEROMETER, &supported);
if (!supported) {
- /* Accelerometer is not supported in the current device */
+ /* Accelerometer is not supported on the current device */
}
</pre>
</li>
<p>Tizen supports long-term data recording for specific sensor types. For example, it can collect pedometer data for a month, by simply requesting the device to record pedometer data:</p>
<ol>
-<li>All sensor types cannot be recorded. Check whether a sensor is supported and allows recording in the current device, before actually making the record request.
+<li>All sensor types cannot be recorded. Check whether a sensor is supported and allows recording on the current device before actually making the record request.
<pre class="prettyprint">
bool supported = false;
sensor_recorder_is_supported(SENSOR_HUMAN_PEDOMETER, &supported);
if (!supported) {
- /* Pedometer is not supported or cannot be recorded in the current device */
+ /* Pedometer is not supported or cannot be recorded on the current device */
}
</pre>
</li>
</li>
</ul>
-<p>The following gesture events are supported in Tizen devices:</p>
+<p>The following gesture events are supported on Tizen devices:</p>
<ul>
<li>Double-tap
<div id="container"><div id="contents"><div class="content">
<h1>Media Content and Metadata</h1>
-<p>The media content and metadata features introduce how you can handle media content and its metadata in your application. You can manage and search various media content in the device, such as media files, bookmarks, albums, and playlists. You can also access the MIME type information, and extract and edit the metadata of the media files.</p>
+<p>The media content and metadata features introduce how you can handle media content and its metadata in your application. You can manage and search various media content on the device, such as media files, bookmarks, albums, and playlists. You can also access the MIME type information, and extract and edit the metadata of the media files.</p>
<p>You can use the following media content and metadata features in your native applications:</p>
<h1>Media Content</h1>
- <p>You can get information about media content from the metadata in the content, such as an ID3 or MP4 tag. You can obtain or update data from the media database, which stores metadata for the media files (such as images, videos, and audio) in the device.</p>
+ <p>You can get information about media content from the metadata in the content, such as an ID3 or MP4 tag. You can obtain or update data from the media database, which stores metadata for the media files (such as images, videos, and audio) on the device.</p>
<p align="center"><strong>Figure: Media content of the device</strong></p>
<p align="center"><img alt="Media content of the device" src="../../images/content.png" /></p>
<p>The media files are updated using an application (by calling the Content API) or a media scanner. When updating the files in the media scanner, the following limitations apply:</p>
<ul><li>SD card insertion and removal: Media files are updated only in the SD card.</li>
-<li>Rebooting the device: Media files are updated in the internal memory and SD card in the device.</li></ul>
+<li>Rebooting the device: Media files are updated in the internal memory and SD card on the device.</li></ul>
<p>Media content is available to only use the files located in the specific paths. You can get the paths by using the <code>storage_get_directory()</code> function. For more information, see the Storage API (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__SYSTEM__STORAGE__MODULE.html">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__SYSTEM__STORAGE__MODULE.html">wearable</a> applications).</p>
<p>You can update database details due to file (or folder) creation or deletion. If a received file (or folder) does not exist in the file system, it is removed from the database.</p>
<p>You can also <a href="#folder_list">retrieve a list of media folders</a>, <a href="#item_list">retrieve a list of media items</a>, and <a href="#update">monitor changes</a> in the media database. In case of the media folders, you can <a href="#find">search for specific folders</a>, <a href="#read_folder">read folder information</a>, and <a href="#folder_content">retrieve folder content</a>.</p></li>
<li>Media information
-<p>You can update the media database due to file creation, deletion, or update
in the device. You can <a href="#info">retrieve media information</a>, and add <a href="#insert">media files</a> and <a href="#scan">media folders</a> to the database.</p>
+<p>You can update the media database due to file creation, deletion, or update
on the device. You can <a href="#info">retrieve media information</a>, and add <a href="#insert">media files</a> and <a href="#scan">media folders</a> to the database.</p>
<p>You can also retrieve <a href="#media_info">general information about the media more specific information about the media type</a>.</p></li>
<li>Media bookmarks
<p>You can <a href="#inserting">insert</a>, <a href="#finding">search for</a>, <a href="#reading">read</a>, and <a href="#removing">remove</a> bookmarks of the video and audio files.</p></li>
<ul>
<li><a href="media_content_metadata_n.htm">Media Content and Metadata</a>
-<p>You can manage and search various media content in the device, such as media files, bookmarks, albums, and playlists. You can also access the MIME type information, and extract and edit the metadata of the media files.</p></li>
+<p>You can manage and search various media content on the device, such as media files, bookmarks, albums, and playlists. You can also access the MIME type information, and extract and edit the metadata of the media files.</p></li>
<li><a href="image_edit_n.htm">Image Editing</a>
<h2 id="wav">WAV Player</h2>
- <p>The WAV Player API (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__MEDIA__WAV__PLAYER__MODULE.html">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__MEDIA__WAV__PLAYER__MODULE.html">wearable</a> applications) provides controlling functions for using audio resources (media files stored in the device). Use the WAV Player API to enable your application to play audio and control playback. You can use the WAV and OGG audio formats.</p>
+ <p>The WAV Player API (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__MEDIA__WAV__PLAYER__MODULE.html">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__MEDIA__WAV__PLAYER__MODULE.html">wearable</a> applications) provides controlling functions for using audio resources (media files stored on the device). Use the WAV Player API to enable your application to play audio and control playback. You can use the WAV and OGG audio formats.</p>
<p>Tizen enables your application to play wave format audio in 1 of 2 ways: </p>
<ul>
<li>Through the multimedia application control <strong>in mobile applications only</strong>
error_code = audio_out_create(SAMPLE_RATE, AUDIO_CHANNEL_MONO, AUDIO_SAMPLE_TYPE_S16_LE, SOUND_TYPE_SYSTEM, &output);
</pre>
-<p>The audio input and output devices support the channel types defined in the <code>audio_channel_e</code> enumeration (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__MEDIA__AUDIO__IO__MODULE.html#ga4e07ead99d581a0a049e8ee632b858b4">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__MEDIA__AUDIO__IO__MODULE.html#ga4e07ead99d581a0a049e8ee632b858b4">wearable</a> applications), and the sample types defined in the <code>audio_sample_type_e</code> enumeration (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__MEDIA__AUDIO__IO__MODULE.html#ga1e66f976b2890f5fc2e9e6ec71af7536">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__MEDIA__AUDIO__IO__MODULE.html#ga1e66f976b2890f5fc2e9e6ec71af7536">wearable</a> applications). For playing the recorded audio, use the same channel and sample type in both audio devices.</p>
+<p>The audio input and output devices support the channel types defined in the <code>audio_channel_e</code> enumeration (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__MEDIA__AUDIO__IO__MODULE.html#ga4e07ead99d581a0a049e8ee632b858b4">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__MEDIA__AUDIO__IO__MODULE.html#ga4e07ead99d581a0a049e8ee632b858b4">wearable</a> applications), and the sample types defined in the <code>audio_sample_type_e</code> enumeration (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__MEDIA__AUDIO__IO__MODULE.html#ga1e66f976b2890f5fc2e9e6ec71af7536">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__MEDIA__AUDIO__IO__MODULE.html#ga1e66f976b2890f5fc2e9e6ec71af7536">wearable</a> applications). For playing the recorded audio, use the same channel and sample type on both audio devices.</p>
<p>The sound types are defined in the <code>sound_type_e</code> enumeration (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__MEDIA__SOUND__MANAGER__VOLUME__MODULE.html#gab0b52eeab59765b94c7a751097738a0b">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__MEDIA__SOUND__MANAGER__VOLUME__MODULE.html#gab0b52eeab59765b94c7a751097738a0b">wearable</a> applications). You can select the sound type according to the audio sample type.</p></li>
</ol>
<ul>
<li><a href="email_n.htm">Email</a>
-<p>You can enable the user to create and send email messages, as long as the user's email account has been correctly configured in the device. You can use attachments in the messages, and monitor the sending status of the messages.</p></li>
+<p>You can enable the user to create and send email messages, as long as the user's email account has been correctly configured on the device. You can use attachments in the messages, and monitor the sending status of the messages.</p></li>
<li><a href="messages_n.htm">Messages</a>
<p>Push enables you to push events from an application server to your application on a Tizen device.</p>
- <p>Once your application is successfully registered in the push server through the <a href="#service">push service</a> (daemon) on the device, your application server can send push messages to the application in that particular device.</p>
+ <p>Once your application is successfully registered in the push server through the <a href="#service">push service</a> (daemon) on the device, your application server can send push messages to the application on that particular device.</p>
<p>When a push message arrives when the application is running, it is automatically delivered to the application. If not, the push service makes a sound or vibrates and adds a ticker or a badge notification to notify the user. By touching this notification, the user can check the message. The application server may send a message with a <code>LAUNCH</code> option. In this case, the push service forcibly launches the application and hands over the message to the application as an <a href="../app_management/app_controls_n.htm">application control</a>.</p>
<p>The main features of the Push API include:</p>
<ul>
<li>The application on the device registers for the push messaging service.</li>
<li>When an application is installed and launched, the device establishes a push session with the Tizen Server by sending a registration request to the Tizen push server through the push service.
<p>The push session is managed by the Tizen server and device platform, so there is no need to create any code to manage it within the application.</p></li>
- <li>If the registration request is approved, the application receives through the push service a registration ID. The registration ID is a unique key used to identify the application installed in that particular device and route the push message.
- <p>The application delivers the registration ID to the application server. This registration ID is used to identify the application installed in that particular device.</p></li>
+ <li>If the registration request is approved, the application receives a registration ID through the push service. The registration ID is a unique key used to identify the application installed on that particular device and route the push message.
+ <p>The application delivers the registration ID to the application server. This registration ID is used to identify the application installed on that particular device.</p></li>
<li>When the application server needs to send a push message to the application on the particular device, it calls the Tizen server's open API to send the message together with the registration ID. (For more information for server developers on sending push messages, see <a href="push_server_n.htm#send_server">Sending Push Notifications</a>.)
<p>A text message of up to 1024 bytes can be sent in a push message. If the application needs to download a large amount of data, the application server sends a link to the data in the push message.</p>
</li>
<li>If the application has already been registered, request the push service for any unread notifications that have arrived before the application is launched.
<p>Request the unread notifications asynchronously. If there is such a notification, it can be received through the <code>_noti_cb()</code> function after the <code>_on_state_registered()</code> function returns. Once the request for unread notifications is successfully delivered, <code>PUSH_SERVICE_ERROR_NONE</code> is returned.</p></li>
<li>If the application is newly registered, send the registration ID issued by the push server to your application server.
-<p>Retrieve the registration ID from the <code>push_conn</code> connection handle. If the ID is new or updated, you need to send it to your application server. This ID is used as a destination address to the application in a particular device. If the application has already sent the ID, you can skip this step. This logic is implemented in the <code>_send_reg_id_if_necessary()</code> function.</p></li>
+<p>Retrieve the registration ID from the <code>push_conn</code> connection handle. If the ID is new or updated, you need to send it to your application server. This ID is used as a destination address to the application on a particular device. If the application has already sent the ID, you can skip this step. This logic is implemented in the <code>_send_reg_id_if_necessary()</code> function.</p></li>
</ul>
<pre class="prettyprint">
<li>Prepare the appID, appSecret, regID, and requestID:
<ul>
<li>The appID and appSecret values are from the email that you received when requesting <a href="#permission">permission to Tizen push servers</a>.</li>
-<li>The regID value is the one that the application server received from your application installed in a Tizen device. Depending on the regID value, the URI of the server to which your application server sends the notification varies.</li>
+<li>The regID value is the one that the application server received from your application installed on a Tizen device. Depending on the regID value, the URI of the server to which your application server sends the notification varies.</li>
<li>The requestID value is used to identify the notification in the push server. When your application server sends notifications using the same requestID value, the last notification overwrites all the previous notifications that are not delivered yet.</li>
</ul>
</li>
<pre class="prettyprint">
"action=LAUNCH"
</pre>
-<p>When the push service
in the target device receives a notification with this message, it launches your application and delivers the notification through an <a href="../../../../org.tizen.guides/html/native/app_management/app_controls_n.htm">Application Controls</a>. Your application can get the notification using the <code>push_service_app_control_to_notification()</code> function. For more information, see how to <a href="#recv_noti_app_not_run">receive notifications when the application is not running</a>.</p>
+<p>When the push service
on the target device receives a notification with this message, it launches your application and delivers the notification through an <a href="../../../../org.tizen.guides/html/native/app_management/app_controls_n.htm">application control</a>. Your application can get the notification using the <code>push_service_app_control_to_notification()</code> function. For more information, see how to <a href="#recv_noti_app_not_run">receive notifications when the application is not running</a>.</p>
<p>The message field takes effect only when the application is not running (more precisely, when the application is not connected to the push service). If a notification with the above message field arrives at the device where the application is running, the push service delivers the notification directly to the application. It does not show the "Hi" message in the quick panel or increase the badge count.</p>
</li>
<h2 id="send_server" name="send_server">Sending Push Notifications</h2>
-<p>Using the Tizen Push APIs, you can send notifications to your applications installed
in Tizen devices. The basics of sending push notification are covered in the <a href="push_n.htm#send">Sending Push Notifications</a>. This use case covers more advanced information, such as sending multiple notifications in one request and sending multicast notifications.</p>
+<p>Using the Tizen Push APIs, you can send notifications to your applications installed
on Tizen devices. The basics of sending push notification are covered in the <a href="push_n.htm#send">Sending Push Notifications</a>. This use case covers more advanced information, such as sending multiple notifications in one request and sending multicast notifications.</p>
<p>To send push notifications:</p>
<tr>
<td><code>regID</code></td>
- <td>Distinguish a recipient from other recipients by assigning a unique registration ID to each recipient. <p>The registration ID is assigned when the application is installed in a device and marked to use an application service.</p>
+ <td>Distinguish a recipient from other recipients by assigning a unique registration ID to each recipient. <p>The registration ID is assigned when the application is installed on a device and marked to use an application service.</p>
<p>The current registration ID passing policy is as follows (it can change in the future):</p>
<ol type="a">
<li>The preloaded push service connects to the push server and registers the application.</li>
<p>Tizen 2.4 introduces new APIs for applications and modifies the behavior of some APIs to improve the quality of the platform. The following sections define the issues you must consider to make your application conform to Tizen 2.4 Application Framework APIs.</p>
<h2 id="bg_app" name="bg_app">New Background Application Policy</h2>
-<p>Since Tizen 2.4, the application on the background goes into a suspended state.</p>
-<p>In the suspended state, the application process is executed with limited CPU resources. In other words, the platform does not allow the running of the background applications, except for some exceptional applications (such as Media and Download) that necessarily work on the background. In this case, the application can designate their background category as an allowed category to avoid going into the suspended state.</p>
-<p>For more information, and a list of background categories that allow the application to run
on the background, see <a href="app_management/efl_ui_app_n.htm#allow_bg">Background Categories</a>.</p>
+<p>Since Tizen 2.4, an application in the background goes into a suspended state.</p>
+<p>In the suspended state, the application process is executed with limited CPU resources. In other words, the platform does not allow the running of the background applications, except for some exceptional applications (such as Media and Download) that necessarily work in the background. In this case, the application can designate their background category as an allowed category to avoid going into the suspended state.</p>
+<p>For more information, and a list of background categories that allow the application to run
in the background, see <a href="app_management/efl_ui_app_n.htm#allow_bg">Background Categories</a>.</p>
<p>You can receive an event when the background application goes to the suspended state. Pass <code>APP_EVENT_SUSPENDED_STATE_CHANGED</code> as <code>event_type</code> to the <code>ui_app_add_event_handler()</code> or <code>service_app_add_event_handler()</code> function to handle the suspended event. You must release the resources properly when your application goes to the suspended state.</p>
<p><code>CONTEXT_HISTORY_COMMON_SETTING_FOR_APP</code></p>
</td>
<td>
- The contextual history contains data on which applications are used in the foreground. From this data, the following statistics are provided:
+ The contextual history contains data on which applications are used on the foreground. From this data, the following statistics are provided:
<ul>
<li>Most recently or frequently used applications, in a descending order of the application use counts.</li>
<li>Most rarely used applications in removable applications, in an ascending order of the application use counts.</li>
<td><code>CONTEXT_HISTORY_TOTAL_COUNT</code></td>
<td>Integer</td>
<td>
- This attribute denotes how many times the application is used in the foreground.
+ This attribute denotes how many times the application is used on the foreground.
</td>
</tr>
<tr>
<td><code>CONTEXT_HISTORY_TOTAL_DURATION</code></td>
<td>Integer</td>
<td>
- This attribute denotes the time the application is being displayed in the foreground in seconds. If the application is used multiple times, it denotes the accumulated time of use.
+ This attribute denotes the time the application is being displayed on the foreground in seconds. If the application is used multiple times, it denotes the accumulated time of use.
</td>
</tr>
<tr>
<li>The Tizen application process can write a file to the path that is returned by the <code>app_get_data_path()</code> function.
<p>Because the application data path is created for each application package, the applications in the same package can share files in the data path. This is a totally secure file sharing method, because applications in the same package are trusted applications.</p></li>
-<li>Tizen applications can write a file to the path that is returned by the <code>app_get_shared_data_path()</code> function, and share the file among all other applications in the device.
-<p>The files in the shared data path can be read by all other applications in the device. Since you cannot control which applications are able to read the file in the shared data path, do not share private information in this way. Sharing data among applications through the shared data path is insecure, and consequently the shared data path is going to be deprecated in the next Tizen release.</p>
+<li>Tizen applications can write a file to the path that is returned by the <code>app_get_shared_data_path()</code> function, and share the file among all other applications on the device.
+<p>The files in the shared data path can be read by all other applications on the device. Since you cannot control which applications are able to read the file in the shared data path, do not share private information in this way. Sharing data among applications through the shared data path is insecure, and consequently the shared data path is going to be deprecated in the next Tizen release.</p>
<p>As an alternative to the shared data path, Tizen 2.4 introduced a feature of sharing a file in its data path using application controls. When an application requests an application control, it can specify a URI and the <code>APP_CONTROL_DATA_PATH</code> extra key. If you pass the file path to the application control as the <code>APP_CONTROL_DATA_PATH</code> extra key, the platform grants temporary read permission to the receiving application. This method is much more secure than sharing a file in the shared data path.</p>
</li>
<li>To share files among applications that you have developed, use the path that is returned by the <code>app_get_shared_trusted_path()</code> function.
</tr>
<tr>
<td><code>app_get_shared_data_path()</code></td>
- <td><ul><li>Read: all application in the device</li>
+ <td><ul><li>Read: all applications on the device</li>
<li>Write: applications in the same package</li></ul></td>
<td>Weak
<p>Do not use this function if you are not sure about its security.</p></td>
<li>Voice control service state
<p>The user controls the state by starting and stopping command recognition.</p></li>
<li>Current language
-<p>A command is valid only when the command language is the same as the current language. The current language can be changed by changing the application or display language in the device.</p>
+<p>A command is valid only when the command language is the same as the current language. The current language can be changed by changing the application or display language on the device.</p>
<p>You can get a notification of the language change in a callback. If the display language is changed to a non-supported one, the voice control language changed to English.</p></li>
<li>Supported language
<p>You can retrieve a list of supported languages to check whether the language that you want is supported.</p></li></ul>
<script type="text/javascript" src="../../../scripts/common.js" charset="utf-8"></script>
<script type="text/javascript" src="../../../scripts/core.js" charset="utf-8"></script>
<script type="text/javascript" src="../../../scripts/search.js" charset="utf-8"></script>
- <title>Configuring Accessibility in a Device</title>
+ <title>Configuring Accessibility on a Device</title>
</head>
<body onload="prettyPrint()" style="overflow: auto;">
<div id="container"><div id="contents"><div class="content">
- <h1>Configuring Accessibility in a Device</h1>
+ <h1>Configuring Accessibility on a Device</h1>
<p>Tizen provides the following accessibility features:</p>
<ul><li><strong>Font size</strong>
<h2 id="create" name="create">Creating an Accessible Application</h2>
-<p>You can use the mobile native <a href="https://developer.tizen.org/development/sample/native/UI/UI_Components" target="_blank">UI Components</a> sample application provided within the Tizen Studio to see how the most important accessibility features are implemented in practice. The sample application contains an AT-SPI2 compliant screen reader, which you can use to test the accessibility features in a device. Enable the screen reader by running the sample application and selecting <strong>Accessibility > Screen Reader > Screen Reader (TTS)</strong>.</p>
+<p>You can use the mobile native <a href="https://developer.tizen.org/development/sample/native/UI/UI_Components" target="_blank">UI Components</a> sample application provided within the Tizen Studio to see how the most important accessibility features are implemented in practice. The sample application contains an AT-SPI2 compliant screen reader, which you can use to test the accessibility features on a device. Enable the screen reader by running the sample application and selecting <strong>Accessibility > Screen Reader > Screen Reader (TTS)</strong>.</p>
<p>In the Tizen 2.4 release, the screen reader is available only inside the UI Components application. This means that when the UI Components application is terminated or paused and sent to the background, the screen reader is automatically disabled, and when the UI Components application is restored, the screen reader is enabled.</p>
<p align="center"><strong>Figure: UI Components sample application</strong></p>
<ul>
<li><a href="accessibility_architecture_n.htm">Accessibility Architecture</a>
<p>The accessibility implementation for Tizen platform is based on the Elementary ATSPI, which enables applications to interact with graphical Elementary components visible on the screen. For example, a screen reader can access the text in the labels and descriptions of any application running on the screen and read it to the user.</p></li>
- <li><a href="accessibility_config_n.htm">Configuring Accessibility in a Device</a>
+ <li><a href="accessibility_config_n.htm">Configuring Accessibility on a Device</a>
<p>Tizen provides 2 accessibility features primarily aimed at low-vision and visually-impaired users. These accessibility solutions allow you to adjust the font size on the Tizen device and to use the built-in screen reader application.</p></li>
<li><a href="accessibility_implementation_n.htm">Implementing Accessible Applications</a>
<p>You can make your application accessible by following good accessibility practices. Using an EFL Elementary sample application, you can see in practice how to implement readable components for the Screen Reader, and customize the UI reading order and the highlight frame appearance.</p></li>
<p>When the user presses the <strong>Menu</strong> or <strong>Back</strong> key, the key generates a signal with its key property. The Ecore library receives the signal and propagates it to the application layers as an event. The EFL Extension library consumes the events and handles the views of the application according to key properties. </p>
</li>
<li><a href="rotary_events_wn.htm">Managing Rotary Events</a> <strong>in wearable applications only</strong>
-<p>The Tizen platform supports rotary events for user interaction on a wearable rotary device or sensor. The rotary device can rotate clockwise or counter-clockwise, and dispatch an event for each movement. EFL Extension manages the rotary events, which are generated from rotary components in wearable devices and delivered to application layers by defining an event callback or a handler function, and registering it.</p></li>
+<p>The Tizen platform supports rotary events for user interaction on a wearable rotary device or sensor. The rotary device can rotate clockwise or counter-clockwise, and dispatch an event for each movement. EFL Extension manages the rotary events, which are generated from rotary components on wearable devices and delivered to application layers by defining an event callback or a handler function, and registering it.</p></li>
<li><a href="key_grab_n.htm">Grabbing Hardware Key Events</a>
<p>Normally, the hardware keys do only what they are designed to do, such as increase the volume or return to the previous screen. In some applications, you can assign special actions to hardware keys. For example, the volume key can be used to increase and decrease the size of the text. This is called key grabbing.</p>
<li id="base_scale"><code>base_scale: [scale factor]</code>
<p>Sets information about the scale factor in the EDC file.</p>
-<p>Object scaling must be defined in the <code>config.xml</code> file of the application to show the application in a proper size in other devices. However, the scaling must be based on the scale 1.0. If the application is based on another scale, this scale must be defined in the <code>config.xml</code> file. This predefined scale is called the base scale.</p>
+<p>Object scaling must be defined in the <code>config.xml</code> file of the application to show the application in a proper size on other devices. However, the scaling must be based on the scale 1.0. If the application is based on another scale, this scale must be defined in the <code>config.xml</code> file. This predefined scale is called the base scale.</p>
-<p>The size of a scalable object is multiplied with the device scale value. If the scalable object with the size 10 is created in a device with the scale 1.0, the size of the object is 20 in a device with the scale 2.0, and 40 in a device with the scale 4.0.</p>
+<p>The size of a scalable object is multiplied with the device scale value. If the scalable object with the size 10 is created on a device with scale 1.0, the size of the object is 20 on a device with scale 2.0, and 40 on a device with scale 4.0.</p>
<p>For more information on supporting multiple screens in one EDC, see the <a href="multiple_screens_n.htm">Multiple Screen Support</a> guide.</p>
</li>
<h1>Multiple Screen Support</h1>
- <p>Tizen is available in various devices, which support different screen sizes and resolutions. When developing Tizen applications, you must take this into account if you want your application to function well in various device models.</p>
+ <p>Tizen is available on various devices, which support different screen sizes and resolutions. When developing Tizen applications, you must take this into account if you want your application to function well on various device models.</p>
<p>Before <a href="#apply">implementing multiple screen support</a>, make sure you are familiar with the <a href="#key_concepts">key concepts of multiple screen support</a>.</p>
<h2 id="key_concepts" name="key_concepts">Key Concepts</h2>
<p>Scale 1.0 in the Tizen native UI framework means that the application is displayed in a set size and is not scaled. Scale 1.0 is used in a display environment, such as a desktop. In the desktop environment, the monitor has a resolution between 1280 x 800 and 1920 x 1080, with a size between 20 and 27 inch, and the DPI between 80 and 100.</p>
- <p>If an application is scaled up or down after implementing it in a desktop environment, it can be used in another device without modifying the code. Each device has a proper scale value for adjusting the application size. Edje, which handles layout and themes in the Tizen native UI framework, gets the size of an object by multiplying the application-specified size with the device-specific scale value.</p>
+ <p>If an application is scaled up or down after implementing it in a desktop environment, it can be used on another device without modifying the code. Each device has a proper scale value for adjusting the application size. Edje, which handles layout and themes in the Tizen native UI framework, gets the size of an object by multiplying the application-specified size with the device-specific scale value.</p>
<p>The following figure illustrates a 50 px wide object in a 1280 px wide monitor. If the same object is displayed without scaling in a mobile environment, it looks very small. To show the object in the mobile environment with a similar size as in the monitor, a device-specific scale value of 2.0 is used, resulting in the object size of 100 px instead of 50 px.</p>
<p align="center"><img alt="Scaling from desktop to mobile" src="../../../images/scaling.png" /> </p>
<h3 id="base" name="base">Base Scale</h3>
- <p>The object is multiplied by the scale specified in the system to show the application in a proper size
in other devices. The scaling must be based on the scale 1.0, or the scale that the application is based on, which must then be defined in the <a href="#set_edc">EDC</a> and <a href="#set_c">C</a> files. This predefined scale is called the <strong>base scale</strong>.</p>
+ <p>The object is multiplied by the scale specified in the system to show the application in a proper size
on other devices. The scaling must be based on the scale 1.0, or the scale that the application is based on, which must then be defined in the <a href="#set_edc">EDC</a> and <a href="#set_c">C</a> files. This predefined scale is called the <strong>base scale</strong>.</p>
- <p>The size of the scalable object is multiplied with the device scale value, as illustrated in the following figure. If the scalable object has a size of 10 in the base scale 1.0, it is created with that same size 10 in a device with the scale 1.0. In a device with the scale 2.0, the object size is 20; and in a device with the scale 4.0, the object size is 40.</p>
+ <p>The size of the scalable object is multiplied with the device scale value, as illustrated in the following figure. If the scalable object has a size of 10 in the base scale 1.0, it is created with that same size 10 on a device with scale 1.0. On a device with scale 2.0, the object size is 20, and on a device with scale 4.0, the object size is 40.</p>
<p align="center"><strong>Figure: Base scale</strong></p>
<p align="center"><img alt="Base scale" src="../../../images/base_scale.png" /> </p>
- <p>The middle object in the above figure has a base scale 2.0. To calculate the size of the scalable object in a device when the base scale is something other than 1.0, use the following formula:</p>
+ <p>The middle object in the above figure has a base scale 2.0. To calculate the size of the scalable object on a device when the base scale is something other than 1.0, use the following formula:</p>
<pre class="prettyprint">
-scale = device_scale (information in the target device) / base_scale (information in the application)
+scale = device_scale (information on the target device) / base_scale (information in the application)
</pre>
-<p>For example, to calculate the size of the scalable object in a device with the scale 4.0 when the base scale in the application is 2.0:</p>
+<p>For example, to calculate the size of a scalable object on a device with scale 4.0 when the base scale in the application is 2.0:</p>
<p>4.0 / 2.0 = 2.0</p>
-<p>Basically, if the object size is 20 with the base scale 2.0, the object size in a device with the scale 4.0 must be 20 * 2.0 = 40.</p>
+<p>Basically, if the object size is 20 with base scale 2.0, the object size on a device with scale 4.0 must be 20 * 2.0 = 40.</p>
<h2 id="apply" name="apply">Applying the Base Scale</h2>
<p>To create an application that supports multiple screen sizes, you must learn how to set the base scale in:</p>
<div id="container"><div id="contents"><div class="content">
<h1>Scalability Support</h1>
- <p>To ensure that your application works well in diverse devices, you must consider scalability when designing the application layout:</p>
+ <p>To ensure that your application works well on diverse devices, you must consider scalability when designing the application layout:</p>
<ul>
<li><a href="#key">Key concepts</a></li>
<li><a href="#elementary">Scalability using Elementary UI components</a></li>
<p align="center"><strong>Figure: Box layout</strong></p>
<p align="center"> <img alt="Box layout" src="../../../images/scale_box.png" /> </p>
-<p>The box-based linear layout is the best solution to ensure a minimum size for the child UI components in any device or any orientation.</p></li>
+<p>The box-based linear layout is the best solution to ensure a minimum size for the child UI components on any device or any orientation.</p></li>
<li>Grid
<p align="center"><strong>Figure: Grid layout</strong></p>
<p align="center"> <img alt="Grid layout" src="../../../images/scale_grid.png" /> </p>
-<p>The grid-based relative layout can always fill the full screen in any device or any orientation. However, the size of the child UI components is changed based on the screen size.</p></li></ul>
+<p>The grid-based relative layout can always fill the full screen on any device or any orientation. However, the size of the child UI components is changed based on the screen size.</p></li></ul>
<h3>Using Weight and Align Properties</h3>
<ul><li>Fixed parts have a minimum size (at least width or height).</li>
<li>When the part <code>scale</code> property is set to 1 (on), the scaling factor has an effect on the minimum size.</li>
-<li>Fixed parts are used when the parts must keep a fixed size in any device or any orientation.</li></ul></li>
+<li>Fixed parts are used when the parts must keep a fixed size on any device or any orientation.</li></ul></li>
<li>Flexible parts
<ul><li>Flexible parts resize according to the container size and other fixed parts' size.</li>
-<li>Flexible parts are used when the parts can be resized in any device or any orientation.</li></ul></li></ul>
+<li>Flexible parts are used when the parts can be resized on any device or any orientation.</li></ul></li></ul>
<p align="center"><strong>Figure: Fixed and flexible parts</strong></p>
<p align="center"> <img alt="Fixed and flexible parts" src="../../../images/scale_fixed_flexible.png" /> </p>
<h2 id="aspect" name="aspect">Aspect Ratio</h2>
<p>In Tizen, the application generally fills out the screen. However, sometimes you want the application to be shown in a specific aspect ratio, regardless of the screen size.</p>
-<p>As images are scaled in different devices, they are resized based on the container size. The images have specific properties that define the area to be shown when resized.</p>
+<p>As images are scaled on different devices, they are resized based on the container size. The images have specific properties that define the area to be shown when resized.</p>
<p>For example, the following table illustrates what happens to the parts marked with yellow rectangles in the following figure, when scaling properties are applied. in the table, the red dashed rectangle illustrates the container size.</p>
</tbody>
</table>
-<p>The following UI components are designed for specific circular wearable devices which have rotary component parts.
In a circular device, you can draw round UI components, such as a slider, progressbar, and scroller. Generally, wearable UI components provide compatibility between the rectangular and circular wearable devices. However, use circular UI components for circular wearable devices only, because they have a dependency with the round UX and rotary events. For more information on the compatibility of the UI components between rectangular and circular, see the <a href="https://developer.tizen.org/design/wearable" target="_blank">Wearable Design</a> guidelines.</p>
+<p>The following UI components are designed for specific circular wearable devices which have rotary component parts.
On a circular device, you can draw round UI components, such as a slider, progressbar, and scroller. Generally, wearable UI components provide compatibility between the rectangular and circular wearable devices. However, use circular UI components for circular wearable devices only, because they have a dependency with the round UX and rotary events. For more information on the compatibility of the UI components between rectangular and circular, see the <a href="https://developer.tizen.org/design/wearable" target="_blank">Wearable Design</a> guidelines.</p>
<p align="center" class="Table"><strong>Table: Available circular UI components</strong></p>
<table border="1">
<h2 id="background_category" name="background_category">Background Execution</h2>
-<p>When a Web application becomes invisible (moves to the background), it is suspended. Before Tizen 2.4, to continue to execute the application
on the background, you had to set the <code>background-support</code> attribute of the <code><tizen:setting></code> element to <code>enable</code> in the <code>config.xml</code> file (in <a href="../../../../org.tizen.studio/html/web_tools/config_editor_w.htm#mw_setting">mobile</a> and <a href="../../../../org.tizen.studio/html/web_tools/config_editor_w.htm#ww_setting">wearable</a> applications).</p>
+<p>When a Web application becomes invisible (moves to the background), it is suspended. Before Tizen 2.4, to continue to execute the application
in the background, you had to set the <code>background-support</code> attribute of the <code><tizen:setting></code> element to <code>enable</code> in the <code>config.xml</code> file (in <a href="../../../../org.tizen.studio/html/web_tools/config_editor_w.htm#mw_setting">mobile</a> and <a href="../../../../org.tizen.studio/html/web_tools/config_editor_w.htm#ww_setting">wearable</a> applications).</p>
-<p>Since Tizen 2.4, the background process management policy has been changed. The system does not allow applications to run
on the background except when they are explicitly declared to do so by having a specific background category. For more information on the available background categories, see the <a href="../../native/app_management/efl_ui_app_n.htm#allow_bg_table">Allowed background application policy</a> table.</p>
+<p>Since Tizen 2.4, the background process management policy has been changed. The system does not allow applications to run
in the background except when they are explicitly declared to do so by having a specific background category. For more information on the available background categories, see the <a href="../../native/app_management/efl_ui_app_n.htm#allow_bg_table">Allowed background application policy</a> table.</p>
<div class="note">
<strong>Note</strong>
- To guarantee that a Web application runs
on the background, at least one <code>background-category</code> element must be declared in the <code>config.xml</code> file (in <a href="../../../../org.tizen.studio/html/web_tools/config_editor_w.htm#mw_bg_category">mobile</a> and <a href="../../../../org.tizen.studio/html/web_tools/config_editor_w.htm#ww_bg_category">wearable</a> applications), and the <code>background-support</code> attribute of the <code><tizen:setting></code> element must be set to <code>enable</code>.
+ To guarantee that a Web application runs
in the background, at least one <code>background-category</code> element must be declared in the <code>config.xml</code> file (in <a href="../../../../org.tizen.studio/html/web_tools/config_editor_w.htm#mw_bg_category">mobile</a> and <a href="../../../../org.tizen.studio/html/web_tools/config_editor_w.htm#ww_bg_category">wearable</a> applications), and the <code>background-support</code> attribute of the <code><tizen:setting></code> element must be set to <code>enable</code>.
</div>
-<p>The following <code>config.xml</code> file example shows how an application can be configured to run on the background:</p>
+<p>The following <code>config.xml</code> file example shows how an application can be configured to run in the background:</p>
<pre class="prettyprint">
<?xml version="1.0" encoding="UTF-8"?>
<widget xmlns="http://www.w3.org/ns/widgets" xmlns:tizen="http://tizen.org/ns/widgets"
<ul>
<li><a href="applications_w.htm">Applications</a>
-<p>You can manage applications and get information about them. You can also handle events and enable an application to run on the background.</p>
+<p>You can manage applications and get information about them. You can also handle events and enable an application to run in the background.</p>
-<p>Tizen provides various application models to allow you to create applications targeted for specific tasks. You can create UI applications to run on the foreground, and service applications to run on the background. The service application is used to perform tasks which need to run periodically or continuously but do not require user interaction.</p></li>
+<p>Tizen provides various application models to allow you to create applications targeted for specific tasks. You can create UI applications to run on the foreground, and service applications to run in the background. The service application is used to perform tasks which need to run periodically or continuously but do not require user interaction.</p></li>
<li><a href="app_group_w.htm">Application Groups</a>
<p>A service application is a type of Tizen Web application that provides an environment for running JavaScript in the background without a graphical user interface (the application follows the <a href="http://www.ecma-international.org/publications/standards/Ecma-262.htm" target="_blank">ECMA-262 specification</a>). The service application is used to perform tasks which need to run periodically or continuously but do not require user interaction. For example, a service application can be used for getting data or listening to platform events in the background. As service applications do not have UI components, they run on top of a more light-weight runtime than UI applications. Therefore, you can expect them to perform better and consume less memory.</p>
-<p>This feature is supported in wearable applications only. The Web service application is an optional feature, which means that it may not be supported in all wearable devices.</p>
+<p>This feature is supported in wearable applications only. The Web service application is an optional feature, which means that it may not be supported on all wearable devices.</p>
<p>The main features of the service application include:</p>
<p>To send data between the devices, use a socket mechanism with the <code>BluetoothSocket</code> interface. The proper socket is received when the devices are connected.</p></li>
-<li><p>To read the data in the server device, use the <code>readData()</code> method:</p>
+<li><p>To read the data on the server device, use the <code>readData()</code> method:</p>
<pre class="prettyprint">
var data = socket.readData();
<li><a href="secure_element_w.htm">Secure Element Access</a> <strong>in mobile and wearable applications only</strong>
-<p>You can access secure elements, such as SIM card and secure SD card, in a device.</p></li>
+<p>You can access secure elements, such as a SIM card or a secure SD card, on a device.</p></li>
<li><a href="download_w.htm">Content Downloads</a>
<li>Service discovery
<p>You can <a href="#Discovering_Devices">discover all Convergence services</a> supported by nearby devices.</p></li>
<li>Remote communication
- <p>You can implement <a href="#Communication_Service">communication between applications</a> in remote devices.</p></li>
+ <p>You can implement <a href="#Communication_Service">communication between applications</a> on remote devices.</p></li>
<li>Remote launch and actions
<p>You can <a href="#Launch_App">launch applications remotely</a>, and <a href="#App_Control">request them to take specific actions</a>.</p></li>
</ul>
<p>You can spawn 2 types of instances: server and client. Typically, the client finds available server services through a discovery, establishes a connection with one of the servers, and launches an application on the server side. The server cannot launch an application on the client side. Both the client and server can exchange text messages and binary payloads.</p>
<div class="note">
<strong>Note</strong>
- The server for the AppCommunicationService can only be implemented in a TV device based on Tizen 3.0. You can develop a mobile or wearable client for the AppCommunicationService, if a server exists.
+ The server for the AppCommunicationService can only be implemented on a TV device based on Tizen 3.0. You can develop a mobile or wearable client for the AppCommunicationService, if a server exists.
</div>
</li>
<li>RemoteAppControlService
<div class="note">
<strong>Note</strong>
- If an application is on the background and uses the <code>sendNDEF()</code> method, an error callback is launched. This method can only be used in the foreground.
+ If an application is in the background and uses the <code>sendNDEF()</code> method, an error callback is launched. This method can only be used on the foreground.
</div>
<h2 id="Exchanging_NDEF_Tags" name="Exchanging_NDEF_Tags">Exchanging NDEF Data with Tags</h2>
<div class="note">
<strong>Note</strong>
- If an application is on the background and uses the <code>writeNDEF()</code> or <code>transceive()</code> method, an error callback is launched. These methods can only be used in the foreground.
+ If an application is in the background and uses the <code>writeNDEF()</code> or <code>transceive()</code> method, an error callback is launched. These methods can only be used on the foreground.
</div>
<h2 id="Using_NFC_Card_Emulation" name="Using_NFC_Card_Emulation">Using NFC Card Emulation</h2>
<li><a href="personal/personal_cover_w.htm">Personal Data</a> <strong>in mobile applications only</strong>
-<p>The personal data features cover the handling of secure data related to the user. You can manage and sync user accounts, and handle call history and bookmarks. You can also manage various user data in the device, such as contact and calendar information.</p></li>
+<p>The personal data features cover the handling of secure data related to the user. You can manage and sync user accounts, and handle call history and bookmarks. You can also manage various user data on the device, such as contact and calendar information.</p></li>
<li><a href="data/data_cover_w.htm">Data Storage and Management</a>
<div class="note">
<strong>Note</strong>
In Tizen Web Device APIs, there are 2 types of APIs: mandatory and optional.
-<p>The mandatory APIs are always available on all Tizen devices. The optional APIs provide functionality that depends on the available device hardware or software capabilities, and they may not be available in all Tizen devices. For example, the Bluetooth and NFC API hardware features are optional, and not supported on all devices.</p>
+<p>The mandatory APIs are always available on all Tizen devices. The optional APIs provide functionality that depends on the available device hardware or software capabilities, and they may not be available on all Tizen devices. For example, the Bluetooth and NFC API hardware features are optional, and not supported on all devices.</p>
<p>To determine the availability of optional APIs, use the <code>tizen.systeminfo.getCapability()</code> method of the System Information API (in <a href="../../../org.tizen.web.apireference/html/device_api/mobile/tizen/systeminfo.html#SystemInfo">mobile</a> and <a href="../../../org.tizen.web.apireference/html/device_api/wearable/tizen/systeminfo.html#SystemInfo">wearable</a> applications).</p>
<p>Note that all mandatory APIs are supported on the Tizen Emulators, while the optional APIs may or may not be supported. For more information on support for each API, see <a href="../../../org.tizen.web.apireference/html/device_api/device_api_cover.html">Tizen Web Device API Reference</a>.</p>
</div>
<p>The following figure shows the layout of the progress bar component in a rectangular and circular UI.</p>
-<p align="center"><strong>Figure: Circle-shaped progress bar component in rectangular and circular devices</strong></p>
- <p align="center"><img alt="Circle-shaped progress bar component in a rectangular device" src="../../../images/rectangular_progress.png" /> <img alt="Circle-shaped progress bar component in a circular device" src="../../../images/round_progress.png" /></p>
+<p align="center"><strong>Figure: Circle-shaped progress bar component on rectangular and circular devices</strong></p>
+ <p align="center"><img alt="Circle-shaped progress bar component on a rectangular device" src="../../../images/rectangular_progress.png" /> <img alt="Circle-shaped progress bar component on a circular device" src="../../../images/round_progress.png" /></p>
<p>To implement the progress bar component:</p>
</pre>
<p>The following figure shows how the media query <code>-tizen-geometric-shape: circle</code> works in a rectangular and circular UI.</p>
-<p align="center"><strong>Figure: Media query in a rectangular device and circular device</strong></p>
+<p align="center"><strong>Figure: Media query on rectangular and circular devices</strong></p>
<p align="center">
- <img alt="Media query in a rectangular device and circular device" src="../../../images/circular_support.png" />
+ <img alt="Media query on rectangular and circular devices" src="../../../images/circular_support.png" />
</p>
<h2 id="incss">Overriding the Circular CSS Style with a Media Query</h2>
-<p>For some styles to be applied selectively, you can use the <code>-tizen-geometric-shape</code> media query feature with a <code>rectangle</code> or <code>circle</code> value to distinguish the type difference. Note that the <code>-tizen-geometric-shape</code> feature is only available in Tizen devices.</p>
+<p>For some styles to be applied selectively, you can use the <code>-tizen-geometric-shape</code> media query feature with a <code>rectangle</code> or <code>circle</code> value to distinguish the type difference. Note that the <code>-tizen-geometric-shape</code> feature is only available on Tizen devices.</p>
<p align="center" class="Table"><strong>Table: <code>-tizen-geometric-shape</code> feature description</strong></p>
</pre>
<h2 id="components">Supported UI Components</h2>
-<p>The following components can be used in both rectangular and circular devices.</p>
+<p>The following components can be used on both rectangular and circular devices.</p>
<p align="center" class="Table"><strong>Table: UI components supported by a rectangular and circular UI</strong></p>
<table>
<p>This feature is supported in wearable applications only.</p>
<p>The following figures show the layout of the footer button component in a rectangular and circular UI.</p>
-<p align="center"><strong>Figure: Footer button component in rectangular and circular devices</strong></p>
- <p align="center"><img alt="Footer button in a rectangular device" src="../../../images/rectangular_footer.png"/> <img alt="Footer button in a circular device" src="../../../images/round_footer.png"/></p>
+<p align="center"><strong>Figure: Footer button component on rectangular and circular devices</strong></p>
+ <p align="center"><img alt="Footer button on a rectangular device" src="../../../images/rectangular_footer.png"/> <img alt="Footer button on a circular device" src="../../../images/round_footer.png"/></p>
-<p align="center"><strong>Figure: Multiple footer buttons in rectangular and circular devices</strong></p>
- <p align="center"><img alt="Multiple footer buttons in a rectangular device" src="../../../images/rectangular_multibtn.png"/> <img alt="Multiple footer buttons in a circular device" src="../../../images/round_multibtn.png"/></p>
+<p align="center"><strong>Figure: Multiple footer buttons on rectangular and circular devices</strong></p>
+ <p align="center"><img alt="Multiple footer buttons on a rectangular device" src="../../../images/rectangular_multibtn.png"/> <img alt="Multiple footer buttons on a circular device" src="../../../images/round_multibtn.png"/></p>
<p>The footer button on the circular UI has the <code>ui-bottom-button</code> class. When there are multiple buttons, the other buttons except for the first button use the drawer component in the circular UI.</p>
<p>The following figure shows the layout of the header component in a rectangular and circular UI.</p>
-<p align="center"><strong>Figure: Header component in rectangular and circular devices</strong></p>
-<p align="center"><img alt="Header component in a rectangular device" src="../../../images/rectangular_header.png" /> <img alt="Header component in a circular device" src="../../../images/round_header.png" /></p>
+<p align="center"><strong>Figure: Header component on rectangular and circular devices</strong></p>
+<p align="center"><img alt="Header component on a rectangular device" src="../../../images/rectangular_header.png" /> <img alt="Header component on a circular device" src="../../../images/round_header.png" /></p>
<p>To implement the header component, edit the HTML code to add the header component to your application screen:</p>
<pre class="prettyprint">
<p>The following figure shows the layout of the index scroll bar component in a rectangular and circular UI.</p>
-<p align="center"><strong>Figure: Index scroll bar component in rectangular and circular devices</strong></p>
-<p align="center"><img alt="Index scroll bar component in a rectangular device" src="../../../images/rectangular_index.png" /> <img alt="Index scroll bar component in a circular device" src="../../../images/round_index.png" /></p>
+<p align="center"><strong>Figure: Index scroll bar component on rectangular and circular devices</strong></p>
+<p align="center"><img alt="Index scroll bar component on a rectangular device" src="../../../images/rectangular_index.png" /> <img alt="Index scroll bar component on a circular device" src="../../../images/round_index.png" /></p>
<p>To implement the index scroll bar component:</p>
<p>This feature is supported in wearable applications only.</p>
<p>The following figure shows the layout of the list component in a rectangular and circular UI.</p>
-<p align="center"><strong>Figure: List component in rectangular and circular devices</strong></p>
-<p align="center"><img alt="List component in a rectangular device" src="../../../images/rectangular_list.png" /> <img alt="List component in a circular device" src="../../../images/round_list.png" /></p>
+<p align="center"><strong>Figure: List component on rectangular and circular devices</strong></p>
+<p align="center"><img alt="List component on a rectangular device" src="../../../images/rectangular_list.png" /> <img alt="List component on a circular device" src="../../../images/round_list.png" /></p>
<p>To implement the list component:</p>
<p>This feature is supported in wearable applications only.</p>
<p>The following figure shows the more options component in a rectangular and circular UI.</p>
-<p align="center"><strong>Figure: More options component in rectangular and circular devices</strong></p>
-<p align="center"><img alt="More options component in a rectangular device" src="../../../images/rectangular_moreoption.png" /> <img alt="More options component in a circular device" src="../../../images/round_moreoption.png" /></p>
+<p align="center"><strong>Figure: More options component on rectangular and circular devices</strong></p>
+<p align="center"><img alt="More options component on a rectangular device" src="../../../images/rectangular_moreoption.png" /> <img alt="More options component on a circular device" src="../../../images/round_moreoption.png" /></p>
<p>To implement the more options component:</p>
<ol>
<p>The following figures show the layout of the popup component in a rectangular and circular UI.</p>
-<p align="center"><strong>Figure: Bottom popup component in rectangular and circular devices</strong></p>
+<p align="center"><strong>Figure: Bottom popup component on rectangular and circular devices</strong></p>
-<p align="center"><img alt="Bottom popup in a rectangular device" src="../../../images/rectangular_popup_bottom.png"/> <img alt="Bottom popup in a circular device" src="../../../images/round_popup_bottom.png"/></p>
+<p align="center"><img alt="Bottom popup on a rectangular device" src="../../../images/rectangular_popup_bottom.png"/> <img alt="Bottom popup on a circular device" src="../../../images/round_popup_bottom.png"/></p>
-<p align="center"><strong>Figure: Side popup component in rectangular and circular devices</strong></p>
+<p align="center"><strong>Figure: Side popup component on rectangular and circular devices</strong></p>
-<p align="center"><img alt="Side popup component in a rectangular device" src="../../../images/rectangular_popup_side.png"/> <img alt="Side popup component in a circular device" src="../../../images/round_popup_side.png"/></p>
+<p align="center"><img alt="Side popup component on a rectangular device" src="../../../images/rectangular_popup_side.png"/> <img alt="Side popup component on a circular device" src="../../../images/round_popup_side.png"/></p>
<p>To implement the popup button component:</p>
<p>This feature is supported in wearable applications only.</p>
<p>The following figure shows the layout of the processing component in a rectangular and circular UI.</p>
-<p align="center"><strong>Figure: Processing component in rectangular and circular devices</strong></p>
+<p align="center"><strong>Figure: Processing component on rectangular and circular devices</strong></p>
- <p align="center"><img alt="Processing component in a rectangular device" src="../../../images/rectangular_processing.png" /> <img alt="Processing component in a circular device" src="../../../images/round_processing.png" /></p>
+ <p align="center"><img alt="Processing component on a rectangular device" src="../../../images/rectangular_processing.png" /> <img alt="Processing component on a circular device" src="../../../images/round_processing.png" /></p>
<p>To implement the processing component:</p>
<ol>
<p>The following figure shows the layout of the thumbnail component in a rectangular and circular UI.</p>
-<p align="center"><strong>Figure: Thumbnail component in rectangular and circular devices</strong></p>
+<p align="center"><strong>Figure: Thumbnail component on rectangular and circular devices</strong></p>
-<p align="center"><img alt="Thumbnail component in a rectangular device" src="../../../images/rectangular_thumbnail.png" /> <img alt="Thumbnail component in a circular device" src="../../../images/round_thumbnail.png" /></p>
+<p align="center"><img alt="Thumbnail component on a rectangular device" src="../../../images/rectangular_thumbnail.png" /> <img alt="Thumbnail component on a circular device" src="../../../images/round_thumbnail.png" /></p>
<p>To implement the thumbnail component:</p>
<h2 id="Uploading_Files" name="Uploading_Files">Uploading Files with Ajax</h2>
-<p>To use the XML HTTP request features in your application, you must learn to upload files on the background with Ajax:</p>
+<p>To use the XML HTTP request features in your application, you must learn to upload files in the background with Ajax:</p>
<ol>
<li><p>Define the input elements for the file upload. Use the <code>upload()</code> method for the button click event to upload the file when the button is clicked.</p>
<pre class="prettyprint">
<div id="container"><div id="contents"><div class="content">
<h1>DeviceOrientation Event Specification</h1>
-<p>Tizen can detect motion data in the device by providing interaction between the user and device through a new UI or UX.</p>
+<p>Tizen can detect motion data on the device by providing interaction between the user and device through a new UI or UX.</p>
<p>This feature is supported in mobile and wearable applications only.</p>
<h1>Touch Events</h1>
-<p>As there is no mouse in a mobile device, the user actions must be handled with touch events, instead of mouse events.</p>
+<p>As there is no mouse on a mobile device, user actions must be handled with touch events instead of mouse events.</p>
<p>This feature is supported in mobile and wearable applications only.</p>
<li><a href="timing_control_w.htm">Timing control for script-based animations</a>\r
<p>Enables you to control animation speed by scheduling frame update requests.</p></li>\r
<li><a href="web_workers_w.htm">Web Workers</a>\r
- <p>Enables you to create and manage HTML5 Web Workers to run an independent JavaScript thread on the background without affecting the device performance.</p></li>\r
+ <p>Enables you to create and manage HTML5 Web Workers to run an independent JavaScript thread in the background without affecting the device performance.</p></li>\r
</ul>\r
\r
<script type="text/javascript" src="../../../scripts/jquery.zclip.min.js"></script>\r
<p align="center"><strong>Figure: Multi-thread application memory performance</strong></p>\r
<p align="center"><img alt="Multi-thread application memory performance" src="../../../images/multithreadapp_memory_inspector.png" /></p>\r
\r
-<p>The following table shows the response speed and memory performance based on the number of Web worker threads used to run the application in a Tizen quad-core processor device.</p>\r
+<p>The following table shows the response speed and memory performance based on the number of Web worker threads used to run the application on a Tizen quad-core processor device.</p>\r
\r
<p align="center" class="Table"><strong>Table: Speed and memory performance</strong></p>\r
<table>\r
<div class="note">
<strong>Note</strong>
- To use drag and drop in a Tizen device, long-press the draggable element. When the context menu opens, select <strong>Drag</strong>.
+ To use drag and drop on a Tizen device, long-press the draggable element. When the context menu opens, select <strong>Drag</strong>.
</div>
<h2 id="handle" name="handle">Handling Drag and Drop Events</h2>
</pre>
</li>
<li>Device and viewport height
-<p>The <code>height</code> attribute refers to restoring the viewport's height, and the <code>device-height</code> attribute refers to restoring the resolution set in the device.</p>
+<p>The <code>height</code> attribute refers to restoring the viewport's height, and the <code>device-height</code> attribute refers to restoring the resolution set on the device.</p>
<p>The same difference applies to the <code>width</code> and <code>aspect-ratio</code> attributes, which can assign 'device-'.</p>
<pre class="prettyprint">
@media screen and (min-device-height: 700px) {
<div id="container"><div id="contents"><div class="content">
<h1>Multiple Screen Support</h1>
- <p>Tizen is available in various devices which support different screen sizes and resolutions. When developing Tizen Web applications, you must take this into account if you want your application to function well in various device models.</p>
+ <p>Tizen is available on various devices which support different screen sizes and resolutions. When developing Tizen Web applications, you must take this into account if you want your application to function well on various device models.</p>
<p>This feature is supported in mobile applications only.</p>
</topic>
<topic href="html/native/ui/efl/accessibility_n.htm" label="Accessibility">
<topic href="html/native/ui/efl/accessibility_architecture_n.htm" label="Accessibility Architecture"></topic>
- <topic href="html/native/ui/efl/accessibility_config_n.htm" label="Configuring Accessibility in a Device"></topic>
+ <topic href="html/native/ui/efl/accessibility_config_n.htm" label="Configuring Accessibility on a Device"></topic>
<topic href="html/native/ui/efl/accessibility_implementation_n.htm" label="Implementing Accessible Applications"></topic>
</topic>
</topic>
<div id="container"><div id="contents"><div class="content">
<h1>Running Applications on the Emulator</h1>
-<p>The Tizen emulator is a tool that reduces the inconvenience of testing the application in a real device, by providing an environment similar to a real device. In other words, if you do not have the real device, you can test on any virtual device.</p>
+<p>The Tizen emulator is a tool that reduces the inconvenience of testing the application on a real device, by providing an environment similar to a real device. In other words, if you do not have the real device, you can test on any virtual device.</p>
<p>Using the Emulator Manager, you can create a variety of environments (different device types) and you can preview the problems during the development process. The emulator provides the actual hardware similar to real device controls, and you can check the application features, such as data processing and user scenarios.</p>
<p>When tapped, it opens a list of options available for the current screen.</p>
</li>
<li><strong>Home</strong> (mobile only)
- <p>When long-pressed, the Task switcher application opens as in a real device.</p>
+ <p>When long-pressed, the Task switcher application opens as on a real device.</p>
</li>
<li><strong>Back</strong>
<p>When tapped, the emulator returns to the previous screen.</p>
<h2 id="eventcast" name="eventcast">Using EventCast</h2>
<p>The emulator supports event injection using ECP (Emulator Control Panel). However, injecting sensor events using ECP is less intuitive and convenient. When you are injecting events, touching the emulator screen simultaneously is impossible. EventCast enables you to inject sensor and touch events more intuitively using a real target device.</p>
-<p>The following figure illustrates how the EventCast application in the target device gathers events and passes them to the emulator controller, which converts and hands them over to the Tizen platform. This is convenient in case you do not have a Tizen mobile device.</p>
+<p>The following figure illustrates how the EventCast application on the target device gathers events and passes them to the emulator controller, which converts and hands them over to the Tizen platform. This is convenient in case you do not have a Tizen mobile device.</p>
<p align="center"><strong>Figure: EventCast architecture</strong></p>
<p align="center"><img alt="eventcast_architecture" src="../images/emulator_feature_eventcast_architecture.png" /></p>
<pre class="prettyprint">
> sdb forward tcp:26102 tcp:9999
</pre>
-<p>After setting up port forwarding, development tools between the device and host can work remotely. For example, GDB (the GNU Project debugger) in a host/gdbserver in a device, and gdbserver in a device opened with the tcp:9999 port:</p>
+<p>After setting up port forwarding, development tools between the device and host can work remotely. For example, GDB (the GNU Project debugger) on a host/gdbserver on a device, and gdbserver on a device opened with the tcp:9999 port:</p>
<pre class="prettyprint">
> sdb shell gdbserver:9999 hellotizen
</pre>
<p>The SDB tool uses a command line to communicate with an emulator instance or a connected target device. You can send commands to a specific device to advance application development, such as file transfer, remote shell command, port forwarding for a debugger, viewing, filtering, and controlling target log output.</p></li>
<li><a href="../common_tools/emulator.htm">Emulator</a> <strong>(Running Applications on the Emulator)</strong>
- <p>The Tizen emulator tool reduces the inconvenience of testing the application in a real device, by providing an environment similar to a real device. With the Emulator Manager, you can create multiple emulator instances, each representing a different environment (device type).</p></li>
+ <p>The Tizen emulator tool reduces the inconvenience of testing the application on a real device, by providing an environment similar to a real device. With the Emulator Manager, you can create multiple emulator instances, each representing a different environment (device type).</p></li>
<li><a href="unit_test_n.htm">Unit Test</a> <strong>(Building Unit Test Projects)</strong>
<p>The unit test tool is used to ensure that the application runs properly as intended in the source code. You can create, build, and edit unit tests, and check and analyze the test results.</p></li>
<div class="note">
<strong>Note</strong>
- This attribute is not supported in Tizen wearable devices. Since Tizen 2.4, this attribute is not supported in all Tizen devices.
+ This attribute is not supported on Tizen wearable devices. Since Tizen 2.4, this attribute is not supported on all Tizen devices.
</div>
</li>
<li><code>exec</code>
<div class="note">
<strong>Note</strong>
- This attribute is not supported in Tizen wearable devices. Since Tizen 2.4, this attribute is not supported in all Tizen devices.
+ This attribute is not supported on Tizen wearable devices. Since Tizen 2.4, this attribute is not supported on all Tizen devices.
</div>
</li>
<li><code>taskmanage</code>
</pre>
<h4 id="icon"><icon> Element</h4>
- <p>This element contains the account provider icon image. Since the icons are used in the device under settings, the account icons are placed in a shared directory.</p>
+ <p>This element contains the account provider icon image. Since the icons are used on the device under settings, the account icons are placed in a shared directory.</p>
<p><strong>Attributes:</strong> </p>
<ul>
<li><code>section</code>
</ul>
<p><strong>Expected children:</strong> </p>
<ul>
- <li><code>icon</code> <p>Mandatory. Since the icons are used in the device under <strong>Settings > Accounts</strong>, place them in a shared directory.</p>
+ <li><code>icon</code> <p>Mandatory. Since the icons are used on the device under <strong>Settings > Accounts</strong>, place them in a shared directory.</p>
<p>Attributes:</p>
<ul><li><code>Account</code>: File path of the account provider icon. The icon size is 72 x 72 pixels.</li>
<li><code>AccountSmall</code>: File path of the account provider small icon. The icon size is 45 x 45 pixels. </li></ul></li>
</ul>
<p><strong>Attributes:</strong> </p>
<ul>
- <li><code>id</code> <p>Mandatory; Tizen application ID, which is a combination of the Tizen package ID and project name. The application ID is unique in the device.</p><p>The project name is a set of characters (0~9, a~z, A~Z) randomly generated by the Tizen Studio. The minimum value is 1 byte and maximum value is 52 bytes.</p></li>
+ <li><code>id</code> <p>Mandatory; Tizen application ID, which is a combination of the Tizen package ID and project name. The application ID is unique among applications on the device.</p><p>The project name is a set of characters (0~9, a~z, A~Z) randomly generated by the Tizen Studio. The minimum value is 1 byte and the maximum value is 52 bytes.</p></li>
<li><code>package</code> <p>Mandatory; Tizen package ID generated by the Tizen Studio, comprises of 10 characters (0~9, a~z, A~Z). The package ID is unique in the Tizen Store.</p></li>
<li><code>required_version</code> <p>Mandatory; Tizen API version required for running the Web application</p></li>
<li><code>launch_mode</code> <p>Optional; sets which launch mode is supported (available values: <code>single</code> (default), <code>group</code>, <code>caller</code>)</p>
<th><tizen:background-category /> element</th>
</tr>
<tr>
- <td>Used to represent the category of the application that is allowed to run on the background.
+ <td>Used to represent the category of an application that is allowed to run in the background.
<div class="note">
<strong>Note</strong>
- In addition to declaring the <code><background-category></code> element, you must <a href="#mw_setting">set the <code><tizen:setting background-support></code> attribute to <code>enable</code></a> to run Web applications on the background.
+ In addition to declaring the <code><background-category></code> element, you must <a href="#mw_setting">set the <code><tizen:setting background-support></code> attribute to <code>enable</code></a> to run Web applications in the background.
</div>
<p><strong>Occurrences:</strong> </p>
<ul>
<li><code>screen-orientation</code><p>Optional; viewport orientation lock (available values: <code>portrait</code> (default), <code>landscape</code>), auto-rotation</p>If the system auto rotation setting is on, the Web application viewport orientation is changed accordingly by default.</li>
<li><code>context-menu</code> <p>Optional; context menu is displayed when the user clicks, for example, an image, text, or link (available values: <code>enable</code> (default), <code>disable</code>)</p></li>
<li><code>background-support</code>
- <p>Optional; application execution continues when it is moved to the background (available values: <code>enable</code> (execution continues on the background), <code>disable</code> (default; application is suspended))</p>
+ <p>Optional; application execution continues when it is moved to the background (available values: <code>enable</code> (execution continues in the background), <code>disable</code> (default; application is suspended))</p>
<div class="note">
<strong>Note</strong>
- Since Tizen 2.4, the system manages background processes more tightly. Even if the <code>background-support</code> attribute is set to <code>enable</code>,
the Web application process can be suspended on the background. To guarantee that the application runs on the background, <a href="#mw_bg_category">add at least one background category</a> for the application with the <code><tizen:background-category></code> element. Only the background categories declared in the system can be used.
+ Since Tizen 2.4, the system manages background processes more tightly. Even if the <code>background-support</code> attribute is set to <code>enable</code>,
a Web application process can be suspended in the background. To guarantee that the application runs in the background, <a href="#mw_bg_category">add at least one background category</a> for the application with the <code><tizen:background-category></code> element. Only the background categories declared in the system can be used.
</div>
</li>
<li><code>encryption</code> <p>Optional; Web application resources (HTML, JavaScript, and CSS files) are stored encrypted (available values: <code>enable</code>, <code>disable</code> (default))</p></li>
</ul>
<p><strong>Attributes:</strong> </p>
<ul>
- <li><code>id</code> <p>Mandatory; Tizen application ID, which is a combination of the Tizen wearable package ID and project name. The application ID is unique in the device.</p><p>The project name is a set of characters (0~9, a~z, A~Z) randomly generated by the Tizen Studio. The minimum value is 1 byte and maximum value is 52 bytes.</p></li>
+ <li><code>id</code> <p>Mandatory; Tizen application ID, which is a combination of the Tizen wearable package ID and project name. The application ID is unique among applications on the device.</p><p>The project name is a set of characters (0~9, a~z, A~Z) randomly generated by the Tizen Studio. The minimum value is 1 byte and the maximum value is 52 bytes.</p></li>
<li><code>package</code> <p>Mandatory; Tizen wearable package ID generated by the Tizen Studio, comprises of 10 characters (0~9, a~z, A~Z). The package ID is unique in the Samsung Apps.</p></li>
<li><code>required_version</code> <p>Mandatory; Tizen API version required for running the Web application</p></li>
<th><tizen:background-category /> element</th>
</tr>
<tr>
- <td>Used to represent the category of the application that is allowed to run on the background.
+ <td>Used to represent the category of an application that is allowed to run in the background.
<div class="note">
<strong>Note</strong>
- In addition to declaring the <code><background-category></code> element, you must <a href="#ww_setting">set the <code><tizen:setting background-support></code> attribute to <code>enable</code></a> to run Web applications on the background.
+ In addition to declaring the <code><background-category></code> element, you must <a href="#ww_setting">set the <code><tizen:setting background-support></code> attribute to <code>enable</code></a> to run Web applications in the background.
</div>
<p><strong>Occurrences:</strong> </p>
<ul>
<li><code>background-support</code>
- <p>Optional; application execution continues when it is moved to the background (available values: <code>enable</code> (execution continues on the background), <code>disable</code> (default; application is suspended))</p>
+ <p>Optional; application execution continues when it is moved to the background (available values: <code>enable</code> (execution continues in the background), <code>disable</code> (default; application is suspended))</p>
<div class="note">
<strong>Note</strong>
- Since Tizen 2.4, the system manages background processes more tightly. Even if the <code>background-support</code> attribute is set to <code>enable</code>,
the Web application process can be suspended on the background. To guarantee that the application runs on the background, <a href="#ww_bg_category">add at least one background category</a> for the application with the <code><tizen:background-category></code> element. Only the background categories declared in the system can be used.
+ Since Tizen 2.4, the system manages background processes more tightly. Even if the <code>background-support</code> attribute is set to <code>enable</code>,
a Web application process can be suspended in the background. To guarantee that the application runs in the background, <a href="#ww_bg_category">add at least one background category</a> for the application with the <code><tizen:background-category></code> element. Only the background categories declared in the system can be used.
</div>
</li>
<li><code>context-menu</code> <p>Optional; sets whether the context menu is shown (available values: <code>enable</code> (default), <code>disable</code>)</p><p>If this option is enabled, the context menu is visible to the user.</p></li>
</ul>
<p><strong>Attributes:</strong> </p>
<ul>
- <li><code>id</code> <p>Mandatory; Tizen service ID, which is a combination of the Tizen wearable package ID and service name.</p><p>The service ID is a set of characters (0~9, a~z, A~Z) and unique in the device. The minimum value is 1 byte and maximum value is 52 bytes.</p></li>
- <li><code>on-boot</code> <p>Optional; sets whether the service application is launched automatically on device booting time (available values: <code>true</code>, <code>false</code> (default))</p>
+ <li><code>id</code> <p>Mandatory; Tizen service ID, which is a combination of the Tizen wearable package ID and service name.</p><p>The service ID is a set of characters (0~9, a~z, A~Z) and unique among service applications on the device. The minimum value is 1 byte and the maximum value is 52 bytes.</p></li>
+ <li><code>on-boot</code> <p>Optional; sets whether the service application is launched automatically on device boot (available values: <code>true</code>, <code>false</code> (default))</p></li>
<div class="note">
<strong>Note</strong>
This attribute is not supported on Tizen wearable devices. Since Tizen 2.4, this attribute is not supported on all Tizen devices.
<p>The SDB tool uses a command line to communicate with an emulator instance or a connected target device. You can send commands to a specific device to advance application development, such as file transfer, remote shell command, port forwarding for a debugger, viewing, filtering, and controlling target log output.</p></li>
<li><a href="../common_tools/emulator.htm">Emulator</a> <strong>(Running Applications on the Emulator)</strong>
- <p>The Tizen emulator tool reduces the inconvenience of testing the application in a real device, by providing an environment similar to a real device. With the Emulator Manager, you can create multiple emulator instances, each representing a different environment (device type).</p></li>
+ <p>The Tizen emulator tool reduces the inconvenience of testing the application on a real device, by providing an environment similar to a real device. With the Emulator Manager, you can create multiple emulator instances, each representing a different environment (device type).</p></li>
<li><a href="web_unit_test_tool_w.htm">Web Unit Testing Tool</a> <strong>(Unit Testing Web Applications)</strong>
<p>The unit test tool is used to ensure that the application runs properly as intended in the source code. You can create, edit, and run unit tests, and check and analyze the test results.</p></li>
<h4>Rule 8. API Privilege Missing</h4>
-<p>To use a privileged Tizen Device API in a target device, the <code>config.xml</code> file of the Tizen Web application must have a corresponding privilege URL defined. An alarm is raised if the privilege is not found in the <code>config.xml</code> file.</p>
+<p>To use a privileged Tizen Device API on a target device, the <code>config.xml</code> file of the Tizen Web application must have a corresponding privilege URL defined. An alarm is raised if the privilege is not found in the <code>config.xml</code> file.</p>
<p>In the following example, the Web application is using the <code>tizen.application.launch()</code> function, which requires the <code>http://tizen.org/privilege/application.launch</code> privilege, which is commented in the <code>config.xml</code> file. So an alarm is raised.</p>
<div class="note">
<strong>Note</strong>
In Tizen native APIs and Web Device APIs, there are 2 types of APIs: mandatory and optional. The fully gray profile icon (as shown in the table above) refers to an optional API.
-<p>The mandatory APIs are always available on all Tizen devices. The optional APIs provide functionality that depends on the available device hardware or software capabilities, and they may not be available in all Tizen devices.</p>
+<p>The mandatory APIs are always available on all Tizen devices. The optional APIs provide functionality that depends on the available device hardware or software capabilities, and they may not be available on all Tizen devices.</p>
</div>
<h2 id="life" name="life">Native Application Life-cycle</h2>
<p>A Tizen native application can be in one of several different states. Typically, the application is launched by the user from the Launcher, or by another application. When the application is starting, the <code>app_create_cb()</code> function is executed and the main event loop starts. The application normally at the top window, with focus.</p>
-<p>When the application loses the focus status, the <code>app_pause_cb()</code> callback is invoked. The application can go into the pause state, which means that your application is not terminated but continues to run on the background, when:</p>
+<p>When the application loses the focus status, the <code>app_pause_cb()</code> callback is invoked. The application can go into the pause state, which means that your application is not terminated but continues to run in the background, when:</p>
<ul>
<li><p>A new application is launched based on a request from your application.</p></li>
<li><p>An alarm is triggered for another application, which becomes the top-most window and hides your application.</p> </li>
</ul>
-<p>Since Tizen 2.4,
the application on the background goes into a suspended state. In the suspended state, the application process is executed with limited CPU resources. In other words, the platform does not allow the running of the background applications, except for some exceptional applications (such as Media and Download) that necessarily work on the background. In this case, the application can <a href="../../../../org.tizen.guides/html/native/app_management/efl_ui_app_n.htm#allow_bg">designate their background category as an allowed category</a> to avoid going into the suspended state.</p>
+<p>Since Tizen 2.4,
an application in the background goes into a suspended state. In the suspended state, the application process is executed with limited CPU resources. In other words, the platform does not allow the running of the background applications, except for some exceptional applications (such as Media and Download) that necessarily work in the background. In this case, the application can <a href="../../../../org.tizen.guides/html/native/app_management/efl_ui_app_n.htm#allow_bg">designate their background category as an allowed category</a> to avoid going into the suspended state.</p>
<p>When your application becomes visible again, the <code>app_resume_cb()</code> callback is invoked. The visibility returns, when:</p>
<h2 id="ambient" name="ambient">Ambient Events in Wearable Applications</h2>
-<p>An ambient mode is available
in a low-powered wearable device. For more information on ambient events in the mobile native profile, see the <a href="../../../../org.tizen.guides/html/native/app_management/watch_app_n.htm">Watch Application</a> guide.</p>
+<p>An ambient mode is available
on a low-powered wearable device. For more information on ambient events in the mobile native profile, see the <a href="../../../../org.tizen.guides/html/native/app_management/watch_app_n.htm">Watch Application</a> guide.</p>
<script type="text/javascript" src="../../scripts/jquery.zclip.min.js"></script>
<script type="text/javascript" src="../../scripts/showhide.js"></script>
<td>public</td>
<td></td>
<td>3.0</td>
-<td>The application can trigger authenticators in the user's device and it can request to use the user's PIN or biometrics (fingerprints or irises) for authentication.</td>
+<td>The application can trigger authenticators on the user's device and it can request to use the user's PIN or biometrics (fingerprints or irises) for authentication.</td>
</tr>
<tr>
<td><code>http://tizen.org/privilege/haptic</code></td>
<td>public</td>
<td></td>
<td>3.0</td>
-<td>The application can trigger authenticators in the user's device and it can request to use the user's PIN or biometrics (fingerprints or irises) for authentication.</td>
+<td>The application can trigger authenticators on the user's device and it can request to use the user's PIN or biometrics (fingerprints or irises) for authentication.</td>
</tr>
<tr>
<td><code>http://tizen.org/privilege/haptic</code></td>
<p align="center"><img src="../../images/app_run_multiple_emulators.png" alt="Selecting the device to use" /></p>
</li>
-<li>Confirm that the application launches in the target device.</li>
+<li>Confirm that the application launches on the target device.</li>
</ol>
<div class="note">
<li>Click <strong>Debug</strong>.</li>
</ul> </li>
- <li><p>Use the application in the emulator as you would in a target device.</p>
+ <li><p>Use the application in the emulator as you would on a target device.</p>
<p>While the application is running, the Tizen Studio <a href="../../../../org.tizen.studio/html/common_tools/log_view.htm">Log view</a> shows the log, debug, and exception messages from the methods defined in the log macros.</p> </li>
<li><p>To stop debugging, do one of the following:</p>
<li>On the Tizen Studio toolbar, click <strong>Run</strong>.</li>
</ul> <p>If the application binary does not exist, it is built automatically for the emulator.</p>
<p>If many active emulator instances are connected, select the emulator to run the application from the dialog box.</p></li>
- <li><p>Use the application in the emulator as you would in a target device.</p>
+ <li><p>Use the application in the emulator as you would on a target device.</p>
<p>While the application is running, the Tizen Studio <strong>Log</strong> view shows the log, debug, and exception messages from the methods defined in the log macros.</p></li>
<li><p>To terminate the run, exit the application on the emulator.</p></li>
</ol>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
</table>
</li>
- <li>Add the background category type (since Tizen 2.4). <p>You can <a href="../../../../org.tizen.guides/html/native/app_management/efl_ui_app_n.htm#bg-category">describe the background category</a> of your Tizen native application.</p> <p>To add background category types to allow running on the background, click <strong>+</strong> in the <strong>Background Category</strong> panel, select the category type, and click <strong>OK</strong>.</p> </li>
+ <li>Add the background category type (since Tizen 2.4). <p>You can <a href="../../../../org.tizen.guides/html/native/app_management/efl_ui_app_n.htm#bg-category">describe the background category</a> of your Tizen native application.</p> <p>To add background category types to allow running in the background, click <strong>+</strong> in the <strong>Background Category</strong> panel, select the category type, and click <strong>OK</strong>.</p> </li>
<li>Add shortcuts. <p>To add a shortcut for the application, click <strong>+</strong> in the <strong>Shortcut List</strong> panel and define the shortcut details, as described in the following table.</p>
<ol>
<li>Connect the wearable target device to your computer:
<ol type="a">
-<li>Define settings in the device:
+<li>Define settings on the device:
<ul>
<li>Go to <strong>Settings > Connections</strong>, and switch on Bluetooth.
<p align="center"><img src="../../images/emulator_target_bt.png" alt="Switch on Bluetooth" /></p>
<p align="center"><img src="../../images/app_run_multiple_emulators.png" alt="Selecting the device to use" /></p>
</li>
-<li>Confirm that the application launches in the target device.</li>
+<li>Confirm that the application launches on the target device.</li>
</ol>
<ol>
<li>Connect the wearable target device to your computer:
<ol type="a">
-<li>Define settings in the device:
+<li>Define settings on the device:
<ul>
<li>Go to <strong>Settings > Connections</strong>, and switch on Bluetooth.
<p align="center"><img src="../../images/emulator_target_bt.png" alt="Switch on Bluetooth" /></p>
<p align="center"><img src="../../images/app_run_multiple_emulators.png" alt="Selecting the device to use" /></p>
</li>
-<li>Confirm that the application launches in the target device.
+<li>Confirm that the application launches on the target device.
<p>Like with the <a href="#watchface">emulator</a>, you must change the watch face in the device settings before you can see the watch application UI on the device.</p></li>
</ol>
<h3 id="ambient" name="ambient">Using the Ambient Mode</h3>
-<p>In a low-powered wearable device, an ambient mode is available. In this mode, the watch application shows a limited UI and receives only the ambient tick event every minute to reduce power consumption.</p>
+<p>On a low-powered wearable device, an ambient mode is available. In this mode, the watch application shows a limited UI and receives only the ambient tick event every minute to reduce power consumption.</p>
<p>The details of the limited UI drawn in the ambient mode depend on the device. In addition, due to the ambient mode being a low power mode, there are limits to the colors that can be shown on the screen. Usually, when designing the ambient mode UI, draw it with limited colors (cyan, magenta, yellow, red, green, blue, black and white), and use less than 15% of the pixels on the screen. If you do not want to draw your own ambient mode UI, set the <code>ambient-support</code> attribute to <code>false</code> in the watch application manifest file to allow the platform to show a default ambient mode UI.</p>
<div class="note">
<strong>Note</strong>
- To use the ambient mode, the user must enable it in the device settings. In addition, in the Gear S2 device, the ambient mode activates only when you are wearing the watch on the wrist.
+ To use the ambient mode, the user must enable it in the device settings. In addition, on the Gear S2 device, the ambient mode activates only when you are wearing the watch on the wrist.
</div>
<p>To use the ambient mode:</p>
<ol>
<li>Define the ambient mode callbacks:
-<ul><li>The <code>ambient_changed</code> callback is called when the ambient mode is enabled or disabled in the device. You can use the callback to initialize your ambient mode UI.</li>
+<ul><li>The <code>ambient_changed</code> callback is called when the ambient mode is enabled or disabled on the device. You can use the callback to initialize your ambient mode UI.</li>
<li>The <code>ambient_tick</code> callback is called every minute while the device is in the ambient mode. You can use the callback to update the time on your watch application in the ambient mode. In this callback, do not perform time-consuming tasks and always update the UI as fast as possible. The platform can put the device to sleep shortly after the ambient tick expires.</li>
</ul>
<pre class="prettyprint">
<p>A widget application is one of the Tizen application types. It can be shown by specific UI applications (such as the home screen and lock screen) that can contain widget applications.</p>
-<p align="center"><strong>Figure: Widget application in a wearable device</strong></p>
-<p align="center"><img alt="Widget application in a wearable device" src="../../images/widget_app_wearable.png" /></p>
+<p align="center"><strong>Figure: Widget application on a wearable device</strong></p>
+<p align="center"><img alt="Widget application on a wearable device" src="../../images/widget_app_wearable.png" /></p>
<p>Study the following instructions to help familiarize yourself with the Tizen <a href="../process/app_dev_process_n.htm">native application development process</a> as well as using the Tizen Studio and installing the created application on the emulator or target device. With the instructions, you can create and run a basic wearable native widget application, which displays some text on the screen with no user interaction:</p>
<p align="center"><img src="../../images/app_run_multiple_emulators.png" alt="Selecting the device to use" /></p>
</li>
-<li>Confirm that the application launches in the target device.
+<li>Confirm that the application launches on the target device.
<p>Like with the <a href="#viewer">emulator</a>, you must add the widget to the home screen before you can see it.</p></li>
</ol>
</tr>
<tr>
<td>Performance and Optimization</td>
- <td>These APIs enable you to retrieve the visibility status of a Web document and detect changes in it, control animation frame rate, and create and manage HTML5 Web Workers to run an independent JavaScript thread on the background.</td>
+ <td>These APIs enable you to retrieve the visibility status of a Web document and detect changes in it, control animation frame rate, and create and manage HTML5 Web Workers to run an independent JavaScript thread in the background.</td>
<td>
<ul>
<li>Guides: <a href="../../../../org.tizen.guides/html/web/w3c/perf_opt/performance_guide_w.htm">Performance and Optimization</a></li>
</tr>
<tr>
<td>Performance and Optimization</td>
- <td>These APIs enable you to retrieve the visibility status of a Web document and detect changes in it, control animation frame rate, and create and manage HTML5 Web Workers to run an independent JavaScript thread on the background.</td>
+ <td>These APIs enable you to retrieve the visibility status of a Web document and detect changes in it, control animation frame rate, and create and manage HTML5 Web Workers to run an independent JavaScript thread in the background.</td>
<td>
<ul>
<li>Guides: <a href="../../../../org.tizen.guides/html/web/w3c/perf_opt/performance_guide_w.htm">Performance and Optimization</a></li>
<p align="center"><img src="../../images/app_run_multiple_emulators.png" alt="Selecting the device to use" /></p>
</li>
-<li>Confirm that the application launches in the target device.</li>
+<li>Confirm that the application launches on the target device.</li>
</ol>
<div class="note">
</tr>
<tr>
<td colspan="2"><strong>Background Category</strong></td>
- <td>Defines the background category type (since Tizen 2.4). <p>To add background category types to allow running on the background, click <strong>+</strong> in the <strong>Background Category</strong> section, select the category type, and click <strong>OK</strong>.</p></td>
+ <td>Defines the background category type (since Tizen 2.4). <p>To add background category types to allow running in the background, click <strong>+</strong> in the <strong>Background Category</strong> section, select the category type, and click <strong>OK</strong>.</p></td>
</tr>
<tr>
<td colspan="2"><strong>Meta Data</strong></td>
<ol>
<li>Connect the wearable target device to your computer:
<ol type="a">
-<li>Define settings in the device:
+<li>Define settings on the device:
<ul>
<li>Go to <strong>Settings > Connections</strong>, and switch on Bluetooth.
<p align="center"><img src="../../images/emulator_target_bt.png" alt="Switch on Bluetooth" /></p>
<p align="center"><img src="../../images/app_run_multiple_emulators.png" alt="Selecting the device to use" /></p>
</li>
-<li>Confirm that the application launches in the target device.</li>
+<li>Confirm that the application launches on the target device.</li>
</ol>
<div class="note">
<ol>
<li>Connect the wearable target device to your computer:
<ol type="a">
-<li>Define settings in the device:
+<li>Define settings on the device:
<ul>
<li>Go to <strong>Settings > Connections</strong>, and switch on Bluetooth.
<p align="center"><img src="../../images/emulator_target_bt.png" alt="Switch on Bluetooth" /></p>
<p align="center"><img src="../../images/app_run_multiple_emulators.png" alt="Selecting the device to use" /></p>
</li>
-<li>Confirm that the application launches in the target device.
+<li>Confirm that the application launches on the target device.
<p>Like with the <a href="#watchface">emulator</a>, you must change the watch face in the device settings before you can see the watch application UI on the device.</p>
</li>
</ol>
<h3 id="ambient">Using the Ambient Mode</h3>
-<p>In a low-powered wearable device, an ambient mode is available. In this mode, the watch application shows a limited UI and receives only the ambient tick event every minute to reduce power consumption.</p>
+<p>On a low-powered wearable device, an ambient mode is available. In this mode, the watch application shows a limited UI and receives only the ambient tick event every minute to reduce power consumption.</p>
<p>The details of the limited UI drawn in the ambient mode depend on the device. In addition, due to the ambient mode being a low power mode, there are limits to the colors that can be shown on the screen. Usually, when designing the ambient mode UI, draw it with limited colors (cyan, magenta, yellow, red, green, blue, black and white), and use less than 15% of the pixels on the screen. If you do not want to draw your own ambient mode UI, set the <code>ambient_support</code> attribute to <code>disable</code> in the <code>config.xml</code> watch application configuration file to allow the platform to show a default ambient mode UI.</p>
<div class="note">
<strong>Note</strong>
- To use the ambient mode, the user must enable it in the device settings. In addition, in the Gear S2 device, the ambient mode activates only when you are wearing the watch on the wrist.
+ To use the ambient mode, the user must enable it in the device settings. In addition, on the Gear S2 device, the ambient mode activates only when you are wearing the watch on the wrist.
<p>Since Tizen 2.3.2, some devices introduce a high color mode for the ambient mode. In the high color mode, you can use more colors (usually, 24-bit color) for drawing the ambient mode UI. To check whether the device supports the high color mode, use the following code:</p>
<p>A widget application is one of the Tizen application types. It can be shown by specific UI applications (such as the home screen and lock screen) that can contain widget applications.</p>
-<p align="center"><strong>Figure: Widget application in a wearable device</strong></p>
-<p align="center"><img alt="Widget application in a wearable device" src="../../images/widget_app_wearable_widget.png" /></p>
+<p align="center"><strong>Figure: Widget application on a wearable device</strong></p>
+<p align="center"><img alt="Widget application on a wearable device" src="../../images/widget_app_wearable_widget.png" /></p>
<p>Study the following instructions to help familiarize yourself with the Tizen <a href="../process/app_dev_process_w.htm">Web application development process</a> as well as using the Tizen Studio and installing the created application on the emulator or target device. With the instructions, you can create and run a basic wearable Web widget application (a Web widget), which displays some text on the screen with no user interaction:</p>
<ol>
<li>Connect the wearable target device to your computer:
<ol type="a">
-<li>Define settings in the device:
+<li>Define settings on the device:
<ul>
<li>Go to <strong>Settings > Connections</strong>, and switch on Bluetooth.
<p align="center"><img src="../../images/emulator_target_bt.png" alt="Switch on Bluetooth" /></p>
<p align="center"><img src="../../images/app_run_multiple_emulators.png" alt="Selecting the device to use" /></p>
</li>
-<li>Confirm that the application launches in the target device.
+<li>Confirm that the application launches on the target device.
<p>Like with the <a href="#viewer">emulator</a>, you must add the widget to the home screen before you can see it.</p></li>
</ol>
projects / sdk / online-doc.git / commitdiff