Also fixed trademark issues for Android, iOS, and iPhone.
This is a manual cherry-pick from the #126188 change
in the tizen_3.0 branch.
PS2: Removed extra ";".
Change-Id: Ic3765630e3f7abb5bf78b5672f33faf7d9f849a1
<h2 id="sdl">SDL</h2>
-<p>SDL (Simple DirectMedia Layer) is a cross-platform software development library. In Tizen, it enables access to graphics hardware using Vulkan. SDL is used for creating high-performance computer games, multimedia applications, and emulators. It provides a low-level hardware abstraction layer to computer multimedia hardware components. It can run on many operating systems, such as Android
, iOS, Linux, Mac OS X, Windows, and Tizen. For more information, see the <a href="https://libsdl.org/" target="_blank">SDL Web site</a>.</p>
+<p>SDL (Simple DirectMedia Layer) is a cross-platform software development library. In Tizen, it enables access to graphics hardware using Vulkan. SDL is used for creating high-performance computer games, multimedia applications, and emulators. It provides a low-level hardware abstraction layer to computer multimedia hardware components. It can run on many operating systems, such as Android
™, iOS, Linux, macOS, Windows®, and Tizen. For more information, see the <a href="https://libsdl.org/" target="_blank">SDL Web site</a>.</p>
<p>You can manage video, audio, some input devices, threads, and timers with SDL. Tizen supports SDL to provide new means of accessing its 3D APIs (Vulkan), which can currently be accessed only through an EFL wrapper library (Evas GL). For more information on Evas GL, see the <a href="../graphics/opengl_n.htm">OpenGL ES</a> guide.</p>
<p>Most applications start and end the main loop, which is used in special situations, such as propagation of events to UI components for handling and updating the application appearance and state. That guarantees the delivery of all events received from low-level input devices, and provides an accurate and speedy render event loop for synchronizing the application UI with events.</p>
-<p>The Ecore library provides main loop abstraction with a clean and tiny event loop library. Applications mainly deal with file descriptor handling, event handling, and timer handling from the beginning of the main loop. In addition, Ecore provides several modules related to, for example, Audio, Cocoa, Connection, Drm, FrameBuffer, Input, IPC, Wayland, Win32, and X11 with convenient methods to communicate with underlying operating systems, such as Ubuntu, Windows®, or Mac OS® X.</p>
+<p>The Ecore library provides main loop abstraction with a clean and tiny event loop library. Applications mainly deal with file descriptor handling, event handling, and timer handling from the beginning of the main loop. In addition, Ecore provides several modules related to, for example, Audio, Cocoa, Connection, Drm, FrameBuffer, Input, IPC, Wayland, Win32, and X11 with convenient methods to communicate with underlying operating systems, such as Ubuntu, Windows®, or macOS.</p>
</li>
<li><a href="threads_n.htm">Threads</a>
<p>The Ecore library provides concurrent processing mechanisms through Ecore threads. An Ecore thread is not a simple wrapper for standard POSIX threads, and it is not meant to be used to run parallel tasks throughout the entire duration of the application, especially when these tasks are performance-critical. Ecore manages tasks using a pool of threads based on system configuration, such as the number of processors the system has, and the maximum amount of concurrent threads set for the application.</p>
<li><strong>Small memory footprint</strong>
<p>Despite its fast performance, EFL's memory footprint is smaller than that of other toolkits with similar features. A small memory footprint is useful in the embedded world, since embedded devices do not normally have much memory.</p></li>
<li><strong>Backend engine support</strong>
- <p>EFL supports several backend engines, such as X11 (OpenGL, Xlib, Xcb), Wayland (OpenGL, SHM), Direct Framebuffer, DRM, memory buffers, PS3 native, Windows®, and Mac OS®. Applications do not need to deal with each backend engine separately.</p></li>
+ <p>EFL supports several backend engines, such as X11 (OpenGL, Xlib, Xcb), Wayland (OpenGL, SHM), Direct Framebuffer, DRM, memory buffers, PS3 native, Windows®, and macOS. Applications do not need to deal with each backend engine separately.</p></li>
<li><strong>GUI and logic separation</strong>
<p>EFL supports a GUI layout (<a href="learn_edc_intro_n.htm">EDC</a>) and logic separation by having the layout description in a plain text file and the logic code in the C or C++ source files.</p></li>
<li><strong>Themeable</strong>
<p>The widget and its parent application can reside on separate devices, as when a Web widget is on a wearable device while the host (parent) application is on a mobile device. In this case, the widget and parent applications can communicate through SAP (Samsung Accessory Protocol) to share data between the widget (the consumer in SAP) and the parent application (the provider in SAP).</p>
-<p>The following example shows SAP communication implementation between a Web widget on a Tizen wearable device and its parent application on an Android mobile device:</p>
+<p>The following example shows SAP communication implementation between a Web widget on a Tizen wearable device and its parent application on an Android™ mobile device:</p>
<ul>
<li>Widget on a Tizen wearable device:
<p>The Tizen Advanced UI (TAU)-based template provides 2 scaling methods: device-width and fixed-width.</p>
<ul>
<li>Device-width scaling
- <p>This scaling mode is suited for most mobile devices, such as Tizen, iPhone® and Android®. In this mode, the viewport width is set to <code>device-width</code>, enabling rem scaling using the Rem and Em units. These units calculate the size of a source element automatically based on the container font size (Em) or the base font size (Rem). In Tizen Web applications, a 320 px screen width is assumed.</p>
+ <p>This scaling mode is suited for most mobile devices, such as Tizen, iPhone, and Android™. In this mode, the viewport width is set to <code>device-width</code>, enabling rem scaling using the Rem and Em units. These units calculate the size of a source element automatically based on the container font size (Em) or the base font size (Rem). In Tizen Web applications, a 320 px screen width is assumed.</p>
<pre class="prettyprint">
<meta name="viewport" content="width=device-width, initial-scale=1, user-scalable=no">
</pre>
<div class="note">
<strong>Note</strong>
- In case of using 3D effects, <code>-webkit-transform: translateZ(0);</code> can be used to accelerate the hardware. However, since hardware acceleration support varies between the OS and devices, the actual resulting effects can vary too. Moreover, in the case of version Android™ 2.1, iOS™3.X and below, note that transition and animation may not be realized.
+ In case of using 3D effects, <code>-webkit-transform: translateZ(0);</code> can be used to accelerate the hardware. However, since hardware acceleration support varies between the OS and devices, the actual resulting effects can vary too. Moreover, in the case of version Android 2.1, iOS 3.X and below, note that transition and animation may not be realized.
</div>
</li>
<li>Create a modal layer pop-up using CSS3:
<div class="note">
<strong>Note</strong>
- If CSS is used, the handling of JavaScript events and UI DOM operations becomes unnecessary, so the load of the UI thread decreases, and the usage of CPU memory decreases as well. However, CSS3 transitions cannot be applied to versions below Android™ 2.3 and for versions above iOS™ 4.3, which are still widely used, so attention is needed when distributing it to various devices.
+ If CSS is used, the handling of JavaScript events and UI DOM operations becomes unnecessary, so the load of the UI thread decreases, and the usage of CPU memory decreases as well. However, CSS3 transitions cannot be applied to versions below Android 2.3 and for versions above iOS 4.3, which are still widely used, so attention is needed when distributing it to various devices.
</div>
<h2 id="hw" name="hw">Using Hardware Acceleration</h2>
<ul>
<li>Display a list of all configurations for which values are set.
- <p>Windows®, Ubuntu, and Mac OS® X:</p>
+ <p>Windows®, Ubuntu, and macOS:</p>
<pre class="prettyprint">
> tizen cli-config -l
> tizen cli-config –g "default.profiles.path=C:\Users\workspace\.metadata\.plugins\org.tizen.common.sign\profiles.xml"
</pre>
- <p>Ubuntu and Mac OS® X:</p>
+ <p>Ubuntu and macOS:</p>
<pre class="prettyprint">
$ tizen cli-config –g default.profiles.path=~/workspace/.metadata/.plugins/org.tizen.common.sign/profiles.xml
</pre>
<p><strong>Examples:</strong></p>
<ul>
<li>List all native application templates.
- <p>Windows®, Ubuntu, and Mac OS® X:</p>
+ <p>Windows®, Ubuntu, and macOS:</p>
<pre class="prettyprint">
> tizen list native-project
</pre>
</li>
<li>List rootstraps.
- <p>Windows®, Ubuntu, and Mac OS® X:</p>
+ <p>Windows®, Ubuntu, and macOS:</p>
<pre class="prettyprint">
> tizen list rootstrap
> cd C:\Users\workspace\basic
</pre>
- <p>Ubuntu and Mac OS® X:</p>
+ <p>Ubuntu and macOS:</p>
<pre class="prettyprint">
$ tizen create native-project -p mobile-2.3 -t basic_ui -n basic -- ~/workspace
> dir C:\Users\workspace\basic\Debug
</pre>
- <p>Ubuntu and Mac OS® X:</p>
+ <p>Ubuntu and macOS:</p>
<pre class="prettyprint">
$ tizen build-native -a x86 -c llvm -C Debug -- ~/workspace/basic
> dir C:\Users\workspace\basic\Release
</pre>
- <p>Ubuntu and Mac OS® X:</p>
+ <p>Ubuntu and macOS:</p>
<pre class="prettyprint">
$ tizen build-native -r mobile-2.4-device.core -C Release -- ~/workspace/basic
$ dir C:\Users\workspace\basicWeb\.buildResult
</pre>
- <p>Ubuntu and Mac OS® X:</p>
+ <p>Ubuntu and macOS:</p>
<pre class="prettyprint">
$ tizen build-web -- ~/workspace/basicWeb
> tizen clean -- C:\Users\workspace\basic
</pre>
- <p>Ubuntu and Mac OS® X:</p>
+ <p>Ubuntu and macOS:</p>
<pre class="prettyprint">
$ tizen clean -- ~/workspace/basic
'mycert' has been generated in 'C:\tizen-sdk-data\keystore\author'.
</pre>
- <p>Ubuntu and Mac OS® X:</p>
+ <p>Ubuntu and macOS:</p>
<pre class="prettyprint">
$ tizen certificate -a MyTizen -p 1234 -c KR -s Seoul -ct Gangnamgu -o Tizen –u
If want to sign by this, add the file of security profiles in CLI configuration like 'tizen cli-config "default.profiles.path=C:\tizen-sdk-data\ide\keystore\profiles.xml"'.
</pre>
- <p>Ubuntu and Mac OS® X:</p>
+ <p>Ubuntu and macOS:</p>
<pre class="prettyprint">
$ tizen security-profiles add -n MyProfile -a ~/tizen-sdk-data/keystore/author/mycert.p12 -p 1234
MyProfile
</pre>
- <p>Ubuntu and Mac OS® X:</p>
+ <p>Ubuntu and macOS:</p>
<pre class="prettyprint">
$ tizen security-profiles list
distributor1 CA path: C:\tizen-sdk\tools\certificate-generator\certificates\distributor\tizen-distributor-ca.cer
</pre>
- <p>Ubuntu and Mac OS® X:</p>
+ <p>Ubuntu and macOS:</p>
<pre class="prettyprint">
$ tizen security-profiles list –n MyProfile
Succeed to remove 'MyProfile' profile
</pre>
- <p>Ubuntu and Mac OS® X:</p>
+ <p>Ubuntu and macOS:</p>
<pre class="prettyprint">
$ tizen security-profiles remove
Package File Location: C:\Users\workspace\basic\Debug\org.tizen.basic-1.0.0-i386.tpk
</pre>
- <p>Ubuntu and Mac OS® X:</p>
+ <p>Ubuntu and macOS:</p>
<pre class="prettyprint">
$ tizen package -t tpk -s MyProfile -- ~/workspace/basic/Debug
Package (C:\Users\workspace\basic\Debug\org.tizen.basic-1.0.0-i386.tpk) is created successfully.
</pre>
- <p>Ubuntu and Mac OS® X:</p>
+ <p>Ubuntu and macOS:</p>
<pre class="prettyprint">
$ tizen package -t tpk -s MyProfile -- ~/workspace/basic/Debug/org.tizen.basic-1.0.0-i386.tpk
<p><strong>Examples:</strong></p>
<ul>
<li>Package the Web multi application.
- <p>Windows®, Ubuntu, and Mac OS® X:</p>
+ <p>Windows®, Ubuntu, and macOS:</p>
<pre class="prettyprint">
> tizen build-app -p "name:webp1,targets:[webbasic,webwidget]"
</ul>
<ul>
<li>Package the native multi package with the debug and release build configurations.
- <p>Windows®, Ubuntu, and Mac OS® X:</p>
+ <p>Windows®, Ubuntu, and macOS:</p>
<pre class="prettyprint">
> tizen build-app -m "name:m1,configs:[Debug,Release]" -b "name:b1,targets:[basic,service],methods:[m1]" -p "name:nativep1,targets:[b1]" -s MyProfile
> tizen install -n org.tizen.basic-1.0.0-i386.tpk -s emulator-26101 -- C:\Users\workspace\basic\Debug
</pre>
- <p>Ubuntu and Mac OS® X:</p>
+ <p>Ubuntu and macOS:</p>
<pre class="prettyprint">
$ tizen install -n org.tizen.basic-1.0.0-i386.tpk -s emulator-26101 -- ~/workspace/basic/Debug
<p><strong>Examples:</strong></p>
<ul>
<li>Run the basic application, whose package ID is <code>org.tizen.basic</code>, on the emulator-26101.
- <p>Windows®, Ubuntu, and Mac OS® X:</p>
+ <p>Windows®, Ubuntu, and macOS:</p>
<pre class="prettyprint">
> $ tizen run -p org.tizen.basic -s emulator-26101
<p><strong>Examples:</strong></p>
<ul>
<li>Uninstall the basic application, whose package ID is <code>org.tizen.basic</code>, from the emulator-26101.
- <p>Windows®, Ubuntu, and Mac OS® X:</p>
+ <p>Windows®, Ubuntu, and macOS:</p>
<pre class="prettyprint">
> tizen uninstall -p org.tizen.basic -s emulator-26101
<p><strong>Examples:</strong></p>
<ul>
<li>Display the manual for the create command.
- <p>Windows®, Ubuntu, and Mac OS® X:</p>
+ <p>Windows®, Ubuntu, and macOS:</p>
<pre class="prettyprint">
> tizen manual create
> tizen.bat create native-project -p mobile-2.4 -t basic-ui -n basic --
C:\Users\workspace
>cd C:\Users\workspace\basic
- Ubuntu and Mac OS® X:
+ Ubuntu and macOS:
$ tizen create native-project -p mobile-2.4 -t basic-ui -n basic -- /ho
me/workspace
$ cd /home/workspace/basic
<p><strong>Examples:</strong></p>
<ul>
<li>Display the CLI version number.
- <p>Windows®, Ubuntu, and Mac OS® X:</p>
+ <p>Windows®, Ubuntu, and macOS:</p>
<pre class="prettyprint">
> tizen version
</tr>
<tr>
<th>Windows®</th>
- <th>Mac OS® X</th>
+ <th>macOS</th>
</tr>
<tr>
<td rowspan="4">File</td>
<ul>
<li>Windows®: <strong>Startup > Tizen Studio > Tools > Dynamic Analyzer</strong></li>
<li>Ubuntu: <strong>Applications > Dynamic Analyzer</strong></li>
- <li>Mac OS® X: <strong>Launchpad > Dynamic Analyzer</strong></li>
+ <li>macOS: <strong>Launchpad > Dynamic Analyzer</strong></li>
</ul>
</li>
<li><strong>In the Project Explorer view:</strong>
<h2 id="speed">Increasing the Application Execution Speed</h2>
-<p>The Tizen x86 emulator exploits <a href="http://www.linux-kvm.org/page/Main_Page" target="_blank">KVM</a> (Kernel-based Virtual Machine in Linux) or <a href="https://developer.tizen.org/sdk/haxm" target="_blank">HAX</a> (Hardware Accelerated eXecution in Windows® and Mac OS® X) with HW virtualization support.</p>
+<p>The Tizen x86 emulator exploits <a href="http://www.linux-kvm.org/page/Main_Page" target="_blank">KVM</a> (Kernel-based Virtual Machine in Linux) or <a href="https://developer.tizen.org/sdk/haxm" target="_blank">HAX</a> (Hardware Accelerated eXecution in Windows® and macOS) with HW virtualization support.</p>
<p>If the CPU VT is disabled in the <strong>Emulator Configuration</strong> view on the Emulator Manager, check the following prerequisites and install KVM or HAX:</p>
<ol>
<li>In Windows®:
<p>To use HAX, you need an Intel VT-x-supported CPU, and you must enable the NX-related setting in the PC BIOS.</p>
</li>
-<li>In Mac OS® X:
-<p>To use HAX, install EFI-related updates on your Intel-based Mac system.</p>
-<p>For more information, see <a href="http://support.apple.com/kb/HT1237" target="_blank">EFI and SMC firmware updates for Intel-based Macs</a>.</p>
+<li>In macOS:
+<p>To use HAX, install EFI-related updates on your Intel-based Mac computer.</p>
+<p>For more information, see <a href="http://support.apple.com/kb/HT1237" target="_blank">EFI and SMC firmware updates for Intel-based Mac computers</a>.</p>
</li>
</ul>
</li>
<li>In Ubuntu:
<p>No installation is required for KVM.</p>
</li>
-<li>In Windows® and Mac OS® X:
+<li>In Windows® and macOS:
<p>The HAXM driver is installed during the Tizen Studio installation. See the installation manual on the <a href="https://developer.tizen.org/sdk/haxm" target="_blank">Tizen Developers site</a>.</p>
</li>
</ul>
<h3>Working with the HW Virtualization, Settings, and Help</h3>
<p>To run the emulator with the HW virtualization support in the Emulator Manager, set the <strong>CPU VT</strong> field to <strong>ON</strong>. The field is disabled if your system cannot support HW virtualization.</p>
-<p>You can also run the emulator with the HW virtualization support from the command line, by including the <code>-enable-kvm</code> (in Ubuntu) or <code>-enable-hax</code> (in Windows® and Mac OS® X) option in the start-up command.</p>
+<p>You can also run the emulator with the HW virtualization support from the command line, by including the <code>-enable-kvm</code> (in Ubuntu) or <code>-enable-hax</code> (in Windows® and macOS) option in the start-up command.</p>
<h2 id="supported">Supported Features</h2>
<ul>
<li>Emulator name (the top row in the menu)
<p>The <strong>Detailed Info</strong> window is displayed, showing the <strong>Shortcut Info</strong> and <strong>VM Info</strong> tabs. The <strong>Shortcut Info</strong> tab lists the <a href="keyboard_shortcuts.htm#emulator">emulator keyboard shortcuts</a> and the <strong>VM Info</strong> tab defines the virtual machine details.</p>
-<p>In Mac OS® X: To use the emulator keyboard shortcuts, open the Keyboard Setting dialog and switch your Mac function keys option to work as standard function keys.</p>
+<p>In macOS: To use the emulator keyboard shortcuts, open the Keyboard Setting dialog and switch your macOS function keys option to work as standard function keys.</p>
<p align="center" class="Table"><strong>Table: VM Info</strong></p>
<table border="1">
<h2 id="multi" name="multi">Using Multi-point Touch</h2>
-<p>To create a multi-point touch effect in the emulator, press and hold the <strong>Ctrl</strong> key (<strong>Command</strong> key in Mac OS® X), while mouse-clicking on the emulator screen.</p>
+<p>To create a multi-point touch effect in the emulator, press and hold the <strong>Ctrl</strong> key (<strong>Command</strong> key in macOS), while mouse-clicking on the emulator screen.</p>
<h3 id="add" name="add">Adding a Touch Point</h3>
-<p>To add a touch point on the emulator screen, press and hold the <strong>Ctrl</strong> key (<strong>Command</strong> key in Mac OS® X) and mouse-click a point on the screen.</p>
+<p>To add a touch point on the emulator screen, press and hold the <strong>Ctrl</strong> key (<strong>Command</strong> key in macOS) and mouse-click a point on the screen.</p>
<p>You can add touch points up to the maximum amount of multi-point touches. To get the maximum amount, use the <code>System::SystemInfo::GetValue()</code> method with the <code>MultiPointTouchCount</code> key.</p>
<p align="center"><strong>Figure: Adding a touch point</strong></p>
<h3 id="move" name="move">Moving an Existing Point</h3>
-<p>To move an existing point one by one, press and hold the <strong>Ctrl</strong> key (<strong>Command</strong> key in Mac OS® X), mouse-click an existing point, and move it to another location on the screen.</p>
+<p>To move an existing point one by one, press and hold the <strong>Ctrl</strong> key (<strong>Command</strong> key in macOS), mouse-click an existing point, and move it to another location on the screen.</p>
<p align="center"><strong>Figure: Moving an existing point</strong></p>
<p align="center"><img alt="Moving an existing point" src="../images/emulator_feature_multitouch_move1.png"/></p>
-<p>To move all existing points together, press and hold the <strong>Ctrl</strong> (<strong>Command</strong> in Mac OS® X) and <strong>Shift</strong> keys, mouse-click an existing point, and move it to another location on the screen.</p>
+<p>To move all existing points together, press and hold the <strong>Ctrl</strong> (<strong>Command</strong> in macOS) and <strong>Shift</strong> keys, mouse-click an existing point, and move it to another location on the screen.</p>
<p align="center"><strong>Figure: Moving all existing points</strong></p>
<p align="center"><img alt="Moving all existing points" src="../images/emulator_feature_multitouch_move2.png"/></p>
-<p>To move 2 existing points symmetrically together, press and hold the <strong>Ctrl</strong> (<strong>Command</strong> in Mac OS® X) and <strong>Alt</strong> keys, mouse-click an existing point, and move it to another location on the screen.</p>
+<p>To move 2 existing points symmetrically together, press and hold the <strong>Ctrl</strong> (<strong>Command</strong> in macOS) and <strong>Alt</strong> keys, mouse-click an existing point, and move it to another location on the screen.</p>
<p align="center"><strong>Figure: Symmetrically moving 2 existing points</strong></p>
<p align="center"><img alt="Symmetrical moving the 2 existing points" src="../images/emulator_feature_multitouch_move3.png" /></p>
<h3 id="end" name="end">Ending the Multi-point Touch</h3>
-<p>To end the multi-point touch, release the <strong>Ctrl</strong> key (<strong>Command</strong> key in Mac OS® X). The touched points on the emulator screen are invalidated, and the next screen touch event is read as a new event, not part of the previous multi-point touch event.</p>
+<p>To end the multi-point touch, release the <strong>Ctrl</strong> key (<strong>Command</strong> key in macOS). The touched points on the emulator screen are invalidated, and the next screen touch event is read as a new event, not part of the previous multi-point touch event.</p>
<p align="center"><strong>Figure: Invalidating touched points</strong></p>
<strong>Note</strong>
<ul>
<li>Network bridging does not work when the underlying physical network device is a wireless device.</li>
-<li>On Mac OS® X, only physical network device named <code>en0</code> can be used for bridging.</li>
+<li>On macOS, only a physical network device named <code>en0</code> can be used for bridging.</li>
</ul>
</div>
<p>In the following host operating systems, you must configure the properties of the bridged network directly:</p>
-<ul><li id="Bridge_on_MAC">Bridge configuration on Mac OS® X Mavericks and above:
+<ul><li id="Bridge_on_MAC">Bridge configuration on macOS Mavericks and above:
<ol>
<li>In the <strong>Apple</strong> menu, click <strong>System Preferences > Network</strong>.</li>
<li>In the <strong>Action</strong> menu, click <strong>Manage Virtual Interfaces</strong>.</li>
<h3 id="eventpre" name="eventpre">Prerequisites</h3>
-<p>When connecting through USB, ADB is required to make a connection. If you have already installed the Android SDK on the computer, ADB is located in the <code><installed Android SDK>/sdk/platform-tools</code> folder. Otherwise, you can download only ADB or install the Android SDK.</p>
+<p>When connecting through USB, ADB is required to make a connection. If you have already installed the Android™ SDK on the computer, ADB is located in the <code><installed Android SDK>/sdk/platform-tools</code> folder. Otherwise, you can download only ADB or install the Android SDK.</p>
<p>To install ADB:</p>
- <ol><li><p>Ubuntu/Mac OS® X: Download ADB and then install it in the <code>/usr/bin</code> folder.</p>
+ <ol><li><p>Ubuntu/macOS: Download ADB and then install it in the <code>/usr/bin</code> folder.</p>
<p>For more information, see <a href="http://code.google.com/p/adb-fastboot-install/" target="_blank">ADB Fastboot Install</a>.</p></li>
<li><p>Windows®: Download ADB and install it in the <code>C:\ADB</code> folder.</p>
<p>For more information, see <a href="http://rubenalamina.mx/custom-installers/android-adb-fastboot/" target="_blank">ADB Fastboot for Windows</a>.</p></li></ol>
<tr>
<th style="text-align:center;">Ubuntu</th>
<th style="text-align:center;">Windows®</th>
- <th style="text-align:center;">Mac OS®</th>
+ <th style="text-align:center;">macOS</th>
</tr>
<tr>
<td><strong>Desktop > Applications > Emulator Manager:</strong>
<td><strong>Start > All Programs > Tizen Studio > Emulator Manager:</strong>
<p align="center"><img src="../images/emulator_manager_win_shortcut.png" alt="Shortcut Windows" /></p></td>
<td><strong>Finder > Applications > Tizen Studio > Emulator Manager:</strong>
- <p align="center"><img src="../images/emulator_manager_mac_shortcut.png" alt="Shortcut Mac" /></p></td>
+ <p align="center"><img src="../images/emulator_manager_mac_shortcut.png" alt="Shortcut macOS" /></p></td>
</tr>
</tbody>
</table>
<th>Command</th>
<th>Ubuntu</th>
<th>Windows®</th>
- <th>Mac OS® X</th>
+ <th>macOS</th>
</tr>
<tr>
<td>Delete</td>
<th>Command</th>
<th>Ubuntu</th>
<th>Windows®</th>
- <th>Mac OS® X</th>
+ <th>macOS</th>
</tr>
<tr>
<td>Build all</td>
<th>Command</th>
<th>Ubuntu</th>
<th>Windows®</th>
- <th>Mac OS® X</th>
+ <th>macOS</th>
</tr>
<tr>
<td>Step into</td>
<th>Command</th>
<th>Ubuntu</th>
<th>Windows®</th>
- <th>Mac OS® X</th>
+ <th>macOS</th>
</tr>
<tr>
<td>Content assist</td>
<th>Command</th>
<th>Ubuntu</th>
<th>Windows®</th>
- <th>Mac OS® X</th>
+ <th>macOS</th>
</tr>
<tr>
<td>New project and file using the Wizard</td>
<th>Command</th>
<th>Ubuntu</th>
<th>Windows®</th>
- <th>Mac OS® X</th>
+ <th>macOS</th>
</tr>
<tr>
<td>Find and replace</td>
<th>Command</th>
<th>Ubuntu</th>
<th>Windows®</th>
- <th>Mac OS® X</th>
+ <th>macOS</th>
</tr>
<tr>
<td>Rename-refactoring</td>
<th>Command</th>
<th>Ubuntu</th>
<th>Windows®</th>
- <th>Mac OS® X</th>
+ <th>macOS</th>
</tr>
<tr>
<td>Insert snippet</td>
<th colspan="2">Command</th>
<th>Ubuntu</th>
<th>Windows®</th>
- <th>Mac OS® X</th>
+ <th>macOS</th>
</tr>
<tr>
<td rowspan="4">HTML editor</td>
<th>Command</th>
<th>Ubuntu</th>
<th>Windows®</th>
- <th>Mac OS® X</th>
+ <th>macOS</th>
</tr>
<tr>
<td>About the analyzer</td>
<th>Command</th>
<th>Ubuntu</th>
<th>Windows®</th>
- <th>Mac OS® X</th>
+ <th>macOS</th>
</tr>
<tr>
<td>Delete virtual machine</td>
<th>Command</th>
<th>Ubuntu</th>
<th>Windows®</th>
- <th>Mac OS® X</th>
+ <th>macOS</th>
</tr>
<tr>
<td>Detailed info</td>
<th colspan="2">Command</th>
<th>Ubuntu</th>
<th>Windows®</th>
- <th>Mac OS® X</th>
+ <th>macOS</th>
</tr>
<tr>
<td rowspan="10">Common</td>
<th>Command</th>
<th>Ubuntu</th>
<th>Windows®</th>
- <th>Mac OS® X</th>
+ <th>macOS</th>
</tr>
<tr>
<td>Close the menu</td>
</li>
<li>CLI and SDB
<ul>
- <li>To use the SDB bash completion feature, enter the <code>source .sdb-complete.bash</code> command on the bash shell. The Tizen Studio does not support the SDB bash auto-completion on Windows® (it is available on Ubuntu and Mac OS® X).</li>
+ <li>To use the SDB bash completion feature, enter the <code>source .sdb-complete.bash</code> command on the bash shell. The Tizen Studio does not support the SDB bash auto-completion on Windows® (it is available on Ubuntu and macOS).</li>
</ul>
</li>
<li>Dynamic Analyzer
<ul>
<li>Installer, Package Manager, and Uninstaller
<ul>
- <li>If the SDK Update Notification appears when you start the Tizen IDE or emulator on Mac OS® X, a terminal (<code>shell.exec</code>) icon can appear on the dock for a few seconds.</li>
+ <li>If the SDK Update Notification appears when you start the Tizen IDE or emulator on macOS, a terminal (<code>shell.exec</code>) icon can appear on the dock for a few seconds.</li>
<li>If there is a multibyte character in the Tizen SDK installation path, some development packages have a difficulty in finding the installed SDK's location when they are working.</li>
</ul>
</li>
<li>EDC Editor
<ul>
<li>You cannot add a new EDC file from the IDE if the EDC Editor is already launched. To avoid this problem, quit the EDC Editor before you add a new EDC file.</li>
- <li>The EDC Editor application instances are limited to a single instance. However, due to a technical issue, multiple EDC Editor instances are allowed on Mac OS.</li>
+ <li>The EDC Editor application instances are limited to a single instance. However, due to a technical issue, multiple EDC Editor instances are allowed on macOS.</li>
</ul>
</li>
<li>Emulator
<li>Native Component Designer
<ul>
<li>The vector-type "part" is not supported. You cannot see the vector image and change the SVG file.</li>
- <li>Playing sound is not supported on Windows® or Mac OS® X.</li>
+ <li>Playing sound is not supported on Windows® or macOS.</li>
</ul>
</li>
<li>Emulator
<li>CLI and SDB
<ul>
- <li>The Tizen Studio does not support the SDB bash auto-completion on Windows® (it is available on Ubuntu and Mac OS® X).</li>
+ <li>The Tizen Studio does not support the SDB bash auto-completion on Windows® (it is available on Ubuntu and macOS).</li>
</ul>
</li>
<li>Native Component Designer
<ul>
<li>The vector-type "part" is not supported. You cannot see the vector image and change the SVG file.</li>
- <li>Playing sound is not supported on Windows® or Mac OS® X.</li>
+ <li>Playing sound is not supported on Windows® or macOS.</li>
</ul>
</li>
<li>Emulator
<li>CLI and SDB
<ul>
- <li>The Tizen Studio does not support the SDB bash auto-completion on Windows® (it is available on Ubuntu and Mac OS® X).</li>
+ <li>The Tizen Studio does not support the SDB bash auto-completion on Windows® (it is available on Ubuntu and macOS).</li>
</ul>
</li>
<h1>Download</h1>
-<p>The Tizen Studio is a comprehensive set of tools for developing Tizen native and Web applications. It consists of an IDE, emulator, toolchain, sample code, and documentation. Tizen Studio runs on Windows® and Ubuntu, as well as Mac OS® X. Tizen applications can be developed without relying on the official Tizen Studio, as long as the application complies with the Tizen packaging rules.</p>
+<p>The Tizen Studio is a comprehensive set of tools for developing Tizen native and Web applications. It consists of an IDE, emulator, toolchain, sample code, and documentation. Tizen Studio runs on Windows® and Ubuntu, as well as macOS. Tizen applications can be developed without relying on the official Tizen Studio, as long as the application complies with the Tizen packaging rules.</p>
<p>For installation instructions, see <a href="installing_sdk.htm">Installing Tizen Studio</a>. For more information, see <a href="1_2_0_release_notes.htm">Release Notes</a>.</p>
<p class="toc-title">Content</p>
<ul class="toc">
<li><a href="#on_Windows">Installing Intel® HAXM on Windows®</a></li>
- <li><a href="#on_MacOS">Installing Intel® HAXM on Mac OS®</a></li>
+ <li><a href="#on_MacOS">Installing Intel® HAXM on macOS</a></li>
</ul>
</div></div>
</div>
<div id="container"><div id="contents"><div class="content">
<h1>Hardware Accelerated Execution Manager</h1>
-<p>The Intel Hardware Accelerated Execution Manager (Intel® HAXM) is a hardware-assisted virtualization engine (hypervisor) that uses Intel Virtualization Technology (VT) to speed up Tizen application emulation on Windows® and
Mac OS® host machines. In combination with Tizen x86 emulator images and the <a href="../cover_page.htm">Tizen Studio</a>, Intel® HAXM speeds up the Tizen emulation on Intel-VT-enabled systems.</p>
-<p>This topic describes how to install the HAXM on your <a href="#on_Windows">Windows®</a> or <a href="#on_MacOS">Mac OS®</a> development system.</p>
+<p>The Intel Hardware Accelerated Execution Manager (Intel® HAXM) is a hardware-assisted virtualization engine (hypervisor) that uses Intel Virtualization Technology (VT) to speed up Tizen application emulation on Windows® and
macOS host machines. In combination with Tizen x86 emulator images and the <a href="../cover_page.htm">Tizen Studio</a>, Intel® HAXM speeds up the Tizen emulation on Intel-VT-enabled systems.</p>
+<p>This topic describes how to install the HAXM on your <a href="#on_Windows">Windows®</a> or <a href="#on_MacOS">macOS</a> development system.</p>
<p>Hardware requirements:</p>
<ul>
</ul>
<p id="on_MacOS"></p>
-<h2>Installing Intel® HAXM on Mac OS®</h2>
-<p>Supported Mac OS® versions: 10.10 Yosemite (64-bit), 10.9 Mavericks (64-bit), 10.8 Mountain Lion (64-bit)</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.1/mac/" target="_blank">http://download.tizen.org/sdk/haxm/6.0.1/mac/</a> and download the Mac installer package.</p>
+<h2>Installing Intel® HAXM on macOS</h2>
+<p>Supported macOS versions: 10.10 Yosemite (64-bit), 10.9 Mavericks (64-bit), 10.8 Mountain Lion (64-bit)</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.1/mac/" target="_blank">http://download.tizen.org/sdk/haxm/6.0.1/mac/</a> and download the macOS installer package.</p>
<p align="center" class="Table"><strong>Table: Windows installer package</strong></p>
<table>
<tbody>
<tr>
- <th>Mac installer</th>
+ <th>macOS installer</th>
<th>File description</th>
<th>File size</th>
<th>MD5 checksum</th>
<ul>
<li>On Microsoft Windows®, the command prompt opens and the installer is automatically executed.</li>
-<li>On Ubuntu and Mac OS® X, open the terminal, go to the directory where the installer is downloaded, and enter the <code>chmod +x</code> command to apply the execute permission to the installer file. Then, execute the installer by entering the command based on the following syntax:
+<li>On Ubuntu and macOS, open the terminal, go to the directory where the installer is downloaded, and enter the <code>chmod +x</code> command to apply the execute permission to the installer file. Then, execute the installer by entering the command based on the following syntax:
<pre class="prettyprint">
web-cli_Tizen_Studio_<version> [options] [<directory path>]
</pre>
<tr>
<th colspan="2"></th>
<th>Microsoft Windows®</th>
- <th>Mac OS®X</th>
+ <th>macOS</th>
<th>Ubuntu</th>
</tr>
<tr>
<p>Download the JDK from the <a href="http://www.oracle.com/technetwork/java/javase/downloads/index.html" target="_blank">official Oracle Web site</a>. Select the appropriate platform for your hardware architecture and Windows® version. Then, run the downloaded execution file and follow the displayed instructions.</p>
</li>
-<li>Mac OS® X
+<li>macOS
<p>Download the JDK from the <a href="http://www.oracle.com/technetwork/java/javase/downloads/index.html" target="_blank">official Oracle Web site</a> and follow the instructions to install the JDK.</p>
-<p>To support legacy Java software on
Mac OS® X, you must download and install the Java for Mac OS X 2015-001. Download it from <a href="https://support.apple.com/kb/DL1572" target="_blank">https://support.apple.com/kb/DL1572</a>.</p>
+<p>To support legacy Java software on
macOS, you must download and install the Java for OS X 2015-001. Download it from <a href="https://support.apple.com/kb/DL1572" target="_blank">https://support.apple.com/kb/DL1572</a>.</p>
</li>
<li>Ubuntu
<tr>
<th>Component</th>
<th>Microsoft Windows®</th>
- <th>Mac OS®X</th>
+ <th>macOS</th>
<th>Ubuntu</th>
</tr>
<tr>
</tbody>
</table>
-<p align="center" class="Table"><strong>Table: Additional Mac OS®X requirements</strong></p>
+<p align="center" class="Table"><strong>Table: Additional macOS requirements</strong></p>
<table>
<tbody>
<tr>
<p>To keep your certificates safe, find your author and distributor certificates in the following directory, and move them to other safe location:</p>
<ul>
-<li>Ubuntu and Mac OS® X:
+<li>Ubuntu and macOS:
<ul>
<li><code>/home/<user>/<TIZEN-SDK-DATA>/keystore/author.p12</code></li>
<li><code>/home/<user>/<TIZEN-SDK-DATA>/keystore/distributor.p12</code></li>
<p>You can uninstall the Tizen SDK using the Uninstaller tool, or by manually deleting the following directories (assuming that you had installed the SDK to the default directory):</p>
<ul>
-<li>Ubuntu and Mac OS® X:
+<li>Ubuntu and macOS:
<ul>
<li><code>/home/<user>/<TIZEN_SDK></code></li>
<li><code>/home/<user>/<TIZEN_SDK_DATA></code></li>
<ul>
<li>On Windows®, select <strong>Start > All Programs > Tizen Studio > Tools > Package Manager</strong>.</li>
- <li>On Mac OS® X, select <strong>Launchpad > Package Manager</strong>.</li>
+ <li>On macOS, select <strong>Launchpad > Package Manager</strong>.</li>
<li>On Ubuntu, select <strong>Dashboard Home > Package Manager</strong>.</li>
</ul>
<p>The <code>project_def.prop</code> file describes the project properties, such as project type and list of source files. When you edit the properties in the <code>project_def.prop</code> file to manipulate the build or packaging process, use the following characters:</p>
<ul>
-<li>"/" is a path separator character (in Windows®, Ubuntu, and Mac OS® X).</li>
+<li>"/" is a path separator character (in Windows®, Ubuntu, and macOS).</li>
<li>"\" is a multi-line character, which is used at the end of each line.</li>
<li>"\ " is a space character, used in a path name that contains a space character.</li>
<li>"#" is a comment character.</li>
<div class="note">
<strong>Note</strong>
- In Windows® and Linux, <strong>Preferences</strong> is located in the <strong>Window</strong> menu. However, in Mac OS® X, it is located in the <strong>Tizen Studio</strong> menu.
+ In Windows® and Linux, <strong>Preferences</strong> is located in the <strong>Window</strong> menu. However, in macOS, it is located in the <strong>Tizen Studio</strong> menu.
</div>
<p align="center"><strong>Figure: Tizen Studio preferences</strong></p>
<td><code>http://tizen.org/privilege/mediastorage</code></td>
<td>public</td>
<td>2.3 / 2.3.1</td>
-<td>When you connect the device to a computer (Windows or Mac) through USB, you can access a dedicated media storage area shown as massive media storage. This region of the storage is called media storage and is usually used for multimedia files, such as photos, videos, and music files. Since this storage area is used for user private data, access to it must be protected with a privilege.
+<td>When you connect the device to a computer (Windows® or macOS) through USB, you can access a dedicated media storage area shown as massive media storage. This region of the storage is called media storage and is usually used for multimedia files, such as photos, videos, and music files. Since this storage area is used for user private data, access to it must be protected with a privilege.
<p>If your application does not have this privilege, no file operations into the media storage area succeed and you receive a permission denied error. If you have this privilege, you can read and write directories and files, create new files, and delete files in the storage area.</p></td>
</tr>
<tr>
projects / sdk / online-doc.git / commitdiff