SQL Database Engine, Sqlite

SQLite Database Engine

You can use the open source modules, whose functions provide access to SQLite and OpenSSL and demonstrate how to encrypt and store application data. The open source modules supported by Tizen are listed in the API modules.

You can use open-source modules to access SQLite and OpenSSL, and use them to encrypt and store application data. The open source modules supported by Tizen are listed within the API modules.

The main features of the Sqlite API include:

Preparing the Database

This guide only covers the basics of encryption and database usage. For more information, see OpenSSL and SQLite Web pages.

This guide only covers the basics of encryption and database usage. For more information, see the OpenSSL and SQLite Web pages.

Note @@ -189,7 +189,7 @@ PrepareToSQL(unsigned char* msg)

This use case shows how to:

Encrypt a message with OpenSSL, prepare it, and store it in the SQLite database with the Base64 encoding.
Encrypt a message with OpenSSL, prepare it, and store it in the SQLite database with Base64 encoding.
Check that the message has been successfully stored by listing the database content.
Retrieve the database content and decrypt the message.

@@ -375,7 +375,7 @@ callback(void *counter, int argc, char **argv, char **azColName)

Use the DecryptRecords() function to select all encrypted records from the database, and decrypt and list them:

Use the SELECT * FROM EncryptedData query where ENCRYPTED='1' query to retrieve all encrypted records.
The callbackdecrypt() callback is invoked for each found record. If there is an error, the SQLite API requires you to release the error message memory with the sqlite3_free() function.
The callbackdecrypt() callback is invoked for each found record. If there is an error, the Sqlite API requires you to release the error message memory with the sqlite3_free() function.
The callback is similar to the earlier callback used to list the database content.
There is an action added for the argv[ i ] && i == 0 case, which includes the encrypted content in columns that are not empty and are DATA.

To decrypt the message, decode the data from Base 64, add a delimiting character, perform the actual decryption with the DecryptMsg() function, and list the decrypted data.

SDL Graphics with Vulkan®

Vulkan® is a generation API for high-efficiency access to graphics and computing on modern GPUs. It is an open-standard, cross-platform API designed from the ground up by industry experts collaborating under the Khronos consortium. It aims to address the inefficiencies of existing 3D APIs, such as OpenGL®, which are designed for single-core processors and lag to map modern hardware. It provides a much lower-level fine-grained control over the GPU to maximize performance and achieve consistent user experience across different operating environments. For general information on Vulkan®, and the comparative merits of Vulkan® and OpenGL®, see the official Khronos Vulkan® Web site and OpenGL® vs. Vulkan®.

Vulkan® is a generation API for high-efficiency access to graphics and computing on modern GPUs. It is an open-standard, cross-platform API designed from the ground up by industry experts collaborating under the Khronos consortium. It aims to address the inefficiencies of existing 3D APIs, such as OpenGL®, which are designed for single-core processors and lag to map modern hardware. It provides a much lower-level fine-grained control over the GPU to maximize performance and achieve a consistent user experience across different operating environments. For general information on Vulkan®, and the comparative merits of Vulkan® and OpenGL®, see the official Khronos Vulkan® Web site and OpenGL® vs. Vulkan®.

The Tizen platform supports the Vulkan API in order to provide the most cutting-edge 3D programming tools for you to create high-quality games and real-time graphics in applications. Vulkan® is especially recommended for performance- or latency-sensitive applications. With Vulkan®, you can achieve a much smoother user experience by parallelizing the rendering job across multiple threads which can feed the GPU in an efficient manner. Applications demanding explicit control on work submission, synchronization, and less power consumption can seriously consider migrating to Vulkan® as well. Tizen allows the use of the Vulkan API through SDL.

Figure: Vulkan® in Tizen

Note - Window surfaces are an entirely optional component in Vulkan®, if you just need off-screen rendering. Vulkan® allows you to do that without hacks, such as creating an invisible window (necessary for OpenGL®). + Window surfaces are an entirely optional component in Vulkan®, if you only need off-screen rendering. Vulkan® allows you to do that without hacks, such as creating an invisible window (necessary for OpenGL®).

The main features of the i18n API include:

Managing text and strings -
You can handle general unicode strings with Ustring and find the location of boundaries in text with Ubrk.
+
You can handle general Unicode strings with Ustring and find the location of boundaries in text with Ubrk.

For search and access, you can perform locale-sensitive string comparison with Ucollator to build searching and sorting routines, search language-sensitive text based on the Ucollator comparison rules with Usearch, and get low-level access to the Unicode Character Database with Uchar.
-
You can manage multiple strings by creating and obtaining enumerations out of a given set of strings with Uenumeration, or managing a set of unicode characters and multicharacter strings with Uset.
-
With Unormalization, you can perform standard unicode normalization.
+
You can manage multiple strings by creating and obtaining enumerations out of a given set of strings with Uenumeration, or managing a set of Unicode characters and multicharacter strings with Uset.
+
With Unormalization, you can perform standard Unicode normalization.
Managing the calendar and dates
With Udatepg, you can generate date format patterns, such as "yy-MM-dd". You can also handle various conversions: you can convert between a Udate object and a set of integer fields with Ucalendar, and you can convert dates and times from their internal representations to textual form and back with Udate.
@@ -80,7 +80,7 @@
You can format and parse numbers for any locale with Unumber.
Managing locales and time zones -
You can use the Ulocale functions to tailor information according to a specific geographical, cultural, or political region. With the Timezone functions, you can get the time zone name, ID, DST savings, raw offset, and region code.
+
You can use the Ulocale functions to tailor information according to a specific geographical, cultural, or political region. With the Timezone functions, you can get the time zone name, ID, DST settings, raw offset, and region code.

Calendar Dates with Ucalendar

The Ucalendar API (in mobile and wearable applications) is used for converting between a Udate object and a set of integer fields, such as I18N_UCALENDAR_YEAR, I18N_UCALENDAR_MONTH, I18N_UCALENDAR_DAY, and I18N_UCALENDAR_HOUR. A Udate object represents a specific instant in time with one millisecond precision.

The types of Ucalendar interpret a Udate according to the rules of a specific calendar system, such as the gregorian or traditional system.

The types of Ucalendar interpret a Udate according to the rules of a specific calendar system, such as the Gregorian or traditional system.

A Ucalendar object can produce all the time field values needed to implement the date-time formatting for a particular language and calendar style (for example, Japanese-Gregorian, Japanese-Traditional).

When computing a Udate from the time fields, 2 special circumstances can arise. The information can be insufficient to compute the Udate (you have only the year and the month, but not the day of the month), or the information can be inconsistent (such as "Tuesday, July 15, 1996" even though July 15, 1996 is actually a Monday).

Unicode Normalization with Unormalization

The Unicode normalization API (in mobile and wearable applications) is for the standard unicode normalization. All instances of i18n_unormalizer_s are unmodifiable and immutable. Instances returned by i18n_unormalization_get_instance() are singletons that must not be deleted by the caller.

The Unicode normalization API (in mobile and wearable applications) is for the standard Unicode normalization. All instances of i18n_unormalizer_s are unmodifiable and immutable. Instances returned by i18n_unormalization_get_instance() are singletons that must not be deleted by the caller.

Number Formats with Unumber

Unicode Strings with Ustring

The Ustring API (in mobile and wearable applications) allows you to handle general unicode strings. Some functions are similar in name, signature, and behavior to the ANSI C <string.h> functions, and other functions provide more Unicode-specific functionality.

The Ustring API (in mobile and wearable applications) allows you to handle general Unicode strings. Some functions are similar in name, signature, and behavior to the ANSI C <string.h> functions, and other functions provide more Unicode-specific functionality.

The i18n uses 16-bit Unicode (UTF-16) in the form of arrays of i18n_uchar code units. UTF-16 encodes each Unicode code point with either 1 or 2 i18n_uchar code units. This is the default form of Unicode, and a forward-compatible extension of the original, fixed-width form that was known as UCS-2. UTF-16 superseded UCS-2 with Unicode 2.0 in 1996.

The i18n also handles 16-bit Unicode text with unpaired surrogates. Such text is not well-formed UTF-16. Code-point-related functions treat unpaired surrogates as surrogate code points, such as separate units.

Although UTF-16 is a variable-width encoding form, such as some legacy multi-byte encodings, it is much more efficient even for random access because the code unit values for single-unit characters versus lead units versus trail units are completely disjoint. This means that it is easy to determine character (code point) boundaries from random offsets in the string.

Linear Acceleration Sensor

The linear acceleration sensor is derived from the accelerometer by excluding the gravity value, and it measures the user-driven changes in the velocity. The linear acceleration sensor is used to detect the dynamic movement of the device and analyze the user's motion profile. The 3-axes linear acceleration components provide a measure of the combined linear motion subjected to the device in the euclidean space.

The linear acceleration sensor is derived from the accelerometer by excluding the gravity value, and it measures the user-driven changes in the velocity. The linear acceleration sensor is used to detect the dynamic movement of the device and analyze the user's motion profile. The 3-axis linear acceleration components provide a measure of the combined linear motion subjected to the device in Euclidean space.

The linear acceleration sensor provides 3 components of acceleration (X, Y, and Z), as the following figure illustrates.

Figure: User-acceleration sensor vector and axes

User-acceleration sensor vector and axes

float

Max. value = 1260

Ultraviolet Sensor

The ultraviolet (UV) sensor measures the ultraviolet index. The sensor detects and provides a measure of the UV rays being exposed to the device.

The ultraviolet (UV) sensor measures the ultraviolet index. The sensor detects and provides a measure of the UV rays the device is exposed to.

The following table lists the measurement data that the ultraviolet sensor provides.

Table: Measurement data detected by the ultraviolet sensor

Microseconds
values[0]: uv index	values[0]: UV index	`float`	Min. value = 0 Max. value = 15	uv index	UV index

float

If the location manager is working correctly, the location state is set to LOCATIONS_SERVICE_ENABLED. The device can receive notifications about location updates and accuracy changes only in this update state.
If the location manager is unable to run on the requested device due to weak radio reception, the location update state is set to LOCATIONS_SERVICE_DISABLED (LOCATIONS_ERROR_SERVICE_NOT_AVAILABLE). If this situation persists for a longer period, it is recommended to stop the service and try again to conserve the device battery.
If the user revokes a permission for the application to use location information, the location update state is set to LOCATIONS_ACCESS_STATE_DENIED, and the location manager stops all on-going services with the application. The application can request the device user for a permission to continue the stopped service.
If the user revokes permission for the application to use location information, the location update state is set to LOCATIONS_ACCESS_STATE_DENIED, and the location manager stops all on-going services with the application. The application can request the device user for permission to continue the stopped service.

Location Methods

The location method is used to specify the desired quality of service of the location manager. For example, a location-based weather forecast application can require location-related information just to distinguish a city or a neighborhood, while a GPS navigation application can require the highest quality level to pinpoint a map location. Selecting the appropriate quality level not only helps the location manager to run the system efficiently, but also leads to a good user experience.

The location method is used to specify the desired quality of service of the location manager. For example, a location-based weather forecast application can require location-related information only to distinguish a city or a neighborhood, while a GPS navigation application can require the highest quality level to pinpoint a map location. Selecting the appropriate quality level not only helps the location manager to run the system efficiently, but also leads to a good user experience.

Using the location_method_e structure (in mobile and wearable applications) allows your application to specify the following methods of location positioning system:

GPS, which uses the global positioning system

Notification area
The notification area is the reserved space for displaying all notifications, except the on-going notifications.
On-going area -
The on-going area is the application screen area and is only used to display notifications for the currently running application.

The on-going area is the application screen area and is only used to display notifications for the currently-running application.

Figure: Notification and on-going areas

Notification and on-going areas

Calendar books
- Determine where the events and todos belong.
- Create calendar books using the local device (with no account), service providers, such as Google or Yahoo (with an account), or applications, such as ChatON, Joyn, or Facebook.
- Create calendar books using the local device (with no account), service providers, such as Google or Yahoo (with an account), or applications, such as Joyn or Facebook.
- Search and organize events using filters and queries.
- Monitor database changes.
@@ -571,7 +571,7 @@ calendar_db_get_all_records(_calendar_calendar_book._uri, 0, 0, &calendar_bo
Figure: Alarm process

-
To get a reminder when an alarm is triggered, the application must set the reminder mime name. After the reminder mime name is set, insert an alarm as a child of an event record:
+
To get a reminder when an alarm is triggered, the application must set the reminder MIME name. After the reminder MIME name is set, insert an alarm as a child of an event record:
```
 /* Set alarm */
 calendar_record_h alarm = NULL;
@@ -586,7 +586,7 @@ calendar_record_set_caltime(alarm, _calendar_alarm.alarm_time, at);
 calendar_record_add_child_record(event, _calendar_event.calendar_alarm, alarm);
 
```
-
When the registered alarm is triggered and the alarm manager notices it, the calendar service calls those packages that have the reminder mime name.
+
When the registered alarm is triggered and the alarm manager notices it, the calendar service calls those packages that have the reminder MIME name.

Filters and Queries
diff --git a/org.tizen.guides/html/native/personal/contacts_n.htm b/org.tizen.guides/html/native/personal/contacts_n.htm index b6ebffc..a6ed1dc 100644 --- a/org.tizen.guides/html/native/personal/contacts_n.htm +++ b/org.tizen.guides/html/native/personal/contacts_n.htm @@ -118,7 +118,7 @@
- Each contact has their own details, such as a name, phone number, and email address.
- Each contact object is associated with a specific address book. -
  The address book can be the local device address book, or an address book related to a specific service provider or application account (such as Samsung or ChatOn).
- Multiple contacts can be associated with the same physical person.
  A person object is an aggregation of one or multiple contact objects.
@@ -153,7 +153,7 @@
You can manage group members and set up many-to-many relationships between groups and contacts.

Address books

You can create address books using the local device (with no account), service providers (such as Samsung account), or applications (such as ChatON or Joyn).
You can create address books using the local device (with no account), service providers (such as Samsung account), or applications (such as Joyn).
You can determine to which address book each contact and group belong.
If the address book is related to an account, you can handle the account using an account ID created with the Account Manager. If the local device address book has no account, the related account ID is 0. You can create only one address book for each account.

diff --git a/org.tizen.guides/html/native/text_input/stt_n.htm b/org.tizen.guides/html/native/text_input/stt_n.htm index 74135f7..9dbe4e0 100644 --- a/org.tizen.guides/html/native/text_input/stt_n.htm +++ b/org.tizen.guides/html/native/text_input/stt_n.htm @@ -131,7 +131,7 @@

Note - STT is not thread-safe and depends on the ecore main loop. Implement STT within the ecore main loop and do not use it in a thread. + STT is not thread-safe and depends on the Ecore main loop. Implement STT within the Ecore main loop and do not use it in a thread.

diff --git a/org.tizen.guides/html/native/text_input/tts_n.htm b/org.tizen.guides/html/native/text_input/tts_n.htm
index 4bc35b0..1c8f446 100644
--- a/org.tizen.guides/html/native/text_input/tts_n.htm
+++ b/org.tizen.guides/html/native/text_input/tts_n.htm
@@ -140,7 +140,7 @@
 
 	   
         Note
-        TTS is not thread-safe and depends on the ecore main loop. Implement TTS within the ecore main loop and do not use it in a thread.
+        TTS is not thread-safe and depends on the Ecore main loop. Implement TTS within the Ecore main loop and do not use it in a thread.
     
 
 diff --git a/org.tizen.guides/html/native/text_input/voice_control_n.htm b/org.tizen.guides/html/native/text_input/voice_control_n.htm
index 7b5e871..dd7e2e3 100644
--- a/org.tizen.guides/html/native/text_input/voice_control_n.htm
+++ b/org.tizen.guides/html/native/text_input/voice_control_n.htm
@@ -291,7 +291,7 @@ initialize_voice_control()
 
    
         Note
-		The voice control feature is not thread-safe and depends on the ecore main loop. Implement voice control within the ecore main loop and do not use it in a thread.
+		The voice control feature is not thread-safe and depends on the Ecore main loop. Implement voice control within the Ecore main loop and do not use it in a thread.
     
 
 
diff --git a/org.tizen.guides/html/native/ui/efl/component_entry_mn.htm b/org.tizen.guides/html/native/ui/efl/component_entry_mn.htm
index 555144e..5b3c568 100644
--- a/org.tizen.guides/html/native/ui/efl/component_entry_mn.htm
+++ b/org.tizen.guides/html/native/ui/efl/component_entry_mn.htm
@@ -295,7 +295,7 @@ elm_entry_line_wrap_set(entry, ELM_WRAP_WORD);
   
    ELM_WRAP_NONE: No wrap
    ELM_WRAP_CHAR: Wrap between characters
-   ELM_WRAP_WORD: Wrap in allowed wrapping points (as defined in the unicode standard)
+   ELM_WRAP_WORD: Wrap in allowed wrapping points (as defined in the Unicode standard)
    ELM_WRAP_MIXED: Word wrap, and if that fails, character wrap
   
 
diff --git a/org.tizen.guides/html/native/ui/efl/component_entry_wn.htm b/org.tizen.guides/html/native/ui/efl/component_entry_wn.htm
index 93143d8..52d666c 100644
--- a/org.tizen.guides/html/native/ui/efl/component_entry_wn.htm
+++ b/org.tizen.guides/html/native/ui/efl/component_entry_wn.htm
@@ -295,7 +295,7 @@ elm_entry_line_wrap_set(entry, ELM_WRAP_WORD);
   
    ELM_WRAP_NONE: No wrap
    ELM_WRAP_CHAR: Wrap between characters
-   ELM_WRAP_WORD: Wrap in allowed wrapping points (as defined in the unicode standard)
+   ELM_WRAP_WORD: Wrap in allowed wrapping points (as defined in the Unicode standard)
    ELM_WRAP_MIXED: Word wrap, and if that fails, character wrap
   
 
diff --git a/org.tizen.guides/html/native/ui/efl/component_genlist_wn.htm b/org.tizen.guides/html/native/ui/efl/component_genlist_wn.htm
index e6eff73..21ab6a2 100644
--- a/org.tizen.guides/html/native/ui/efl/component_genlist_wn.htm
+++ b/org.tizen.guides/html/native/ui/efl/component_genlist_wn.htm
@@ -213,7 +213,7 @@ itc->func.del = _item_del;
    The event_info callback parameter points at an Elm_Object_Item object that contains the item to be expanded.
    contract,request: The user wants to collapse a tree branch item. The callback decides whether the item can collapse (if it has any children) and calls the elm_genlist_item_expanded_set() function to set the state.
    The event_info callback parameter points at an Elm_Object_Item object that contains the item to be collapsed.
-   realized: The item is created as a real evas object.
+   
realized: The item is created as a real Evas object.
    The event_info callback parameter points at an Elm_Object_Item object that contains the item to be created.
    unrealized: The item is going to be unrealized. Provided content objects are deleted and the item object is deleted or put into a floating cache.
    The event_info callback parameter points at an Elm_Object_Item object that contains the item to be deleted.
diff --git a/org.tizen.guides/html/native/ui/efl/component_icon_mn.htm b/org.tizen.guides/html/native/ui/efl/component_icon_mn.htm
index 3ad5af4..67241e7 100644
--- a/org.tizen.guides/html/native/ui/efl/component_icon_mn.htm
+++ b/org.tizen.guides/html/native/ui/efl/component_icon_mn.htm
@@ -50,7 +50,7 @@
  In the following cases, use an icon instead of an image:
  
    You need a thumbnail version of an original image.
-   You need freedesktop.org-provided icon images.
+   You need freedesktop.org-provided icon images.
    You need theme-provided icon images (Edje groups).
  
 
@@ -68,7 +68,7 @@ icon = elm_icon_add(parent);
 
 
 Set an image to the icon.
-To set a standard icon from freedesktop.org, use the elm_icon_standard_set() function:
+To set a standard icon from freedesktop.org, use the elm_icon_standard_set() function:
  Evas_Object *icon;
 Evas_Object *parent;
diff --git a/org.tizen.guides/html/native/ui/efl/component_icon_wn.htm b/org.tizen.guides/html/native/ui/efl/component_icon_wn.htm
index 16357d8..3f0f52c 100644
--- a/org.tizen.guides/html/native/ui/efl/component_icon_wn.htm
+++ b/org.tizen.guides/html/native/ui/efl/component_icon_wn.htm
@@ -57,7 +57,7 @@
 Adding an Icon Component
 
 To create an icon component, use the elm_icon_add() function.
-To set the icon as a freedesktop.org Home standard icon, use the elm_icon_standard_set() function.
+To set the icon as the freedesktop.org standard Home icon, use the elm_icon_standard_set() function.
 
  Evas_Object *icon;
diff --git a/org.tizen.guides/html/native/ui/efl/data_types_n.htm b/org.tizen.guides/html/native/ui/efl/data_types_n.htm
index 61d68c4..602b41a 100644
--- a/org.tizen.guides/html/native/ui/efl/data_types_n.htm
+++ b/org.tizen.guides/html/native/ui/efl/data_types_n.htm
@@ -418,7 +418,7 @@ iterating_array()
 
 
 Use the eina_array_iterator_new() function to create an iterator for the array. The function returns a newly allocated iterator associated with the array. If the array is NULL or the count of the array members is less than or equal to 0, the function returns NULL. If the memory cannot be allocated, NULL is returned and EINA_ERROR_OUT_OF_MEMORY is thrown. Otherwise, a valid iterator is returned.
-Pass to this function the array for which you want to create a new iterator. The iterator is used to run a sequential walk through the array, just like the eina_array_foreach() function.
+Pass to this function the array for which you want to create a new iterator. The iterator is used to run a sequential walk through the array, exactly like the eina_array_foreach() function.
 To create an iterator and use it to print the data of each array element:
  static Eina_Bool
@@ -1214,7 +1214,7 @@ list = eina_list_remove_list(list, to_remove);
 
 
 
-To move elements in a list, you can use various function, such as eina_list_promote_list() that promotes an element to the top of the list or eina_list_demote_list() that puts the specified element at the end of the list. Remember that everything is a list so the second parameter represents the "list" (node) you want to move. Use the functions just like the eina_list_remove_list() function.
+
To move elements in a list, you can use various functions, such as eina_list_promote_list() that promotes an element to the top of the list or eina_list_demote_list() that puts the specified element at the end of the list. Remember that everything is a list so the second parameter represents the "list" (node) you want to move. Use the functions exactly like the eina_list_remove_list() function.
  list = eina_list_promote_list(list, eina_list_data_find_list(list, "ivi"));
 
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 23c2cbc..0b90565 100644
--- a/org.tizen.guides/html/native/ui/efl/introduction_n.htm
+++ b/org.tizen.guides/html/native/ui/efl/introduction_n.htm
@@ -139,7 +139,7 @@
 
 For those familiar with traditional game programming, this is familiar, except that you have also implemented the main loop with an infinite while or for loop that fetches input events, updates the game world, renders the updated scene, and then loops and repeats as quickly as it can.
 
-In EFL, the main loop is not "dumb" and does not consume CPU resources unless there is work to do. It sleeps and consumes no CPU time until an event happens (except in rare circumstances, for example, when you use Idlers that are called in a loop during what normally would be idle time waiting for something to happen). From EFL's point of view, all of this is handled in Ecore, and it supports many constructs for manipulating the main loop in a logical and flexible way. EFL handles animation through animators, where the main loop handles timing out and scheduling these at regularly spaced intervals in time (on a best-effort basis), as with timers, pollers, idle enterers, idle exiters, idlers, jobs, fd handlers (file descriptor handlers) and event handlers.
+In EFL, the main loop is not "dumb" and does not consume CPU resources unless there is work to do. It sleeps and consumes no CPU time until an event happens (except in rare circumstances, for example, when you use idlers that are called in a loop during what normally would be idle time waiting for something to happen). From EFL's point of view, all of this is handled in Ecore, and it supports many constructs for manipulating the main loop in a logical and flexible way. EFL handles animation through animators, where the main loop handles timing out and scheduling these at regularly spaced intervals in time (on a best-effort basis), as with timers, pollers, idle enterers, idle exiters, idlers, jobs, fd handlers (file descriptor handlers) and event handlers.
 
 In the EFL view, the application, when executing any callbacks other than idlers, is "active". It goes in and out of this active state by calling the idle enterer and exiter callbacks (edge-triggered callbacks), which are triggered whenever going in and out of the idle state. Idlers themselves do not transition the main loop as such from being in an idle state, so any idler that needs to "wake up" the loop (to make the application conceptually active) needs to queue something that ordinarily wakes up the main loop, such as a job or timer. This is the only exception due to the conceptual model and the need for efficiency (not entering and exiting idle per idler call).
 
diff --git a/org.tizen.guides/html/native/ui/efl/learn_edc_part_n.htm b/org.tizen.guides/html/native/ui/efl/learn_edc_part_n.htm
index d7a35bf..35d5b80 100644
--- a/org.tizen.guides/html/native/ui/efl/learn_edc_part_n.htm
+++ b/org.tizen.guides/html/native/ui/efl/learn_edc_part_n.htm
@@ -63,7 +63,7 @@ part {
    /* Repeat the mouse events to the parts below the current one */
    repeat_events: 0/1;
    ignore_flags: NONE;
-   /* Set whether the part sizes scale with the edje scaling factor */
+   /* Set whether the part sizes scale with the Edje scaling factor */
    scale: 0/1;
    /* Set whether fully-transparent pixels are considered in collision detection */
    precise_is_inside: 0/1;
@@ -581,7 +581,7 @@ part {
 Sets the cursor mode for a textblock part. The available modes are:
 
 UNDER: Cursor draws below the character pointed at. This is the default setting.
-BEFORE: Cursor is drawn as a vertical line before the current character, just like many other GUI toolkits handle it
+BEFORE: Cursor is drawn as a vertical line before the current character, in the same way as many other GUI toolkits handle it.
 
 
 
diff --git a/org.tizen.guides/html/native/ui/efl/main_loop_n.htm b/org.tizen.guides/html/native/ui/efl/main_loop_n.htm
index 0994303..27d492a 100644
--- a/org.tizen.guides/html/native/ui/efl/main_loop_n.htm
+++ b/org.tizen.guides/html/native/ui/efl/main_loop_n.htm
@@ -115,7 +115,7 @@ ecore_timer_add(2.0, my_timed_cb, my_data);
 
 To delay the timer's next occurrence, use the ecore_timer_delay() function. The function adds the specified time to the current interval. It does not change the future occurrences' interval. You can also reset the current interval to its full value by using the ecore_timer_reset() function.
 
-To pause the currently running timer, use the ecore_timer_freeze() function. The remaining time is saved and used again when the timer is resumed with the ecore_timer_thaw() function.
+To pause the currently-running timer, use the ecore_timer_freeze() function. The remaining time is saved and used again when the timer is resumed with the ecore_timer_thaw() function.
 
 To query the current value of the defined timer infrastructure precision, use the ecore_timer_precision_get() function. A higher delay means that more timers can be run together. It diminishes the need to use system wake-ups and thus lowers the power consumption.
 To set the precision, use the ecore_timer_precision_set() function. This sets the precision for all timers. For example, there are 2 timers, one that expires in 2.0 seconds and another that expires in 2.1 seconds. If the precision is set to 0.1 seconds, Ecore requests the next expiration to happen in 2.1 seconds and runs both callbacks at once, instead of one at 2.0 seconds and the other one 0.1 seconds later. However, if there is no timer expiring in 2.1 seconds, the timeout is at the minimum interval, 2 seconds.
@@ -199,7 +199,7 @@ ecore_animator_timeline_add(5., my_anim_cb, my_data);
 
 To manage the animator:
 
-To pause the currently running animator, use the ecore_animator_freeze() function. Note that time continues ticking even if the animator is frozen, and that resuming the animation using the ecore_animator_thaw() function does not actually resume, if the full runtime has been passed in the meanwhile.
+To pause the currently-running animator, use the ecore_animator_freeze() function. Note that time continues ticking even if the animator is frozen, and that resuming the animation using the ecore_animator_thaw() function does not actually resume, if the full runtime has been passed in the meanwhile.
 
 To query Ecore for the interval between 2 animator calls, use the ecore_animator_frametime_get() function.
 
diff --git a/org.tizen.guides/html/web/app_management/app_group_w.htm b/org.tizen.guides/html/web/app_management/app_group_w.htm
index d8be0f2..5b64908 100644
--- a/org.tizen.guides/html/web/app_management/app_group_w.htm
+++ b/org.tizen.guides/html/web/app_management/app_group_w.htm
@@ -85,7 +85,7 @@
 		  The GROUP launch mode means that the application can be launched as a sub application
       belonging to the same group as the caller application which is causing the application to be launched.
     
-	Additionally, if the launch mode is not set to SINGLE in the config.xml file and the application is launched by the launchAppControl() method of the ApplicationManager interface (in mobile, wearable, and TV applications) with the ApplicationControl object (in mobile, wearable, and TV applications), the launchMode property of this object overrides the launch mode of the called application. If the launch mode in the config.xml file is set to SINGLE, the value of the ApplicationControl.launchMode property is ignored and the sub application is always called in the SINGLE mode.
+	Additionally, if the launch mode is not set to SINGLE in the config.xml file and the application is launched by the launchAppControl() method of the ApplicationManager interface (in mobile, wearable, and TV applications) with the ApplicationControl object (in mobile, wearable, and TV applications), the launchMode property of this object overrides the launch mode of the called application. If the launch mode in the config.xml file is set to SINGLE, the value of the ApplicationControl.launchMode property is ignored and the sub application is always called in the SINGLE mode.
 To launch an application in a GROUP mode:
 
 
diff --git a/org.tizen.guides/html/web/app_management/service_app_w.htm b/org.tizen.guides/html/web/app_management/service_app_w.htm
index fd20b28..add2aea 100644
--- a/org.tizen.guides/html/web/app_management/service_app_w.htm
+++ b/org.tizen.guides/html/web/app_management/service_app_w.htm
@@ -270,7 +270,7 @@ var watchId = localMsgPort.addMessagePortListener(onreceived);
 
 
  Application
- This API provides information about the currently running and installed applications and ways to launch other applications.
+ This API provides information about the currently-running and installed applications and ways to launch other applications.
 Note that the getRequestedAppControl() method is only valid inside the onRequest() callback.
 
 
diff --git a/org.tizen.guides/html/web/connectivity/bluetooth_w.htm b/org.tizen.guides/html/web/connectivity/bluetooth_w.htm
index 06e1086..0b551fc 100644
--- a/org.tizen.guides/html/web/connectivity/bluetooth_w.htm
+++ b/org.tizen.guides/html/web/connectivity/bluetooth_w.htm
@@ -159,7 +159,7 @@ if (adapter.powered) {
 }

To display the Bluetooth visibility switch, use the application/x-bluetooth-visibility mime option. Bluetooth visibility means that the device is discoverable by other Bluetooth devices.

To display the Bluetooth visibility switch, use the application/x-bluetooth-visibility MIME option. Bluetooth visibility means that the device is discoverable by other Bluetooth devices.

 var bluetoothVisibilityAppControl = new tizen.ApplicationControl('http://tizen.org/appcontrol/operation/edit', null, 'application/x-bluetooth-visibility');
 
diff --git a/org.tizen.guides/html/web/connectivity/nfc_w.htm b/org.tizen.guides/html/web/connectivity/nfc_w.htm
index 9678cfb..a7ee575 100644
--- a/org.tizen.guides/html/web/connectivity/nfc_w.htm
+++ b/org.tizen.guides/html/web/connectivity/nfc_w.htm
@@ -350,7 +350,7 @@ adapter.cardEmulationMode = 'OFF';
 To tell the platform which AID groups are requested by the application, a metadata element must be included in the config.xml file:
  <?xml version="1.0" encoding="utf-8"?>
-<widget xmlns:tizen="http://tizen.org/ns/wdigets" xmlns="http://www.w3.org/ns/widgets"
+<widget xmlns:tizen="http://tizen.org/ns/widgets" xmlns="http://www.w3.org/ns/widgets"
         id="http://yourdomain/NFCtest" version="1.0.0" viewmodes="maximized">
    <profile name="wearable"/>
    <tizen:application id="ZmAk4fxZWY.NFCtest" package="ZmAk4fxZWY" required_version="2.3.1"/>
diff --git a/org.tizen.guides/html/web/data/file_archiving_w.htm b/org.tizen.guides/html/web/data/file_archiving_w.htm
index 3d69389..abf3b89 100644
--- a/org.tizen.guides/html/web/data/file_archiving_w.htm
+++ b/org.tizen.guides/html/web/data/file_archiving_w.htm
@@ -47,7 +47,7 @@
 
 File Archiving
 
-  Tizen enables you to operate on the zip archive files.
+  Tizen enables you to operate on ZIP archive files.
 
 The Archive API is mandatory for both Tizen mobile and wearable profiles, which means that it is supported in all mobile and wearable devices. All mandatory APIs are supported on the Tizen Emulators.
 
@@ -63,7 +63,7 @@
 	You can abort an on-going archive operation.

To start any kind of zip operation (packing or unpacking), you must first call the open() method of the ArchiveManager interface (in mobile, wearable, and TV applications). The first parameter is a FileReference object (in mobile, wearable, and TV applications), which can be a File object (in mobile, wearable, and TV applications) or the virtual path. The second parameter is a FileMode enumerator (in mobile, wearable, and TV applications), whose values are described in the following table.

To start any kind of ZIP operation (packing or unpacking), you must first call the open() method of the ArchiveManager interface (in mobile, wearable, and TV applications). The first parameter is a FileReference object (in mobile, wearable, and TV applications), which can be a File object (in mobile, wearable, and TV applications) or the virtual path. The second parameter is a FileMode enumerator (in mobile, wearable, and TV applications), whose values are described in the following table.

Table: File modes

diff --git a/org.tizen.guides/html/web/data/file_system_w.htm b/org.tizen.guides/html/web/data/file_system_w.htm index 1212549..9da0bef 100644 --- a/org.tizen.guides/html/web/data/file_system_w.htm +++ b/org.tizen.guides/html/web/data/file_system_w.htm @@ -226,7 +226,7 @@ function onsuccess(files) {

Managing Files and Directories

YTou can manage files and directories in many ways:

You can manage files and directories in many ways:

You can read and write to a file by first using the openStream() method to open the file. You can specify the file mode and encoding.
The openStream() method returns a FileStream object (in mobile, wearable, and TV applications), which is a handle to the opened file. All actual operations, such as read, write, or close, on the file are performed through the FileStream object based on a position attribute, which represents the current position in the file.
diff --git a/org.tizen.guides/html/web/text_input/input_method_w.htm b/org.tizen.guides/html/web/text_input/input_method_w.htm index fe780f5..33931c7 100644 --- a/org.tizen.guides/html/web/text_input/input_method_w.htm +++ b/org.tizen.guides/html/web/text_input/input_method_w.htm @@ -52,11 +52,11 @@
Architecture

IME applications differ from other applications in that they do not follow the normal application life-cycle management and they need a mechanism to interact with the client application requesting the IME.
-
Tizen provides a special architecture to guarantee that Web IME applications work just like native IME applications (however, there are some restrictions due to the capability limitations of the Web applications in general). A Web IME application can be run within the core Input Service Engine process, which is also used to run native IME applications.
+
Tizen provides a special architecture to guarantee that Web IME applications work exactly like native IME applications, but with some restrictions due to capability limitations of Web applications in general. A Web IME application can be run within the core Input Service Engine process, which is also used to run native IME applications.

The following figure shows the overall architecture of the Tizen Web IME support.

Figure: Tizen Web IME support architecture

-
When a Web IME is executed, the Input Service framework launches the Input Service Engine process, just like with native IME applications. The Input Service Engine process loads a special bridge IME module, ise-web-helper-agent, which executes a Web IME within its Web container and communicates with the executed Web IME.
+
When a Web IME is executed, the Input Service framework launches the Input Service Engine process, as with native IME applications. The Input Service Engine process loads a special bridge IME module, ise-web-helper-agent, which executes a Web IME within its Web container and communicates with the executed Web IME.

The communication between the Web IME and the ise-web-helper-agent module is accomplished by 2 utility modules, web-helper-agent on the Web helper agent side and web-helper-client on the Web IME side. Therefore, a Web IME application must contain the web-helper-client.js, which is created automatically when you create a Web IME project using the Tizen Studio.

Since the Web IME runs within a Web container and communicates with it, as a Web IME application developer you do not need knowledge of the platform architecture or details of the native API. You can develop Web IME applications as if they were normal Web applications, as long as the web-helper-client.js file is included and properly used.
@@ -423,7 +423,7 @@ Keycode: {
Hardware Key Events
-
The Web IME is capable of not only showing a soft keyboard and emitting key events to client application, but also handling hardware key events and translating them to a specific language. This is very common when typing texts in CJK (Chinese, Japanese, and Korean) languages, where each key event must be composed to produce a final result string.
+
The Web IME is capable of not only showing a soft keyboard and emitting key events to client application, but also handling hardware key events and translating them to a specific language. This is very common when entering texts in CJK (Chinese, Japanese, and Korean) languages, where each key event must be composed to produce a final result string.

When a hardware key is pressed, the client application receives the key event and requests the Input Service framework to translate the key event. The request is then delivered to the currently selected Web IME through the event handler.

When creating the handler object for WebHelperClient, implement the onProcessKeyEvent() method if you want to translate each hardware key event.
diff --git a/org.tizen.guides/index.xml b/org.tizen.guides/index.xml index 164bca0..1e21da2 100644 --- a/org.tizen.guides/index.xml +++ b/org.tizen.guides/index.xml @@ -343,7 +343,7 @@ - +
diff --git a/org.tizen.studio/html/common_tools/da_advanced.htm b/org.tizen.studio/html/common_tools/da_advanced.htm index 1b45752..577da17 100644 --- a/org.tizen.studio/html/common_tools/da_advanced.htm +++ b/org.tizen.studio/html/common_tools/da_advanced.htm @@ -94,11 +94,11 @@
Data Load and Save Dialogs

You can save the tracing result into a file and load it later for analysis:
- You can save the analysis result to a zip file. +
- You can save the analysis result to a ZIP file.
  Figure: Saving data
- You can load the analysis result from the zip file. After loading, the chart and table data are updated from the loaded data. +
- You can load the analysis result from the ZIP file. After loading, the chart and table data are updated from the loaded data.
  Figure: Loading data

- + diff --git a/org.tizen.studio/html/common_tools/emulator_control_panel.htm b/org.tizen.studio/html/common_tools/emulator_control_panel.htm index 7796130..6b2edfb 100644 --- a/org.tizen.studio/html/common_tools/emulator_control_panel.htm +++ b/org.tizen.studio/html/common_tools/emulator_control_panel.htm @@ -39,7 +39,7 @@

Using Emulator Control Keys, Menu, and Panel

Before deploying your application, it is important that you test it in an environment similar to a real device.

You can run the application in the emulator, and test a variety of user scenarios, such as network access, audio input and out, and text messages. With a mouse and keyboard, you can control the application in the emulator just like on an actual device.

You can run the application in the emulator, and test a variety of user scenarios, such as network access, audio input and output, and text messages. With a mouse and keyboard, you can control the application in the emulator exactly like on an actual device.

While the application is running, you can use the Emulator Control Panel to simulate events for a variety of system options that the actual device provides. For example, by manipulating the virtual battery, you can simulate the application in different charge environments.

The emulator controls consist of internal and external parts:

In the Light card, you can simulate ambient light conditions using the Lux slider. The range of this value is from 0 Lux to 65635 Lux.
If automatic screen brightness is activated in the device settings, the display changes based on the simulated light value.
In the Proximity card, you can set the proximity sensor state to Far or Near.
In the Pressure card, you can control the pressure sensor using the hPa slider. The range of this value is from 260 hPa to 1260 hPa (Hectopascals).
In the Pressure card, you can control the pressure sensor using the hPa slider. The range of this value is from 260 hPa to 1260 hPa (hectopascals).
In the Ultraviolet card, you can control the ultraviolet sensor using the Index slider. The unit is UV index and the range of this value is from 0 to 15.0.
In the Heart Rate card, you can control the HRM (Heart Rate Monitor) sensor. You can use the bpm slider to set the heart rate value between 0 and 220 bpm, and the ms slider to set the peak-to-peak time between 0 and 5000 ms (milliseconds).
In the Pedometer card, you can simulate user movement with the device by selecting a movement pace:
- Multibuttonentry allows the user to enter text so that the text is divided into chunks and managed as a set of buttons.
- Gengrid displays objects on a grid layout and renders only the visible objects.
- Index gives you quick access to a group of other UI items.
- Flipselector is a set of text items and a selector that flips up or down to change the currently shown text item.
- Flipselector is a set of text items and a selector that flips up or down to change the currently-shown text item.
- Background can be used to set a solid background decoration to a window or a container object. It works like an image, but has some background-specific properties, such as setting it to a tiled, centered, scaled, or stretched mode.
- Datetime can display and input date and time values.
- Image can load and display an image from a file or memory.
- Label displays text with simple HTML-like markup.
- Progressbar can be used to display the progress status of a given task.
- Layout is a container component that takes a standard Edje design file and wraps it very thinly in a UI component.
- Map displays a map, using the OpenStreetMap provider.
- Map displays a map, using the OpenStreetMap provider.
- Calendar displays month views.
- Colorselector provides a color selector. It has different modes, each of them showing a different color selection configuration.
- Entry is a box in which the user can enter text.