Application

Application features include managing various types of applications and packages, and handling events.

Application features include managing various types of applications and packages, badges, notifications, input devices and handling events, communicate with other web or native applications.

The main application features are:

Alarm
Allows you to schedule an application to be run at a specific time
Application
Allows you to monitor and retrieve information about the applications installed or running on the device, manage control mechanisms that launch other applications, and broadcast and listen for events.
Application Group
Allows you to define the application launch mode and group your applications into entities that can be managed together.
Badge
Allows you to create and update badges on the home screen.
Input Device
Allows you to manage input keys in the application.
Message Port
Allows you to send and receive messages through message ports.
Notification
Allows you to create and display different types of notifications.
Package
Allows you to retrieve information about packages and manage package installation.

The following guides apply in mobile applications only:

diff --git a/org.tizen.guides/html/web/tizen/ui/badge_w.htm b/org.tizen.guides/html/web/tizen/application/badge_w.htm similarity index 92% rename from org.tizen.guides/html/web/tizen/ui/badge_w.htm rename to org.tizen.guides/html/web/tizen/application/badge_w.htm index 7ca8f3a..b45ab61 100644 --- a/org.tizen.guides/html/web/tizen/ui/badge_w.htm +++ b/org.tizen.guides/html/web/tizen/application/badge_w.htm @@ -22,7 +22,7 @@

Related Info

@@ -43,9 +43,9 @@

The main features of the Badge API include:

Managing badges -
You can set and get the badge number.

You can set and get the badge number.

Listening to badge changes -
You can receive notifications on badge changes to display and react to badges.

You can receive notifications on badge changes to display and react to badges.

diff --git a/org.tizen.guides/html/web/tizen/ui/inputdevice_w.htm b/org.tizen.guides/html/web/tizen/application/inputdevice_w.htm similarity index 87% rename from org.tizen.guides/html/web/tizen/ui/inputdevice_w.htm rename to org.tizen.guides/html/web/tizen/application/inputdevice_w.htm index 5044d89..76d428c 100644 --- a/org.tizen.guides/html/web/tizen/ui/inputdevice_w.htm +++ b/org.tizen.guides/html/web/tizen/application/inputdevice_w.htm @@ -22,7 +22,7 @@

Related Info

@@ -37,13 +37,13 @@

The main features of the Input Device API include:

Gathering a list of supported keys -
You can get a list of all supported keys +
You can get a list of all supported keys using the InputDeviceManager interface.
Getting key information by its name -
You can gather information about the key by its name +
You can gather information about the key by its name using the InputDeviceManager interface and InputDeviceKey object.
Registering and unregistering key events -
When you want to react to Input Device key presses, register the applicable key using the InputDeviceManager interface. After registering the input device key, the application receives a DOM keyboard event when the key is pressed or released. When the events are no longer needed, unregister the key.
+
When you want to react to Input Device key presses, register the applicable key using the InputDeviceManager interface. After registering the input device key, the application receives a DOM keyboard event when the key is pressed or released. When the events are no longer needed, unregister the key.

The application cannot register the mandatory keys (ArrowLeft, ArrowRight, ArrowUp, ArrowDown, Enter, and Back).

diff --git a/org.tizen.guides/html/web/tizen/input_output/message_port_w.htm b/org.tizen.guides/html/web/tizen/application/message_port_w.htm similarity index 94% rename from org.tizen.guides/html/web/tizen/input_output/message_port_w.htm rename to org.tizen.guides/html/web/tizen/application/message_port_w.htm index 5202274..d3ca912 100644 --- a/org.tizen.guides/html/web/tizen/input_output/message_port_w.htm +++ b/org.tizen.guides/html/web/tizen/application/message_port_w.htm @@ -22,7 +22,7 @@

Related Info

@@ -46,7 +46,7 @@

A message port supports sending and receiving methods:

A Tizen Web application can send messages to another application using the sendMessage() method of the RemoteMessagePort interface. +

A Tizen Web application can send messages to another application using the sendMessage() method of the RemoteMessagePort interface.
To receive response messages from the other application, your application can specify a local message port when it sends the message. You can receive response messages using the callback method which is registered through the addMessagePortListener() method of the LocalMessagePort interface.
The application that wants to receive messages from your application can mostly be implemented as a Tizen Web or native application. To implement it as a native application, see the mobile native Message Port Communication guide.

diff --git a/org.tizen.guides/html/web/tizen/ui/noti_w.htm b/org.tizen.guides/html/web/tizen/application/noti_w.htm similarity index 93% rename from org.tizen.guides/html/web/tizen/ui/noti_w.htm rename to org.tizen.guides/html/web/tizen/application/noti_w.htm index 5f7194e..b806104 100644 --- a/org.tizen.guides/html/web/tizen/ui/noti_w.htm +++ b/org.tizen.guides/html/web/tizen/application/noti_w.htm @@ -22,7 +22,7 @@

Related Info

@@ -39,9 +39,9 @@

The main features of the Notification API include:

To display a notification, you need to create a Notification object (in mobile and wearable applications), or its subtype.

diff --git a/org.tizen.guides/html/web/tizen/input_output/archive_w.htm b/org.tizen.guides/html/web/tizen/base/archive_w.htm similarity index 89% rename from org.tizen.guides/html/web/tizen/input_output/archive_w.htm rename to org.tizen.guides/html/web/tizen/base/archive_w.htm index 9ae1e5f..ac340d4 100644 --- a/org.tizen.guides/html/web/tizen/input_output/archive_w.htm +++ b/org.tizen.guides/html/web/tizen/base/archive_w.htm @@ -22,7 +22,7 @@

Related Info

@@ -42,9 +42,9 @@

The main features of the Archive API include:

Accessing archive content
You can read the content of an archive file using the ArchiveFile interface (in mobile and wearable applications).
Creating new archives
You can create archive files and add files into them using the ArchiveFile interface.
Extracting archived files
You can extract a single file or all files from an archive file using the ArchiveFile interface.
Accessing archive content
You can read the content of an archive file using the ArchiveFile interface (in mobile and wearable applications).
Creating new archives
You can create archive files and add files into them using the ArchiveFile interface.
Extracting archived files
You can extract a single file or all files from an archive file using the ArchiveFile interface.
Aborting operations
You can abort an on-going archive operation using the operation ID and the abort() method of the ArchiveManager interface.

You can abort the operations for the open(), add(), extractAll(), getEntries(), getEntryByName(), and extract() methods.

diff --git a/org.tizen.guides/html/web/tizen/input_output/io_guide_w.htm b/org.tizen.guides/html/web/tizen/base/base_guide_w.htm similarity index 76% rename from org.tizen.guides/html/web/tizen/input_output/io_guide_w.htm rename to org.tizen.guides/html/web/tizen/base/base_guide_w.htm index 647a3f1..de53ee4 100644 --- a/org.tizen.guides/html/web/tizen/input_output/io_guide_w.htm +++ b/org.tizen.guides/html/web/tizen/base/base_guide_w.htm @@ -10,7 +10,7 @@ - Input/Output + Base @@ -22,23 +22,24 @@

Related Info

Input/Output

Input/output features include information on how your application can process input and output data.

The main input/output features are:

+ +

Base

Base features include managing the common files, zip archive files and handling events and organizeing data.

The main base features are:

Archive
Enables you to operate on the zip archive files.
Filesystem
Enables you to access specific parts of the device file system.
Message Port
Allows you to send and receive messages through message ports.

- +

Messaging

Messaging features include managing messaging functionalities for SMS, MMS, email and receive push notifications from a push server.

The main messaging features are:

Push
Allows you to receive push notifications from a push server.

+ +

The following guides apply in mobile applications only:

Messaging
Allows you to create applications with messaging functionalities using SMS, MMS, and email.

+ + + +

+ +

+ + + + + + + \ No newline at end of file diff --git a/org.tizen.guides/html/web/tizen/communication/messaging_w.htm b/org.tizen.guides/html/web/tizen/messaging/messaging_w.htm similarity index 55% rename from org.tizen.guides/html/web/tizen/communication/messaging_w.htm rename to org.tizen.guides/html/web/tizen/messaging/messaging_w.htm index 13f569b..febb488 100644 --- a/org.tizen.guides/html/web/tizen/communication/messaging_w.htm +++ b/org.tizen.guides/html/web/tizen/messaging/messaging_w.htm @@ -22,7 +22,7 @@

Related Info

@@ -40,7 +40,7 @@

The main features of the Messaging API include:

Message writing
You can create a message by using the Message object constructor, and you can set the message attributes and parameters using a MessageInit object (for example, you can set the message service type - SMS, MMS or email - by using the type parameter).

You can add attachments to your MMS and email messages by creating a MessageAttachment object with the file path and the MIME type (image/png, text/pdf, or text/html) for each object and assigning an array of those objects to the attachments attribute of the Message object.

To save message drafts for later, use the addDraftMessage() method of the MessageStorage interface.
+
Message writing
You can create a message by using the Message object constructor, and you can set the message attributes and parameters using a MessageInit object (for example, you can set the message service type - SMS, MMS or email - by using the type parameter).

You can add attachments to your MMS and email messages by creating a MessageAttachment object with the file path and the MIME type (image/png, text/pdf, or text/html) for each object and assigning an array of those objects to the attachments attribute of the Message object.

To save message drafts for later, use the addDraftMessage() method of the MessageStorage interface.

@@ -51,17 +51,17 @@

Message sending
You can send messages by using the sendMessage() method of the MessageService interface.

The method requires both success and error event handlers. Depending on the result of the sending operation, the message is moved to the device's Sent Items folder or Drafts folder, and additionally stored in the message storage database.
Message sending
You can send messages by using the sendMessage() method of the MessageService interface.

The method requires both success and error event handlers. Depending on the result of the sending operation, the message is moved to the device's Sent Items folder or Drafts folder, and additionally stored in the message storage database.
Message management -
You can find, update, and delete stored messages with methods provided by the MessageStorage interface: findMessages(), updateMessages(), and removeMessages(). The interface allows you to manage message storages.
-
When searching for messages, you can create attribute filters, attribute range filters, and composite filters based on specific filter attributes. You can also sort the search results.

You can find, update, and delete stored messages with methods provided by the MessageStorage interface: findMessages(), updateMessages(), and removeMessages(). The interface allows you to manage message storages.

When searching for messages, you can create attribute filters, attribute range filters, and composite filters based on specific filter attributes. You can also sort the search results.

Message storage change notifications -
You can register event listeners to monitor changes in the message storage, a particular conversation, or a particular message folder.
+
You can register event listeners to monitor changes in the message storage, a particular conversation, or a particular message folder.

The addMessagesChangeListener(), addConversationsChangeListener(), and addFoldersChangeListener() methods of the MessageStorage interface register an event listener, which starts asynchronously once the method returns the subscription identifier for the listener. You can use the MessagesChangeCallback, MessageConversationsChangeCallback, and MessageFoldersChangeCallback interfaces to define listener event handlers for receiving notifications about the changes.
Finding folders
You can find message folders by using the findFolders() method of the MessageStorage interface.
Full message content retrieval from the email server
It is possible that an email message is accessible through the Message object, but its full body or attachment has not been downloaded yet. You can load email messages and attachments from the email service with the loadMessageBody() and loadMessageAttachment() methods of the MessageService interface.
To keep your email service accounts up-to-date, synchronize them with their respective external servers, such as Gmail and Microsoft Exchange, with the sync() method. You can also synchronize just one folder, such as the Inbox, with the syncFolder() method.

You can specify the maximum number of messages that can be retrieved in each folder.
Finding folders
You can find message folders by using the findFolders() method of the MessageStorage interface.
Full message content retrieval from the email server
It is possible that an email message is accessible through the Message object, but its full body or attachment has not been downloaded yet. You can load email messages and attachments from the email service with the loadMessageBody() and loadMessageAttachment() methods of the MessageService interface.
To keep your email service accounts up-to-date, synchronize them with their respective external servers, such as Gmail and Microsoft Exchange, with the sync() method. You can also synchronize just one folder, such as the Inbox, with the syncFolder() method.

You can specify the maximum number of messages that can be retrieved in each folder.
SMS and dual SIM -
If there are multiple SIM cards in the device, by default the system determines which one is used to send a message. You can also specify the SIM card when sending an SMS.
+
If there are multiple SIM cards in the device, by default the system determines which one is used to send a message. You can also specify the SIM card when sending an SMS.

Related Info

@@ -46,8 +46,8 @@

The push service provides the RESTful open API for sending a push message. For more information on the Tizen Push Server API, see Sending Push Notifications.

The main features of the Push API include:

Registering to the push service
You can register or unregister the application for the push service. If the registration process is successful, it returns the registration identifier through the PushRegisterSuccessCallback listener (in mobile and wearable applications).
Receiving push notifications
You can connect to the push service and start receiving push notifications with the connectService() method. You must pass the PushNotificationCallback listener (in mobile and wearable applications) instance as a parameter in the method to receive push notifications.
Registering to the push service
You can register or unregister the application for the push service. If the registration process is successful, it returns the registration identifier through the PushRegisterSuccessCallback listener (in mobile and wearable applications).
Receiving push notifications
You can connect to the push service and start receiving push notifications with the connectService() method. You must pass the PushNotificationCallback listener (in mobile and wearable applications) instance as a parameter in the method to receive push notifications.

diff --git a/org.tizen.guides/html/web/tizen/system/fm_radio_w.htm b/org.tizen.guides/html/web/tizen/multimedia/fm_radio_w.htm similarity index 90% rename from org.tizen.guides/html/web/tizen/system/fm_radio_w.htm rename to org.tizen.guides/html/web/tizen/multimedia/fm_radio_w.htm index f1c212d..9b70c27 100644 --- a/org.tizen.guides/html/web/tizen/system/fm_radio_w.htm +++ b/org.tizen.guides/html/web/tizen/multimedia/fm_radio_w.htm @@ -22,7 +22,7 @@

Related Info

@@ -38,11 +38,11 @@

The main features of the FM Radio API include:

Managing the radio -
You can control the radio playback and change frequency.

You can control the radio playback and change frequency.

Scanning available radio channels -
You can scan the available frequencies to find a channel.

You can scan the available frequencies to find a channel.

Getting information about interruptions -
The Tizen system has a feature to prevent interference between radio sound and other source of sound. The sound of the radio is interrupted in reaction to various events, such as an incoming call or notification sound. You can use the oninterrupted event handler to detect the reason for the interruption.

The Tizen system has a feature to prevent interference between radio sound and other source of sound. The sound of the radio is interrupted in reaction to various events, such as an incoming call or notification sound. You can use the oninterrupted event handler to detect the reason for the interruption.

The available operations depend on the current radio state. Radio states and transitions between them are illustrated in the following figure.

Figure: FM radio states and transitions

diff --git a/org.tizen.guides/html/web/tizen/multimedia/multimedia_guide_w.htm b/org.tizen.guides/html/web/tizen/multimedia/multimedia_guide_w.htm index 9627458..69c5fb8 100644 --- a/org.tizen.guides/html/web/tizen/multimedia/multimedia_guide_w.htm +++ b/org.tizen.guides/html/web/tizen/multimedia/multimedia_guide_w.htm @@ -34,15 +34,14 @@

Multimedia features include managing the device sound volume and media keys.

The main multimedia features are:

Media Key
Enables you to handle media keys in your application.
Media Controller
Enables you to communicate between the media controller server and client.
Sound
Enables you to control the volume level of several sound types and get information about the current sound mode and the state of the current sound devices.

- -

The following guides apply in mobile applications only:

Media Controller
Enables you to communicate between the media controller server and client.

- +

FM Radio

Enables you to access and control the device FM radio.

+ +

diff --git a/org.tizen.guides/html/web/tizen/communication/bluetooth_w.htm b/org.tizen.guides/html/web/tizen/network/bluetooth_w.htm similarity index 51% rename from org.tizen.guides/html/web/tizen/communication/bluetooth_w.htm rename to org.tizen.guides/html/web/tizen/network/bluetooth_w.htm index 1ecbc39..aff150e 100644 --- a/org.tizen.guides/html/web/tizen/communication/bluetooth_w.htm +++ b/org.tizen.guides/html/web/tizen/network/bluetooth_w.htm @@ -22,7 +22,7 @@

Related Info

@@ -38,35 +38,35 @@

The main features of the Bluetooth API include:

Managing the local Bluetooth adapter
You can manage the local Bluetooth adapter using the system-provided service through the ApplicationControl interface (in mobile and wearable applications).

To use the Bluetooth functionality of the device, you must switch the Bluetooth adapter on.
Discovering devices
You can discover other Bluetooth devices.

The device discovery process can retrieve multiple types of Bluetooth devices, such as printers, mobile phones, and headphones. To find the kind of devices you want to communicate with, the BluetoothClass interface (in mobile and wearable applications) is used to define characteristics and capabilities of a Bluetooth device. The BluetoothClassDeviceMajor interface (in mobile and wearable applications) and BluetoothClassDeviceMinor interface (in mobile and wearable applications) specify the identifiers for major and minor Class of Device (CoD).

In addition, you can retrieve the known devices which were bonded or found in a prior discovery process.
Creating a bonding with a Bluetooth device
You can create a bonding with another device retrieved through the discovery process. The bonding allows the 2 devices to establish a connection.
Connecting to and exchanging data with a Bluetooth device
You can connect to and exchange data with a remote Bluetooth device. When you attempt to open a connection to another device, a Service Discovery Protocol (SDP) look-up is performed on the device, and the protocol and channel to be used for the connection are determined. If a connection is established and the socket is opened successfully, a BluetoothSocket instance (in mobile and wearable applications) with an open state is returned. The socket is subsequently used for exchanging data between the connected devices.

If a device allows other devices to use its functionalities through this kind of connection, it is said to provide a service.
Communicating with a health source device
The Health Device Profile defines the requirements for the Bluetooth health device implementation. In the profile, there are 2 device type: one device is a source, such as a blood pressure monitor or pulse oximeter, while the other is a sink, such as a mobile phone or laptop. You can use your device as a sink and communicate with a health source device.
Managing the local Bluetooth adapter
You can manage the local Bluetooth adapter using the system-provided service through the ApplicationControl interface (in mobile and wearable applications).

To use the Bluetooth functionality of the device, you must switch the Bluetooth adapter on.
Discovering devices
You can discover other Bluetooth devices.

The device discovery process can retrieve multiple types of Bluetooth devices, such as printers, mobile phones, and headphones. To find the kind of devices you want to communicate with, the BluetoothClass interface (in mobile and wearable applications) is used to define characteristics and capabilities of a Bluetooth device. The BluetoothClassDeviceMajor interface (in mobile and wearable applications) and BluetoothClassDeviceMinor interface (in mobile and wearable applications) specify the identifiers for major and minor Class of Device (CoD).

In addition, you can retrieve the known devices which were bonded or found in a prior discovery process.
Creating a bonding with a Bluetooth device
You can create a bonding with another device retrieved through the discovery process. The bonding allows the 2 devices to establish a connection.
Connecting to and exchanging data with a Bluetooth device
You can connect to and exchange data with a remote Bluetooth device. When you attempt to open a connection to another device, a Service Discovery Protocol (SDP) look-up is performed on the device, and the protocol and channel to be used for the connection are determined. If a connection is established and the socket is opened successfully, a BluetoothSocket instance (in mobile and wearable applications) with an open state is returned. The socket is subsequently used for exchanging data between the connected devices.

If a device allows other devices to use its functionalities through this kind of connection, it is said to provide a service.
Communicating with a health source device
The Health Device Profile defines the requirements for the Bluetooth health device implementation. In the profile, there are 2 device type: one device is a source, such as a blood pressure monitor or pulse oximeter, while the other is a sink, such as a mobile phone or laptop. You can use your device as a sink and communicate with a health source device.

The main Bluetooth (4.0) Low Energy features include:

Managing the local Bluetooth adapter -
The Bluetooth adapter management is performed the same way as in the regular Bluetooth API.

The Bluetooth adapter management is performed the same way as in the regular Bluetooth API.

Discovering Bluetooth Low Energy devices -
You can discover Bluetooth Low Energy devices in range. Through the discovery process, you can obtain basic information about available remote devices, such as their names and provided services.

You can discover Bluetooth Low Energy devices in range. Through the discovery process, you can obtain basic information about available remote devices, such as their names and provided services.

Managing the advertising options -
You can manage advertising to control how your device announces itself to other Bluetooth Low Energy devices to be discovered.

You can manage advertising to control how your device announces itself to other Bluetooth Low Energy devices to be discovered.

Connecting to a Bluetooth Low Energy device -
You can connect to a remote Bluetooth Low Energy device. When connected, you can access services and characteristics of the remote device.

You can connect to a remote Bluetooth Low Energy device. When connected, you can access services and characteristics of the remote device.

Receiving notifications on connection state changes -
You can monitor the connection state to detect when the connection to the remote device is lost.

You can monitor the connection state to detect when the connection to the remote device is lost.

Retrieving Bluetooth GATT services -
You can retrieve information about Bluetooth GATT services provided by the remote device.
+
You can retrieve information about Bluetooth GATT services provided by the remote device.

Every GATT service defines characteristics it includes. By knowing the service, you know what features the Bluetooth device exposes.
Accessing the Bluetooth GATT characteristic value -
You can read and write the Bluetooth GATT characteristic value.
+
You can read and write the Bluetooth GATT characteristic value.

Characteristics allows you to monitor and sometimes control remote Bluetooth Low Energy devices. For example, a sensor reading can be exposed by the sensor device as a Bluetooth GATT characteristic.
Receiving notifications on characteristic value changes -
You can monitor a characteristic value to detect any changes, for example, in sensor readings and battery level.

You can monitor a characteristic value to detect any changes, for example, in sensor readings and battery level.

Accessing the Bluetooth GATT descriptor value -
You can read and write the Bluetooth GATT descriptor value.

You can read and write the Bluetooth GATT descriptor value.

diff --git a/org.tizen.guides/html/web/tizen/communication/comm_guide_w.htm b/org.tizen.guides/html/web/tizen/network/network_guide_w.htm similarity index 79% rename from org.tizen.guides/html/web/tizen/communication/comm_guide_w.htm rename to org.tizen.guides/html/web/tizen/network/network_guide_w.htm index 2d1eeb6..5c7ae92 100644 --- a/org.tizen.guides/html/web/tizen/communication/comm_guide_w.htm +++ b/org.tizen.guides/html/web/tizen/network/network_guide_w.htm @@ -10,7 +10,7 @@ - Communication + Network @@ -22,31 +22,24 @@

Related Info

Communication

Communication features include information on how your application can send data to networks and other applications, and receive data back from them.

Network

Network features include information on how your application can send data to networks and other applications, and receive data back from them.

The main communication features are:

The main network features are:

Bluetooth
Allows you to use Bluetooth functionalities, such as managing the Bluetooth service, pairing, and exchanging messages between Bluetooth-enabled devices.
NFC
Allows you to share contacts, photos, and videos, use the device as a smartcard, and communicate with other NFC-enabled devices.
Push
Allows you to receive push notifications from a push server.
Secure Element
Allows you to access secure elements, such as SIM card and secure SD card, in a device.

The following guides apply in mobile applications only:

Messaging
Allows you to create applications with messaging functionalities using SMS, MMS, and email.

- - diff --git a/org.tizen.guides/html/web/tizen/communication/nfc_w.htm b/org.tizen.guides/html/web/tizen/network/nfc_w.htm similarity index 76% rename from org.tizen.guides/html/web/tizen/communication/nfc_w.htm rename to org.tizen.guides/html/web/tizen/network/nfc_w.htm index 11c60aa..491244d 100644 --- a/org.tizen.guides/html/web/tizen/communication/nfc_w.htm +++ b/org.tizen.guides/html/web/tizen/network/nfc_w.htm @@ -23,7 +23,7 @@

Related Info

@@ -59,13 +59,13 @@

The main features of the NFC API include:

NFC device management
You can manage NFC connectivity by enabling or disabling the NFC service.

To use NFC, retrieve the default NFC adapter using the getDefaultAdapter() method of the NFCAdapter interface (in mobile and wearable applications). You can enable and disable NFC using the setPowered() method.
NFC tag and peer detection
To receive notifications when an NFC tag or peer device has been detected, the setTagListener() and setPeerListener() methods of the NFCAdapter interface register event listeners, which trigger notifications when an NFC tag or peer device is detected, respectively. You can use the NFCTagDetectCallback (in mobile and wearable applications) and NFCPeerDetectCallback (in mobile and wearable applications) interfaces to define event handlers for receiving the notifications about attaching and detaching NFC tags and peers, respectively.
NDEF message manipulation
You can handle NDEF messages by first creating NDEF records, using the NDEFRecord interface (in mobile and wearable applications), and then adding the records to an NDEF message using the records attribute of the NDEFMessage interface (in mobile and wearable applications).
NDEF data exchange
You can exchange NDEF data between tags and peers. To exchange data between tags, read from tags and write to tags using the readNDEF() and writeNDEF() methods.

To exchange data between peers, the setReceiveNDEFListener() method of the NFCPeer interface (in mobile and wearable applications) registers an event listener, which triggers an event when an NDEF message is received from a peer.

You can use the NDEFMessageReadCallback interface (in mobile and wearable applications) to define event handlers for reading NDEF messages from tags and peer devices.
+
NFC device management
You can manage NFC connectivity by enabling or disabling the NFC service.

To use NFC, retrieve the default NFC adapter using the getDefaultAdapter() method of the NFCAdapter interface (in mobile and wearable applications). You can enable and disable NFC using the setPowered() method.
NFC tag and peer detection
To receive notifications when an NFC tag or peer device has been detected, the setTagListener() and setPeerListener() methods of the NFCAdapter interface register event listeners, which trigger notifications when an NFC tag or peer device is detected, respectively. You can use the NFCTagDetectCallback (in mobile and wearable applications) and NFCPeerDetectCallback (in mobile and wearable applications) interfaces to define event handlers for receiving the notifications about attaching and detaching NFC tags and peers, respectively.
NDEF message manipulation
You can handle NDEF messages by first creating NDEF records, using the NDEFRecord interface (in mobile and wearable applications), and then adding the records to an NDEF message using the records attribute of the NDEFMessage interface (in mobile and wearable applications).
NDEF data exchange
You can exchange NDEF data between tags and peers. To exchange data between tags, read from tags and write to tags using the readNDEF() and writeNDEF() methods.

To exchange data between peers, the setReceiveNDEFListener() method of the NFCPeer interface (in mobile and wearable applications) registers an event listener, which triggers an event when an NDEF message is received from a peer.

You can use the NDEFMessageReadCallback interface (in mobile and wearable applications) to define event handlers for reading NDEF messages from tags and peer devices.
NFC card emulation
You can enable NFC card emulation and monitor the secure element transaction taking place using the NFCAdapter interface. The secure element transaction is carried out by the device. The Tizen application can detect the transaction, but does not take part in it. Interpreting the transaction data requires knowledge about the data protocol the transaction uses. With the required knowledge, the application can detect whether the transaction was successful.
NFC host-based card emulation (HCE)
You can handle HCE events and transactions taking place using the NFCAdapter interface. HCE is an on-device technology that permits a phone to perform card emulation on an NFC-enabled device without relying on access to a secure element. The transaction data is routed to the host application directly, instead of routing to a secure element. The Tizen application can detect the transaction and can take part in it.
NFC card emulation
You can enable NFC card emulation and monitor the secure element transaction taking place using the NFCAdapter interface. The secure element transaction is carried out by the device. The Tizen application can detect the transaction, but does not take part in it. Interpreting the transaction data requires knowledge about the data protocol the transaction uses. With the required knowledge, the application can detect whether the transaction was successful.
NFC host-based card emulation (HCE)
You can handle HCE events and transactions taking place using the NFCAdapter interface. HCE is an on-device technology that permits a phone to perform card emulation on an NFC-enabled device without relying on access to a secure element. The transaction data is routed to the host application directly, instead of routing to a secure element. The Tizen application can detect the transaction and can take part in it.

diff --git a/org.tizen.guides/html/web/tizen/communication/secure_element_w.htm b/org.tizen.guides/html/web/tizen/network/secure_element_w.htm similarity index 73% rename from org.tizen.guides/html/web/tizen/communication/secure_element_w.htm rename to org.tizen.guides/html/web/tizen/network/secure_element_w.htm index 703bb59..ea8313c 100644 --- a/org.tizen.guides/html/web/tizen/communication/secure_element_w.htm +++ b/org.tizen.guides/html/web/tizen/network/secure_element_w.htm @@ -22,7 +22,7 @@

Related Info

@@ -38,9 +38,9 @@

The main features of the Secure Element API include:

Managing secure elements
You manage secure elements by retrieving all the available secure element readers and receiving notifications of reader changes using the SEService interface (in mobile and wearable applications). You can also shut down secure elements.
Opening and closing sessions and channels
You can open a session to connect to a secure element reader. Within a session, you can open basic or logical channels. When the channel or session is no longer needed, you can close them.
Transmitting APDUs to the applet
You can transmit application protocol data units (APDU) to a secure element using a channel.
Managing secure elements
You manage secure elements by retrieving all the available secure element readers and receiving notifications of reader changes using the SEService interface (in mobile and wearable applications). You can also shut down secure elements.
Opening and closing sessions and channels
You can open a session to connect to a secure element reader. Within a session, you can open basic or logical channels. When the channel or session is no longer needed, you can close them.
Transmitting APDUs to the applet
You can transmit application protocol data units (APDU) to a secure element using a channel.

diff --git a/org.tizen.guides/html/web/tizen/social/calendar_w.htm b/org.tizen.guides/html/web/tizen/social/calendar_w.htm index 012d196..11108d3 100644 --- a/org.tizen.guides/html/web/tizen/social/calendar_w.htm +++ b/org.tizen.guides/html/web/tizen/social/calendar_w.htm @@ -67,7 +67,7 @@ -

When searching for calendar items, you can create attribute filters, attribute range filters, and composite filters based on specific filter attributes. You can also sort the search results.

@@ -128,4 +128,4 @@ var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga - \ No newline at end of file + diff --git a/org.tizen.guides/html/web/tizen/social/call_history_w.htm b/org.tizen.guides/html/web/tizen/social/call_history_w.htm index a597cc3..e8b8c21 100644 --- a/org.tizen.guides/html/web/tizen/social/call_history_w.htm +++ b/org.tizen.guides/html/web/tizen/social/call_history_w.htm @@ -41,7 +41,7 @@

The main features of the Call History API include:

Call history tracking
You can search and store data about all incoming and outgoing calls using the CallHistory interface. The retrieved data is displayed as a list using the CallHistoryEntry interface. You can also manage the call history by removing unnecessary call history items.
-
When searching for call history items, you can create attribute filters, attribute range filters, and composite filters based on specific filter attributes. You can also sort the search results.

When searching for call history items, you can create attribute filters, attribute range filters, and composite filters based on specific filter attributes. You can also sort the search results.

Change tracking
You can register event listeners to monitor changes in the call history using the CallHistoryChangeCallback listener interface.

@@ -66,4 +66,4 @@ var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga - \ No newline at end of file + diff --git a/org.tizen.guides/html/web/tizen/social/contact_w.htm b/org.tizen.guides/html/web/tizen/social/contact_w.htm index 7ffe644..79df2e6 100644 --- a/org.tizen.guides/html/web/tizen/social/contact_w.htm +++ b/org.tizen.guides/html/web/tizen/social/contact_w.htm @@ -55,7 +55,7 @@

When searching for contacts, you can create attribute filters, attribute range filters, and composite filters based on specific filter attributes. You can also sort the search results.

Group management
You can manage contact groups, including getting, updating, and deleting them, using the applicable methods of the AddressBook interface.
Contact change notifications
You can keep the address book in your application synchronized with external contact manager by receiving notifications in your application when contact information changes.

The addChangeListener() method of the Addressbook interface registers an event listener, which starts asynchronously once the addChangeListener() method returns the subscription identifier for the listener. You can use the AddressBookChangeCallback interface to define listener event handlers for receiving the notifications.
@@ -68,7 +68,7 @@

Every change made to the address book triggers an event for which you can define a notification. For batch mode operations, each requested batch operation generates only a single event.
Person management
You can manage persons, including searching, updating, and deleting, by using the applicable methods of the ContactManager interface. When managing a single person at a time, the operations are handled in a synchronous mode.

You can handle multiple persons simultaneously using the applicable batch methods: updateBatch() and removeBatch().

Persons are automatically added or modified when contacts are added to or unlinked from existing persons. You cannot add persons directly.
When searching for persons, you can filter and sort the search results based on specific filter attributes.
Person management
You can manage persons, including searching, updating, and deleting, by using the applicable methods of the ContactManager interface. When managing a single person at a time, the operations are handled in a synchronous mode.

You can handle multiple persons simultaneously using the applicable batch methods: updateBatch() and removeBatch().

Persons are automatically added or modified when contacts are added to or unlinked from existing persons. You cannot add persons directly.
When searching for persons, you can filter and sort the search results based on specific filter attributes.
vCard format conversions
You can convert the contacts to vCard format or back to import and export contacts.

The vCard (RFC 2426) file format (.vcf or .vcard) is a standard for electronic business cards, which contain contact information, such as name, address, phone numbers, email addresses, URLs, logos, photographs, and audio clips.
The Contact API supports vCard version 3.0.

@@ -93,4 +93,4 @@ var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga - \ No newline at end of file + diff --git a/org.tizen.guides/html/web/tizen/social/social_guide_w.htm b/org.tizen.guides/html/web/tizen/social/social_guide_w.htm index 4f853dc..3c543a1 100644 --- a/org.tizen.guides/html/web/tizen/social/social_guide_w.htm +++ b/org.tizen.guides/html/web/tizen/social/social_guide_w.htm @@ -39,7 +39,6 @@

The main social features are:

Account
Allows you to use existing configured on-line accounts and providers, and create new accounts of known types.
Bookmark
Allows you to manage the Tizen Web browser bookmark list on a device.
Calendar
Allows you to manage calendars, events, and tasks on a device.
Call History
Allows you to search, manage, and monitor the call history of a device.

Related Info

@@ -36,7 +36,7 @@

The Media Key API is optional for both Tizen mobile and wearable profiles, which means that it may not be supported in all mobile and wearable devices. The Media Key API is not supported on any Tizen Emulators.

The media keys are used to control multimedia playback. The user can click keys, such as PLAY and FAST FORWARD, and you can detect the key clicks in your application and change the playback accordingly.

The main features of the Media Key API include:

The main system features are:

Human Activity Monitor
Enables you to access the human activity data from various sensors on the device.
Media Key
Enables you to handle media keys in your application.
Power
Enables you to access the state of the device power resource.
Sensor
Enables you to manage sensor data from various sensors on the device.
System Information
Enables you to access and monitor various device details, such as battery level, available device storage, version number, model name, and the cellular network being used.
System Setting
Enables you to access the device wallpaper settings, such as the home screen and lock screen wallpaper image, incoming call ringtone, and email notification tone.
Time
Enables you to use locale-specific calendar features by retrieving date and time information, and manage time features, such as the time zone.

The following guides apply in mobile applications only:

Web Setting
Enables you to set Web view properties, such as setting Web view user agents and deleting Web view cookies.

The following guides apply in mobile applications only:

FM Radio
Enables you to access and control the device FM radio.
Web Setting
Enables you to set Web view properties, such as setting Web view user agents and deleting Web view cookies.

diff --git a/org.tizen.guides/html/web/tizen/ui/ui_guide_w.htm b/org.tizen.guides/html/web/tizen/ui/ui_guide_w.htm deleted file mode 100644 index d6f34cd..0000000 --- a/org.tizen.guides/html/web/tizen/ui/ui_guide_w.htm +++ /dev/null @@ -1,69 +0,0 @@ - - - - - - - - - - - - - User Interface - - - - - -

- -

User Interface

User interface (UI) features include managing badges, notifications, and input devices.

The main UI features are:

Badge
Allows you to create and update badges on the home screen.
Notification
Allows you to create and display different types of notifications.

- -

The following guides apply in mobile applications only:

Input Device
Allows you to manage input keys in the application.

- - - -

- -

- - - - - - - \ No newline at end of file diff --git a/org.tizen.guides/index.xml b/org.tizen.guides/index.xml index bfce9c6..c31aafc 100644 --- a/org.tizen.guides/index.xml +++ b/org.tizen.guides/index.xml @@ -6,61 +6,61 @@ - - + + + + + + + - + + + + + - - - - - - - - - - - + + + - - - + + + + + + + + + + + + + + + + - - - - - - - - - - - - - -

Application

Input/Output

Base

Handling Generic Events

Managing Location Coordinates

Messaging

Communication

Network

User Interface