The SDK contains all the tools required for the development of both native and web Tizen applications. It consists of an IDE based on Eclipse, Emulator, Simulator for web applications, a tool chain, several sample applications, and full documentation. The Tizen SDK is compatible with the following platforms:

The minimum hardware requirements of the development systems are as follows:

Several Tizen SDK installation options are available. You can choose between network, image, or a command-line installation without GUI.

For network installation, please perform the following steps:

If you prefer offline installation, then please follow these steps:

The Tizen IDE is based on Eclipse. Most of the source code of Eclipse is written using the Java programming language. In general, the main advantage of applications created with Java is that they are compatible with different platforms, and this is the main reason why the Tizen IDE and SDK work fine on several desktop operating systems.

compatible with the following platforms:

The minimum hardware requirements of the development systems are as follows:

Several Tizen SDK installation options are available. You can choose between network, image, or a command-line installation without GUI.

For network installation, please perform the following steps:

If you prefer offline installation, then please follow these steps:

The Tizen IDE is based on Eclipse. Most of the source code of Eclipse is written using the Java programming language. In general, the main advantage of applications created with Java is that they are compatible with different platforms, and this is the main reason why the Tizen IDE and SDK work fine on several desktop operating systems.

network installation, please perform the following steps:

If you prefer offline installation, then please follow these steps:

The Tizen IDE is based on Eclipse. Most of the source code of Eclipse is written using the Java programming language. In general, the main advantage of applications created with Java is that they are compatible with different platforms, and this is the main reason why the Tizen IDE and SDK work fine on several desktop operating systems.

It is recommended to ensure that your development system matches the requirements of the Tizen SDK before proceeding with the installation. The Tizen SDK is compatible with the 32-bit and 64-bit versions of Windows 7, as well as with the 32-bit version of Windows XP. Although Windows 8 is not officially listed among the supported platforms, the version for Windows 7 should be compatible with it.

The installation of the Tizen SDK on Windows is straightforward. The simplest way to complete it successfully is to rely on the network installation procedure described in the previous recipe.

The installation of the Tizen SDK on Windows is straightforward. The simplest way to complete it successfully is to rely on the network installation procedure described in the previous recipe.

Tizen SDK on Windows is straightforward. The simplest way to complete it successfully is to rely on the network installation procedure described in the previous recipe.

The network installation manager of the Tizen SDK for Mac OS is distributed as a standard disk image with the dmg extension.

Download the .dmg file and launch it by following the provided instructions in the recipe Installing the Tizen SDK.

If you plan to develop native Tizen applications on Mac OS X, install command-line tools following the Apple guidelines for the version of Mac OS X that you are using (https://developer.apple.com/library/ios/technotes/tn2339/_index.html).

On Mac OS X 10.7.5 (also known as Mac OS X Lion) or later, the Install Manager might fail due to the security settings of the operating system. These settings have to be modified to temporarily prevent the Mac OS X Gatekeeper from blocking the Install Manager and to allow you to proceed with the Tizen SDK installation. Please perform the following steps to configure Gatekeeper on Mac OS X and to solve the issue:

Download the .dmg file and launch it by following the provided instructions in the recipe Installing the Tizen SDK.

If you plan to develop native Tizen applications on Mac OS X, install command-line tools following the Apple guidelines for the version of Mac OS X that you are using (https://developer.apple.com/library/ios/technotes/tn2339/_index.html).

On Mac OS X 10.7.5 (also known as Mac OS X Lion) or later, the Install Manager might fail due to the security settings of the operating system. These settings have to be modified to temporarily prevent the Mac OS X Gatekeeper from blocking the Install Manager and to allow you to proceed with the Tizen SDK installation. Please perform the following steps to configure Gatekeeper on Mac OS X and to solve the issue:

version of Mac OS X that you are using (https://developer.apple.com/library/ios/technotes/tn2339/_index.html).

On Mac OS X 10.7.5 (also known as Mac OS X Lion) or later, the Install Manager might fail due to the security settings of the operating system. These settings have to be modified to temporarily prevent the Mac OS X Gatekeeper from blocking the Install Manager and to allow you to proceed with the Tizen SDK installation. Please perform the following steps to configure Gatekeeper on Mac OS X and to solve the issue:

Officially, Tizen SDK 2.2.1 is compatible only with two versions of Ubuntu: 12.04 and 12.10. Despite this, it is absolutely possible to install and run the SDK on newer versions too. This is applicable to the following versions of Ubuntu:

Although Ubuntu 13.10 is not officially supported, the Tizen SDK can be installed successfully on it as well, but a workaround related to libudev.so.1 should be applied to run SDB. Please check the troubleshooting section of the recipe for more information about fixing SDB on Ubuntu 13.10.

The full installation process can be divided into four milestones:

Visit tizen.org to get the Tizen SDK or just execute the following commands to download Tizen SDK 2.2.1 using your web browser or command-line tool such as wget. For example, if you have a 32-bit version of Ubuntu, then you can run the following command in the terminal:

wget https://cdn.download.tizen.org/sdk/InstallManager/tizen-sdk-2.2.1/tizen-sdk-ubuntu32-v2.2.71.bin

The URL of the installation file for the 64-bit version is slightly different, so it can be downloaded by executing the following command:

wget https://cdn.download.tizen.org/sdk/InstallManager/tizen-sdk-2.2.1/tizen-sdk-ubuntu64-v2.2.71.bin

Oracle JRE must be installed before launching the Tizen SDK.Please note that OpenJDK is not supported. Please follow these steps if you do not have Oracle JRE installed:

Furthermore, Java can be enabled for the Mozilla Firefox web browser that is shipped as the default web browser for Ubuntu. A couple of additional steps must be executed:

We are almost ready to launch the Tizen SDK installer, but before that, some dependencies must be installed.

Ensure that the following packages are installed:

If you are wondering whether a package has already been installed on your development platform, please check it by executing the command dpkg -s followed by the package's name or the list of packages. To install any of the packages from the preceding list, open a terminal and execute sudo apt-get install followed by the name of the package, as follows:

sudo apt-get install expect gtk2-engines-pixbuf libgnome2-0 qemu-user-static libwebkitgtk-1.0-0 gettext module-init-tools libudev-dev

Users of Ubuntu 12.10 or any older version should install the package gksudo as well by executing the following command:

sudo apt-get install gksudo

Please note that if you are using Ubuntu 13.04 or a newer version, you will not be able to install this package as it is not available any more. Instead, you should install package gksu by executing the following command:

sudo apt-get install gksu

Finally, it is time to proceed with the installation of the Tizen SDK. Make sure that the binary file of the Install Manager has executable permissions and launch it. Please note that <version> and <bits> must be replaced with values that match the file downloaded at the beginning of the tutorial:

chmod +x tizen-sdk-ubuntu<bits>-v<version>.bin
./tizen-sdk-ubuntu<bits>-v<version>.bin

When the Install Manager launches, follow the instructions from the Installing the Tizen SDK recipe to complete the installation.

If you are unsure which install type is appropriate for your needs, it is recommended that you select Typical.

In this section, you will learn how to troubleshoot your GNU/Linux installation of Tizen.

The full installation process can be divided into four milestones:

Visit tizen.org to get the Tizen SDK or just execute the following commands to download Tizen SDK 2.2.1 using your web browser or command-line tool such as wget. For example, if you have a 32-bit version of Ubuntu, then you can run the following command in the terminal:

wget https://cdn.download.tizen.org/sdk/InstallManager/tizen-sdk-2.2.1/tizen-sdk-ubuntu32-v2.2.71.bin

The URL of the installation file for the 64-bit version is slightly different, so it can be downloaded by executing the following command:

wget https://cdn.download.tizen.org/sdk/InstallManager/tizen-sdk-2.2.1/tizen-sdk-ubuntu64-v2.2.71.bin

Oracle JRE must be installed before launching the Tizen SDK.Please note that OpenJDK is not supported. Please follow these steps if you do not have Oracle JRE installed:

Furthermore, Java can be enabled for the Mozilla Firefox web browser that is shipped as the default web browser for Ubuntu. A couple of additional steps must be executed:

We are almost ready to launch the Tizen SDK installer, but before that, some dependencies must be installed.

Ensure that the following packages are installed:

If you are wondering whether a package has already been installed on your development platform, please check it by executing the command dpkg -s followed by the package's name or the list of packages. To install any of the packages from the preceding list, open a terminal and execute sudo apt-get install followed by the name of the package, as follows:

sudo apt-get install expect gtk2-engines-pixbuf libgnome2-0 qemu-user-static libwebkitgtk-1.0-0 gettext module-init-tools libudev-dev

Users of Ubuntu 12.10 or any older version should install the package gksudo as well by executing the following command:

sudo apt-get install gksudo

Please note that if you are using Ubuntu 13.04 or a newer version, you will not be able to install this package as it is not available any more. Instead, you should install package gksu by executing the following command:

sudo apt-get install gksu

Finally, it is time to proceed with the installation of the Tizen SDK. Make sure that the binary file of the Install Manager has executable permissions and launch it. Please note that <version> and <bits> must be replaced with values that match the file downloaded at the beginning of the tutorial:

chmod +x tizen-sdk-ubuntu<bits>-v<version>.bin
./tizen-sdk-ubuntu<bits>-v<version>.bin

When the Install Manager launches, follow the instructions from the Installing the Tizen SDK recipe to complete the installation.

If you are unsure which install type is appropriate for your needs, it is recommended that you select Typical.

In this section, you will learn how to troubleshoot your GNU/Linux installation of Tizen.

tizen.org to get the Tizen SDK or just execute the following commands to download Tizen SDK 2.2.1 using your web browser or command-line tool such as wget. For example, if you have a 32-bit version of Ubuntu, then you can run the following command in the terminal:

wget https://cdn.download.tizen.org/sdk/InstallManager/tizen-sdk-2.2.1/tizen-sdk-ubuntu32-v2.2.71.bin

The URL of the installation file for the 64-bit version is slightly different, so it can be downloaded by executing the following command:

wget https://cdn.download.tizen.org/sdk/InstallManager/tizen-sdk-2.2.1/tizen-sdk-ubuntu64-v2.2.71.bin

Oracle JRE must be installed before launching the Tizen SDK.Please note that OpenJDK is not supported. Please follow these steps if you do not have Oracle JRE installed:

Furthermore, Java can be enabled for the Mozilla Firefox web browser that is shipped as the default web browser for Ubuntu. A couple of additional steps must be executed:

We are almost ready to launch the Tizen SDK installer, but before that, some dependencies must be installed.

Ensure that the following packages are installed:

If you are wondering whether a package has already been installed on your development platform, please check it by executing the command dpkg -s followed by the package's name or the list of packages. To install any of the packages from the preceding list, open a terminal and execute sudo apt-get install followed by the name of the package, as follows:

sudo apt-get install expect gtk2-engines-pixbuf libgnome2-0 qemu-user-static libwebkitgtk-1.0-0 gettext module-init-tools libudev-dev

Users of Ubuntu 12.10 or any older version should install the package gksudo as well by executing the following command:

sudo apt-get install gksudo

Please note that if you are using Ubuntu 13.04 or a newer version, you will not be able to install this package as it is not available any more. Instead, you should install package gksu by executing the following command:

sudo apt-get install gksu

Finally, it is time to proceed with the installation of the Tizen SDK. Make sure that the binary file of the Install Manager has executable permissions and launch it. Please note that <version> and <bits> must be replaced with values that match the file downloaded at the beginning of the tutorial:

chmod +x tizen-sdk-ubuntu<bits>-v<version>.bin
./tizen-sdk-ubuntu<bits>-v<version>.bin

When the Install Manager launches, follow the instructions from the Installing the Tizen SDK recipe to complete the installation.

If you are unsure which install type is appropriate for your needs, it is recommended that you select Typical.

In this section, you will learn how to troubleshoot your GNU/Linux installation of Tizen.

your GNU/Linux installation of Tizen.

Please perform the following steps to add extra repositories and install additional packages:

Perform the following actions to remove an extra repository and all packages installed from it:

Each repository contains additional packages that are optional and can be added or deleted by the developer at any time. A repository is specified by a URL, so it is mandatory to have a network connection to the repository's server to download any of its packages. If you are experiencing issues connecting to a repository using HTTP Secure (HTTPS), you can try using the same URL with HTTP.

A proxy has to be used if you want to access repositories from a computer behind a firewall. To configure a proxy, launch Install Manager and click on the Proxy settings button.

following actions to remove an extra repository and all packages installed from it:

Each repository contains additional packages that are optional and can be added or deleted by the developer at any time. A repository is specified by a URL, so it is mandatory to have a network connection to the repository's server to download any of its packages. If you are experiencing issues connecting to a repository using HTTP Secure (HTTPS), you can try using the same URL with HTTP.

A proxy has to be used if you want to access repositories from a computer behind a firewall. To configure a proxy, launch Install Manager and click on the Proxy settings button.

, you can try using the same URL with HTTP.

A proxy has to be used if you want to access repositories from a computer behind a firewall. To configure a proxy, launch Install Manager and click on the Proxy settings button.

The first step of the journey into application development for Tizen starts with the launch of the Tizen IDE. It is based on Eclipse, so it is not a surprise that the Tizen IDE also asks you to select a workspace. If you do not want to be asked to select the workspace every time you start the IDE, just check the option Use this as default and do not ask again. To change the workspace when the Tizen IDE is running, just navigate to File | Switch Workspace.

A welcome screen will be displayed on the first start screen of the Tizen IDE. Click on Workbench to open the Tizen Web perspective and start developing applications. If you want to have a look at the documentation, select any of the other three options. You can get back to the home screen at any time by navigating to Help | Welcome. If you are searching for Tizen's official development documentation, just navigate to Help | Help Contents.

For a lot of developers, the look and feel of their IDE is a key factor for their productivity. Tizen IDE supports all customization options provided by Eclipse. This recipe contains only a few hints for customization of the background and text colors. For more information, please have a look at Tizen IDE and Eclipse documentation or just delve into the preferences.

Execute the following actions to change the background color of the text editor:

Text colors depend on the syntax coloring of the programming languages. Tizen web applications are developed using HTML, CSS, and JavaScript, while the development of native mobile applications relies on C++. Follow these simple steps to change the syntax coloring:

Perform the following steps if you want to change the fonts:

These are the most popular and important views in the Tizen IDE:

official development documentation, just navigate to Help | Help Contents.

For a lot of developers, the look and feel of their IDE is a key factor for their productivity. Tizen IDE supports all customization options provided by Eclipse. This recipe contains only a few hints for customization of the background and text colors. For more information, please have a look at Tizen IDE and Eclipse documentation or just delve into the preferences.

Execute the following actions to change the background color of the text editor:

Text colors depend on the syntax coloring of the programming languages. Tizen web applications are developed using HTML, CSS, and JavaScript, while the development of native mobile applications relies on C++. Follow these simple steps to change the syntax coloring:

Perform the following steps if you want to change the fonts:

These are the most popular and important views in the Tizen IDE:

steps if you want to change the fonts:

These are the most popular and important views in the Tizen IDE:

Tizen IDE:

If an Active Secure profile is not set, the following error message will be displayed on the screen when you try to run an application on a device or emulator from the Tizen IDE:

Signing issue due to missing Active Secure profile

Please set up a secure profile before launching any applications from the Tizen IDE to avoid this annoying warning.

The Active Secure profile can be created manually through the command line or using the integrated graphical user interface from the Tizen IDE.

The recommended way is to generate a certificate through the Tizen IDE. The steps are as follows:

An alternative approach is to create a certificate using the command line and set it as secure profile on the Tizen IDE. Perform the following steps if you prefer to use a terminal:

The creation process of the certificate is similar no matter which approach or operating system you prefer to use. Both the batch file for Windows and the bash script for Linux and Mac OS run CertificateGenerator.jar through the java -jar command. This tool is written in Java and its file format is Java archive (JAR). The advantage of using Java for these kinds of applications is the multiplatform compatibility of Java, as the same code works on any of the operating systems supported by the Tizen SDK: Linux, Mac OS, and Windows.

is not set, the following error message will be displayed on the screen when you try to run an application on a device or emulator from the Tizen IDE:

Signing issue due to missing Active Secure profile

Please set up a secure profile before launching any applications from the Tizen IDE to avoid this annoying warning.

The Active Secure profile can be created manually through the command line or using the integrated graphical user interface from the Tizen IDE.

The recommended way is to generate a certificate through the Tizen IDE. The steps are as follows:

An alternative approach is to create a certificate using the command line and set it as secure profile on the Tizen IDE. Perform the following steps if you prefer to use a terminal:

The creation process of the certificate is similar no matter which approach or operating system you prefer to use. Both the batch file for Windows and the bash script for Linux and Mac OS run CertificateGenerator.jar through the java -jar command. This tool is written in Java and its file format is Java archive (JAR). The advantage of using Java for these kinds of applications is the multiplatform compatibility of Java, as the same code works on any of the operating systems supported by the Tizen SDK: Linux, Mac OS, and Windows.

generate a certificate through the Tizen IDE. The steps are as follows:

An alternative approach is to create a certificate using the command line and set it as secure profile on the Tizen IDE. Perform the following steps if you prefer to use a terminal:

The creation process of the certificate is similar no matter which approach or operating system you prefer to use. Both the batch file for Windows and the bash script for Linux and Mac OS run CertificateGenerator.jar through the java -jar command. This tool is written in Java and its file format is Java archive (JAR). The advantage of using Java for these kinds of applications is the multiplatform compatibility of Java, as the same code works on any of the operating systems supported by the Tizen SDK: Linux, Mac OS, and Windows.

batch file for Windows and the bash script for Linux and Mac OS run CertificateGenerator.jar through the java -jar command. This tool is written in Java and its file format is Java archive (JAR). The advantage of using Java for these kinds of applications is the multiplatform compatibility of Java, as the same code works on any of the operating systems supported by the Tizen SDK: Linux, Mac OS, and Windows.

It is mandatory to download and install Google Chrome on the development system if you intend to test applications on Tizen Web Simulator. The installation path of the Google Chrome browser can be specified in the Preferences of the simulator.

Three options are available to launch an application inside the Web Simulator:

Google Chrome will be started automatically with the Web Simulator. Adjust the orientation and zooming of the simulator by editing the configurations from the panel on the left-hand side of the browser.

Please note that the Web Simulator is compatible only with HTML5 web applications and it is useless for native applications. The simulator loads the HTML file specified at config.xml when the web application is launched. By default, the name of the file is index.html.

Three options are available to launch an application inside the Web Simulator:

Google Chrome will be started automatically with the Web Simulator. Adjust the orientation and zooming of the simulator by editing the configurations from the panel on the left-hand side of the browser.

Please note that the Web Simulator is compatible only with HTML5 web applications and it is useless for native applications. The simulator loads the HTML file specified at config.xml when the web application is launched. By default, the name of the file is index.html.

launch an application inside the Web Simulator:

Google Chrome will be started automatically with the Web Simulator. Adjust the orientation and zooming of the simulator by editing the configurations from the panel on the left-hand side of the browser.

Please note that the Web Simulator is compatible only with HTML5 web applications and it is useless for native applications. The simulator loads the HTML file specified at config.xml when the web application is launched. By default, the name of the file is index.html.

Please ensure that you are running the Tizen Emulator on a computer with a minimum screen resolution of 1280 x 1024 pixels and the latest version of graphical drivers with OpenGL support. It is recommended to use an Intel CPU with Virtualization Technology (VTx). The performance of the emulator depends on the hardware of the computer and it might work slowly on low resource machines. Details about the requirements for the Tizen Emulator are available at https://developer.tizen.org/downloads/sdk/installing-sdk/prerequisites-tizen-sdk.

To create new instances of the Tizen Emulator, launch the Emulator Manager and click on the button with the label Create New VM.

Select the name of the emulator, display resolution, density, skin, and size of RAM. Then, enable or disable the GPU and the hardware visualization of the CPU. When all configurations are set, click on Confirm, as shown in the following screenshot:

The Tizen Emulator

The emulator will appear within the window of the Emulator Manager. Hit the play button to launch it. The loading of Tizen on the virtual machine may vary depending on the hardware of the development system. Wait until Tizen is completely loaded and then use it.

As an alternative, advanced users may launch the emulator from a terminal through a command with the following syntax:

/emulator-x86 --skin-args <skin options> --qemu-args <QEMU options>

Both skin options such as the height and width of the resolution as well as various QEMU options can be specified as arguments of the command. For details of the supported options, please check the user manual in the official Tizen SDK 2.2.1 development documentation:

https://developer.tizen.org/dev-guide/2.2.1/org.tizen.gettingstarted/html/dev_env/emulator_startup_options.htm

Virtualization Technology (VTx). The performance of the emulator depends on the hardware of the computer and it might work slowly on low resource machines. Details about the requirements for the Tizen Emulator are available at https://developer.tizen.org/downloads/sdk/installing-sdk/prerequisites-tizen-sdk.

To create new instances of the Tizen Emulator, launch the Emulator Manager and click on the button with the label Create New VM.

Select the name of the emulator, display resolution, density, skin, and size of RAM. Then, enable or disable the GPU and the hardware visualization of the CPU. When all configurations are set, click on Confirm, as shown in the following screenshot:

The Tizen Emulator

The emulator will appear within the window of the Emulator Manager. Hit the play button to launch it. The loading of Tizen on the virtual machine may vary depending on the hardware of the development system. Wait until Tizen is completely loaded and then use it.

As an alternative, advanced users may launch the emulator from a terminal through a command with the following syntax:

/emulator-x86 --skin-args <skin options> --qemu-args <QEMU options>

Both skin options such as the height and width of the resolution as well as various QEMU options can be specified as arguments of the command. For details of the supported options, please check the user manual in the official Tizen SDK 2.2.1 development documentation:

https://developer.tizen.org/dev-guide/2.2.1/org.tizen.gettingstarted/html/dev_env/emulator_startup_options.htm

Tizen Emulator, launch the Emulator Manager and click on the button with the label Create New VM.

Select the name of the emulator, display resolution, density, skin, and size of RAM. Then, enable or disable the GPU and the hardware visualization of the CPU. When all configurations are set, click on Confirm, as shown in the following screenshot:

The Tizen Emulator

The emulator will appear within the window of the Emulator Manager. Hit the play button to launch it. The loading of Tizen on the virtual machine may vary depending on the hardware of the development system. Wait until Tizen is completely loaded and then use it.

As an alternative, advanced users may launch the emulator from a terminal through a command with the following syntax:

/emulator-x86 --skin-args <skin options> --qemu-args <QEMU options>

Both skin options such as the height and width of the resolution as well as various QEMU options can be specified as arguments of the command. For details of the supported options, please check the user manual in the official Tizen SDK 2.2.1 development documentation:

https://developer.tizen.org/dev-guide/2.2.1/org.tizen.gettingstarted/html/dev_env/emulator_startup_options.htm

After successful installation of the Tizen SDK, SDB is located under tizen_sdk/SDK/sdb. To use the client, an SDB command must be executed within its directory unless the sdb location has been added to the environmental path variable.

To add SDB to the environmental path of Windows 7, perform the following steps:

If you are using Windows XP, the following steps will be helpful if you want to add SDB to the environmental path:

To add SDB to the environmental path for all users on Ubuntu, append the SDB directory to the path that is defined at file /etc/environment. Log out and log in again or just reboot to apply the changes.

To add SDB to the environmental path for all users on Mac OS X Leopard and above, create a text file at the directory /etc/paths.d/ and set the location of SDB within it using root privileges, for example, sudo -s 'echo "<tizen_sdk>/sdb" > /etc/paths.d/sdb'.

A quick and easy alternative approach to achieve a similar result on UNIX-like operating systems, such as Linux and Mac OS, without modifying /etc/environment or creating a file at /etc/paths.d is to create a symbolic link to SDB in the bin directory using root privileges, for example, sudo ln –s <tizen_sdk>/sdb /bin/sdb.

Please note that <tizen_sdk> in both examples must be replaced with the actual path, depending on the installation.

To add SDB to the environmental path of Windows 7, perform the following steps:

If you are using Windows XP, the following steps will be helpful if you want to add SDB to the environmental path:

To add SDB to the environmental path for all users on Ubuntu, append the SDB directory to the path that is defined at file /etc/environment. Log out and log in again or just reboot to apply the changes.

To add SDB to the environmental path for all users on Mac OS X Leopard and above, create a text file at the directory /etc/paths.d/ and set the location of SDB within it using root privileges, for example, sudo -s 'echo "<tizen_sdk>/sdb" > /etc/paths.d/sdb'.

A quick and easy alternative approach to achieve a similar result on UNIX-like operating systems, such as Linux and Mac OS, without modifying /etc/environment or creating a file at /etc/paths.d is to create a symbolic link to SDB in the bin directory using root privileges, for example, sudo ln –s <tizen_sdk>/sdb /bin/sdb.

Please note that <tizen_sdk> in both examples must be replaced with the actual path, depending on the installation.

environmental path of Windows 7, perform the following steps:

If you are using Windows XP, the following steps will be helpful if you want to add SDB to the environmental path:

To add SDB to the environmental path for all users on Ubuntu, append the SDB directory to the path that is defined at file /etc/environment. Log out and log in again or just reboot to apply the changes.

To add SDB to the environmental path for all users on Mac OS X Leopard and above, create a text file at the directory /etc/paths.d/ and set the location of SDB within it using root privileges, for example, sudo -s 'echo "<tizen_sdk>/sdb" > /etc/paths.d/sdb'.

A quick and easy alternative approach to achieve a similar result on UNIX-like operating systems, such as Linux and Mac OS, without modifying /etc/environment or creating a file at /etc/paths.d is to create a symbolic link to SDB in the bin directory using root privileges, for example, sudo ln –s <tizen_sdk>/sdb /bin/sdb.

Please note that <tizen_sdk> in both examples must be replaced with the actual path, depending on the installation.

Perform the following steps to enable and use SDB:

According to the Tizen 2.2.1 official development guide, the values provided for option in the preceding command can be:

The following is a list of all the supported SDB commands with some brief information about them:

Android developers will be happy to find out a lot of similarities between Tizen Smart Development Bridge and Android Debug Bridge. Similar names of both tools is not a coincidence. Both tools have common purposes. Most of the commands are executed using the same keywords on both platforms and have similar behavior.

The following are several use cases of SDB commands:

According to the Tizen 2.2.1 official development guide, the values provided for option in the preceding command can be:

The following is a list of all the supported SDB commands with some brief information about them:

Android developers will be happy to find out a lot of similarities between Tizen Smart Development Bridge and Android Debug Bridge. Similar names of both tools is not a coincidence. Both tools have common purposes. Most of the commands are executed using the same keywords on both platforms and have similar behavior.

The following are several use cases of SDB commands:

The life cycle of an application for Tizen can be divided into six major steps as shown in the following diagram:

Tizen application life cycle

The development of an application is a continuous process. You have to provide regular updates with new features and enhancements. Arm yourself with patience. Some steps might require more time than expected. Sometimes, you may even need to go back to a previous step, for example, if the QA of Tizen Store rejects the application.

Before you start, make sure that you have successfully installed the Tizen developer environment. A Tizen device or emulator is required to debug applications. If you do not have a device, just create an emulator using Tizen Emulator Manager.

Tizen is open, and so is its ecosystem. Tizen Store is the official store that is maintained by Samsung, but you can publish your applications to other stores too. If you wish, you can even create your own store.

an application is a continuous process. You have to provide regular updates with new features and enhancements. Arm yourself with patience. Some steps might require more time than expected. Sometimes, you may even need to go back to a previous step, for example, if the QA of Tizen Store rejects the application.

Before you start, make sure that you have successfully installed the Tizen developer environment. A Tizen device or emulator is required to debug applications. If you do not have a device, just create an emulator using Tizen Emulator Manager.

Tizen is open, and so is its ecosystem. Tizen Store is the official store that is maintained by Samsung, but you can publish your applications to other stores too. If you wish, you can even create your own store.

Tizen is open, and so is its ecosystem. Tizen Store is the official store that is maintained by Samsung, but you can publish your applications to other stores too. If you wish, you can even create your own store.

Web applications are installed and executed as standalone applications on Tizen, thanks to the Web Runtime (WRT) engine. All standard HTML5 APIs are supported. There are certain features that are not covered by these APIs, so Tizen web runtime fills the gap by providing additional JavaScript functions.

This recipe demonstrates WRT in action by creating a simple Hello World web application and running it on a Tizen device or an emulator.

Upon creating a new project, the Tizen IDE automatically generates the directory structure and creates files if a template is selected.

All configurations and permissions of the application are set at the XML file config.xml. The Tizen IDE provides means to simplify the editing process of the file. The name, the identifier, the version, the icon file, as well as the entry file, which is index.html by default, are among the configurations stored in config.xml. Access to sensitive APIs should also be set by describing privileges at this file if the application uses such sensitive APIs.

Several JavaScripts and CSSes are included using the following HTML code to make sure that the application is compatible with Tizen WRT and use the standard Tizen look and feel:

<link rel="stylesheet" href="tizen-web-ui-fw/latest/themes/tizen-white/tizen-web-ui-fw-theme.css" name="tizen-theme"/>
<script src="tizen-web-ui-fw/latest/js/jquery.js"></script>
<script src="tizen-web-ui-fw/latest/js/tizen-web-ui-fw-libs.js"></script>
<script src="tizen-web-ui-fw/latest/js/tizen-web-ui-fw.js" data-framework-theme="tizen-white"></script>
<script type="text/javascript" src="./js/main.js"></script>

The file js/main.js will be generated by the IDE, and it will contain the JavaScript source code for initialization of the application and for the handling of the back hardware button. Pay attention to the fact that jQuery is also included because the Tizen Web UI framework is based on jQuery Mobile.

If you have any trouble creating a Hello World application from scratch, use the example provided with the book.

Web Runtime (WRT) engine. All standard HTML5 APIs are supported. There are certain features that are not covered by these APIs, so Tizen web runtime fills the gap by providing additional JavaScript functions.

This recipe demonstrates WRT in action by creating a simple Hello World web application and running it on a Tizen device or an emulator.

Upon creating a new project, the Tizen IDE automatically generates the directory structure and creates files if a template is selected.

All configurations and permissions of the application are set at the XML file config.xml. The Tizen IDE provides means to simplify the editing process of the file. The name, the identifier, the version, the icon file, as well as the entry file, which is index.html by default, are among the configurations stored in config.xml. Access to sensitive APIs should also be set by describing privileges at this file if the application uses such sensitive APIs.

Several JavaScripts and CSSes are included using the following HTML code to make sure that the application is compatible with Tizen WRT and use the standard Tizen look and feel:

<link rel="stylesheet" href="tizen-web-ui-fw/latest/themes/tizen-white/tizen-web-ui-fw-theme.css" name="tizen-theme"/>
<script src="tizen-web-ui-fw/latest/js/jquery.js"></script>
<script src="tizen-web-ui-fw/latest/js/tizen-web-ui-fw-libs.js"></script>
<script src="tizen-web-ui-fw/latest/js/tizen-web-ui-fw.js" data-framework-theme="tizen-white"></script>
<script type="text/javascript" src="./js/main.js"></script>

The file js/main.js will be generated by the IDE, and it will contain the JavaScript source code for initialization of the application and for the handling of the back hardware button. Pay attention to the fact that jQuery is also included because the Tizen Web UI framework is based on jQuery Mobile.

If you have any trouble creating a Hello World application from scratch, use the example provided with the book.

Upon creating a new project, the Tizen IDE automatically generates the directory structure and creates files if a template is selected.

All configurations and permissions of the application are set at the XML file config.xml. The Tizen IDE provides means to simplify the editing process of the file. The name, the identifier, the version, the icon file, as well as the entry file, which is index.html by default, are among the configurations stored in config.xml. Access to sensitive APIs should also be set by describing privileges at this file if the application uses such sensitive APIs.

Several JavaScripts and CSSes are included using the following HTML code to make sure that the application is compatible with Tizen WRT and use the standard Tizen look and feel:

<link rel="stylesheet" href="tizen-web-ui-fw/latest/themes/tizen-white/tizen-web-ui-fw-theme.css" name="tizen-theme"/>
<script src="tizen-web-ui-fw/latest/js/jquery.js"></script>
<script src="tizen-web-ui-fw/latest/js/tizen-web-ui-fw-libs.js"></script>
<script src="tizen-web-ui-fw/latest/js/tizen-web-ui-fw.js" data-framework-theme="tizen-white"></script>
<script type="text/javascript" src="./js/main.js"></script>

The file js/main.js will be generated by the IDE, and it will contain the JavaScript source code for initialization of the application and for the handling of the back hardware button. Pay attention to the fact that jQuery is also included because the Tizen Web UI framework is based on jQuery Mobile.

If you have any trouble creating a Hello World application from scratch, use the example provided with the book.

The Tizen platform provides the following JavaScript-based APIs for development of web applications:

Launch the Tizen IDE and create a new project for Tizen web application, and append the privileges required for the API that you plan to use for config.xml, for example, http://tizen.org/privilege/alarm.

Take, for instance, the following JavaScript code, which demonstrates the simple usage of the Alarm and Application APIs:

// Get the ID of the current application
var sAppId = tizen.application.getCurrentApplication().appInfo.id;

// Set an alarm which will occur after couple of hours
var myAlarm = new tizen.AlarmRelative(2 * tizen.alarm.PERIOD_HOUR);
if (null != myAlarm) {
  tizen.alarm.add(myAlarm, sAppId);
}

All additional device APIs that are used in web applications for Tizen are accessed through the tizen JavaScript object. A set of generic functions, including error handling and filters, is also provided with the tizen object.

The Application API is used to retrieve the ID of the current application, and it is assigned to the JavaScript variable sAppId. After that, a relative alarm that will occur after a couple of hours is created and assigned to the variable myAlarm using the Alarm API. Finally, on the last line of the code snippet, the alarm is added to the alarm storage of the current application.

As you can see, both APIs used in the code snippet are accessed through the tizen JavaScript object.

Launch the Tizen IDE and create a new project for Tizen web application, and append the privileges required for the API that you plan to use for config.xml, for example, http://tizen.org/privilege/alarm.

Take, for instance, the following JavaScript code, which demonstrates the simple usage of the Alarm and Application APIs:

// Get the ID of the current application
var sAppId = tizen.application.getCurrentApplication().appInfo.id;

// Set an alarm which will occur after couple of hours
var myAlarm = new tizen.AlarmRelative(2 * tizen.alarm.PERIOD_HOUR);
if (null != myAlarm) {
  tizen.alarm.add(myAlarm, sAppId);
}

All additional device APIs that are used in web applications for Tizen are accessed through the tizen JavaScript object. A set of generic functions, including error handling and filters, is also provided with the tizen object.

The Application API is used to retrieve the ID of the current application, and it is assigned to the JavaScript variable sAppId. After that, a relative alarm that will occur after a couple of hours is created and assigned to the variable myAlarm using the Alarm API. Finally, on the last line of the code snippet, the alarm is added to the alarm storage of the current application.

As you can see, both APIs used in the code snippet are accessed through the tizen JavaScript object.

http://tizen.org/privilege/alarm.

Take, for instance, the following JavaScript code, which demonstrates the simple usage of the Alarm and Application APIs:

// Get the ID of the current application
var sAppId = tizen.application.getCurrentApplication().appInfo.id;

// Set an alarm which will occur after couple of hours
var myAlarm = new tizen.AlarmRelative(2 * tizen.alarm.PERIOD_HOUR);
if (null != myAlarm) {
  tizen.alarm.add(myAlarm, sAppId);
}

All additional device APIs that are used in web applications for Tizen are accessed through the tizen JavaScript object. A set of generic functions, including error handling and filters, is also provided with the tizen object.

The Application API is used to retrieve the ID of the current application, and it is assigned to the JavaScript variable sAppId. After that, a relative alarm that will occur after a couple of hours is created and assigned to the variable myAlarm using the Alarm API. Finally, on the last line of the code snippet, the alarm is added to the alarm storage of the current application.

As you can see, both APIs used in the code snippet are accessed through the tizen JavaScript object.

is used to retrieve the ID of the current application, and it is assigned to the JavaScript variable sAppId. After that, a relative alarm that will occur after a couple of hours is created and assigned to the variable myAlarm using the Alarm API. Finally, on the last line of the code snippet, the alarm is added to the alarm storage of the current application.

As you can see, both APIs used in the code snippet are accessed through the tizen JavaScript object.

Perform the following steps to localize a Tizen application:

Localization Wizard creates a folder called locales at the root level of the application package and creates separate folders in it for each selected locale. All files that have been chosen for localization of the selected locale will be included in its folder. For example, if we decide to create the French localization of index.html, then the folder /locales/fr will be created and the file will be copied in it.

If a file is not selected for localization, it will not appear in the locales folder, and its original version from the root level of the package will be automatically loaded.

When a web application is launched, Tizen will try to load the content using the current locale, which is configured by the user at the platform settings. If such a locale is not present, then the application will be loaded using its default localization.

In Tizen web applications, dynamic string localization using JavaScript is also possible, thanks to the open source library, Globalize. Perform the following steps to enable and use this library:

Pay attention to the fact that the messages are case sensitive. The output on the Tizen device or Emulator on which the display language has been set to English will be as follows:

Hello
Bonjour

For more information about the open source library, Globalize, visit https://github.com/jquery/globalize.

Localization Wizard creates a folder called locales at the root level of the application package and creates separate folders in it for each selected locale. All files that have been chosen for localization of the selected locale will be included in its folder. For example, if we decide to create the French localization of index.html, then the folder /locales/fr will be created and the file will be copied in it.

If a file is not selected for localization, it will not appear in the locales folder, and its original version from the root level of the package will be automatically loaded.

When a web application is launched, Tizen will try to load the content using the current locale, which is configured by the user at the platform settings. If such a locale is not present, then the application will be loaded using its default localization.

In Tizen web applications, dynamic string localization using JavaScript is also possible, thanks to the open source library, Globalize. Perform the following steps to enable and use this library:

Pay attention to the fact that the messages are case sensitive. The output on the Tizen device or Emulator on which the display language has been set to English will be as follows:

Hello
Bonjour

For more information about the open source library, Globalize, visit https://github.com/jquery/globalize.

In Tizen web applications, dynamic string localization using JavaScript is also possible, thanks to the open source library, Globalize. Perform the following steps to enable and use this library:

Pay attention to the fact that the messages are case sensitive. The output on the Tizen device or Emulator on which the display language has been set to English will be as follows:

Hello
Bonjour

For more information about the open source library, Globalize, visit https://github.com/jquery/globalize.

that the messages are case sensitive. The output on the Tizen device or Emulator on which the display language has been set to English will be as follows:

Hello
Bonjour

For more information about the open source library, Globalize, visit https://github.com/jquery/globalize.

The tools to build Tizen applications are integrated with the Tizen IDE. The building process is simple and it is fully automated. Please ensure that the Tizen SDK and IDE are properly installed before you proceed.

Perform the described actions to build a Tizen web application from the Tizen IDE:

The package produced by the Tizen IDE is created according to W3C recommendations for web applications. For more information, visit http://www.w3.org/TR/widgets/.

The content of the package is compressed using the ZIP archive algorithms and its file must have the extension .wgt. Its MIME type is application/widget.

Several files and folders with reserved names shown in the following table have to be included inside the package of the Tizen web application. After successful installation, a directory, whose name matches the package ID, is created at /opt/usr/apps. The directory hierarchy also includes folders bin (for the application's binary files), data, and res.

Web applications can be installed through SDB through the Tizen IDE or the command-line interface if the developer mode is enabled. Users can download the application from Tizen Store or other stores once it is published.

The package manager of the operating system on the device is responsible for the installation and the management of installed applications. To see the list of all installed applications, launch Settings and select Manage Applications. Click on the application to remove it or to stop it if it is running.

Since Tizen 2.0, it is possible to develop mobile applications using C/C++ programming languages. Although in most of the cases, web applications should be preferred and recommended, native programming is useful for faster performance, low-level access to device capabilities, compatibility with existing Bada applications, as well as third-party libraries and frameworks, such as Qt for Tizen. Native programming for Tizen supports both service applications and applications with GUI.

helloWorldFrame* phelloWorldFrame = new (std::nothrow) helloWorldFrame;
TryReturn(phelloWorldFrame != null, false, "The memory is insufficient.");
phelloWorldFrame->Construct();
phelloWorldFrame->SetName(L"helloWorldNative");
AddFrame(*phelloWorldFrame);

After the successful development and testing of a native application, all of its files must be bundled together into a single installation file, whose extension is .tpk. This file is called package. It sounds similar to the Android application package file (APK), and it has the same purpose. The .tpk file is used to install native applications on Tizen devices and should be uploaded to Tizen Store when the application is published.

Perform the described actions to build a Tizen web application from the Tizen IDE:

The package produced by the Tizen IDE is created according to W3C recommendations for web applications. For more information, visit http://www.w3.org/TR/widgets/.

The content of the package is compressed using the ZIP archive algorithms and its file must have the extension .wgt. Its MIME type is application/widget.

Several files and folders with reserved names shown in the following table have to be included inside the package of the Tizen web application. After successful installation, a directory, whose name matches the package ID, is created at /opt/usr/apps. The directory hierarchy also includes folders bin (for the application's binary files), data, and res.