From: Editor Lionbridge Date: Mon, 15 May 2017 08:27:45 +0000 (+0300) Subject: Change Mac OS X to macOS X-Git-Tag: GitHub/PR#40/tizen-studio~175^2 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=def79328610b03de7280f91271d5b7e7f08624cc;p=sdk%2Fonline-doc.git Change Mac OS X to macOS 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 --- diff --git a/org.tizen.guides/html/native/graphics/vulkan_n.htm b/org.tizen.guides/html/native/graphics/vulkan_n.htm index 39bbbe4..346c078 100644 --- a/org.tizen.guides/html/native/graphics/vulkan_n.htm +++ b/org.tizen.guides/html/native/graphics/vulkan_n.htm @@ -127,7 +127,7 @@

SDL

-

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 SDL Web site.

+

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 SDL Web site.

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 OpenGL ES guide.

diff --git a/org.tizen.guides/html/native/ui/efl/core_loop_n.htm b/org.tizen.guides/html/native/ui/efl/core_loop_n.htm index 98649ad..4bf117e 100644 --- a/org.tizen.guides/html/native/ui/efl/core_loop_n.htm +++ b/org.tizen.guides/html/native/ui/efl/core_loop_n.htm @@ -47,7 +47,7 @@

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.

-

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.

+

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.

  • Threads

    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.

    diff --git a/org.tizen.guides/html/native/ui/efl/introduction_n.htm b/org.tizen.guides/html/native/ui/efl/introduction_n.htm index a6b44b7..e829760 100644 --- a/org.tizen.guides/html/native/ui/efl/introduction_n.htm +++ b/org.tizen.guides/html/native/ui/efl/introduction_n.htm @@ -70,7 +70,7 @@
  • Small memory footprint

    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.

  • Backend engine support -

    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.

    • +

    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.

  • GUI and logic separation

    EFL supports a GUI layout (EDC) and logic separation by having the layout description in a plain text file and the logic code in the C or C++ source files.

  • Themeable diff --git a/org.tizen.guides/html/web/app_management/web_widget_ww.htm b/org.tizen.guides/html/web/app_management/web_widget_ww.htm index 77e8312..945537b 100644 --- a/org.tizen.guides/html/web/app_management/web_widget_ww.htm +++ b/org.tizen.guides/html/web/app_management/web_widget_ww.htm @@ -960,7 +960,7 @@ tizen.application.launch('ApplicationIDToLaunch', onGetAppsContextSuccess);

    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).

    -

    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:

    +

    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: