From: Young-Ae Kang
Date: Thu, 17 Nov 2016 08:41:11 +0000 (+0900)
Subject: Changed from org.tizen.tutorials to org.tizen.training.
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=refs%2Fchanges%2F29%2F98429%2F2;p=sdk%2Fonline-doc.git
Changed from org.tizen.tutorials to org.tizen.training.
PS2: [LB] Reviewed
Change-Id: I0fd2085743fa805c615f2bffb8a78d8186472d46
---
diff --git a/org.tizen.devtools/html/common_tools/da_overview.htm b/org.tizen.devtools/html/common_tools/da_overview.htm
index 95a9744..b1d2e94 100644
--- a/org.tizen.devtools/html/common_tools/da_overview.htm
+++ b/org.tizen.devtools/html/common_tools/da_overview.htm
@@ -26,7 +26,7 @@
Dynamic Analyzer
- You can monitor the performance and reliability of your native application on a target device or the Emulator by running the dynamic analyzer tool included within the Tizen SDK.
+ You can monitor the performance and reliability of your native application on a target device or the Emulator by running the dynamic analyzer tool included within the Tizen SDK.
Dynamic Analyzer provides various functions for profiling applications. To better understand the profiling result, you need to know about each component that tool screen contains, providing you with the tracing information of your application.
Figure: Dynamic Analyzer screen
@@ -83,7 +83,7 @@
The analysis result helps you to recognize and fix bottlenecks, bugs, and memory and resource leaks.
For instructions on running the dynamic analyzer and ways to analyze the result and utilize the result
- for improving your application performance, see Dynamic Analysis.
+ for improving your application performance, see Dynamic Analysis.
You can use table filtering to see only the information you want in the result table.
diff --git a/org.tizen.devtools/html/native_tools/api_privilege_checker_n.htm b/org.tizen.devtools/html/native_tools/api_privilege_checker_n.htm
index fd7248c..7e0db61 100644
--- a/org.tizen.devtools/html/native_tools/api_privilege_checker_n.htm
+++ b/org.tizen.devtools/html/native_tools/api_privilege_checker_n.htm
@@ -23,8 +23,8 @@
API and Privilege Checker
- The Tizen IDE provides the API and privilege checker tool to identify potential problems in the application code related to API and privilege usage.
- In project properties, you can enable the checker during the building process or code editing stage. You can also perform the checks manually in the Project Explorer view by choosing a project, opening the context menu, and selecting Check API and Privilege Violations With Build.
+ The Tizen IDE provides the API and privilege checker tool to identify potential problems in the application code related to API and privilege usage.
+ In project properties, you can enable the checker during the building process or code editing stage. You can also perform the checks manually in the Project Explorer view by choosing a project, opening the context menu, and selecting Check API and Privilege Violations With Build.
The results of the check are displayed in the Problems view. The following tables define the different alarms that the checks can generate.
diff --git a/org.tizen.devtools/html/native_tools/manifest_text_editor_n.htm b/org.tizen.devtools/html/native_tools/manifest_text_editor_n.htm
index 153ee21..a8b2e6a 100644
--- a/org.tizen.devtools/html/native_tools/manifest_text_editor_n.htm
+++ b/org.tizen.devtools/html/native_tools/manifest_text_editor_n.htm
@@ -43,7 +43,7 @@
Manifest Text Editor
A Tizen native application package consists of exactly 1 manifest file, called tizen-manifest.xml, which is used to describe the application information. The manifest file is composed of XML elements, which include the root <manifest> element and its child elements representing application information, such as <version>, and <privileges>. The child elements are organized into a specific hierarchy. The elements can have attributes associated with them, providing more information about the element.
-The manifest file information can be edited using the manifest editor, or you can modify the XML structure directly using the text editor. To open the manifest editor, double-click the tizen-manifest.xml file in the Project Explorer view of the IDE. To use the text editor, right-click the tizen-manifest.xml file in the Project Explorer view and select Open with > Text Editor.
+The manifest file information can be edited using the manifest editor, or you can modify the XML structure directly using the text editor. To open the manifest editor, double-click the tizen-manifest.xml file in the Project Explorer view of the IDE. To use the text editor, right-click the tizen-manifest.xml file in the Project Explorer view and select Open with > Text Editor.
The following example illustrates the content and structure of a tizen-manifest.xml file:
@@ -1188,7 +1188,7 @@
<privileges> Element
-The <privileges> element represents required privileges for the Tizen application. Applications that use sensitive APIs must declare the required privileges in the tizen-manifest.xml file. Since the privilege categories differ for each API type, make sure you define a correct privilege related to the API you need.
+The <privileges> element represents required privileges for the Tizen application. Applications that use sensitive APIs must declare the required privileges in the tizen-manifest.xml file. Since the privilege categories differ for each API type, make sure you define a correct privilege related to the API you need.
Press Add to open the Add Privilege dialog.
Figure: Editing the <privileges> element in the manifest editor
@@ -1239,7 +1239,7 @@
http://tizen.org/privilege/account.read
-For more information on the expected values, see Security and API Privileges.
+For more information on the expected values, see Security and API Privileges.
@@ -1289,7 +1289,7 @@
"http://tizen.org/feature/camera"
"http://tizen.org/feature/fmradio"
-For more information on the expected values and the application filtering mechanism, see Application Filtering.
+For more information on the expected values and the application filtering mechanism, see Application Filtering.
@@ -1706,4 +1706,4 @@ var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga