<div class="note">
<strong>Note</strong>
- The APIs used in this use case are deprecated since Tizen 2.3.1. For scanning nearby BLE devices in Tizen 2.3.1 and
later, see <a href="#le_scan">Managing Bluetooth LE Scans</a>.
+ The APIs used in this use case are deprecated since Tizen 2.3.1. For scanning nearby BLE devices in Tizen 2.3.1 and
higher, see <a href="#le_scan">Managing Bluetooth LE Scans</a>.
</div>
<p>To start the BLE discovery operation:</p>
<ul>
<li>Use the <code>download_cancel()</code> function. It changes the download state to <code>DOWNLOAD_STATE_CANCELED</code>. From this state, you can restart the download with the <code>download_start()</code> function.</li>
-<li>After you stop a download, the download handle ID is stored for 48 hours (even if the device is powered off), allowing you to resume the download later on. If you have no need to resume the process later on, unload all data concerning the download handle from the memory with the <code>download_destroy()</code> function.</li>
+<li>After you stop a download, the download handle ID is stored for 48 hours (even if the device is powered off), allowing you to resume the download later. If you have no need to resume the process later, unload all data concerning the download handle from the memory with the <code>download_destroy()</code> function.</li>
</ul>
<h2 id="prerequisites">Prerequisites</h2>
<p>Use the Web features to create a simple Web browser:</p>
<ol>
<li><a href="#window">Create a window object</a>, and <a href="#layout">set the window layout and view</a>.
-<p>Later
on, you can use various helper functions to <a href="#helper">find the created window</a>.</p></li>
+<p>Later, you can use various helper functions to <a href="#helper">find the created window</a>.</p></li>
<li><a href="#show">Show the window and set the focus</a>.
<p>You can <a href="#keymouse">handle key and mouse events</a> in the window.</p></li>
<li>When no longer needed, <a href="#finalize">terminate the window</a>. </li>
<strong>Note</strong>
The <code>.po</code> files must be placed in the <code>res/po</code> directory of the application. The files can be edited using the <a href="../../../../org.tizen.studio/html/native_tools/po_file_editor_n.htm">PO file editor</a> provided by the Tizen Studio.
<p>The <code>.po</code> file is compiled into a <code>.mo</code> file, and the <code>.mo</code> file name is defined using the project name that you define when you create the project in the Tizen Studio. The application ID is made based on the project name, and the framework finds the application <code>.mo</code> file based on the application ID.</p>
-<p>Be careful if you change the application ID in the Tizen manifest editor later on, because the <code>.mo</code> file name is not automatically changed, and problems can occur when getting the string resources.</p>
+<p>Be careful if you change the application ID in the Tizen manifest editor later, because the <code>.mo</code> file name is not automatically changed, and problems can occur when getting the string resources.</p>
</div>
<p>The application must load the proper resource set depending on the current device locale. If no matching resource set is found for the current locale, the default resource set is used.</p>
/* Create the playlist */
media_playlist_insert_to_db("playlist_for_tutorial", &playlist);
</pre>
-<p>You can modify the playlist name later on using the <code>media_playlist_set_name()</code> function.</p>
+<p>You can modify the playlist name later using the <code>media_playlist_set_name()</code> function.</p>
</li>
<li><p>Define a callback function for the <code>media_info_foreach_media_from_db()</code> function, called for each available media item. Use the callback to cast the user data to a proper type and copy the media ID to a list:</p>
<p>To display the progress bar and update the progress data:</p>
-<ol><li><p>Use the <code>NOTIFICATION_TYPE_ONGOING</code> parameter to create a notification with a progress bar. To be able to retrieve the notification handle later on to update the progress data, set a notification tag with the <code>notification_set_tag()</code> function.</p>
+<ol><li><p>Use the <code>NOTIFICATION_TYPE_ONGOING</code> parameter to create a notification with a progress bar. To be able to retrieve the notification handle and update the progress data later, set a notification tag with the <code>notification_set_tag()</code> function.</p>
<p>To set the initial progress:</p>
<pre class="prettyprint">
<li>If the data is tagged as exportable, the key manager returns the raw value of the data.</li>
<li>If the data is tagged as non-exportable, the key manager does not return its raw value.
<p>In that case, the key manager provides secure cryptographic operations for non-exportable keys without revealing key values to clients.</p></li></ul>
-<p>All the data in the key manager is protected by an internal key. In addition, a client can encrypt its data using its own password. If a client provides a password when storing data, the data is encrypted with that password. To obtain the data from the key manager later on, the same password must be provided. The additional password provides protection in case the device is lost.</p>
+<p>All of the data in the key manager is protected by an internal key. In addition, a client can encrypt its data using its own password. If a client provides a password when storing data, the data is encrypted with that password. To obtain the data from the key manager later, the same password must be provided. The additional password provides protection in case the device is lost.</p>
<p>When storing data:</p>
<ul><li>For small-size sensitive data, store it within the key manager.</li>
<li>For large-size sensitive data, store it as a local file and encrypt it with a key stored within the key manager.</li>
<h2 id="change" name="change">Changing the Image</h2>
-<p>The image object can be changed later on by calling the <code>ImageView::SetImage()</code> function:</p>
+<p>The image object can be changed later by calling the <code>ImageView::SetImage()</code> function:</p>
<pre class="prettyprint">
imageView.SetImage( newImage );
<p>There are certain restrictions when writing stereoscopic applications using DALi:</p>
<ul>
-<li>When a stereo mode is selected, the default render task source actor is set to an uninitialized actor so it does not render anything. Changing the default render task source actor later on produces undesired results, as the user does not want to see anything rendered by the default camera when stereo mode is on.</li>
+<li>When a stereo mode is selected, the default render task source actor is set to an uninitialized actor so it does not render anything. Changing the default render task source actor later produces undesired results, as the user does not want to see anything rendered by the default camera when stereo mode is on.</li>
<li>Stereo cameras are parented to the default camera, so if the application needs to change the camera position or orientation, it must change the default camera transformation. The handle to the default camera can be obtained from the default render task as follows:
<pre class="prettyprint">
<p>The genlist has a separate style for itself and for its items. The genlist style determines the characteristics of the entire scrollable area.</p>
-<p>The genlist items have a gradient opacity from the top to the bottom rather than an explicit divider from Tizen 2.4. Each item is identified by its color made by blending its opacity and background color (or image). The <code>solid</code> prefix in a genlist style name means that genlist items have an explicit divider and background color. To set a genlist with a solid background color:</p>
+<p>The genlist items have a gradient opacity from the top to the bottom rather than an explicit divider since Tizen 2.4. Each item is identified by its color made by blending its opacity and background color (or image). The <code>solid</code> prefix in a genlist style name means that genlist items have an explicit divider and background color. To set a genlist with a solid background color:</p>
<pre class="prettyprint">
elm_object_style_set(genlist, "solid/default");
</pre>
Evas_Object *next_btn, Evas_Object *content, const char *item_style);
</pre>
<ul>
-<li><p>In Tizen, the <code>next_btn</code> (fourth parameter) is not shown, so use <code>NULL</code>. The <code>prev_btn</code> (third parameter) is supported, but auto pushing is also supported from Tizen 2.4. As a result, use <code>NULL</code> for <code>prev_btn</code> too, and set the auto-pushed flag (about the <code>prev_btn</code>) to <code>true</code> (like below).</p>
+<li><p>In Tizen, the <code>next_btn</code> (fourth parameter) is not shown, so use <code>NULL</code>. The <code>prev_btn</code> (third parameter) is supported, but auto pushing is also supported since Tizen 2.4. As a result, use <code>NULL</code> for <code>prev_btn</code> too, and set the auto-pushed flag (about the <code>prev_btn</code>) to <code>true</code> (like below).</p>
<pre class="prettyprint">
/*
Make prev_btn automatically,
<p>To create an inline array, use the <code>eina_inarray_new()</code> function:</p>
<ul><li>The first parameter is the size of the value. In this example, only the characters are stored, and because of that, only <code>sizeof(char)</code> is passed to the function.</li>
<li>The second parameter defines the size of the array allocation step. For example, if you set it to 4, the function returns an inline array of 4 elements, and the next time you grow the inline array, it grows by 4 elements and becomes an array of 8 elements. If you set the step to 0, the function sets a default safe value.
-<p>The step can be changed later on using the <code>eina_inarray_step_set()</code> function.</p></li></ul>
+<p>The step can be changed later using the <code>eina_inarray_step_set()</code> function.</p></li></ul>
<p>The <code>eina_inarray_new()</code> function returns a pointer to the new <code>Eina_Inarray</code> variable.</p>
<pre class="prettyprint">
<div class="note">
<strong>Note</strong>
- From Tizen 2.4 onwards, the platform-defined application controls and aliased application IDs which were defined in previous Tizen versions may not be supported. If they are used, the application control behavior is undefined and cannot be guaranteed.
+ Since Tizen 2.4, the platform-defined application controls and aliased application IDs which were defined in previous Tizen versions may not be supported. If they are used, the application control behavior is undefined and cannot be guaranteed.
</div>
</li>
<h3 id="appcontrol_event" name="appcontrol_event">Preventing Page Reloads for Incoming Requests</h3>
<p>When a Web application receives an application control request from another application, the receiving application finds the proper page for that request and loads that page. If the found page is already loaded and displayed, the page is reloaded (refreshed) to process the incoming application control request. However, in some cases, a Web application is able to handle the application control request without reloading the page in order to keep the previous context.</p>
-<p>From Tizen 2.4 onwards, the Web runtime provides a way to handle application control requests without page reloading by extending the <code><tizen:app-control></code> element of the <code>config.xml</code> file and sending a new <code>appcontrol</code> event to the receiving application.</p>
+<p>Since Tizen 2.4, the Web runtime provides a way to handle application control requests without page reloading by extending the <code><tizen:app-control></code> element of the <code>config.xml</code> file and sending a new <code>appcontrol</code> event to the receiving application.</p>
<p>The following code example demonstrates a service description in the <code>config.xml</code> file, which can handle an image editing application control request without reloading the Web page:</p>
<pre class="prettyprint">
<tizen:app-control>
<li>Receiving push notifications
<p>You can <a href="#Receiving">connect to the push service and start receiving push notifications</a>.</p> </li>
<li>Retrieving missed push messages
- <p>While the application is not running, messages cannot be delivered. You can <a href="#UnreadNotifications">retrieve such missed push messages</a> later on.</p></li>
+ <p>While the application is not running, messages cannot be delivered. You can <a href="#UnreadNotifications">retrieve such missed push messages</a> later.</p></li>
<li>Getting push messages when the application is launched by the push service
<p>The application can be launched by the push service. In that case, you must <a href="#HandlingWhenLaunched">determine the reason for the launch, and react to it</a> appropriately. If the application is launched due to a notification, you can <a href="#GetPushMessage">retrieve and read the last message delivered from the push service</a>.</p></li>
<li>Sending push notifications
<div id="container"><div id="contents"><div class="content">
<h1>IME Application</h1>
-<p>Tizen Web IME (Input Method Editor) applications are written in HTML5 for Tizen, combining HTML, JavaScript, and CSS into a package that can be installed on a Tizen device, such as Samsung Gear, or the Tizen emulator. Both the Tizen device and the emulator must run Tizen version 2.3 or later to run Web IME applications.</p>
+<p>Tizen Web IME (Input Method Editor) applications are written in HTML5 for Tizen, combining HTML, JavaScript, and CSS into a package that can be installed on a Tizen device, such as Samsung Gear, or the Tizen emulator. Both the Tizen device and the emulator must run Tizen version 2.3 or higher to run Web IME applications.</p>
<p>This feature is supported in wearable applications only.</p>
<li>To add remote device information, click <strong>New</strong>.
<p>In a dialog box, enter the <strong>Name</strong>, <strong>IP</strong>, and <strong>Port</strong> of the remote device.</p>
-<p>To modify the remote device information later on, select the device in the Remote Device Manager, click <strong>Edit</strong>, and modify the <strong>Name</strong>, <strong>IP</strong>, and <strong>Port</strong> in a dialog box.</p></li>
+<p>To modify the remote device information later, select the device in the Remote Device Manager, click <strong>Edit</strong>, and modify the <strong>Name</strong>, <strong>IP</strong>, and <strong>Port</strong> in the dialog box.</p></li>
</ul>
</li>
<li>In the Remote Device Manager, select a remote device.</li>
</li>
</ul>
<h2 id="data">Data Load and Save Dialogs</h2>
-<p>You can save the tracing result into a file and load it later on for analysis:</p>
+<p>You can save the tracing result into a file and load it later for analysis:</p>
<ul>
<li>You can save the analysis result to a zip file.
<p align="center"><strong>Figure: Saving data</strong></p>
<ul>
<li>Installer, Package Manager, and Uninstaller
<ul>
- <li>The Tizen Studio does not support OpenJDK any longer. Also, it requires Oracle JDK 1.8 or later.</li>
+ <li>The Tizen Studio does not support OpenJDK any longer. Also, it requires Oracle JDK 1.8 or higher.</li>
<li>The new UX has been applied to the Installer, Package Manager (Update Manager), and Uninstaller.</li>
<li>The Update Manager title has been changed to <strong>Package Manager</strong>. The older versions of the Update Manager do not support the auto-update to the new Package Manager. If you want to use the new Package Manager, install the Tizen Studio using the new Installer.</li>
<li>The Package Manager tabs have been changed to <strong>Main SDK</strong>, <strong>Extension SDK</strong>, and <strong>Progress</strong>:
</li>
<li>SDB
<ul>
- <li>To use the SDB bash completion feature, enter the <code>source .sdb-complete.bash</code> command on the bash shell. The feature runs manually from the official Tizen 2.4 release onwards due to the Installer and Update Manager issue.</li>
+ <li>To use the SDB bash completion feature, enter the <code>source .sdb-complete.bash</code> command on the bash shell. The feature runs manually since the official Tizen 2.4 release due to the Installer and Update Manager issue.</li>
</ul>
</li>
</ul>
<p id="on_Windows"></p>
<h2>Installing Intel® HAXM on Windows®</h2>
-<p>Supported Windows® versions: 8.1/8/7 (32/64-bit), Vista (32/64-bit), XP SP2 or later (32-bit only)</p>
+<p>Supported Windows® versions: 8.1/8/7 (32/64-bit), Vista (32/64-bit), XP SP2 or higher (32-bit only)</p>
<p><strong>HAXM is installed automatically as part of the Tizen Studio</strong>. If you want to install the HAXM individually, visit <a href="http://download.tizen.org/sdk/haxm/6.0.4/win/" target="_blank">http://download.tizen.org/sdk/haxm/6.0.4/win/</a> and download the Windows installer package.
</p>
<li>Adjust the amount of RAM to be allocated to Intel® HAXM.
<p align="center"> <img alt="Adjust RAM" src="../images/hardware_ram.png" /> </p>
- <p>The installer also functions as a configuration tool for Intel® HAXM. To change the memory settings later on, run the installer again.</p>
+ <p>The installer also functions as a configuration tool for Intel® HAXM. To change the memory settings later, run the installer again.</p>
<div class="note">
<strong>Note</strong>
</li>
<li>Adjust the amount of RAM to be allocated to Intel® HAXM or set it to <strong>2048 MB</strong> as the default value.
<p align="center"> <img alt="Default value" src="../images/hardware_os_default.png" /> </p>
- <p>The installer also functions as a configuration tool for Intel® HAXM. To change the memory settings later on, run the installer again.</p>
+ <p>The installer also functions as a configuration tool for Intel® HAXM. To change the memory settings later, run the installer again.</p>
</li>
<li>Confirm your Intel® HAXM memory allocation settings, and click <strong>Continue</strong>.
<p align="center"> <img alt="Memory limit" src="../images/hardware_os_continue.png" /> </p>
<li><code>reload</code> <p>Optional; sets whether the page is reloaded when it is already loaded (available values: <code>enable</code> (default), <code>disable</code>)</p><p><strong>Since: 2.4</strong></p>
<div class="note">
<strong>Note</strong>
- The <code>reload</code> attribute is supported from Tizen 2.4 onwards. If the <code>required_version</code> in the application's <code>config.xml</code> file is set to a version older than Tizen 2.4, and the <code>reload</code> attribute is used, the application installation fails.
+ The <code>reload</code> attribute is supported since Tizen 2.4. If the <code>required_version</code> in the application's <code>config.xml</code> file is set to a version older than Tizen 2.4, and the <code>reload</code> attribute is used, the application installation fails.
</div>
</li>
</ul>
<p><strong>Since: 2.4</strong></p>
<div class="note">
<strong>Note</strong>
- The <code>launch_mode</code> attribute is supported from Tizen 2.4 onwards. If the <code>required_version</code> in the application's <code>config.xml</code> file is set to a version older than Tizen 2.4, and the <code>launch_mode</code> attribute is used, the application installation fails.
+ The <code>launch_mode</code> attribute is supported since Tizen 2.4. If the <code>required_version</code> in the application's <code>config.xml</code> file is set to a version older than Tizen 2.4, and the <code>launch_mode</code> attribute is used, the application installation fails.
</div>
</li>
</ul><p><strong>Example:</strong></p><pre class="prettyprint"><tizen:application id="1234abcDEF.projectname"
<div class="note">
<strong>Note</strong>
- The <code>reload</code> attribute is supported from Tizen 2.4 onwards. If the <code>required_version</code> in the application's <code>config.xml</code> file is set to a version older than Tizen 2.4, and the <code>reload</code> attribute is used, the application installation fails.
+ The <code>reload</code> attribute is supported since Tizen 2.4. If the <code>required_version</code> in the application's <code>config.xml</code> file is set to a version older than Tizen 2.4, and the <code>reload</code> attribute is used, the application installation fails.
</div>
</li>
</ul>
<div class="note">
<strong>Note</strong>
The <code>ambient_support</code> option is only used for watch applications, and ignored in all non-watch applications.
- <p>The <code>ambient_support</code> attribute is supported from Tizen 2.3.1 onwards. If the <code>required_version</code> in the application's <code>config.xml</code> file is set to a version older than Tizen 2.3.1, and the <code>ambient_support</code> attribute is used, the application installation fails.</p>
+ <p>The <code>ambient_support</code> attribute is supported since Tizen 2.3.1. If the <code>required_version</code> in the application's <code>config.xml</code> file is set to a version older than Tizen 2.3.1, and the <code>ambient_support</code> attribute is used, the application installation fails.</p>
</div>
</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>
<p><strong>Since: 2.4</strong></p>
<div class="note">
<strong>Note</strong>
- The <code>launch_mode</code> attribute is supported from Tizen 2.4 onwards. If the <code>required_version</code> in the application's <code>config.xml</code> file is set to a version older than Tizen 2.4, and the <code>launch_mode</code> attribute is used, the application installation fails.
+ The <code>launch_mode</code> attribute is supported since Tizen 2.4. If the <code>required_version</code> in the application's <code>config.xml</code> file is set to a version older than Tizen 2.4, and the <code>launch_mode</code> attribute is used, the application installation fails.
</div>
</li>
</ul><p><strong>Example:</strong> </p><pre class="prettyprint"><tizen:application id="1234abcDEF.projectname"
</pre>
</li>
<li>Set the display mode.
-<p>The available display modes are defined in the <code>player_display_mode_e</code> enumeration (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__MEDIA__PLAYER__DISPLAY__MODULE.html#gaafcf6f7487d8cb376e1851a6e1253f3a">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__MEDIA__PLAYER__DISPLAY__MODULE.html#gaafcf6f7487d8cb376e1851a6e1253f3a">wearable</a> applications). Note that the DST ROI mode is deprecated from Tizen 3.0.</p>
+<p>The available display modes are defined in the <code>player_display_mode_e</code> enumeration (in <a href="../../../../org.tizen.native.mobile.apireference/group__CAPI__MEDIA__PLAYER__DISPLAY__MODULE.html#gaafcf6f7487d8cb376e1851a6e1253f3a">mobile</a> and <a href="../../../../org.tizen.native.wearable.apireference/group__CAPI__MEDIA__PLAYER__DISPLAY__MODULE.html#gaafcf6f7487d8cb376e1851a6e1253f3a">wearable</a> applications). Note that the DST ROI mode is deprecated since Tizen 3.0.</p>
<pre class="prettyprint">
error_code = player_set_display_mode(ad->player, PLAYER_DISPLAY_MODE_FULL_SCREEN);
dlog_print(DLOG_ERROR, LOG_TAG, "player_set_display_mode = %d", error_code);
projects / sdk / online-doc.git / commitdiff