From c4abcb4770156d1c1c3724c8a17d5e639ab9a8e4 Mon Sep 17 00:00:00 2001 From: Editor Lionbridge Date: Mon, 26 Jun 2017 16:06:34 +0300 Subject: [PATCH] Implement full content edit for preview This change contains a full language, structure, and style edit for the preview content that has been copied from TD to Git. The purpose of this change is to match the quality and style of the preview content to that of the rest of the Tizen library. The Getting Started section has been restructured, since it seems that there are actually 3 different scenarios: creating a new project, creating a new project with a cross-platform solution, and porting an existing cross-platform solution to Tizen. PS2: Added the What's New section changes from TD PS3: Installation topic has been rewritten based on a trial installation PS4: Rebase PS5: Redid some images on a Windows 10 machine, redid emulator screenshot. PS6: Implemented responses to queries. PS7: Removed profile icons and profile info from dependencies. Moved the API Checker topic within the TOC to reflect the TD. Modified the What's New topic based on the latest TD changes. Minor style fixes in the Installation topic. Modified oversized roadmap image. PS8: Minor terminology, grammar, and tagging fixes Changed "Tizen Platform-Specific API" to "TizenFX API" PS9: Changed 1 more instance to "TizenFX API" PS10: Fixed "TizenFX API" term in an image. Change-Id: I6c24b7efb98b792c3fb3d46320412c1e3ff77701 --- preview/html/cover_page.htm | 117 ++-- .../getting_started/cross_platform_project.htm | 83 +++ preview/html/getting_started/first_app.htm | 548 ++++++++---------- .../{download.htm => getting_started_cover.htm} | 20 +- preview/html/getting_started/gridview.htm | 14 +- preview/html/getting_started/installing.htm | 213 +++---- .../html/getting_started/porting_xamarinforms.htm | 129 ++--- preview/html/images/add_tizen_project2.png | Bin 44817 -> 0 bytes preview/html/images/addnewproject.png | Bin 388234 -> 0 bytes preview/html/images/addnewproject2.png | Bin 47554 -> 0 bytes preview/html/images/buildsolution.png | Bin 126663 -> 0 bytes preview/html/images/cert_reg_check.png | Bin 0 -> 222 bytes preview/html/images/cert_reg_plus.png | Bin 602 -> 0 bytes preview/html/images/cert_reg_remove_cert.png | Bin 33377 -> 0 bytes preview/html/images/cert_reg_trash.png | Bin 521 -> 201 bytes preview/html/images/cert_reg_trash_check.png | Bin 0 -> 6804 bytes preview/html/images/change_nuget_version.png | Bin 44625 -> 0 bytes preview/html/images/cs_creating05.png | Bin 33655 -> 0 bytes preview/html/images/cs_creating06.png | Bin 16426 -> 0 bytes ...creating04.png => cs_creating_classlibrary.png} | Bin ...ng => cs_creating_classlibrary_netstandard.png} | Bin .../images/cs_creating_classlibrary_refresh.png | Bin 0 -> 9586 bytes .../cs_creating_classlibrary_restore_nuget.png | Bin 0 -> 14190 bytes ...8.png => cs_creating_classlibrary_warnings.png} | Bin .../cs_device_manager_connection_explorer_view.png | Bin 48657 -> 11423 bytes preview/html/images/cs_device_manager_explorer.png | Bin 32762 -> 0 bytes .../html/images/cs_device_manager_first_screen.png | Bin 9952 -> 8527 bytes .../html/images/cs_device_manager_log_add_tab.png | Bin 7743 -> 0 bytes .../images/cs_device_manager_log_added_tab.png | Bin 53589 -> 43430 bytes .../html/images/cs_device_manager_log_export.png | Bin 45172 -> 15579 bytes preview/html/images/cs_device_manager_menu.png | Bin 11922 -> 11552 bytes preview/html/images/cs_device_manager_prompt.png | Bin 3579 -> 0 bytes preview/html/images/cs_device_manager_start.png | Bin 0 -> 16785 bytes preview/html/images/cs_enhancing01_1.png | Bin 13588 -> 0 bytes preview/html/images/cs_enhancing02_1.png | Bin 14247 -> 0 bytes preview/html/images/cs_first01.png | Bin 23105 -> 0 bytes preview/html/images/cs_first02_1.png | Bin 39859 -> 0 bytes preview/html/images/cs_first08.png | Bin 17812 -> 0 bytes preview/html/images/cs_first09_1.png | Bin 9606 -> 0 bytes .../images/cs_first_building_certificate_01.png | Bin 12527 -> 0 bytes .../images/cs_first_building_certificate_02.png | Bin 24682 -> 0 bytes .../images/cs_first_building_certificate_03.png | Bin 44411 -> 0 bytes .../images/cs_first_building_emulator_enhanced.png | Bin 0 -> 12965 bytes .../images/cs_first_building_emulator_list.png | Bin 4587 -> 2831 bytes .../images/cs_first_building_emulator_manager.png | Bin 46828 -> 43378 bytes .../images/cs_first_building_emulator_mobile.png | Bin 0 -> 3174 bytes .../html/images/cs_first_building_emulator_tv1.png | Bin 4047 -> 2689 bytes preview/html/images/cs_first_building_process.png | Bin 38968 -> 0 bytes .../html/images/cs_first_building_sdb_prompt.png | Bin 0 -> 9243 bytes .../images/cs_first_building_selected_emulator.png | Bin 6567 -> 0 bytes preview/html/images/cs_first_creating_menupath.png | Bin 0 -> 16083 bytes .../html/images/cs_first_creating_new_project.png | Bin 0 -> 34842 bytes .../images/cs_first_creating_project_wizard.png | Bin 0 -> 10536 bytes .../images/cs_first_creating_project_wizard_p3.png | Bin 10810 -> 0 bytes .../images/cs_first_creating_solution_explorer.png | Bin 27654 -> 0 bytes preview/html/images/cs_install01.png | Bin 42123 -> 0 bytes preview/html/images/cs_install02.png | Bin 31108 -> 0 bytes preview/html/images/cs_install03.png | Bin 17776 -> 0 bytes preview/html/images/cs_install04.png | Bin 17424 -> 0 bytes preview/html/images/cs_install05.png | Bin 8867 -> 0 bytes preview/html/images/cs_install06.png | Bin 5579 -> 0 bytes preview/html/images/cs_install07_1.png | Bin 17298 -> 0 bytes preview/html/images/cs_launch_tizen_emu.png | Bin 0 -> 4265 bytes preview/html/images/cs_overview-707x282.png | Bin 49052 -> 0 bytes preview/html/images/cs_overview.png | Bin 15802 -> 10576 bytes preview/html/images/cs_prerequiste02.png | Bin 70521 -> 0 bytes preview/html/images/demo1.jpg | Bin 116054 -> 0 bytes preview/html/images/deploy.png | Bin 43747 -> 0 bytes preview/html/images/em_skin.png | Bin 28389 -> 0 bytes preview/html/images/emulator_control_panel2-1.png | Bin 43072 -> 0 bytes preview/html/images/emulator_control_panel2.png | Bin 25695 -> 0 bytes preview/html/images/emulator_control_panel_hds.png | Bin 49467 -> 5379 bytes .../html/images/emulator_control_panel_layers.png | Bin 0 -> 21283 bytes .../html/images/emulator_control_panel_network.png | Bin 39229 -> 11071 bytes .../html/images/emulator_control_panel_open2.png | Bin 72983 -> 74763 bytes preview/html/images/emulator_manager_create.png | Bin 192 -> 0 bytes .../images/emulator_manager_template_config2.png | Bin 28885 -> 0 bytes preview/html/images/emulator_tv_mobile.png | Bin 0 -> 17018 bytes preview/html/images/hardware_ram.png | Bin 17772 -> 0 bytes preview/html/images/hardware_start_instal.png | Bin 184574 -> 0 bytes preview/html/images/launchtizenemul.png | Bin 30362 -> 0 bytes preview/html/images/log_view_icon.png | Bin 0 -> 323 bytes preview/html/images/log_view_icon_clear.png | Bin 0 -> 327 bytes preview/html/images/log_view_icon_export.png | Bin 0 -> 240 bytes preview/html/images/log_view_icon_lock.png | Bin 0 -> 284 bytes preview/html/images/log_view_icon_remove_tab.png | Bin 0 -> 247 bytes preview/html/images/logviewer_default.png | Bin 63136 -> 0 bytes preview/html/images/logviewer_entry_point.png | Bin 6023 -> 6159 bytes preview/html/images/logviewer_keyword_filter.png | Bin 8230 -> 5967 bytes preview/html/images/logviewer_scroll_lock.png | Bin 0 -> 258 bytes preview/html/images/managenugetpackages.png | Bin 39699 -> 0 bytes preview/html/images/managenugetpackages2.png | Bin 102764 -> 0 bytes preview/html/images/manifest_features.png | Bin 32359 -> 0 bytes preview/html/images/manifest_privileges.png | Bin 29330 -> 0 bytes preview/html/images/manifest_text_editor.png | Bin 26292 -> 0 bytes preview/html/images/openproject.png | Bin 25220 -> 0 bytes preview/html/images/platform_mismatch_warning.png | Bin 13465 -> 0 bytes preview/html/images/pw1.png | Bin 35518 -> 0 bytes preview/html/images/release_plan_preview4_m1.png | Bin 164397 -> 0 bytes preview/html/images/roadmap.png | Bin 0 -> 503938 bytes .../images/solution_explorer_tizen_project2.png | Bin 45320 -> 0 bytes preview/html/images/tizenemulmanager.png | Bin 24411 -> 0 bytes preview/html/images/tizenprojectwizard.png | Bin 12401 -> 0 bytes preview/html/images/tizentvdemo1.png | Bin 37034 -> 0 bytes preview/html/images/tizentvdemo2.png | Bin 32611 -> 0 bytes preview/html/images/vs_em_2.png | Bin 23978 -> 0 bytes preview/html/images/vs_em_4.png | Bin 49909 -> 0 bytes preview/html/images/vs_em_launch.png | Bin 40671 -> 0 bytes preview/html/images/vs_em_launched.png | Bin 38887 -> 0 bytes ...d_debug.png => vs_emulator_activated_debug.png} | Bin preview/html/images/vs_emulator_launch.png | Bin 0 -> 4533 bytes .../{vs_em_1.png => vs_emulator_manager.png} | Bin ...ger_clone.png => vs_emulator_manager_clone.png} | Bin preview/html/images/vs_emulator_manager_config.png | Bin 0 -> 23897 bytes ...r_delete.png => vs_emulator_manager_delete.png} | Bin ...ng => vs_emulator_manager_device_template2.png} | Bin ...r_modify.png => vs_emulator_manager_modify.png} | Bin .../images/vs_emulator_manager_platform_config.png | Bin 0 -> 19055 bytes .../vs_emulator_manager_template_config2.png | Bin 0 -> 13826 bytes preview/html/images/vs_emulatormanager_1.png | Bin 19832 -> 19424 bytes preview/html/images/vs_emulatormanager_2.png | Bin 1944 -> 0 bytes .../html/images/vs_install_confirm_settings.png | Bin 0 -> 19789 bytes preview/html/images/vs_install_debugger.png | Bin 0 -> 11747 bytes preview/html/images/vs_install_disable_hyperv.png | Bin 0 -> 18708 bytes .../html/images/vs_install_extensions_check.png | Bin 0 -> 39615 bytes preview/html/images/vs_install_haxm.png | Bin 0 -> 47244 bytes preview/html/images/vs_install_haxm_confirm.png | Bin 0 -> 15259 bytes preview/html/images/vs_install_haxm_finished.png | Bin 0 -> 38951 bytes .../html/images/vs_install_haxm_installation.png | Bin 0 -> 15709 bytes preview/html/images/vs_install_haxm_ram.png | Bin 0 -> 20270 bytes preview/html/images/vs_install_installshield.png | Bin 0 -> 70931 bytes .../images/vs_install_installshield_finish.png | Bin 0 -> 73995 bytes .../html/images/vs_install_license_agreement.png | Bin 0 -> 27468 bytes preview/html/images/vs_install_new_project.png | Bin 0 -> 17326 bytes ...iste01.png => vs_install_programs_features.png} | Bin preview/html/images/vs_install_readme.png | Bin 0 -> 25850 bytes preview/html/images/vs_install_username.png | Bin 0 -> 15704 bytes preview/html/images/vs_install_vstools.png | Bin 0 -> 11557 bytes ...anifest_editing.png => vs_manifest_editing.png} | Bin preview/html/images/vs_manifest_features.png | Bin 0 -> 46779 bytes ...ifest_overview.png => vs_manifest_overview.png} | Bin preview/html/images/vs_manifest_privileges.png | Bin 0 -> 35741 bytes preview/html/images/vs_manifest_text_editor.png | Bin 0 -> 10096 bytes .../{pw2.png => vs_project_wizard_properties.png} | Bin preview/html/images/vs_project_wizard_template.png | Bin 0 -> 34999 bytes preview/html/images/vstools_cert_certificate1.png | Bin 19185 -> 16726 bytes preview/html/images/vstools_cert_default.png | Bin 5924 -> 4868 bytes preview/html/images/vstools_cert_menu.png | Bin 18897 -> 0 bytes preview/html/images/vstools_cert_profile1.png | Bin 10402 -> 9213 bytes preview/html/images/vstools_cert_result.png | Bin 27862 -> 6646 bytes preview/html/images/vstools_solution.png | Bin 23165 -> 20360 bytes preview/html/images/xamarin_add_new_project.png | Bin 0 -> 45157 bytes .../html/images/xamarin_add_tizen_templates.png | Bin 0 -> 33313 bytes ...ojects.png => xamarin_added_tizen_projects.png} | Bin preview/html/images/xamarin_application.png | Bin 58557 -> 75376 bytes .../html/images/xamarin_basicanimation_mobile.png | Bin 0 -> 146422 bytes ...{demo1.png => xamarin_basicanimation_tizen.png} | Bin .../html/images/xamarin_basicanimation_tizentv.png | Bin 0 -> 17601 bytes ...n_blank_app.png => xamarin_blank_app_tizen.png} | Bin preview/html/images/xamarin_build_solution.png | Bin 0 -> 36721 bytes .../html/images/xamarin_change_nuget_version.png | Bin 0 -> 91472 bytes preview/html/images/xamarin_manage_nuget.png | Bin 0 -> 38338 bytes preview/html/images/xamarin_manage_packages.png | Bin 0 -> 117935 bytes preview/html/images/xamarin_open_new_project.png | Bin 0 -> 20991 bytes preview/html/images/xamarin_platform_mismatch.png | Bin 0 -> 10732 bytes .../xamarin_projectwizard_basicanimation.png | Bin 0 -> 8029 bytes .../images/xamarin_solution_explorer_tizen.png | Bin 0 -> 36264 bytes preview/html/index.htm | 14 +- preview/html/introduction/overview.htm | 161 ------ preview/html/introduction/roadmap.htm | 8 +- preview/html/introduction/whats_new.htm | 90 +++ preview/html/tools/api-privilege_checker.htm | 4 - preview/html/tools/certificate_manager.htm | 125 ++-- preview/html/tools/device_manager.htm | 218 +++---- preview/html/tools/emulator_control_panel.htm | 628 ++++++++++----------- preview/html/tools/emulator_manager.htm | 214 ++++--- preview/html/tools/log_viewer.htm | 70 ++- preview/html/tools/manifest_editor.htm | 452 +++++++-------- preview/html/tools/manifest_elements.htm | 103 ++-- preview/html/tools/project_wizard.htm | 86 +-- preview/html/tools/tools_overview.htm | 40 +- preview/index.xml | 14 +- 182 files changed, 1587 insertions(+), 1764 deletions(-) create mode 100644 preview/html/getting_started/cross_platform_project.htm rename preview/html/getting_started/{download.htm => getting_started_cover.htm} (69%) delete mode 100644 preview/html/images/add_tizen_project2.png delete mode 100644 preview/html/images/addnewproject.png delete mode 100644 preview/html/images/addnewproject2.png delete mode 100644 preview/html/images/buildsolution.png create mode 100644 preview/html/images/cert_reg_check.png delete mode 100644 preview/html/images/cert_reg_plus.png delete mode 100644 preview/html/images/cert_reg_remove_cert.png create mode 100644 preview/html/images/cert_reg_trash_check.png delete mode 100644 preview/html/images/change_nuget_version.png delete mode 100644 preview/html/images/cs_creating05.png delete mode 100644 preview/html/images/cs_creating06.png rename preview/html/images/{cs_creating04.png => cs_creating_classlibrary.png} (100%) rename preview/html/images/{cs_creating07.png => cs_creating_classlibrary_netstandard.png} (100%) create mode 100644 preview/html/images/cs_creating_classlibrary_refresh.png create mode 100644 preview/html/images/cs_creating_classlibrary_restore_nuget.png rename preview/html/images/{cs_creating08.png => cs_creating_classlibrary_warnings.png} (100%) delete mode 100644 preview/html/images/cs_device_manager_explorer.png delete mode 100644 preview/html/images/cs_device_manager_log_add_tab.png delete mode 100644 preview/html/images/cs_device_manager_prompt.png create mode 100644 preview/html/images/cs_device_manager_start.png delete mode 100644 preview/html/images/cs_enhancing01_1.png delete mode 100644 preview/html/images/cs_enhancing02_1.png delete mode 100644 preview/html/images/cs_first01.png delete mode 100644 preview/html/images/cs_first02_1.png delete mode 100644 preview/html/images/cs_first08.png delete mode 100644 preview/html/images/cs_first09_1.png delete mode 100644 preview/html/images/cs_first_building_certificate_01.png delete mode 100644 preview/html/images/cs_first_building_certificate_02.png delete mode 100644 preview/html/images/cs_first_building_certificate_03.png create mode 100644 preview/html/images/cs_first_building_emulator_enhanced.png create mode 100644 preview/html/images/cs_first_building_emulator_mobile.png delete mode 100644 preview/html/images/cs_first_building_process.png create mode 100644 preview/html/images/cs_first_building_sdb_prompt.png delete mode 100644 preview/html/images/cs_first_building_selected_emulator.png create mode 100644 preview/html/images/cs_first_creating_menupath.png create mode 100644 preview/html/images/cs_first_creating_new_project.png create mode 100644 preview/html/images/cs_first_creating_project_wizard.png delete mode 100644 preview/html/images/cs_first_creating_project_wizard_p3.png delete mode 100644 preview/html/images/cs_first_creating_solution_explorer.png delete mode 100644 preview/html/images/cs_install01.png delete mode 100644 preview/html/images/cs_install02.png delete mode 100644 preview/html/images/cs_install03.png delete mode 100644 preview/html/images/cs_install04.png delete mode 100644 preview/html/images/cs_install05.png delete mode 100644 preview/html/images/cs_install06.png delete mode 100644 preview/html/images/cs_install07_1.png create mode 100644 preview/html/images/cs_launch_tizen_emu.png delete mode 100644 preview/html/images/cs_overview-707x282.png delete mode 100644 preview/html/images/cs_prerequiste02.png delete mode 100644 preview/html/images/demo1.jpg delete mode 100644 preview/html/images/deploy.png delete mode 100644 preview/html/images/em_skin.png delete mode 100644 preview/html/images/emulator_control_panel2-1.png delete mode 100644 preview/html/images/emulator_control_panel2.png create mode 100644 preview/html/images/emulator_control_panel_layers.png delete mode 100644 preview/html/images/emulator_manager_create.png delete mode 100644 preview/html/images/emulator_manager_template_config2.png create mode 100644 preview/html/images/emulator_tv_mobile.png delete mode 100644 preview/html/images/hardware_ram.png delete mode 100644 preview/html/images/hardware_start_instal.png delete mode 100644 preview/html/images/launchtizenemul.png create mode 100644 preview/html/images/log_view_icon.png create mode 100644 preview/html/images/log_view_icon_clear.png create mode 100644 preview/html/images/log_view_icon_export.png create mode 100644 preview/html/images/log_view_icon_lock.png create mode 100644 preview/html/images/log_view_icon_remove_tab.png delete mode 100644 preview/html/images/logviewer_default.png create mode 100644 preview/html/images/logviewer_scroll_lock.png delete mode 100644 preview/html/images/managenugetpackages.png delete mode 100644 preview/html/images/managenugetpackages2.png delete mode 100644 preview/html/images/manifest_features.png delete mode 100644 preview/html/images/manifest_privileges.png delete mode 100644 preview/html/images/manifest_text_editor.png delete mode 100644 preview/html/images/openproject.png delete mode 100644 preview/html/images/platform_mismatch_warning.png delete mode 100644 preview/html/images/pw1.png delete mode 100644 preview/html/images/release_plan_preview4_m1.png create mode 100644 preview/html/images/roadmap.png delete mode 100644 preview/html/images/solution_explorer_tizen_project2.png delete mode 100644 preview/html/images/tizenemulmanager.png delete mode 100644 preview/html/images/tizenprojectwizard.png delete mode 100644 preview/html/images/tizentvdemo1.png delete mode 100644 preview/html/images/tizentvdemo2.png delete mode 100644 preview/html/images/vs_em_2.png delete mode 100644 preview/html/images/vs_em_4.png delete mode 100644 preview/html/images/vs_em_launch.png delete mode 100644 preview/html/images/vs_em_launched.png rename preview/html/images/{vs_em_activated_debug.png => vs_emulator_activated_debug.png} (100%) create mode 100644 preview/html/images/vs_emulator_launch.png rename preview/html/images/{vs_em_1.png => vs_emulator_manager.png} (100%) rename preview/html/images/{emulator_manager_clone.png => vs_emulator_manager_clone.png} (100%) create mode 100644 preview/html/images/vs_emulator_manager_config.png rename preview/html/images/{emulator_manager_delete.png => vs_emulator_manager_delete.png} (100%) rename preview/html/images/{emulator_manager_device_template2.png => vs_emulator_manager_device_template2.png} (100%) rename preview/html/images/{emulator_manager_modify.png => vs_emulator_manager_modify.png} (100%) create mode 100644 preview/html/images/vs_emulator_manager_platform_config.png create mode 100644 preview/html/images/vs_emulator_manager_template_config2.png delete mode 100644 preview/html/images/vs_emulatormanager_2.png create mode 100644 preview/html/images/vs_install_confirm_settings.png create mode 100644 preview/html/images/vs_install_debugger.png create mode 100644 preview/html/images/vs_install_disable_hyperv.png create mode 100644 preview/html/images/vs_install_extensions_check.png create mode 100644 preview/html/images/vs_install_haxm.png create mode 100644 preview/html/images/vs_install_haxm_confirm.png create mode 100644 preview/html/images/vs_install_haxm_finished.png create mode 100644 preview/html/images/vs_install_haxm_installation.png create mode 100644 preview/html/images/vs_install_haxm_ram.png create mode 100644 preview/html/images/vs_install_installshield.png create mode 100644 preview/html/images/vs_install_installshield_finish.png create mode 100644 preview/html/images/vs_install_license_agreement.png create mode 100644 preview/html/images/vs_install_new_project.png rename preview/html/images/{cs_prerequiste01.png => vs_install_programs_features.png} (100%) create mode 100644 preview/html/images/vs_install_readme.png create mode 100644 preview/html/images/vs_install_username.png create mode 100644 preview/html/images/vs_install_vstools.png rename preview/html/images/{manifest_editing.png => vs_manifest_editing.png} (100%) create mode 100644 preview/html/images/vs_manifest_features.png rename preview/html/images/{manifest_overview.png => vs_manifest_overview.png} (100%) create mode 100644 preview/html/images/vs_manifest_privileges.png create mode 100644 preview/html/images/vs_manifest_text_editor.png rename preview/html/images/{pw2.png => vs_project_wizard_properties.png} (100%) create mode 100644 preview/html/images/vs_project_wizard_template.png delete mode 100644 preview/html/images/vstools_cert_menu.png create mode 100644 preview/html/images/xamarin_add_new_project.png create mode 100644 preview/html/images/xamarin_add_tizen_templates.png rename preview/html/images/{addedprojects.png => xamarin_added_tizen_projects.png} (100%) create mode 100644 preview/html/images/xamarin_basicanimation_mobile.png rename preview/html/images/{demo1.png => xamarin_basicanimation_tizen.png} (100%) create mode 100644 preview/html/images/xamarin_basicanimation_tizentv.png rename preview/html/images/{tizen_blank_app.png => xamarin_blank_app_tizen.png} (100%) create mode 100644 preview/html/images/xamarin_build_solution.png create mode 100644 preview/html/images/xamarin_change_nuget_version.png create mode 100644 preview/html/images/xamarin_manage_nuget.png create mode 100644 preview/html/images/xamarin_manage_packages.png create mode 100644 preview/html/images/xamarin_open_new_project.png create mode 100644 preview/html/images/xamarin_platform_mismatch.png create mode 100644 preview/html/images/xamarin_projectwizard_basicanimation.png create mode 100644 preview/html/images/xamarin_solution_explorer_tizen.png delete mode 100644 preview/html/introduction/overview.htm create mode 100644 preview/html/introduction/whats_new.htm diff --git a/preview/html/cover_page.htm b/preview/html/cover_page.htm index 18a1cc3..0df682e 100644 --- a/preview/html/cover_page.htm +++ b/preview/html/cover_page.htm @@ -12,50 +12,101 @@ - What's New + Overview - +
+ +
-

What's New

+

Overview

+

Tizen .NET is a new application framework for Tizen based on .NET.

+

Tizen .NET is an exciting new way to develop applications for the Tizen operating system, running on 50 million Samsung devices, including TVs, wearables, mobile phones, and many other IoT devices around the world. The existing Tizen frameworks are either C-based with no advantages of a managed runtime, or HTML5-based with fewer features and lower performance than the C-based solution. With Tizen .NET, you can use the C# programming language and the Common Language Infrastructure standards, and benefit from a managed runtime for faster application development and code execution that is efficient and secure.

+

To start developing Tizen applications using .NET, familiarize yourself with Visual Studio Tools for Tizen:

-
News and Updates -
  • Visual Studio 2017 Support. Visual Studio Tools for Tizen has supported Microsoft’s Visual Studio 2017 released on March 2017 since the second preview.
-
+
    +
  • Getting Started +

    Learn about installing Visual Studio Tools for Tizen, creating your first Tizen .NET application, and porting existing Xamarin.Forms applications to Tizen.

    • +
  • Visual Studio Tools for Tizen +

    Learn about the Tizen-specific Visual Studio development tools. You can create an application project, edit the code to meet your needs, and run the application on the emulator or a target device.

    • +
+For more information on the latest new features and the release plan roadmap, see What's New and Roadmap. + +

Managed Runtime Advantages

+ +

A managed runtime offers the following advantages to your application development:

+ +
    +
  • Faster development +

    Application development is accelerated since the managed runtime handles many functions that otherwise have to be coded into the application. The Tizen Native API and Tizen Web API already provide this benefit.

    • +
  • Safer code +

    Managed runtimes can handle, for example, bound checking, type safety, garbage collection, memory protection services, and objects being invoked directly. The Tizen Web API already provides some of these benefits, but not type safety, as JavaScript is not a strongly typed language.

    • +
  • Lower deployment costs +

    Component-based architecture makes it easier and faster to deploy applications in an enterprise environment characterized by multiple platforms, devices, and legacy systems.

    • +
  • Better quality software +

    Managed runtimes free you to focus on the business logic and code specific to the application, while reducing the number of coding errors.

    • +
  • Cross-platform support +

    The managed code is portable. Tizen .NET applications can have large portions of their logic applied to other systems supported by the .NET Core and Xamarin.Forms portions of the runtime.

    • +
+ +

Tizen .NET Features and Components

+ +

Tizen .NET enables you to build .NET applications with Xamarin.Forms and the Tizen .NET framework. Xamarin.Forms allows you to easily create a user interface, and the TizenFX API provides numerous interfaces to much of the hardware that is found in modern TV, mobile, wearable, and IoT devices.

+ +

Figure: Tizen .NET architecture

+

Tizen .NET architecture

+ +

Tizen .NET consists of the following main components:

-

The third preview of Tizen .NET, an application framework for Tizen based on .NET, is now available. The third preview stepped forward. Key new features are as follows:

    -
  • New Tools. Device Manager, Log Viewer, and API and Privilege checker were introduced with Visual Studio Tools for Tizen. Tizen-specific tools were added to further improve your productivity.
    • - -
  • Project Wizard. Visual Studio Tools for Tizen provide a number of different options to build applications. For instance, you can build an application that runs on a single device type or an application that runs on multiple device types. You can build an application that runs on Tizen only or an application that runs on multiple platforms. The project wizard helps you to select the right project type with step-by-step guides.
    • - -
  • Self-contained Application. Application developers can create and install them to target devices or emulators without pre-installed .NET runtime.
    • - -
  • More Tizen platform-specific API. The third preview significantly increases the number of Tizen-specific API available for .NET developers. Following packages have become newly available. For the full pakage list, see Tizen Platform-Specific API. -
      -
    • Thumbnail Utility (capi-media-thumbnail-util)
      • -
    • Wave Player (capi-media-wav-player)
      • -
    • Tone Player (capi-media-tone-player)
      • -
    • Media Stream Recording (capi-media-streamrecorder)
      • -
    • Media Metadata Editor (capi-media-metadata-editor)
      • -
    • Screen Mirroring (capi-media-screen-mirroring)
      • -
    • Camera (capi-media-camera)
      • -
    • Data Control (capi-data-control)
      • -
    • Widget Viewer (widget_viewer_evas)
      • -
    • FIDO (fido-client)
      • -
    • Message (capi-messaing-messages)
      • -
    • Email (capi-messaing-email)
      • -
    • Input Method Manager (capi-ui-inputmethod-manager)
      • -
    • Bluetooth (capi-network-bluetooth)
      • -
    • Alarm (capi-appfw-alarm)
      • -
    • Maps (capi-maps-service)
      • -
    • -
+
  • .NET Core +

    .NET Core is a general-purpose development platform maintained by Microsoft and the .NET community on GitHub. It is cross-platform, supporting Windows®, macOS, and Linux, and can be used in device, cloud, and embedded/IoT scenarios.

    + +

    .NET Core is composed of the following parts:

    + +
      +
    • The .NET runtime, which provides basic services, such as a type system, assembly loading, a garbage collector, and native interop.
      • +
    • A set of framework libraries, which provide primitive data types, application composition types, and fundamental utilities.
      • +
    • A set of SDK tools and language compilers that enable the base developer experience, available in the .NET Core SDK.
      • +
    • The dotnet application host, which is used to launch .NET Core applications. It selects and hosts the runtime, provides an assembly loading policy, and launches the application. The application host is also used to launch SDK tools similarly.
      • +
    +
    • +
  • Xamarin.Forms as a UI framework +

    Xamarin.Forms is a cross-platform UI toolkit that allows you to efficiently create native user interface layouts that can be shared across iOS, Android™, Windows Phone, and Universal Windows Platform applications.

    +
    • +
  • TizenFX API +

    Tizen .NET supports C# APIs, which expose Tizen-specific features:

    +
      +
    • Tizen.Account provides CRUD (Create, Read, Update, Delete) account management functionality and the OAuth Core RFC 6749 protocol.
      • +
    • Tizen.Applications provides the Tizen application framework, including application state change events, inter-application messaging, and notification services.
      • +
    • Tizen.Common provides predefined color names.
      • +
    • Tizen.Content provides content management services, such as file and media downloading, storing and indexing audio and video content, and associating content types with helper applications.
      • +
    • Tizen.Location manages geographical location services and geofencing.
      • +
    • Tizen.Maps provides methods to create map-aware applications.
      • +
    • Tizen.Messaging provides methods to receive push notifications.
      • +
    • Tizen.Multimedia interacts with media services, including audio playback, recording, and device policy.
      • +
    • Tizen.Network controls connectivity devices and retrieves network information.
      • +
    • Tizen.Security provides access to secure storage for passwords, keys, certificates, and other sensitive data.
      • +
    • Tizen.Sensor provides sensor types and sensor information.
      • +
    • Tizen.System provides device-specific services, including status, system information and settings, feedback, and sensor control and access.
      • +
    • Tizen.Telephony provides call, modem, network, and SIM information.
      • +
    • Tizen.Uix provides methods to recognize speech, synthesize voice from text, and play synthesized sound data.
      • +
    • Tizen.Log provides methods to print log messages to the Tizen logging system.
      • +
    • Tizen.Tracer provides methods to write trace messages to the system trace buffer.
      • +
    +
    • + diff --git a/preview/html/getting_started/cross_platform_project.htm b/preview/html/getting_started/cross_platform_project.htm new file mode 100644 index 0000000..ae315dc --- /dev/null +++ b/preview/html/getting_started/cross_platform_project.htm @@ -0,0 +1,83 @@ + + + + + + + + + + + + + + + Creating Tizen Projects as Cross-platform Solutions + + + + +
    +
    + +
    + +

    Creating Tizen Projects as Cross-platform Solutions

    + +

    The Xamarin cross-platform template consists of a shared PCL (Portable Class Library) and multiple platform-dependent application projects. If you create your Tizen project as a cross-platform solution, you can easily add other platform-dependent project versions, such as iOS and Android™, to the same solution later.

    + +

    To create a Tizen project as a cross-platform solution:

    + +
      +
    1. In the Visual Studio menu, go to File > New > Project.
      2. +
    2. Select Visual C# > Cross-Platform > Blank App (Xamarin.Forms Portable). +

      Select a cross-platform template

      +
      3. +
    3. In the Solution Explorer view, right-click the new solution and select Add > New Project.
      4. +
    4. Select Tizen > Blank App (Tizen Xamarin.Forms Portable) and click OK. +

      +
      5. +
    5. In the Tizen Project Wizard, define the Tizen application package name and profile, and click OK. +

      The Solution Explorer view shows the 1 or 2 Tizen projects (depending on the selected profiles) that are added to the existing cross-platform Xamarin.Forms solution. The Tizen project is set as the startup project.

      +

      +
      6. +
    + +

    Problems with NuGet Package Versions

    + +

    Since Tizen projects have dependencies with the Xamarin.Forms NuGet package version, you need to install the Xamarin.Forms NuGet package that has the same version as Xamarin.Forms.Platform.Tizen. Mismatched NuGet versions can cause build or packaging problems.

    + +

    Figure: Mismatched NuGet version warning

    +

    + +

    To install the proper Xamarin.Forms NuGet package, right-click the solution in the Solution Explorer view and select Manage NuGet Packages for Solution.

    + +

    Figure: Installing the correct NuGet package

    +

    + + + + + +
    + +Go to top + + + + + + + + \ No newline at end of file diff --git a/preview/html/getting_started/first_app.htm b/preview/html/getting_started/first_app.htm index b4af295..58af2b9 100644 --- a/preview/html/getting_started/first_app.htm +++ b/preview/html/getting_started/first_app.htm @@ -18,17 +18,17 @@
    + @@ -38,271 +38,200 @@

    Creating Your First Tizen .NET Application

    -

    The Tizen .NET framework allows you to efficiently and easily create beautiful applications for Tizen. A great way to experience this yourself is to follow the steps to your first Tizen .NET application. If you have to set up your development environment, please go to set up the development environment.

    +

    The Tizen .NET framework allows you to easily and efficiently create applications for Tizen. Study the following instructions to help familiarize yourself with the Tizen .NET application development process. With the instructions, you can create and run a basic .NET application, which displays some text on the screen with no user interaction.

    -

    To get started,

    +
      +
    1. Before you get started with developing Tizen applications, set up the development environment. +
      2. +
    2. Create a project using Visual Studio. +

      This step shows how you can use a predesigned project template that creates all the basic files and folders required for your project.

      3. +
    3. Build the application. +

      After you have implemented code for the features you want, this step shows how you can build the application to validate and compile the code.

      4. +
    4. Deploy and run the application. +

      This step shows how you can deploy and run the application on the emulator or a real target device.

      5. +
    5. Enhance the application. +

      This step shows how you can enhance your application by creating a UI and making small alterations to it to improve the usability of the application.

      6. +
    - +

    Creating a Project

    -

    After completing the above steps, you will have created your first application, and you can move on to Enhancing your application.

    +

    The following example shows you how to create and configure a basic Tizen .NET application project in Visual Studio. An application project contains all the files that make up an application.

    +

    The following figures illustrate the application to be created. The application screen displays the Welcome to Xamarin Forms! text and no user interaction is provided.

    -

    Creating a Project

    +

    Figure: Application running on the mobile emulator

    -

    To build a Tizen .NET application, you must follow these general steps:

    +

    Application running on the mobile emulator

    -
      -
    1. Create a project.
      2. -
    2. Design the user interface for the application.
      3. -
    3. Write code to implement the logic of the application.
      4. -
    4. Build and deploy the application.
      5. -
    +

    Figure: Application running on the TV emulator

    -

    You can perform all of these steps in the IDE. The Tizen .NET preview works in Microsoft's Visual Studio (2015). After making sure the development environment is properly set up, you can create a new Tizen .NET project:

    +

    Application running on the TV emulator

    + +

    To create a new Tizen .NET project:

    1. Launch Visual Studio.
      2. -
    2. To create a new project, select File > New > Project. -

      Create a new project

      -
      3. -
    3. In the New Project window, select Tizen in the Templates tree on the left, and select Blank App (Tizen Xamarin.Forms Portable). Visual Studio defines a name, location and solution name for you, but you can modify the values: at least set the name to something meaningful. -

      Select a template

      - Once you are happy with the name and location, click OK. - -

      +
    4. In the Visual Studio menu, select File > New > Project. +

      Create a new project

      +

      The New Project dialog opens.

      +
      5. +
    5. Select Templates > Visual C# > Tizen, and select the Blank App (Tizen Xamarin.Forms Portable) template. +

      Define the project properties and click OK. You can enter the name, location, solution, and solution name.

      +

      Select a template

      +

      The Tizen Project Wizard opens.

      6. +
    6. Define the package name and the profiles to add to your solution. Click OK. +

      Tizen Project Wizard

      +

      If you select the Common profile, you cannot select Mobile or TV.

    -

    Tizen Project Wizard window is shown as next step. You can define the package name and define which profiles are added in your solution. Click OK.  If you select Common profile, Mobile and TV profile cannot be selected.

    - -

    A solution with 2 or 3 projects is created:

    +

    A solution with 2 or 3 projects is created and shown in the Solution Explorer view:

      -
    • One project is named <projectname> (Portable) and contains the Xamarin.Forms code, which can be shared across platforms.
      • -
    • If you selected the common profile in the Tizen Project Wizard, a common project is added with <projectname>.Tizen suffix and contains the code to instantiate your common application within the Tizen framework.
      • -
    • If you selected the mobile profile in the Tizen Project Wizard, a mobile project is added with <projectname>.TizenMobile suffix and contains the code to instantiate your mobile application within the Tizen framework.
      • -
    • If you selected the TV profile in the Tizen Project Wizard, a TV project is added with <projectname>.TizenTV suffix and contains the code to instantiate your TV application within the Tizen framework.
      • +
    • The <projectname> (Portable) project contains the Xamarin.Forms code shared across platforms.
      • +
    • If you select the common profile in the Tizen Project Wizard, a common project titled <projectname>.Tizen is added. It contains code to instantiate your common application within the Tizen framework.
      • +
    • If you select the mobile profile in the Tizen Project Wizard, a mobile project titled <projectname>.TizenMobile is added. It contains code to instantiate your mobile application within the Tizen framework.
      • +
    • If you select the TV profile in the Tizen Project Wizard, a TV project titled <projectname>.TizenTV is added. It contains code to instantiate your TV application within the Tizen framework.
    +

    Figure: Project with mobile and TV profiles

    +

    Project with mobile and TV profiles

    +

    If you are already familiar with Xamarin.Forms, this project has the same structure as a Xamarin.Forms portable application. The "Portable" project is the portable class library and the others are the platform-specific projects; however, in the Tizen .NET preview, only the Tizen platform-specific project is generated.

    -

    If you are already familiar with Xamarin.Forms, this project has exactly the same structure as a Xamarin.Forms portable application, with the "Portable" project being the portable class library and the others being the platform-specific projects; however, for the Tizen .NET preview, only the Tizen platform-specific project is generated.

    - -

    +

    The .cs file in the portable project already contains simple Xamarin.Forms code that makes a basic UI.

    -

    The .cs file in the portable project already contains simple Xamarin.Forms code, which makes a basic UI. Therefore, you can now build and run your application.

    +

    Restoring NuGet Packages When Using Class Libraries

    +

    If you add a Class Library (Tizen) to your solution in Visual Studio, the editing window for the class library CS files shows red wavy lines.

    +

    Red wavy lines

    -

    When you are done running your first application, you can enhance it further by reading a brief overview of what the code generated by the template is doing, and learning about a few more concepts to add to your application appeal.

    - -

    Adding a Class Library and Restoring NuGet Manually

    - -

    To add a class library and restore NuGet manually:

    +

    To avoid the red lines, you must restore NuGet packages manually by adding the .NETStandard.Library to the class library references:

      -
    1. If you add a Class Library (Tizen) in Visual Studio, the editing window shows red wavy lines. -

      Red wavy lines

      -
      2. -
    2. Right-click the solution item in the Solution Explorer view and click Restore NuGet Packages. -

      Restore NuGet packages

      - -

      Wait for the NuGet restoring to complete. Click the ClassLibrary project, and then click Refresh when the Refresh button appears.

      - -

      Refresh

      -
      3. -
    3. The .NETStandard.Library shows up and the code looks clean. -

      .NETStandard.Library

      +
    4. Right-click the solution in the Solution Explorer view and select Restore NuGet Packages. +

      Restore NuGet packages

      5. +
    5. Wait for NuGet package restoration to complete. +

      In the Solution Explorer view, select the class library project, and when the Refresh button appears in the view toolbar, click it.

      +

      Refresh

      +

      The .NETStandard.Library is added to the references, and the red lines in the code disappear.

      +

      .NETStandard.Library

    -

    The following figure shows warning messages that you can see in the Error List window when building the project. These can occur because the application is based on the Microsoft.NETCore.App and the Class library is based on NETStandard.Library, and the difference makes Visual Studio 2015 or 2017 show a warning. However, it is OK to run the project, because the Microsoft.NETCore.App includes the NETStandard.Library set.

    +

    The following figure shows warning messages that can appear in the Error List window when building the project. These can occur because the application is based on Microsoft.NETCore.App but the class library is based on .NETStandard.Library, and the difference makes Visual Studio 2015 or 2017 show a warning. However, running the project is unaffected, because the Microsoft.NETCore.App includes the .NETStandard.Library set.

    Figure: Warning messages

    +

    Warning messages

    -

    Warning messages

    - -

     

    - -

    Adding a Tizen Project to an Existing Xamarin Cross Platform Project

    - -

    The Xamarin cross platform template consist of a shared PCL (Portable Class Library) and multiple platform dependent application projects for IOS and Android.

    - -

    To add a new Tizen project:

    - -
      -
    1. In the Visual Studio menu, go to File > New > Project to open the New Project dialog.
      2. -
    2. Select Cross-Platform and Blank App (Xamarin.Forms Portable). -

      -
      3. -
    3. Right-click the solution item in the Solution Explorer view and click Add > New Project.
      4. -
    4. Select Tizen Blank App (Tizen Xamarin.Forms Portable) and click OK. -

      -
      5. -
    5. Select the Tizen application’s package name and profile in the Tizen project wizard. -

      -
      6. -
    6. The Solution Explorer shows the 2 Tizen projects are added in your existing Xamarin.Forms solution. The Tizen project is set as a startup project. -

      -
      7. -
    -
    NoteSince the Tizen projects have dependencies with the Xamarin.Forms NuGet package version, you need to install the Xamarin.Forms NuGet package that has the same version as Xamarin.Forms.Platform.Tizen. Mismatching NuGet versions can cause build or packaging problems. To install the proper Xamarin.Forms NuGet package, right-click the solution item in the Solution Explorer view and select Manage NuGet Packages for Solution.
    +

    Building Your Application

    -

    Figure: Mismatched NuGet version warning

    +

    After you have created the application project, you can implement the required features. In this example, only the default features from the project template are used, and no code changes are required.

    -

    +

    When your application code is ready, build the application. The building process performs a validation check and compiles your files. You must sign the application package with an author certificate when building the application. If you have not yet registered a Tizen certificate in Visual Studio, see Certificate Manager.

    -

     

    +

    There are 2 different ways to build the application:

    +
      +
    • In the Visual Studio menu, select Build > Build Solution.
      • +
    • In the Solution Explorer view, right-click the solution name and select Build.
      • +
    +

    Tizen .NET applications are always deployed as installed packages. The package files have the .tpk file extension, and the package generation is controlled by the manifest file. The Visual Studio template generates the manifest file (tizen-manifest.xml) to the top level of the <projectname>.Tizen project (if you create a project with both mobile and TV profiles, a separate manifest file is generated for each profile).

    -

    Figure: Installing the correct NuGet package

    +

    For this example application, the default manifest is sufficient. If you want to make any changes in the application, such as changing the application icon or installing resources that are used by the application at runtime, see Packaging Your Application.

    +

    After you have built the application, deploy and run it.

    -

    -

    Building and Running Your Application

    +

    Deploying and Running Your Application

    -

    When you have created your first project, you can build and run it:

    +

    To run the application, you must first deploy it to the target: either a device or an emulator. Deploying means transferring the package file (.tpk) to the target and invoking the Tizen package manager to install it.

    +

    To deploy and run the application on the emulator:

      -
    1. Register an author certificate.
      2. -
    2. Build the solution.
      3. -
    3. Deploy the application to a target.
      4. -
    4. Run the application.
      5. -
    - -

    1 Registering an Author Certificate

    - -

    If you already have registered a certificate in Visual Studio or can use a default Tizen certificate, you can skip this step.

    - -

    After installing the Visual Studio plugin, and before making Tizen package, it is useful to set up a signing certificate.

    - -

    You have 3 options:

    - -
      -
    • Use a default Tizen certificate -

      If you do not need to upload your application to Tizen Application store, you can use a default certificate and deploy your application in the Tizen Emulator too. You can check this in Menu > Tools > Options > Tizen > Certification. If you do not check the Sign the .tpk  file using the following option box, your application is made with a default certificate.

      - -

      Figure: Tizen default certificate registration

      - -

      -
      • -
    • Use a Tizen certificate profile -

      If you have used Tizen Studio and have already generated a certificate profile using the Tizen Certificate Manager (Menu > Tools > Tizen > Tizen Certificate Manager, the usage is added in tools menu too), the profile information can be read in %ToolPath/Tizen/SDK/user-data/profile.

      - -

      Figure: Tizen certificate profile registration

      - -

      +
    • +

      In the Visual Studio menu, select Tools > Tizen > Tizen Emulator Manager.

      +

      Alternatively, you can launch the Tizen Emulator Manager by clicking Launch Tizen Emulator in the Visual Studio toolbar.

      +

      Launch Tizen Emulator

    • -

      Use your own certificates.

      - -

      If you already have author and distributor certificates, you can import them in Menu > Tools > Options > Tizen > Certification.

      - -

      Figure: Tizen certificates registration

      +

      In the Emulator Manager, select an emulator from the list and click Launch.

      If no applicable emulator instance exists, create one.

      +

      Tizen Emulator Manager

      • +
    • +

      Once you launch an emulator instance, you can deploy the application by clicking the emulator instance in the Visual Studio toolbar.

      +

      You can change the deployment target in the Visual Studio toolbar by selecting the target from the drop-down list.

      +

      Tizen Emulator Manager

      -

      +

      Select deployment target

      • -
    - -

     

    - -

    2 Building the Solution

    - -

    To build the solution, go to Build > Build Solution in the main Visual Studio menu (you can also right-click the solution title in the Solution Explorer window and select Build). If the build process works all the way through to the end, the final part of the build output window shows something similar to the following figure - indicating that a .tpk package was built.

    - -

    Figure: Building process output

    +
  • If deployment is successful, the application icon is visible on the emulator or device screen. Click the icon to launch the application. The following figures show the launched application on the mobile and TV emulator. -

    - -

    Tizen .NET applications are always deployed as installed packages. The package files take the .tpk suffix, and the package generation is controlled by the manifest file. The Visual Studio template generates a package manifest, which is named tizen-manifest.xml and placed at the top level of the .Tizen project. The default manifest is sufficient to build these example applications without modification. If you need to make any changes, such as changing the icon displayed when the application is installed (it defaults to the Tizen logo), or installing resources that are used by the application at runtime, see Packaging Your Tizen .NET Application.

    - -

    3 Deploying the Application

    - -

    To run the application, you must first deploy it to the target: either a device or an emulator. Deploying means transfering the .tpk (package file) to the target and invoking the Tizen package manager to install it; this usually happens in a single command.

    - -

    To deploy to a target:

    +

    Application running on the mobile emulator

    +

    Application running on the TV emulator

    • + +

    Visual Studio uses the Smart Development Bridge (SDB) to communicate with the target device or emulator. If you encounter problems with detecting the device in Visual Studio, you can check the SDB manually:

      -
    1. The target can be a development device (connected to a USB port), or the Tizen emulator. Launch the emulator from the Visual Studio menu by going to Menu > Tools > Tizen > Tizen Emulator Manager. - -

      -
      2. -
    2. You can create emulators as shown above by clicking Create. For more information on creating emulator instances, see Emulator Manager.
      3. -
    3. The emulator launches after a small delay. When it is up and running, the display inside Visual Studio changes a bit, and the green debug button updates to show the running emulator. -

      -
      4. +
    4. In the Visual Studio menu, select Tools > Tizen > Tizen Sdb Command Prompt.
      5. +
    5. At the command prompt, enter sdb devices. +

      Emulator detection

      +

      A list of the attached devices appears.

      +
    -

    Communication with the device happens through the SDB program (Smart Development Bridge). Visual Studio uses this program behind the scenes, so you normally do not have to use it directly, but in case there are problems, you can run the SDB manually to check that it actually finds the device.
    -To check the SDB, click Menu > Tools > Tizen > Tizen Sdb Command Prompt, and type sdb devices.

    - -

    The following figure shows an example of a successful emulator detection.

    - -

    Figure: Emulator detection

    +

    If problems occur during deployment, try to install the application manually using the SDB:

    -

    Emulator detection

    - -

    If you want to change the target to be deployed, you can change it in the Visual Studio configuration manager as shown in the following figure. After selecting the right target in the combo box, go to debugging or start without debugging.

    - -

    Figure: Emulator list

    - -

    - -

    4 Running the Application

    +
      +
    • Mobile application: +
      +$ sdb install <path-to-package>/XamarinApplication1.TizenMobile.tpk
+
      +
      • +
    • TV application: +
      +$ sdb install <path-to-package>/XamarinApplication1.TizenTV.tpk
+
      +
      • +
    -

    After the deployment, you can launch the application. If the deployment was successful, the application icon is visible on the device screen. Click the icon to launch the application. The following figure shows the launched application (as seen on the emulator).

    -

    Figure: Application running on the mobile emulator

    +

    Enhancing Your Application

    -

    Application running

    +

    Xamarin.Forms provides a way to build portable applications which run in a native way. It provides a set of controls for building a user interface, as well as generates code which adapts the user interface code to use the native facilities of the supported platforms. The following is a brief introduction to the Xamarin.Forms controls, and how to use them to build on the application you have just created.

    -

    Figure: Application running on the TV emulator

    +

    Understanding the Source Code

    -

    +

    The C# code from your first application displays a label centered on the screen, containing the Welcome to Xamarin Forms! text. This XamarinApplication1 application created from the template is set up and ready to be built and run by Visual Studio right after you create it, as described above.

    -

    If the deployment had problems, try to use the SDB to install the application:

    +

    The Xamarin.Forms controls used to create the user interface of a Tizen .NET application can be broadly categorized into 4 groups:

    -
    -$ sdb install <path-to-package>/XamarinApplication1.TizenMobile.tpk
    +
      +
    • Pages represent screens within an application. The UI of an application is built from one or more pages and with a navigation mechanism, if needed. The navigation scheme is specified by the INavigation interface. Many pages are of the ContentPage type, which describes the view of a single screen.
      • +
    • Layouts are containers used to compose views into logical structures. Some available types are absolute, grid, relative, and stack layouts; each provide mechanisms, such as orientation, spacing, and padding, to control the layout. The StackLayout class is a basic layout where you can simply stack controls on top of, or side-by-side, one another. Layouts can also be bundled with and nested into each other.
      • +
    • Views are the controls displayed on the user interface, such as labels, buttons, and text entry boxes.
      • +
    • Cells are specialized elements used for items in tables and lists, which help describe how the items must be rendered.
      • +
    -
    -

    or

    +

    The following shows the portable code portion of the Tizen Xamarin.Forms Portable project XamarinApplication1.cs file, generated by the template:

    -
    -$ sdb install <path-to-package>/XamarinApplication1.TizenTV.tpk
    - -

    If the installation succeeds, the application icon shows up on the emulator or device screen, and you can click it to launch the application.

    -
    -
    - -

    Enhancing Your Tizen .NET Application

    - -

    The C# code from your first application displays a label centered on the screen, containing the Welcome to Xamarin Forms! text. The Hello application (created from the template) is set up and ready to be built and run by Visual Studio right after you create it, as shown in the preceding sections of this topic.

    - -

    Xamarin.Forms provides a way to build portable applications which run in a native way: it provides a set of controls to help build a user interface, as well as generating code which adapts the user interface code to use the native facilities of the supported platforms. The following information just scratches the surface of these controls, but it is enough to give you an idea of how to build on the initial application.

    - -

    The following example shows the portable code portion of the Tizen Xamarin.Forms Portable project XamarinApplication1.cs file, generated by the template:

    - -
     using System;
 using System.Collections.Generic;
 using System.Linq;
 using System.Text;
 using Xamarin.Forms;
- 
+
 namespace XamarinApplication1
 {
     public class App : Application
     {
         public App()
         {
-            // Root page of your application
+            /// Root page of your application
             MainPage = new ContentPage
             {
                 Content = new StackLayout
                 {
                     VerticalOptions = LayoutOptions.Center,
-                    Children = {
-                        new Label {
+                    Children =
+                    {
+                        new Label
+                        {
                             HorizontalTextAlignment = TextAlignment.Center,
                             Text = "Welcome to Xamarin Forms!"
                         }
@@ -312,53 +241,38 @@ namespace XamarinApplication1
         }
         protected override void OnStart()
         {
-            // Handle when your app starts
+            /// Handle when your app starts
         }
         protected override void OnSleep()
         {
-            // Handle when your app sleeps
+            /// Handle when your app sleeps
         }
         protected override void OnResume()
         {
-            // Handle when your app resumes
+            /// Handle when your app resumes
         }
     }
 }
    -

     

    - -

    The Xamarin.Forms controls used to create the user interface of a Tizen .NET application can be roughly categorized into 4 groups:

    +

    This application is constructed with the following Xamarin.Forms controls:

      -
    • Pages represent screens within an application. The UI of an application is built from one or more pages and with a navigation mechanism, if needed. The navigation scheme is specified by the INavigation interface. Many pages are of the ContentPage type, which describes the view of a single screen.
      • -
    • Layouts are containers used to compose views into logical structures. Some available types are absolute, grid, relative, and stack layouts; each provide mechanisms, such as orientation, spacing, and padding, to control the layout. The StackLayout class is a basic layout where you just stack controls on top of one another (or side-by-side). Layouts can be bundled and nested in each other.
      • -
    • Views are the controls displayed on the user interface, such as labels, buttons, and text entry boxes.
      • -
    • Cells are specialized elements used for items in tables and lists, which help describe how the items must be rendered.
      • -
    - -

    You can read all about how Xamarin.Forms works at the Xamarin Developer Center. In addition, there is a comprehensive book about Xamarin.Forms from Microsoft Press, which is available as a free download. This topic does not duplicate the definitive documentation, only introduces the controls in use in the example above, and a bit more.

    - -

    The Xamarin.Forms controls in play in this application:

    - -
      -
    1. The App class is declared, deriving from the Application class, which is the Xamarin.Forms class that represents a cross-platform mobile application.
      2. -
    2. The App class constructor creates a ContentPage instance (line 14) where you set up the view to display.
      3. -
    3. You assign what you want to display to the Content property of that class. -

      In this case, the content is a container, specifically a StackLayout instance (line 16). This is just a layout that positions its child elements in a single vertical (by default) or horizontal line - thus the name: the elements are "stacked" on top of one another.

      +
    4. The App class is declared, deriving from the Xamarin.Forms.Application class, which represents a cross-platform mobile application.
      5. +
    5. The App class constructor creates a ContentPage instance where you set up the view to display.
      6. +
    6. You assign what you want to display to the Content property of the ContentPage class. +

      In this case, the content is a container, specifically a StackLayout instance. This layout positions ("stacks") its child elements in a single vertical (default) or horizontal line.

      7. -
    7. You set up the child elements by adding to the Children property (line 19) - in this case just a single Label instance (line 20), whose Text property you set to the message you want to display.
      8. -
    8. Some lines (18 and 21) implement some control over the layout.
      9. -
    9. Besides the App constructor, the rest of the file is just boilerplate - event handlers from the Application class that can be filled in if the application needs code to handle application state changes.
      10. -
    - -

    That is a very brief view without any real details; the Xamarin.Forms documentation goes into much more detail on each of the classes, interfaces, properties, and attributes involved and is a good place to do further research.

    +
  • Child elements are added to the Children property. In this example, a single Label instance is added, whose Text property is the message you want to display.
    • +
  • Some lines implement control over the layout. For example, the stack is set to vertically center the child elements, and the label is set to use center-alignment for its text.
    • +
  • Besides the App constructor, the rest of the file is just a template. Event handlers from the Application class can be filled in if the application needs to handle application state changes.
    • + -

    The code does not show the instantiation of the App class. Since application launching is platform-specific, the launching part, including the instatiation of the App class and the declaration of the Main() method (required as the entry point of every C# program), happens in the .Tizen project, in the matching file there. For example, if the file you are looking at in the portable project is named XamarinApplication1.TizenMobile.cs or  XamarinApplication1.TizenTV.cs, the platform-specific file is XamarinApplication1.TizenMobile.cs or   XamarinApplication1.TizenTV.cs  in the .Tizen project. For an application like this one, which just uses Xamarin.Forms controls, the generated code at the .Tizen part of the project contains everything needed, and you do not need to make any modifications. The following example shows the content of the XamarinApplication1.TizenMobile.cs or  XamarinApplication1.TizenTV.cs file:

    +

    The code does not show the instantiation of the App class. Since application launching is platform-specific, the launching part, including the instantiation of the App class and the declaration of the Main() function (required as the entry point of every C# program), happens in the <projectname>.Tizen project, in the matching file there. For example, if the file you are looking at in the portable project is named <projectname>.cs, the platform-specific file in the <projectname>.Tizen project is <projectname>.TizenMobile.cs or <projectname>.TizenTV.cs. For an application like this one, which uses only Xamarin.Forms controls, the generated code at the <projectname>.Tizen part of the project contains everything needed, and you do not need to make any modifications. The following example shows the content of the <projectname>.TizenMobile.cs file:

    -
    +
     using System;
- 
+
 namespace XamarinApplication1.TizenMobile
 {
     class Program : global::Xamarin.Forms.Platform.TizenMobile.FormsApplication
@@ -378,72 +292,72 @@ namespace XamarinApplication1.TizenMobile
 }
 
    
 
-
    Defining a Button
    
+
    Adding a Button and Second Label
    
+
+
    To modify and build a new application, create a new project. The default name for the second project is XamarinApplication2 (as shown in the namespace declaration in the following step list), but of course you can name it anything you want.
    
+
+
    The basic template uses a label which displays text in an area of the screen. The properties inherited from the base classes of Label give control over the display: font attributes, families, and sizes, as well as layout options. Modify the application by adding a button control. It is similar to the label, but is specifically designed to react to click events. As a result, the Button class defines the Clicked event, which tells the application what to do when the click event takes place.
    
+
+
    In order to do something visible on the screen to show that you have received the click event, define another label. Give the new label a value to be displayed in the initial state, and make the button click event handler update the text and button color once the click event triggers.
    
 
-
    The basic template uses a label, which displays text in an area of the screen. The properties inherited from the base classes of Label give lots of control over the display: font attributes, families, and sizes as well as layout options. A button control is relatively similar, but is specifically designed to react to click events. As a result, the Button class defines an event called Clicked, which tells the application what to do when the click event takes place. To instantiate a generic button:
    
 
-
    +
    To modify the application by adding a button and label:
    
+
      
+    
    1. Instantiate a generic button:
+	
        
+		
      1. Add the OnButtonClicked event handler to the button's Clicked event:
+
         Button button = new Button
 {
     Text = "Click here!"
 };
 button.Clicked += OnButtonClicked;
-
        
-
-
        The above example adds the OnButtonClicked method to the button's Clicked event, and you need to define that method. When an event triggers, 2 parameters are delivered to any handler set up to watch it. The first parameter is an object representing the control that triggered the event and the second parameter is the event data appropriate to the event type:
        
-
-
        +
        2. 
+
      2. Define the OnButtonClicked event handler.
+
        When an event triggers, 2 parameters are delivered to any handler set up to watch it. The first parameter is an object representing the control that triggered the event and the second parameter is the event data appropriate to the event type:
        
+
         void OnButtonClicked(object sender, EventArgs e)
 {
-    // Do something with the click event
+    /// Do something with the click event
 }
 
        
-
-
        Adding a Label to be Updated When the Button is Clicked
        
-
-
        To build the modified application, create a new project. The default name for the second project is XamarinApplication2 (as shown in the namespace declaration in the following code example), but of course you can name it anything you want.
        
-
-
        In order to do something visible on the screen to show that you actually got the click event, define another label. Give the label a value (by setting the Text property) to be displayed in the initial state, and have the event handler update the Text property (and color) once the click event triggers:
        
-
-
          
-	
        1. Since the the click event triggers outside the class constructor, you must declare the label and a click counter up at the class level (lines 11-12).
          2. 
-	
        2. The button is instantiated (line 16) as is the new label (line 23): these 2 are then included as children of the StackLayout (lines 41-42), so they are stacked below the label from the initial program.
          3. 
-	
        3. In this example, the initial text of the first label is changed to "Welcome to Tizen!".
          4. 
-	
        4. The event handler is added (lines 47-52). In it, increment the click counter, build a string showing how many times the button has been clicked, and set the Text property of the label to that string. Just for visual effect, also set the color of the label to something different than the initial color (which was set at line 26).
          5. 
-
        
-
-
        The following example shows the modified code:
        
-
-
        +    
        3. 
+	
      2. 
+	
    2. Instantiate a new label and define its property changes in the click event handler:
+	
        
+		
      1. Since the click event triggers outside the class constructor, declare the label and a click counter at the class level:
+
         using System;
 using System.Collections.Generic;
 using System.Linq;
 using System.Text;
 using Xamarin.Forms;
- 
+
 namespace XamarinApplication2
 {
     public class App : Application
     {
-        Label label;
-        int clicks = 0;
- 
+        Label label;
+        int clicks = 0;
+
        2. 
+		
      2. Instantiate the button and label, and include them later as children of the StackLayout, so they are stacked below the label from the initial program. Give the new label a value to be displayed in the initial state by setting the Text property.
+
                 public App()
         {
-            Button button = new Button
-            {
-                Text = "Click here!",
-                BackgroundColor = Color.Red,
-                HorizontalOptions = LayoutOptions.Center,
-            };
-            button.Clicked += OnButtonClicked;
-            label = new Label
-            {
-                Text = "unclicked",
-                HorizontalOptions = LayoutOptions.Center,
-            };
- 
-            // The root page of your application
+            Button button = new Button
+            {
+                Text = "Click here!",
+                BackgroundColor = Color.Red,
+                HorizontalOptions = LayoutOptions.Center,
+            };
+            button.Clicked += OnButtonClicked;
+            label = new Label
+            {
+                Text = "unclicked",
+                HorizontalOptions = LayoutOptions.Center,
+            };
+
+            /// The root page of your application
             MainPage = new ContentPage
             {
                 Content = new StackLayout
@@ -454,73 +368,91 @@ namespace XamarinApplication2
                             HorizontalTextAlignment = TextAlignment.Center,
                             Text = "Welcome to Tizen!"
                         },
-                        button,
-                        label,
+                        button,
+                        label,
                     }
                 }
             };
         }
+
        3. 
+		
      3. Change the initial text of the first label to "Welcome to Tizen":
+
        +                Content = new StackLayout
+                {
+                    VerticalOptions = LayoutOptions.Center,
+                    Children = {
+                        new Label {
+                            HorizontalTextAlignment = TextAlignment.Center,
+                            Text = "Welcome to Tizen!"
+                        },
+                        button,
+                        label,
+                    }
+                }
+
        4. 
+		
      4. Modify the click event handler content.
+		
        Increment the click counter, build a string showing how many times the button has been clicked, and set the Text property of the label to that string.
        
+		
        Just for visual effect, you can also set the button background color to something different than the initial color set when the button was instantiated.
        
+
                 void OnButtonClicked(object s, EventArgs e)
         {
-            clicks += 1;
-            label.Text = String.Format("Number of clicks: {0}", clicks);
+            clicks += 1;
+            label.Text = String.Format("Number of clicks: {0}", clicks);
+            button.BackgroundColor = Color.Blue;
         }
         protected override void OnStart()
         {
-            // Handle when your app starts
+            /// Handle when your app starts
         }
         protected override void OnSleep()
         {
-            // Handle when your app sleeps
+            /// Handle when your app sleeps
         }
         protected override void OnResume()
         {
-            // Handle when your app resumes
+            /// Handle when your app resumes
         }
     }
-
-
 }
-
        
+
    
+
+
 
-
    The following image shows what happens if you try out the modified code and run the application with it. At the startup, the button is red and the text below the button is unclicked. After a couple of clicks, the click counter is displayed below the button, and the button color has changed.
    
+
    The following image shows what happens when you run the modified code. At startup, the button is red and the text below the button is unclicked. After a couple of clicks, the click counter is displayed below the button, and the button color has changed.
    
 
 
    Figure: Enhanced application
    
+
    Enhanced application
    
 
-
    Enhanced application 
    
+
    This topic only introduces the controls in use in the example above. For more information on Xamarin.Forms, see the Xamarin Developer Center. There is also a comprehensive book about Xamarin.Forms available as a free download from Microsoft Press.
    
 
-
    Packaging Your Tizen .NET Application
    
+
    Packaging Your Application
    
 
-
    This section gives a basic overview of packaging, to aid in understanding how to make simple changes. For more complex applications, see the packaging information in the Tizen documentation.
    
+
    A Tizen .NET application is deployed in the form of an installable package, with the package file extension .tpk. A Tizen .NET package has a relatively simple structure: internally it is a ZIP file with content that matches the directory layout of the project.
    
 
-
    A Tizen .NET application is deployed in the form of an installable package, where the package file takes the suffix .tpk. A Tizen .NET package has a relatively simple structure: internally it is a zipfile with content that matches the directory layout of the project.
    
-
-
    In the following figure, the layout of the platform specific (.Tizen) project is shown. It includes the lib, res, and shared (with a res subdirectory containing an image file) directories , and the tizen-manifest.xml file. There is also the bin directory, which Visual Studio only shows if you select the Show all files option for the solution. These pieces all go into the package.
    
-
-
    Figure: Project layout
    
-
-
    Project layout
    
-
-
    Package generation (and in fact installation) is controlled by a package manifest file, which is named tizen-manifest.xml. The Visual Studio template generates a package manifest, and places it at the top of the directory tree of the .Tizen project. The following figure shows the .tpk file for the initial application, to illustrate how the combination of the directory layout and the package manifest leads to the actual package.
    
-
-
    Figure: Package content
    
+
    The package contains the following:
    
+
      
+	
    • The shared directory, which is for items that are considered system-wide (shareable).
+	
      The application icon is packaged in the shared/res directory on installation, and the icon appears on the home screen with the icons for the other applications. You can either replace the icon (which is just a copy of the default Tizen logo) with one of your own using the file name generated by Visual Studio, or put a new icon in the same project directory and update the package manifest to indicate the new name.
      • 
+	
    • The res directory, which is for application-private resources.
+	
      If the application needs a file to open at runtime, it can be placed here.
      • 
+	
    • The bin directory, which contains the generated application executable.
      • 
+	
    • The lib directory, which contains the generated application support code.
+	
      If you use nugget libraries, they are imported in the lib directory.
      • 
+	
    • The package manifest, which defines the application properties and is used at the installation time.
      • 
+	
    • 2 signature files (author and distributor), which are checked at the installation time.
      • 
+
    
 
-
    Package content
    
+
    The following figure shows the layout of the platform-specific (Tizen) project. It includes the lib, res, and shared (with a res subdirectory containing an image file) directories, and the tizen-manifest.xml file. There is also the bin directory, which Visual Studio only shows if you select the Show all files option for the solution. These pieces all go into the package.
    
 
-
    The initial points to learn here are:
    
+
    Figure: Project layout
    
+
    Project layout
    
 
-
      
-	
    • The shared directory is for items that are considered systemwide (shareable). The application icon is packaged in shared/res: on installation, the icon appears on the home screen with the icons for the other applications. You can either replace the icon (which is just a copy of the default Tizen logo) with one of your own using the file name generated by Visual Studio, or put a new icon in the same project directory and update the package manifest to indicate the new name.
      • 
-	
    • The res directory is for application-private resources. If the application needs a file to open at runtime, it can be placed here.
      • 
-	
    • The bin directory contains the generated application executable.
      • 
-	
    • The lib directory contains the generated application support code.
      
-	 If you use nugget libraries, they are imported in the lib directory.
      • 
-	
    • The package manifest is included in the package, as it is used at the installation time.
      • 
-	
    • 2 signature files (author and distributor) are included, as they are checked at the installation time.
      • 
-
    
+
    Package generation (and in fact installation) is controlled by the tizen-manifest.xml package manifest file. The following figure shows the .tpk file for the initial application, to illustrate how the combination of the directory layout and the package manifest leads to the actual package.
    
 
-
    Other information relating to packaging includes declarations of features and privileges, and the placement of language-specific files.
    
+
    Figure: Package content
    
+
    Package content
    
 
+
    When packaging your application, you also need to consider whether any feature or privilege declarations are needed in the manifest file, and how to place any language-specific files.
    
 
 
 
diff --git a/preview/html/getting_started/download.htm b/preview/html/getting_started/getting_started_cover.htm
similarity index 69%
rename from preview/html/getting_started/download.htm
rename to preview/html/getting_started/getting_started_cover.htm
index e9df214..408d037 100644
--- a/preview/html/getting_started/download.htm
+++ b/preview/html/getting_started/getting_started_cover.htm
@@ -12,7 +12,7 @@
     
     
     
-    Downloading Visual Studio Tools for Tizen Preview
+    Getting Started
 
 
 
@@ -22,15 +22,23 @@
 
 
    
 
- 
    Downloading Visual Studio Tools for Tizen Preview
    
+ 
    Getting Started
    
 
-
    Note  The latest Visual Studio Tools for Tizen installer automatically detects the installed Visual Studio version (2015 or 2017), and installs the applicable Tizen .NET development environment.
    
+
    The Visual Studio Tools for Tizen Preview is a collection of tools for developing Tizen .NET applications. It consists of a Visual Studio extension for templates, a debugger, and the Tizen Emulator. The Visual Studio Tools for Tizen Preview runs on Windows® with Visual Studio.
    
 
-
    The Visual Studio Tools for Tizen Preview is a collection of tools for developing Tizen .NET applications. It consists of Visual Studio extension for templates, debugger, and Tizen Emulator. The Visual Studio Tools for Tizen Preview runs on Windows® with Visual Studio.
    
+
    To get started with developing your own Tizen .NET applications:
    
+
+
+
    Downloading Visual Studio Tools for Tizen
    
 
-
    For the installation of Visual Studio Tools for Tizen Preview, your system requires more than 1.5GB available disk space.
    
+
    Note The latest Visual Studio Tools for Tizen installer automatically detects the installed Visual Studio version (2015 or 2017), and installs the applicable Tizen .NET development environment.
    
 
-
    You can download by selecting a server below where is located near your side.
    
+
    Download the Visual Studio Tools for Tizen Preview installer by selecting the location that is closest to you:
    
 
 
+
    Figure: Exporting a log file
    
+
    Exporting a log file
    
 
 
 
diff --git a/preview/html/tools/emulator_control_panel.htm b/preview/html/tools/emulator_control_panel.htm
index ec757b0..048a7b6 100644
--- a/preview/html/tools/emulator_control_panel.htm
+++ b/preview/html/tools/emulator_control_panel.htm
@@ -15,87 +15,86 @@
     Emulator Control Panel
 
 
-
+
 
 
-
 
    
 
   
    Emulator Control Panel
    
 
 
    Before deploying your application, it is important that you test it in an environment similar to a real device.
    
 
-
    You can run the application in the emulator, and test a variety of user scenarios, such as network access, audio input and out, and text messages. You can control the application in the emulator with mouse and keyboard buttons, like if you used an actual device.
    
+
    You can run the application in the emulator, and test a variety of user scenarios, such as network access, audio input and out, and text messages. With a mouse and keyboard, you can control the application in the emulator just like on an actual device.
    
 
-
    During the run, you can use the Emulator Control Panel to inject events for several system options that the actual device provides. For example, by manipulating the optional battery, you can simulate the application in different charge environments.
    
+
    While the application is running, you can use the Emulator Control Panel to simulate events for a variety of system options that the actual device provides. For example, by manipulating the virtual battery, you can simulate the application in different charge environments.
    
 
 
    The emulator controls consist of internal and external parts:
    
 
 
      
-	
    • The HOME, Volume control and Back buttons, for example, are external parts controlling the device from the outside.
+	
    • The HOME, Volume control and Back buttons, for example, are external parts controlling the device from the outside.
 
-	
      In the emulator, the external parts are called the emulator control keys and menu.
      
-	
      • 
-	
    • Battery level and screen brightness, for example, are internal parts controlling the device from the inside. In the emulator, the internal parts are called the Emulator Control Panel.
      • 
+
      In the emulator, the external parts are called the emulator control keys and menu.
      
+	
    • Battery level and screen brightness, for example, are internal parts controlling the device from the inside. In the emulator, the internal parts are called the Emulator Control Panel.
      • 
 
    
 
 
    Using the Control Keys and Context Menu
    
 
-
    The control keys are visible on the emulator when you start it. To access the context menu, right-click the emulator. The following figure illustrates the TV and mobile emulator.
    
+
    The control keys are visible on the emulator when you start it. To access the context menu, right-click the emulator.
    
 
-
    Figure: TV and mobile emulator
    
+
    Figure: TV and mobile emulators
    
+
    TV and mobile emulators
    
 
-
    
+
    NoteYou can create a custom resolution emulator by using the Emulator Manager CLI, and launch it with the TV and mobile skin. It is not guaranteed that all applications are correctly shown in the custom resolution.
    
 
-
    NoteYou can create a custom resolution emulator by using the Emulator Manager CLI, and launch it with the TV and mobile skin. It is not guaranteed that all the applications are correctly shown in the custom resolution.
    
-
-
    Control Keys
    
+
    Control Keys
    
 
 
    The following hardware keys are available on the emulator:
    
 
 
      
-	
    • Menu
-
-	
      When tapped, it opens a list of options available for the current screen. This button can be used to delete an application on the TV platform.
      
+	
    • Menu
+	
      When tapped, a list of options available for the current screen opens. On the TV platform, the options include removing an application.
      
 	
      • 
-	
    • Home
-	
      When long-pressed, the Task switcher application opens as in a real device.
      
+	
    • Home
+  	
      When long-pressed, the Task switcher application opens as on a real device.
      
 	
      • 
-	
    • Back
+	
    • Back
 	
      When tapped, the emulator returns to the previous screen.
      
 	
      • 
-	
    • Power
-	
      You can power off the display by tapping the Power key in most general situations. Sometimes, the display does not power off though you tap the Power key. This is to guarantee the operation of a current application, such as the Stopwatch in the Clock application. If you tap the Power or Home key again, the display is powered on.
      
+	
    • Power
+  	
      You can power off the display by tapping the Power key in most situations. Sometimes, the display does not power off when you tap the Power key. This is to guarantee the operation of a current application, such as the Stopwatch in the Clock application. If you tap the Power or Home key again, the display is powered on.
      
 	
      • 
-	
    • Volume Up and Volume Down (mobile only)
+	
    • Volume Up and Volume Down (mobile only)
 	
      When tapped, the volume changes accordingly.
      
 	
      • 
 	
    • 
-	
      Arrow keys (TV only)
      
+	
      Arrow keys (TV only)
      
 
-	
      When tapped, the cursor or selection moves to the desired direction.
      
+	
      When tapped, the cursor or selection moves in the desired direction.
      
 	
      • 
 	
    • 
-	
      OK (TV only)
      
+	
      OK (TV only)
      
 
 	
      When tapped, the item is selected.
      
 	
      • 
 
    
 
-
     
    
-
-
+
 
 
    You can access the context menu by right-clicking the emulator. In the menu, you can select:
    
 
 
      
 	
    • Emulator name (the top row in the menu)
-	
      The Detailed Info window is displayed, showing the Shortcut Info and VM Info tabs. The Shortcut Info tab lists the emulator keyboard shortcuts and the VM Info tab defines the virtual machine details.
      
-
-	
      In Mac OS® X: To use the emulator keyboard shortcuts, open the Keyboard Setting dialog and switch your Mac function keys option to work as standard function keys.
      
+	
      The Detailed Info window is displayed, showing the Shortcut Info and VM Info tabs. The Shortcut Info tab lists the emulator keyboard shortcuts and the VM Info tab defines the virtual machine details.
      
 
-	
      Table: VM Info
      
+	
      Table: VM Info
      
 
 	
@@ -104,360 +103,132 @@
 				
-				
+			  
-				
+			  
-				
+			  
-				
+			  
-				
-				
+			  
+			  
-				
+			  
-				
+			  
-				
+			  
-				
-				
+			  
+			  
-				
-				
+			  
+			  
-				
+			  
-				
+				
-				
+				
-				
+			  
-				
-				
+			  
+				
      
 		
      Description
 			
      
 			
      VM NameVM Name
 				VM name
 			
      
 			
      Skin NameSkin Name
 				Skin name
 			
      
 			
      CPU ArchCPU Arch
 				CPU architecture
 			
      
 			
      RAM SizeRAM Size
 				RAM size (in MB)
 			
      
 			
      DisplayTarget display resolution (in DPI; Dots Per Inch)DisplayTarget display resolution (in DPI; Dots Per Inch)
 			
      
 			
      Network connectionNetwork Connection
 				NAT (Network Address Translation) or Bridged
 			
      
 			
      CPU VirtualizationCPU Virtualization
 				Whether hardware virtualization is supported
 			
      
 			
      GPU VirtualizationGPU Virtualization
 				Whether GPU virtualization is supported
 			
      
 			
      Platform Image VersionVersion of the used platform imagePlatform Image VersionVersion of the used platform image
 			
      
 			
      Platform Image FileLocation of the used platform imagePlatform Image FileLocation of the used platform image
 			
      
 			
      Directory SharingDirectory Sharing
 				Whether host directory sharing is used
 			
      
 			
      File Shared PathFile Shared Path
 				Path to the shared host directory
 			
      
 			
      Kernel Log FileKernel Log File
 				Kernel log file path
 			
      
 			
      Emulator Log FileEmulator Log File
 				Emulator (Qemu) log file path
 			
      
 			
      Emulator VersionTizen Emulator versionEmulator VersionTizen Emulator version
 			
      
 		      
 	
      
 	
      • 
-	
    • Always On Top
+	
    • Always On Top
 	
      Select this option to keep the emulator window on top of other windows.
      
 	
      • 
-	
    • Rotate (mobile only)
-	
      Select either Portrait, Landscape, Reverse Portrait, or Reverse Landscape as the orientation of the emulator.
      
-	
      • 
-	
    • Scale (mobile only)
-	
      Scale the size of the emulator between 1x, 1/2x (default), 3/4x, and 1/4x.
      
-	
      • 
-	
    • Advanced > Controller
-	
      Show or hide the controller window.
      
+	
    • Rotate (mobile only)
+
      Select either Portrait, Landscape, Reverse Portrait, or Reverse Landscape as the orientation of the emulator.
      • 
 
-	
      NoteThe Controller menu is not supported in the profile-specific skin.
      
-	
-	
    • Advanced > Screenshot
-	
      Capture a screenshot of the emulator.
      
-	
      • 
-	
    • Advanced > About
-	
      Display the emulator version and build time.
      
-	
      • 
-	
    • Advanced > Force Reboot
-	
      Force the emulator to reboot. Since force rebooting the emulator can cause problems, use the reboot option from the SDB shell to reboot the emulator. Use Force Reboot only when absolutely necessary.
      
-	
      • 
-	
    • Advanced > Force Close
-	
      Force the emulator to exit. Since force stopping the emulator can cause problems, use the Close option to exit the emulator. Use Force Close only when absolutely necessary.
      
-	
      • 
-	
    • Shell
-	
      Open a Smart Development Bridge (SDB) shell command window.
      
-	
      • 
-	
    • Control Panel
-	
      Help to control or monitor the state of the emulator dynamically.
      
-	
      • 
-	
    • Close
-	
      Exit the emulator.
      
-	
      • 
-
    
-
-
    NoteIn Ubuntu, you must change a global GNOME setting to view the menu icons:
-
-
      
-	
    1. In the command console, execute the gconf-editor command.
      2. 
-	
    2. In the tree, navigate to desktop > gnome > interface.
      3. 
-	
    3. Enable the menus_have_icons option.
      4. 
-
    
-
    
-
-
    Using the Control Panel
    
+
  • Scale (mobile only)
+
    Scale the size of the emulator between 1x, 1/2x (default), 3/4x, and 1/4x.
    • 
 
-
    With the Emulator Control Panel, you can inject system events and perform related tasks.
    
-
-
    Figure: Emulator Control Panel
    
-
-
    Emulator Control Panel
    
-
-
    The control panel consists of 3 layers:
    
-
-
      
-	
    • Dialog, which is the main application window, shows a list of testable device cards.
      • 
-	
    • Card, which represents each device, shows the representative device status. By clicking a card, you can inject an event directly or open Popup to do it.
      • 
-	
    • Popup displays testable events for each device.
      • 
-
    
-
-
    Figure: Emulator Control Panel Layers
    
-
-
    
-
-
    To open the control panel:
    
-
-
      
-	
    1. Launch the emulator.
      2. 
-	
    2. Right-click the emulator and select Control Panel.
      3. 
-
    
-
-
    Figure: Opening the control panel
    
-
-
    Opening the control panel
    
-
-
    The main features of the Emulator Control Panel are described in the following sections.
    
-
-
    Controlling the Network Setting
    
-
-
    You can control the user network.
    
-
-
    To lose the network connection, set the link status to off. To forward a remote or local port to an inside port of the emulator, enter values in text boxes, and click Apply.
    
-
-
    Figure: Network Setting
    
-
-
    
-
-
    Mounting a Host Directory
    
-
-
    The specified host directory is mounted to /mnt/host to share resources. Therefore, file transfer is possible through the host directory sharing feature without using the SDB utility.
    
-
-
    Figure: Host Directory Sharing
    
-
-
    
-
-
    Providing Device Data
    
-
-
    The control panel can be used to simulate device data, such as the battery level, adding or removing a earjack (headset) or USB device, setting RSSI (remote signal strength indicator) information, and attaching and detaching the SD card:
    
-
-
      
-	
    • In the Battery card, set the battery level using the Level slider. To set the charger status to connected or disconnected, select the appropriate Charger radio button.
      • 
-	
    • In the EarJack card, select the earjack setting:
-	
        
-		
      • 3 Wire
        • 
-		
      • 4 Wire
        • 
-		
      • Disconnect
        • 
-	
      
-	
      • 
-	
    • In the USB card, set the USB device setting to the connected or disconnected state.
      • 
-	
    • In the RSSI card, set the RSSI information level using the Level slider.
      • 
-	
    • In the SD Card card, select the 4G, 8G, 16G, or 32G SD card and attach it to the emulator at runtime.
-	
      NoteThe same SD card cannot be attached to multiple emulators at the same time.
      
-	
      • 
-
    
-
-
    The device information set using the control panel is reflected on the indicator bar of the device.
    
-
-
    Providing Location Data
    
-
-
    The control panel can be used to provide imitated responses to location data requests by loading GPS log files, manually entering location coordinates, or injecting markers directly on the map in the Location tab:
    
-
-
      
-	
    • Loading a GPS log file
-	
      In the Log section, select the pre-logged GPS data file (NMEA183 format) and click Inject Log to send the location data to the emulator.
      
-	
      • 
-	
    • Manually entering location coordinates
-	
      In the Manual section, enter the coordinates and click Inject Location to send the location data to the emulator. The range of the latitude, longitude, altitude, and horizontal accuracy is from -90 to 90, -180 to 180, -300 to 100000, and 0 to 100000, respectively.
      
-	
      • 
-	
    • Injecting markers on the map
-	
      In the Map section, right-click the desired map locations and click Inject Markers to send the location data to the emulator.
      
-	
      • 
-
    
-
-
    Providing NFC Data
    
-
-
    The control panel can be used to test the near-field communication (NFC) features, such as NFC data exchange format (NDEF) events, NFC tag detection, and peer-to-peer (P2P) data connections in the NFC tab.
    
+	
  • Advanced > Controller
+	
    Show or hide the controller window.
    
+
    
+    Note
+    The Controller menu is not supported in the profile-specific skin.
+
    • 
+
  • Advanced > Screenshot
+
    Capture a screenshot of the emulator.
    • 
 
-
    NoteThe control panel only sends NFC-related events to the emulator. There is no actual information exchange between the control panel and emulator. Therefore, for features such as writing information to an NFC tag, the emulator simply displays a success message.
    
+
  • Advanced > About
+
    Display the emulator version and build time.
    • 
 
-
      
-	
    • Creating NDEF messages
-	
      An NDEF message contains one or more NDEF records. In the NDEF Message section:
      
+
    • Advanced > Force Reboot
+
      Force the emulator to reboot. Since force rebooting the emulator can cause problems, use the reboot option from the SDB shell to reboot the emulator. Use Force Reboot only when absolutely necessary.
      • 
 
-	
        
-		
      1. Select the record type name format.
        2. 
-		
      2. Enter the record type name, ID, and payload.
        3. 
-		
      3. Click Add.
        4. 
-	
      
+
    • Advanced > Force Close
+
      Force the emulator to exit. Since force stopping the emulator can cause problems, use the Close option to exit the emulator. Use Force Close only when absolutely necessary.
      • 
 
-	
      You can add multiple NDEF records, as required, in the NDEF message.
      
+
    • Shell
+
      Open a Smart Development Bridge (SDB) shell command window.
      • 
 
-	
      Click Edit or Remove to modify or delete a selected record.
      
-	
-	
    • Attaching and detaching NFC tags
-	
      In the NFC Tag section:
      
+
    • Control Panel
+
      Control or monitor the state of the emulator dynamically. 
      • 
 
-	
        
-		
      1. Select the tag type.
        2. 
-		
      2. Click Tag Attach.
-		
        If the NDEF record list is not empty, an NDEF message is created using this list and the attach message is sent to the emulator with the NDEF message.
        
-		
        3. 
-		
      3. When the tag operation is finished, click Tag Detach.
        4. 
-	
      
-	
-	
    • Creating a P2P data Connection
-	
      In the Peer to Peer section:
      
+
    • Close
+
      Exit the emulator.
      • 
 
-	
        
-		
      • To send the emulator the discovered state of the new device, click P2P Discovered.
        • 
-		
      • To send the emulator an NDEF message, click P2P Send.
        • 
-		
      • To send the emulator the detached state of the connected device, click P2P Detached.
        • 
-	
      
-	
 
    
 
-
    Providing Sensor Data
    
-
-
    In the control panel, you can model your actions, such as shaking, throwing, and tilting the device for the emulator instance. In addition, you can generate a single sensor event on the instance, or inject sequences of 3-axis sensor events to the instance.
    
-
-
    To control 3-axis sensors, select Event Injector > Sensor > 3-Axis Sensor. The 3-Axis Sensor tab consist of 4 subtabs, in which you can adjust the acceleration, magnetic, and gyro sensors of the emulator instance. In the GUI subtab, you can intuitively adjust various sensor data by using 3D graphics. In the other subtabs, you can inject a single event into the individual sensor, or use the sensor data files to inject sequences of events into the sensor.
    
-
-
      
-	
    • GUI
-	
      In the GUI subtab, you can select an active sensor and move the 3D model of the emulator instance by the 3 axis sliders or direction buttons (Portrait, Landscape, Reverse Portrait, and Reverse Landscape). The instance monitor displays the acceleration, magnetic, and gyro values.
      
-
-	
      To better control the movement, select the With axis checkbox to see the axes in the emulator image. You can also fix the Y or Z axis by selecting the X/Z or X/Y radio button, respectively. To change the emulator accelerator value in the direction of the movement, select the Move radio button.
      
-	
      • 
-	
    • Acceleration
-	
      You can control the acceleration of the instance along the coordinate axes. When the instance is standing, the acceleration value of the Y axis is -1 g as gravitational acceleration. By using the sliders in the Acceleration subtab, you can control the acceleration 3-axis values from -2 g to 2 g.
      
-	
      • 
-	
    • Magnetic
-	
      You can control the magnetic values of the instance along the coordinate axes. When the instance is standing, the magnetic 3-axis tesla values (azimuth 0) are set for the North. By using the sliders in the Magnetic subtab, you can control the magnetic 3-axis values from -2000 uT to 2000 uT.
      
-	
      • 
-	
    • Gyro
-	
      You can control the gyro (rotation angle per second) of the instance along the coordinate axes. By using the sliders in the Gyro subtab, you can control the gyro 3-axis values from -573 deg/s to 573 deg/s.
      
-	
      • 
-	
    • Event file
-	
      The event file consists of predefined events. It is written in ASCII. By loading the event file in the Acceleration, Magnetic, or Gyro subtab, you can replay a sequence of predefined events. You can also add multiple event files to replay. The format of each line in the event file is:
      
-
-	
      -timestamp, x, y, z
-
      
+
      Using the Control Panel
      
 
-	
      When you add the event files and click Start, the predefined events are injected at their specified relative timestamp. The timestamp unit is 0.01 seconds. Some events can be discarded, if they exceed certain limits of performance, resource, or logic. When you add multiple event files, the files are executed in sequence. You can also repeat the replay.
      
-	
      • 
-
    
+
    With the Emulator Control Panel, you can simulate system events and perform related tasks.
    
 
-
    In the Event Injector > Sensor tab, you can control other sensors, such as light, proximity, pressure, ultraviolet, and HRM sensors:
    
+
    The control panel consists of 3 layers:
    
 
 
      
-	
    • To control the light sensor, set the Lux value in the Light tab. The range of this value is from 0 Lux to 65635 Lux.
-
-	
      If you set brightness as auto, the display is changed based on the injected light value.
      
-	
      • 
-	
    • To control the proximity sensor, set it on or off in the Proximity tab.
      • 
-	
    • To control the pressure sensor, set the hPa (Hectopascal) value in the Pressure tab. The range of this value is from 260 hPa to 1260 hPa.
      • 
-	
    • To control the ultraviolet sensor, use the slider in the Ultraviolet tab. The unit is UV index and the range of this value is from 0 to 15.0.
      • 
-	
    • To control the HRM (Heart Rate Monitor) sensor, use the sliders in the Heart Rate Monitor tab. You can set the Heart Rate value between 0 and 220, and the Peek-to-Peek value between 0 and 5000 (in milliseconds).
      • 
+
    • Dialog is the main Emulator Control Panel window, which shows a list of testable device cards.
      • 
+
    • Card represents a peripheral device or system option, and shows the respective device or option status. By clicking a card, you can simulate an event directly or open a Popup to do it. 
      • 
+
    • Popup displays testable events for a peripheral device.
      • 
 
    
 
-
    Providing Telephony Features
    
-
-
    The control panel can be used to generate incoming calls and messages in the Telephony tab.
    
-
-
      
-	
    • Generating incoming calls
-	
      Incoming calls are generated in the Event Injector > Telephony > Call tab.
      
-
-	
      NoteA Mobile Termination (MT) call is made from the Event Injector view to the emulator. A Mobile Origination (MO) call is made from the emulator to the Event Injector view using the phone application of the emulator.
      
-
-	
      To make an MT call:
      
+
      Figure: Emulator Control Panel layers
      
+
      Emulator Control Panel layers
      
 
-	
        
-		
      1. Enter the phone number you want to imitate the call from.
        2. 
-		
      2. Click Connect.
        3. 
-		
      3. To hide the phone number on the emulator, select the Hidden option.
-		
        The caller ID on the emulator is set to "Unknown".
        
-		
        4. 
-	
      
-
-	
      To make an MO call, use the emulator's phone application:
      
-
-	
        
-		
      1. To ready the emulator for the connection, click Alert.
        2. 
-		
      2. To ready the emulator for the call, click Connect.
        3. 
-	
      
-	
      • 
-	
    • Generating messages
-	
      SMS messages are generated in the Event Injector > Telephony > Messaging tab. After sending a message, your application waits for the asynchronous send status message. You can generate this status report for SMS messages using the same Messaging tab.
      
-
-	
      To generate an SMS message:
      
-
-	
        
-		
      1. Enter the sender phone number you want to imitate.
        2. 
-		
      2. Enter the message body text and click Send Msg.
        3. 
-	
      
-
-	
      To generate status reports, set the sending status value for the SMS message:
      
-
-	
        
-		
      • SMS OK (Success)
        • 
-		
      • SMS Not Available
        • 
-	
      
-
-	
      You can also generate MMS message status reports. To generate MMS status reports, set the sending status value for the MMS message:
      
-
-	
        
-		
      • MMS OK (Success)
        • 
-		
      • MMS Failure
        • 
-	
      
-	
      • 
-
    
-
-
    Providing Memory Data
    
-
-
    The control panel can be used to simulate low memory status in the Memory tab.
    
-
-
    Set the low memory status using the radio buttons:
    
-
-
      
-	
    • Hard-Warning (40 MB and under)
      • 
-	
    • Soft-Warning (60 MB and under)
      • 
-	
    • Normal (sufficient)
      • 
-
    
+
    To open the control panel:
    
 
-
    Control Panel Features on Different Profiles
    
+
      
+	
    1. Launch the emulator.
      2. 
+	
    2. Click the Control Panel button, or right-click the emulator and select Control Panel.
 
-
      The following table lists the control panel features and their availability on different profiles.
      
+
      Opening the control panel
      
+
    
 
-
    Table: Control panel features
    
+
    The following table lists the control panel features and their availability on different profiles. The instructions for using the features are described below the table.
    
+
    Table: Control panel features
    
 
 
@@ -477,7 +248,7 @@ timestamp, x, y, z
 			
-			
+ 
@@ -492,41 +263,47 @@ timestamp, x, y, z
 			
-			
-			
+ 
+			
-			
+ 
-			
+ 
-			
+ 
-			
+ 
-			
+ 
-			
+ 
+ 
+  
+ 
+ 
+ 
+ 
@@ -544,13 +321,19 @@ timestamp, x, y, z
 			
-			
+ 
+ 
+ 
+ 
+ 
+ 
+   
-			
+ 
@@ -562,12 +345,189 @@ timestamp, x, y, z
 			
-			
+			
    
 	
    Host Directory Sharing
 			Yes
 			YesFile transfer is possible through the host directory sharing feature without using the SDB utility.You can transfer files through the host directory sharing feature without using the SDB utility.
 		
    
 		
    
 			BatteryYou can set the remote signal strength.
 		
    
 		
    Sensor3-Axis SensorSensor3-Axis
 			Yes
 			NoYou can inject user acceleration, magnetic, and gyroscope values.You can simulate user acceleration, magnetic, and gyroscope values.
 		
    
 		
    
 			Light
 			Yes
 			NoYou can inject a lux value into the light sensor.You can simulate a lux value for the light sensor.
 		
    
 		
    
 			Proximity
 			Yes
 			NoYou can inject the presence of nearby objects.You can simulate the presence of nearby objects.
 		
    
 		
    
 			Pressure
 			Yes
 			NoYou can inject an hPa value into the pressure sensor.You can simulate an hPa value for the pressure sensor.
 		
    
 		
    
 			Ultraviolet
 			Yes
 			NoYou can inject an ultraviolet index.You can simulate an ultraviolet index value.
 		
    
 		
    
 			Heart Rate Monitor
 			Yes
 			NoYou can inject the heart rate and peek-to-peek time.You can simulate the user heart rate and peak-to-peak time.
    PedometerYesNoYou can simulate user movement with the device.
 		
    
 		
    
 			EarjackSD Card
 			Yes
 			NoYou can inject a 4, 8, 16, or 32G SD card.You can simulate a 4G, 8G, 16G, or 32G SD card.
 		
    
 		
    NFCYesNoYou can simulate near-field communication (NFC) events.
    
 			Location
 			Yes
 			NoYou can inject latitude and longitude values using a map, manually, or from a log file.You can simulate latitude and longitude values using a map, manually, or from a log file.
 		
    
 		
    
 			TelephonyMemory
 			Yes
 			NoYou can set the low memory status.You can set the memory status.
 		
    
 	    
 
    
+
    Controlling the Network Setting
    
+
    In the Network card, you can control the user network.
    
+
    To lose the network connection, set the Link Status switch off. To forward a remote or local port to an inside port of the emulator, enter values in the text boxes, and click Apply.
    
+
+
    Figure: Network popup
    
+
    Network popup
    
+
+
    Mounting a Host Directory
    
+
    In the HDS card, you can configure host directory sharing (HDS) to share resources and transfer files without using the SDB utility. The specified host directory is mounted to /mnt/host.
    
+
+
    Figure: Host Directory Sharing popup
    
+
    Host directory sharing popup
    
+
+
    Providing Device Data
    
+
    The control panel can be used to simulate various device data:
    
+
      
+
    • In the Battery card, you can set the battery level using the Level slider. You can also connect or disconnect a charger using the Charger switch.
      • 
+
    • In the Ear Jack card, you can add or remove an earjack (headset) device. You can add a 3-wire or 4-wire device.
      • 
+
    • In the USB card, you can connect or disconnect a USB device.
      • 
+
    • In the RSSI card, you can set the RSSI (remote signal strength indicator) information level.
      • 
+
    • In the SDCard card, you can attach or detach an SD card to or from the emulator at runtime. You can attach a 4G, 8G, 16G, or 32G SD card.
+
+
      
+    Note
+    The same SD card cannot be attached to multiple emulators at the same time.
+
      
+
      • 
+
    
+
+
    Device information set using the control panel is reflected on the indicator bar of the emulator screen.
    
+
+
    Providing Location Data
    
+
    In the Location card, you can provide simulated responses to location data requests:
    
+
      
+
    • Injecting map markers
+
      In the Map Image section, right-click the desired map locations and click Inject Markers to send the location data to the emulator.
      • 
+
    • Manually entering location coordinates
+
      In the Manual section, enter the coordinates and click Inject Location to send the location data to the emulator. The range of the latitude, longitude, altitude, and horizontal accuracy is from -90 to 90, -180 to 180, -300 to 100000, and 0 to 100000, respectively.
      • 
+
    • Loading a GPS log file
+
      In the Log section, select a pre-logged GPS data file (in NMEA183 format) and click Inject Log to send the location data to the emulator.
      • 
+
    
+
+
    Providing NFC Data
    
+
    In the NFC card, you can test near-field communication (NFC) features.
    
+
    
+    Note
+    The control panel only sends NFC-related events to the emulator. There is no actual information exchange between the control panel and emulator. Therefore, for information exchange features, such as writing information to an NFC tag, the emulator simply displays a success message.
+
    
+
      
+
    • Creating NFC data exchange format (NDEF) messages
+
      An NDEF message contains 1 or more NDEF records. In the NDEF Message section:
      
+
+	
        
+		
      1. Select the record type name format.
        2. 
+		
      2. Enter the record type name, ID, and payload.
        3. 
+		
      3. Click Add.
        4. 
+	
      
+
+
      You can add multiple NDEF records in the NDEF message.
      
+
+	
      Click Edit or Remove to modify or delete a selected record.
      
+	
      • 
+	
    • Attaching and detaching NFC tags
+
      In the NDEF Tag section:
      
+	
        
+	
      1. Select the tag type.
        2. 
+	
      2. Click the switch to attach or detach the tag.
+
        If the NDEF record list is not empty, an NDEF message is created using this list and the attach message is sent to the emulator with the NDEF message.
        3. 
+	
      
+	
      • 
+
    • Creating a peer-to-peer (P2P) data connection
+
      In the PEER TO PEER section:
      
+	
        
+	
      • To inform the emulator that a new device has been discovered, click P2P Discovered.
        • 
+	
      • To send the emulator an NDEF message, click P2P Send.
        • 
+	
      • To inform the emulator that a connected device has been detached, click P2P Detached.
        • 
+	
      
+	
      • 
+
    
+
+
    Providing Sensor Data
    
+
+
    In the control panel, you can model user actions, such as shaking, throwing, and tilting the device, for the emulator instance. In addition, you can simulate a single sensor event on the instance, or send sequences of 3-axis sensor events to the instance.
    
+
    • In the Sensor card, you can control the 3-axis sensors. The popup consists of 4 tabs, where you can adjust the acceleration, magnetic, and gyro sensors of the emulator instance. In the GUI tab, you can intuitively adjust various sensor data by using 3D graphics.
+
        
+	
      • GUI
+
        In the GUI tab, you can select an active sensor and move the 3D model of the emulator instance with the 3 axis sliders or the direction buttons (Portrait, Landscape, Reverse Portrait, and Reverse Landscape). The instance monitor displays the acceleration, magnetic, and gyro values.
        
+
+
        To better control the movement, select the With axis check box to see the axes in the emulator image. You can also fix the Y or Z axis by selecting the X/Z or X/Y radio button, respectively. To change the emulator accelerator value in the direction of the movement, select the Move radio button.
        • 
+	
      • Acceleration
+
        In the Acceleration tab, you can control the acceleration of the instance along the coordinate axes. When the emulated device is stationary and vertical in portrait orientation, the acceleration value of the Y axis is 1 g (gravitational acceleration). You can control the acceleration 3-axis values from -2 g to 2 g, using the sliders.
        • 
+	
      • Magnetic
+
        In the Magnetic tab, you can control the magnetic field values of the instance along the coordinate axes. When the emulated device is stationary and vertical in portrait orientation, the Y axis is at true north and the magnetic field strength values are 1, 0, and -10 µT (microtesla). You can control the magnetic field 3-axis values from -2000 µT to 2000 µT, using the sliders.
        • 
+	
      • Gyro
+
        In the Gyro tab, you can control the gyro (rotation angle per second) of the instance along the coordinate axes. You can control the gyro 3-axis values from -573 degrees/s to 573 degrees/s, using the sliders.
        • 
+
      
+
      You can simulate a single event on the individual sensor, or use sensor data files to simulate sequences of events on the sensor. A sensor data file consists of predefined events. It is written in ASCII. By loading a data file in the Acceleration, Magnetic, or Gyro tab, you can play a sequence of predefined events. You can also add multiple data files to be played in sequence. The format of each line in the event file is:
      
+
+	
      +timestamp, x, y, z
+
      
+
+
      When you add the event files and click Start, the predefined events are simulated at their specified relative timestamp. The timestamp unit is 0.01 seconds. Some events can be discarded, if they exceed certain limits of performance, resource, or logic.
      • 
+
+
    • In the Light card, you can simulate ambient light conditions using the Lux slider. The range of this value is from 0 Lux to 65635 Lux.
+
      If automatic screen brightness is activated in the device settings, the display changes based on the simulated light value.
      • 
+
    • In the Proximity card, you can set the proximity sensor state to Far or Near.
      • 
+
    • In the Pressure card, you can control the pressure sensor using the hPa slider. The range of this value is from 260 hPa to 1260 hPa (Hectopascals).
      • 
+
    • In the Ultraviolet card, you can control the ultraviolet sensor using the Index slider. The unit is UV index and the range of this value is from 0 to 15.0.
      • 
+
    • In the Heart Rate card, you can control the HRM (Heart Rate Monitor) sensor. You can use the bpm slider to set the heart rate value between 0 and 220 bpm, and the ms slider to set the peak-to-peak time between 0 and 5000 ms (milliseconds).
      • 
+
    • In the Pedometer card, you can simulate user movement with the device by selecting a movement pace:
        
+    
      • Stop
        • 
+    
      • Walk Slowly
        • 
+    
      • Walk
        • 
+    
      • Run Slowly
        • 
+    
      • Run
        • 
+    
      
+
      • 
+
    
+
+
    Providing Telephony Features
    
+
+
    In the Telephony card, you can generate incoming calls and messages:
    
+
+
      
+	
    • Generating incoming calls
+	
      Incoming calls are generated in the Call tab.
      
+
+
      
+    Note
+    A Mobile Termination (MT) call is made from the Emulator Control Panel to the emulator. A Mobile Origination (MO) call is made from the emulator to the Emulator Control Panel using the emulator's phone application.
+
      
+	
      To make an MT call:
      
+
+	
        
+	
      1. In the MT Call section, enter the phone number you want to imitate the call from.
        2. 
+		
      2. Click Connect.
        3. 
+		
      3. To hide the phone number on the emulator, select the Hidden option.
+	
        The caller ID on the emulator is set to "Unknown".
        4. 
+	
      
+
+	
      To make an MO call:
      
+	
        
+   
      1. Call a phone number using the emulator's phone application.
        In the MO Call section, you can see the call ID, number, and call type.
        2. 
+	
      2. To disconnect the call, click Disconnect.
        3. 
+	
      
+	
      • 
+	
    • Generating messages
+	
      SMS messages are generated in the Messaging tab. After sending a message, your application waits for the asynchronous send status message. You can generate this status report for SMS messages using the same Messaging tab.
      
+
+	
      To generate an SMS message:
      
+
+	
        
+		
      1. Enter the sender phone number you want to imitate.
        2. 
+		
      2. Enter the message body text and click Send Msg.
        3. 
+	
      
+	
      To generate status reports, select the sending status value for the SMS message and click Set. The available values are:
      
+	
        
+	
      • SMS OK(Success)
        • 
+		
      • SMS Not Available
        • 
+	
      
+
+	
      You can also generate MMS message status reports. To generate MMS status reports, select the sending status value for the MMS message and click Set. The available values are:
      
 
-
       
      
+	
        
+	
      • MMS OK(Success)
        • 
+		
      • MMS Failure
        • 
+	
      
+	
      • 
+
    
+
+
    Providing Memory Data
    
+
+
    In the Memory card, you can select a specific memory status using the radio buttons:
    
+
      
+
    • Hard Warning (40 MB and under)
      • 
+
    • Soft Warning (60 MB and under)
      • 
+
    • Normal (Sufficient)
      • 
+
    
 
 
 
diff --git a/preview/html/tools/emulator_manager.htm b/preview/html/tools/emulator_manager.htm
index c741f96..64af6c7 100644
--- a/preview/html/tools/emulator_manager.htm
+++ b/preview/html/tools/emulator_manager.htm
@@ -15,194 +15,170 @@
     Emulator Manager
 
 
-
+
 
 
 
 
    
 
   
    Emulator Manager
    
 
-
    The Visual Studio Tools for Tizen provides emulators to run your application in a virtual environment.
    
+
    You can use emulators to run your application in a virtual environment.
    
 
-
    In order to test the application in a variety of environments, you need a variety of emulators. The Visual Studio Tools for Tizen provides the Emulator Manager to help you easily create and manage the emulator instances.
    
-
-
    Basically, the Emulator Manager allows you to easily generate emulator instances from a pre-defined platform and template. In addition, you can define the settings of the virtual device, such as skin, resolution, and hardware devices.
    
+
    In order to test the application in a variety of environments, you need a variety of emulators. The Emulator Manager helps you easily create and manage emulator instances. Basically, the Emulator Manager allows you to generate emulator instances from a predefined platform and template. In addition, you can define the settings of the virtual device, such as skin, resolution, and hardware devices.
    
 
 
    The main features of the Emulator Manager are:
    
-
 
      
-	
    • Creating a new emulator instance or hardware profile
      • 
-	
    • Managing an existing emulator instance or hardware profile
      • 
-	
    • Deleting an emulator instance or hardware profile
      • 
-	
    • Launching and stopping the emulator instance
      • 
+
    • Defining a new emulator instance or hardware profile
      • 
+
    • Editing an existing emulator instance or hardware profile
      • 
+
    • Deleting an emulator instance or hardware profile
      • 
+
    • Starting and stopping the emulator instance
      • 
 
    
 
 
    Accessing the Emulator Manager
    
 
 
    If you do not have the Emulator Manager installed, you can install it using the Visual Studio Tools for Tizen installer.
    
-
 
    There are 2 different ways to access the Emulator Manager from Visual Studio:
    
 
 
      
-	
    • Go to Tools > Tizen, and select Tizen Emulator Manager.
      • 
+	
    • In the Visual Studio menu, go to Tools > Tizen > Tizen Emulator Manager.
      • 
 
    
 
-
    Figure: Launch the Emulator Manager in the Tools menu
    
-
-
    
+
    Figure: Launch the Emulator Manager in the Tools menu
    
+
    Launch from the Tools menu
    
 
 
      
-	
    • Click Launch Tizen Emulator on the Visual Studio toolbar.
      • 
+	
    • On the Visual Studio toolbar, click Launch Tizen Emulator.
      • 
 
    
-
-
    Figure: Launch the Emulator Manager in the Visual Studio
    
-
-
    
+
    Figure: Launch the Emulator Manager in Visual Studio
    
+
    Launch from the Visual Studio toolbar
    
 
 
    Creating an Emulator Instance
    
 
-
    The Emulator Manager can help you to select the recommended platform and template. When you need another device environment, you can edit the existing emulator instance, or create a new one with a more suitable platform and template. You can also create platforms and templates to suit your needs.
    
+
    The Emulator Manager can help you to select the recommended platform and template. When you need another device environment, you can edit an existing emulator instance, or create a new one with a more suitable platform and template. You can also create new platforms and templates to suit your needs.
    
 
-
    Figure: Emulator Manager
    
-
-
    
+
    Figure: Emulator Manager
    
+
    Emulator Manager
    
 
 
    To create a new emulator instance:
    
 
 
      
-	
    1. In the Emulator Manager, click Create.
      2. 
-	
    2. Select the platform (system image), and click Next.
      3. 
-	
    3. Select the template (device definition), and click Next.
      4. 
-	
    4. Change properties as needed, and click Finish.
+	
    5. In the Emulator Manager, click Create.
      6. 
+	
    6. Select the platform (system image), and click Next.
      7. 
+	
    7. Select the template (device definition), and click Next.
      8. 
+	
    8. Modify the properties as needed, and click Finish.
 	
      The emulator instance appears in the Emulator Manager.
      
+
      To view the emulator instance details, right-click the instance and select Detail.
      
 
-	
      To view the detailed information, right-click the emulator to see a context menu.
      
-
-	
      Note
-
-	
      To run the application faster, switch on CPU VT and GPU. If CPU VT is disabled, check Increasing the Application Execution Speed for more information. If GPU is disabled, install the latest vendor-provided graphic driver.
      
+	
      Note
+	To run the application faster, switch on CPU VT and GPU. If CPU VT is disabled, check Increasing the Application Execution Speed for more information. If GPU is disabled, install the latest vendor-provided graphic driver.
 
-	
      Mobile emulator supports HD(720x1280) or WVGA(480x800) resolutions.
      
+	
      The mobile emulator supports HD (720x1280) and WVGA (480x800) resolutions.
      
 	
      
 	
      9. 
 
    
 
-
    Figure: Emulator Configuration dialog
    
-
-
    
-
 
    Creating Platforms
    
 
-
    To create an emulator, you have to first select the platform. You can create, modify, and delete a custom platform, and view the generated platforms. Most application developers do not need a custom platform, but it can be useful for a platform developer.
    
-
-
    Figure: Platforms list
    
-
-
    
+
    To create an emulator, you must first select the platform. You can create, modify, and delete a custom platform, and view the generated platforms. Most application developers do not need a custom platform, but it can be useful for a platform developer.
    
 
+
    Figure: Platform list
    
+
    Platform list
    
 
    To create a custom platform:
    
 
 
      
-	
    1. Click the create icon (Create icon).
      2. 
-	
    2. In the dialog box, select a base platform and platform image file.
-	
      You can create a custom platform using a qcow2 or raw format image.
      
-
-	
      Qcow2 is a platform image format that is released with the Tizen Studio. Using the Emulator Manager's "Export as" feature, you can also create a qcow2 image.
      
+    
    3. In the Emulator Manager, click Create.
      4. 
+	
    4. Click +.
      5. 
+	
    5. In the Platform Configuration dialog, select a base platform and platform image file.
+	
      You can create a custom platform using a qcow2 or raw format image. Qcow2 is a platform image format that is released with the Tizen Studio. You can also create a qcow2 image by exporting an emulator.
      
 
-	
      A platform image of the development stage is in the raw format. If you try launching an emulator with a raw image, you can see the current state of this image. This can be useful for platform developers.
      
+	
      A platform image in the development stage is in raw format. If you launch an emulator with a raw image, you can see the current state of the image. This can be useful for platform developers.
      
 	
      6. 
-	
    6. Click OK to save your configuration and click Next.
-	
      The newly created platform is added to the list with a settings icon.
      
+	
    7. Click OK to save your configuration.
+	
      The new platform is added to the list.
      
 	
      8. 
 
    
 
-
    Figure: Platform configuration
    
-
-
    
-
-
    Creating Templates
    
-
-
    The Emulator Manager provides several device template types. A device template refers to, for example, the screen resolution and size, and the sensors in the device specification. You can make an emulator instanced based on the desired template.
    
-
-
    Figure: Device templates
    
-
-
    Device templates
    
-
-
    You can create a new template from the beginning, or clone a template and change some properties.
    
-
-
      
-	
    • To create a new template, click the create icon (Create icon) to open a dialog box. Click OK to save your settings.
      • 
-	
    • To clone a new template, click the clone icon (Clone icon), make the appropriate changes, and click OK .
      • 
-
    
-
-
    After configuring the template, click Next. The new device template is added to the list with a settings icon.
    
-
-
    Figure: Template configuration
    
-
-
    Template configuration
    
-
-
    Managing the Emulator
    
-
-
    In the Emulator Manager, you can edit, delete, reset, and export emulator instances:
    
-
-
      
-	
    • To edit an emulator instance, click Edit, make the appropriate changes, and click Confirm.
      • 
-	
    • To delete an emulator instance, click Delete.
      • 
-	
    • To reset an emulator instance, right-click it and select Reset.
      • 
-	
    • To export an emulator instance, right-click it and select Export As. Specify the new image file location.
-	
      When you export the emulator instance, the same state as in the platform image is replicated.
      
-	
      • 
-
    
+
    Figure: Platform Configuration dialog
    
+
    Platform Configuration dialog
    
 
-
    Managing Platforms and Templates
    
-
-
    To manage the template:
    
+
    To manage the created platforms:
    
 
 
      
-	
    • To modify a template, click the modify icon (Modify icon), make the appropriate changes, and click Confirm. You can only modify the custom device templates you have created.
      • 
-	
    • To delete a template, click the delete icon (Delete icon). You can only delete the custom device templates you have created.
      • 
+	
    • To edit a platform, click Edit (Edit platform), make the desired changes, and click OK. You can only edit the custom platforms you have created.
      • 
+	
    • To delete a platform, click Delete (Delete). You can only delete the custom platforms you have created.
      • 
 
    
 
-
    To manage the platforms:
    
-
-
      
-	
    • To modify a custom platform, click the modify icon (Modify icon), make the appropriate changes, and click Confirm. You can only modify the custom platforms you have created.
      • 
-	
    • To delete a custom platform, click the delete icon (Delete icon). You can only delete the custom platforms you have created.
      • 
-
    
+
    Creating Templates
    
 
-
    Launching an Emulator Instance
    
+
    The Emulator Manager provides several device template types. A device template defines, for example, the screen resolution and size, and the sensors in the device specification. You can make an emulator instance based on the desired template.
    
 
-
    To launch an emulator instance:
    
+
    Figure: Device templates
    
 
-
      
-	
    • Launch the Emulator Manager and select an emulator instance on the list.
      • 
-	
    • Click Launch.
      • 
-
    
+
    Device templates
    
 
-
    Figure: Launch an emulator instance
    
+
    You can create a custom template in 2 ways:
    
 
-
    
+
      
+    
    1. In the Emulator Manager, click Create.
      2. 
+    
    2. Select a platform and click Next.
      3. 
+
+    
    3. To create a new template:
+    
        
+	
      • To create a new template from the beginning:
+        
        1. Click +.
          2. 
+            
        2. Define the features for the template.
          3. 
+            
        3. Click OK.
+            
          The new template is added to the list with a settings icon.
          4. 
+        
        • 
+	
      • To create a new template based on an existing one:
+        
        1. Select the template you want to clone.
          2. 
+            
        2. Click clone template (Clone icon).
          3. 
+            
        3. Make the desired changes.
          4. 
+            
        4. Click OK.
+            
          The new template is added to the list with a settings icon.
          5. 
+        
        • 
+    
      
+
    
+
    Figure: Template Configuration dialog
    
+
    Template Configuration dialog
    
+
+
    To manage the created templates:
    
 
 
      
-	
    • The selected emulator is booted after a few seconds.
      • 
+	
    • To edit a template, click edit template (Edit template), make the desired changes, and click OK. You can only edit the custom templates you have created.
      • 
+	
    • To delete a template, click delete (Delete). You can only delete the custom templates you have created.
      • 
 
    
 
-
    Figure: Launched emulator instance
    
+
    Managing and Launching Emulator Instances
    
 
-
    
+
    In the Emulator Manager, you can launch, edit, delete, reset, and export emulator instances:
    
 
+
      
+	
    1. Launch the Emulator Manager.
      2. 
+    
    2. Select an emulator instance from the list.
      3. 
+	
    3. Manage the instance:
 
        
-	
      • The debug and launch options are activated after the emulator has booted. The name of the emulator instance is displayed on the toolbar.
        • 
+
      • To launch the emulator, click Launch.
+
        The debug and launch options are activated after the emulator has booted. The name of the emulator instance is displayed on the Visual Studio toolbar.
        
+
        Emulator instance on Visual Studio toolbar
        • 
+
      • To edit an emulator, click Edit, make the desired changes, and click Confirm.
        • 
+
      • To delete an emulator, click Delete.
        • 
+
      • To reset an emulator, right-click it and select Reset.
        • 
+
      • To export an emulator, right-click it and select Export as. Specify the new image file location.
+	
        When you export the emulator instance, the state of the platform image is replicated.
        • 
 
      
-
-
      Figure: Activated debug option
      
-
-
      
-
-
       
      
-
-
+
      4. 
+
    
 
 
 
diff --git a/preview/html/tools/log_viewer.htm b/preview/html/tools/log_viewer.htm
index 9c58566..c4dccf4 100644
--- a/preview/html/tools/log_viewer.htm
+++ b/preview/html/tools/log_viewer.htm
@@ -15,74 +15,72 @@
     Log Viewer
 
 
-
+
 
 
 
 
    
 
   
    Log Viewer
    
 
-
    This topic explains how to insert logging methods to your code and check the logs of your application in the Log Viewer.
    
+
    You can debug your application by inserting logging methods to your application code, running the application, and checking the application logs in the Log Viewer tool.
    
 
-
    Viewing Logs in Log Tabs
    
+
    The Log Viewer helps you debug your application by capturing all the events logged by the platform and your application. The Log Viewer shows the logs through the dlog logging service. The service consists of the dlogutil and dlog library. You can also see logs with the dlogutil command in the CLI environment, and create log entries with the dlog library.
    
 
-
     If you want to open the Log Viewer, go to Tools > Tizen > Tizen Log Viewer in the Visual Studio menu.
    
+
    Figure: Log Viewer
    
+
    Log Viewer
    
 
-
    Figure: Log Viewer Menu
    
+
    The Log Viewer displays a log table consisting of the following fields:
    
 
-
    
-
-
     
    
-
-
    The Log Viewer helps you debug your application by capturing all the events logged by the platform and your application. The Log Viewer shows the logs through the dlog logging service. The service consists of the dlogutil and dlog library. You can also see logs with the dlogutil command in the CLI environment, and create log entries with the dlog library.
    
-
-
     
    
+
      
+	
    • Time: log time
      • 
+	
    • Level: priority level indicates the urgency of the log message
      • 
+	
    • Pid: process ID
      • 
+	
    • Tid: thread ID
      • 
+	
    • Tag: identification of the log message source
      • 
+	
    • Msg: log message
      • 
+
    
 
-
    Figure: Log Viewer
    
+
    Creating Log Messages
    
 
-
    
+
    You can create a log message in your application with the dlog library. Before using the dlog library, make sure you know which priorities and tags to use and how to send the message to the log device. With appropriate properties and tags, it is easy to filter and check messages.
    
 
-
    Creating a Log Message
    
+
    For more information, see the System Logs guide.
    
 
-
    You can create a log message in your application with the dlog library. Before using the dlog library, make sure you know which priorities and tags to use and how to send the message to the log device. With appropriate properties and tags, it is easy to filter and check the messages.
    
+
    Launching the Log Viewer
    
+
    To launch the Log Viewer, in the Visual Studio menu, go to Tools > Tizen > Tizen Log Viewer.
    
 
-
    For more information, see the System Logs guide.
    
+
    Figure: Log Viewer launch
    
+
    Log Viewer launch
    
 
 
    Understanding and Filtering Logs
    
 
-
    The log table consists of the following fields:
    
-
-
      
-	
    • Time: log time
      • 
-	
    • Level: priority level indicates the urgency of the log message
      • 
-	
    • Pid: process ID
      • 
-	
    • Tid: thread ID
      • 
-	
    • Tag: identification of the log message source
      • 
-	
    • Msg: log message
      • 
-
    
-
-
    Figure: Log table fields
    
-
-
    
 
    In the log table, you have the following options and functions:
    
 
 
      
 	
    • Log level filtering option
-	
      In the Log Viewer, you can filter the log messages using the V (verbose), D (debug), I (info), W (warning), E (error), and F (fatal) buttons to show specific log messages suitable to the selected type.
      
+	
      In the Log Viewer, you can filter the log messages using the V (verbose), D (debug), I (info), W (warning), E (error), and F (fatal) buttons to show the log messages matching the selected type.
      
 	
      • 
 	
    • Keyword filtering option
-	
      You can filter the log messages by selecting one of the PID, Tag, and Message options, or entering keywords in the bottom of the Log Viewer. The keywords must be separated by a space.
      
+	
      You can filter the log messages by selecting one of the PID, Tag, and Message options, or entering keywords in the bottom of the Log Viewer. The keywords must be separated by a space.
      
 	
      • 
 	
    • Scroll lock
-	
      The log table shows the latest logs by default. This can make you uncomfortable when checking the specified log. Enable scroll lock when checking a specified log.
      
+
      The log table shows the latest logs by default. While the application is running, the log table scrolls as new logs are added to the table. To stop the table from scrolling while you are checking a specific log, click the Scroll Lock button (Scroll lock button).
      
 	
      • 
 	
    • Clearing the table
-	
      You can remove all log messages from the log tab by clicking the Clear button.
      
+	
      You can remove all log messages from the log tab by clicking Clear.
      
 	
      • 
 	
    • Exporting logs to a file
-	
      You can export the current log messages in the Log Viewer and save them as a log file by clicking the Export button.
      
+	
      You can export the current log messages in the Log Viewer and save them as a log file by clicking Export.
      
 	
      • 
 
    
 
diff --git a/preview/html/tools/manifest_editor.htm b/preview/html/tools/manifest_editor.htm
index 5a913a1..0e24a67 100644
--- a/preview/html/tools/manifest_editor.htm
+++ b/preview/html/tools/manifest_editor.htm
@@ -15,49 +15,56 @@
     Tizen Manifest Editor
 
 
-
+
 
 
 
 
    
 
+
   
    Tizen Manifest Editor
    
 
-
    A Tizen .Net application project consists of exactly 1 manifest file, called tizen-manifest.xml, which is used to describe the application information. The manifest file is composed of XML elements, which include the root <manifest> element and its child elements representing application information, such as <version>, and <privileges>. The child elements are organized into a specific hierarchy. The elements can have attributes associated with them, providing more information about the element.
    
+
    A Tizen .NET application project contains a manifest file, called tizen-manifest.xml, which is used to describe the application information. The manifest file is composed of XML elements, which include the root <manifest> element and its child elements representing application information, such as <version>, and <privileges>. The child elements are organized into a specific hierarchy. The elements can have attributes associated with them, providing more information on the element.
    
 
-
    Editing the Manifest File
    
+
    Editing the Manifest File
    
 
-
    There are 2 different ways to edit the tizen-manifest.xml file:
    
+
    There are 2 different ways to edit the tizen-manifest.xml file:
    
 
 
      
-	
    • Use the text editor to modify the XML structure directly:
-	
      Figure: Text Editor
      
-
-	
      
+	
    • Use the manifest editor to modify the manifest in a form editor:
+	
      Double-click the tizen-manifest.xml file in the Solution Explorer view.
      
 
+	
      Figure: Manifest editor
      
+    
      Manifest editor
      
+	
      • 
+	
    • Use the text editor to modify the XML structure directly:
 	
        
-		
      1. Right-click the tizen-manifest.xml file in the Solution Explorer.
        2. 
-		
      2. Select Open with > XML (Text) Editor.
        3. 
+		
      3. Right-click the tizen-manifest.xml file in the Solution Explorer view.
        4. 
+		
      4. Select Open with > XML (Text) Editor.
        5. 
 	
      
+	
      Figure: Text editor
      
+	
      Text editor
      
 	
      • 
-	
    • Use the manifest editor to modify the manifest in a form editor:
-	
      Double-click the tizen-manifest.xml file in the Solution Explorer.
      
 
-	
      Figure: Manifest editor
      
-	
      • 
 
    
 
-
    
+
    Note
+The tizen-manifest.xml file must conform to both the standard XML file format and the Tizen .NET application specification requirements. Editing the manifest file XML structure with the text editor is intended for advanced users only. If the file does not conform to the standard and the requirements, errors can occur during installation.
    
 
-
    Note
    
-The tizen-manifest.xml file must conform to both the standard XML file format and the Tizen .Net application specification requirements. Editing the manifest file XML structure with the text editor is intended for advanced users only. If the file does not conform to the standard and requirements, errors can occur during installation.
    
+
    Manifest Element Hierarchy
    
 
-
    Manifest Element Hierarchy
    
+
    The Tizen .NET application manifest file consists of XML elements organized in a hierarchy. The following tree structure shows the relationship between the elements of the tizen-manifest.xml file.
    
 
-
    The Tizen .Net application manifest file consists of XML elements organized in a hierarchy. The following tree structure shows the relationship between the elements of the tizen-manifest.xml file.
    
-
-
+
    @@ -69,129 +76,129 @@ The tizen-manifest.xml file must conform to both the stan
 	
-			
+			
-			
-			
+			
+			
-			
-			
+			
+			
-			
-			
+			
+			
-			
-			
+			
+			
-			
-			
-			
+			
+			
+			
-			
-			
-			
+			
+			
+			
-			
-			
-			
+			
+			
+			
-			
-			
-			
+			
+			
+			
-			
-			
-			
+			
+			
+			
-			
-			
-			
+			
+			
+			
-			
-			
+			
+			
-			
-			
-			
+			
+			
+			
-			
-			
-			
-			
+			
+			
+			
+			
-			
-			
-			
-			
+			
+			
+			
+			
-			
-			
+			
+			
-			
-			
-			
+			
+			
+			
-			
-			
-			
-			
+			
+			
+			
+			
-			
-			
-			
-			
+			
+			
+			
+			
-			
-			
-			
-			
+			
+			
+			
+			
-			
-			
+			
+			
-			
-			
-			
+			
+			
+			
-			
-			
+			
+			
    
 	
 		
 		

 	
 		
    <manifest><manifest>
 		
    
 		
     <author> <author>
 		
    
 		
     <description> <description>
 		
    
 		
     <profile> <profile>
 		
    
 		
     <ui-application> <ui-application>
 		
    
 		
      <label>  <label>
 		
    
 		
      <icon>  <icon>
 		
    
 		
      <app-control>  <app-control>
 		
    
 		
      <metadata>  <metadata>
 		
    
 		
      <datacontrol>  <datacontrol>
 		
    
 		
      <background-category>  <background-category>
 		
    
 		
     <shortcut-list> <shortcut-list>
 		
    
 		
      <shortcut>  <shortcut>
 		
    
 		
       <icon>   <icon>
 		
    
 		
       <label>   <label>
 		
    
 		
     <account> <account>
 		
    
 		
      <account-provider>  <account-provider>
 		
    
 		
       <icon>   <icon>
 		
    
 		
       <label>   <label>
 		
    
 		
       <capability>   <capability>
 		
    
 		
     <privileges> <privileges>
 		
    
 		
      <privilege>  <privilege>
 		
    
 		
     <feature> <feature>
 		
    
 	    
 
    
 
-
    Manifest Elements
    
+
    Manifest Elements
    
 
-
    The following sections summarize the elements used in the tizen-manifest.xml file of the .Net application.
    
+
    The following sections summarize the elements used in the tizen-manifest.xml file of a Tizen .NET application.
    
 
 
    <manifest> Element
    
 
-
    This element contains the manifest information of the Tizen .Net application. The <manifest> element is an easily readable description of the Tizen package and serves as a container for the other elements of the configuration document.
    
+
    This element contains the manifest information for a Tizen .NET application. The <manifest> element is an easily-readable description of the Tizen package and serves as a container for the other elements of the configuration document.
    
 
-
    For more information on the relationship between the elements, see the element hierarchy.
    
+
    For more information on the relationship between the elements, see the element hierarchy.
    
 
-
    Occurrences:
    
+
    Occurrences:
    
 
 
      
 	
    • 
@@ -199,7 +206,7 @@ The tizen-manifest.xml file must conform to both the stan
 	
      • 
 
    
 
-
    Expected children (in the following order):
    
+
    Expected children (in the following order):
    
 
 
@@ -242,36 +249,36 @@ The tizen-manifest.xml file must conform to both the stan
 	
    
 	
 
    
 
-
    Figure: Editing the <manifest> element in the manifest editor
    
+
    Figure: Editing the <manifest> element in the manifest editor
    
 
-
    
+
    Editing the manifest element in the manifest editor
    
 
-
    Attributes:
    
+
    Attributes:
    
 
 
      
 	
    • 
 	
      api-version
      
 
-	
      API version number for the application (available value: number in the "x.y.z" format, where z is optional, for example, 3.0)
      
+	
      API version number for the application (available value: number in the "x.y.z" format, where z is optional, for example, 3.0)
      
 	
      • 
 	
    • 
 	
      install-location
      
 
-	
      Installation location for the application (available value: "auto")
      
+	
      Installation location for the application (available value: "auto")
      
 
-	
      NoteThis attribute is read-only. Do not attempt to modify it.
      
+	
      NoteThis attribute is read-only. Do not attempt to modify it.
      
 	
      • 
 	
    • 
 	
      package
      
 
-	
      Package of the application (available value: "org.tizen.applicationName")
      
+	
      Package of the application (available value: "org.tizen.<applicationName>")
      
 	
      • 
 	
    • 
 	
      type
      
 
-	
      Package type of the application (available value: "tpk")
      
+	
      Package type of the application (available value: "tpk")
      
 
-	
      NoteThis attribute is read-only. Do not attempt to modify it.
      
+	
      NoteThis attribute is read-only. Do not attempt to modify it.
      
 	
      • 
 	
    • 
 	
      version
      
@@ -280,27 +287,28 @@ The tizen-manifest.xml file must conform to both the stan
 	
      • 
 
    
 
-
    For example:
    
+
    For example:
    
 
 
     <manifest xmlns="http://tizen.org/ns/packages" api-version="3.0" package="org.tizen.uiapp" version="1.0.0">
-   <author>.....</author>
-   <description>.....</description>
-   <profile name="mobile"/>
-   <ui-application>.....</ui-application>
-   <shortcut-list>.....</shortcut-list>
-   <account>.....</account>
-   <privileges>.....</privileges>
-   <feature>.....</feature>
-</manifest>
    
+   <author>.....</author>
+   <description>.....</description>
+   <profile name="common"/>
+   <ui-application>.....</ui-application>
+   <shortcut-list>.....</shortcut-list>
+   <account>.....</account>
+   <privileges>.....</privileges>
+   <feature>.....</feature>
+</manifest>
+

    <author> Element

    This element represents the creator of the Tizen package.

    -

    For more information on the relationship between the elements, see the element hierarchy.

    +

    For more information on the relationship between the elements, see the element hierarchy.

    -

    Occurrences:

    +

    Occurrences:

    • @@ -308,7 +316,7 @@ The tizen-manifest.xml file must conform to both the stan
    -

    Attributes:

    +

    Attributes:

    • @@ -323,30 +331,31 @@ The tizen-manifest.xml file must conform to both the stan
    -

    Expected value:

    +

    Expected value:

    • Package creator name in string
    -

    For example:

    +

    For example:

    -<author email="email@email.com" href="http://test.com">author</author>
    +<author email="email@email.com" href="http://test.com">author</author> +

    <description> Element

    This element contains an easily readable description of the Tizen package.

    -

    For more information on the relationship between the elements, see the element hierarchy.

    +

    For more information on the relationship between the elements, see the element hierarchy.

    -

    Occurrences:

    +

    Occurrences:

    • 1 or more (optional)
    -

    Attributes:

    +

    Attributes:

    • xml:lang @@ -355,13 +364,13 @@ The tizen-manifest.xml file must conform to both the stan
    -

    Expected value:

    +

    Expected value:

    • Description value in string
    -

    For example:

    +

    For example:

     <description xml:lang="en-us">This is a sample</description>
@@ -369,24 +378,24 @@ The tizen-manifest.xml file must conform to both the stan
 
 
    <profile> Element
    
 
-
    In Tizen .Net application, the <profile> element set to common. This element has no child elements.
    
+
    In a Tizen .NET application, the <profile> element must be set to common. This element has no child elements.
    
 
-
    Occurrences:
    
+
    Occurrences:
    
 
 
      
 	
    • 1
      • 
 
    
 
-
    Attributes:
    
+
    Attributes:
    
 
 
      
 	
    • name
 
-	
      Profile name (available values: common, mobile, tv)
      
+	
      Profile name (available values: common, mobile, tv)
      
 	
      • 
 
    
 
-
    For example:
    
+
    For example:
    
 
 
     <profile name="common"/>
@@ -394,17 +403,17 @@ The tizen-manifest.xml file must conform to both the stan
 
 
    <ui-application> Element
    
 
-
    This element contains the manifest information of a Tizen .Net UI application with a graphical user interface (GUI).
    
+
    This element contains the manifest information for a Tizen .NET UI application with a graphical user interface (GUI).
    
 
-
    For more information on the relationship between the elements, see the element hierarchy.
    
+
    For more information on the relationship between the elements, see the element hierarchy.
    
 
-
    Occurrences:
    
+
    Occurrences:
    
 
 
      
 	
    • 1 or more (optional)
      • 
 
    
 
-
    Expected children (in the following order):
    
+
    Expected children (in the following order):
    
 
 
@@ -439,7 +448,7 @@ The tizen-manifest.xml file must conform to both the stan
 	
    
 	
 
    
 
-
    Attributes:
    
+
    Attributes:
    
 
 
      
 	
    • appid
@@ -452,63 +461,64 @@ The tizen-manifest.xml file must conform to both the stan
 	
      Application executable file path (string)
      
 	
      • 
 	
    • hw-acceleration
-	
      Indicates the application hardware acceleration status (available values: not defined (depends on the system setting), on (use hardware acceleration), off (do not use hardware acceleration))
      
+	
      Indicates the application hardware acceleration status (available values: not defined (depends on the system setting), on (use hardware acceleration), off (do not use hardware acceleration))
      
 
 	
      By default, this value is not defined.
      
 	
      • 
 	
    • launch_mode
-	
      Application launch mode (available values: single (launched as a main application), group (launched as a sub application), caller (caller application))
      
+	
      Application launch mode (available values: single (launched as a main application), group (launched as a sub application), caller (caller application))
      
 
-	
      By default, this value is set to single.
      
+	
      By default, this value is set to single.
      
 	
      • 
 	
    • multiple
-	
      Indicates whether the application can be launched as a multiple (available values: true, false)
      
+	
      Indicates whether the application can be launched as a multiple (available values: true, false)
      
 
-	
      NoteThis attribute is read-only. Do not attempt to modify it.
      
+	
      NoteThis attribute is read-only. Do not attempt to modify it.
      
 	
      • 
 	
    • nodisplay
-	
      Indicates whether the application is shown in the app-tray (available values: true, false)
      
+	
      Indicates whether the application is shown in the app tray (available values: true, false)
      
 	
      • 
 	
    • taskmanage
-	
      Indicates whether the application is shown in the task manager (available values: true, false)
      
+	
      Indicates whether the application is shown in the task manager (available values: true, false)
      
 	
      • 
 	
    • type
-	
      Tizen application type (available values: dotnet)
      
+	
      Tizen application type (available value: dotnet)
      
 
-	
      NoteThis attribute is read-only. Do not attempt to modify it.
      
+	
      NoteThis attribute is read-only. Do not attempt to modify it.
      
 	
      • 
 
    
 
-
    For example:
    
+
    For example:
    
 
 
    -<ui-application appid="org.tizen.uiapp" exec="uiapp" hw-acceleration="on" launch_mode="single" 
-                multiple="false" nodisplay="false" taskmanage="true" type="dotnet">
-   <label>uiapplication</label>
-   <label xml:lang="en-gb">testlang</label>
-   <icon>uiapp.png</icon>
-   <app-control>
-      <operation name="http://tizen.org/appcontrol/operation/dial"/>
-      <mime name="application/vnd.ms-excel"/>
-   </app-control>
-   <metadata key="testkey" value="testvalue"/>
-   <datacontrol access="ReadOnly" 
-                providerid="http://uiapp.com/datacontrol/provider/uiapp" type="Sql"/>
-</ui-application>
    
+<ui-application appid="org.tizen.uiapp" exec="uiapp" hw-acceleration="on" launch_mode="single"
+                multiple="false" nodisplay="false" taskmanage="true" type="dotnet">
+   <label>uiapplication</label>
+   <label xml:lang="en-gb">testlang</label>
+   <icon>uiapp.png</icon>
+   <app-control>
+      <operation name="http://tizen.org/appcontrol/operation/dial"/>
+      <mime name="application/vnd.ms-excel"/>
+   </app-control>
+   <metadata key="testkey" value="testvalue"/>
+   <datacontrol access="ReadOnly"
+                providerid="http://uiapp.com/datacontrol/provider/uiapp" type="Sql"/>
+</ui-application>
+
    
 
 
    <shortcut-list> Element
    
 
 
    This element contains the shortcut template list used for adding a shortcut to the home screen.
    
 
-
    For more information on the relationship between the elements, see the element hierarchy.
    
+
    For more information on the relationship between the elements, see the element hierarchy.
    
 
-
    Occurrences:
    
+
    Occurrences:
    
 
 
      
 	
    • 1 (optional)
      • 
 
    
 
-
    Expected children:
    
+
    Expected children:
    
 
 
@@ -523,25 +533,25 @@ The tizen-manifest.xml file must conform to both the stan
 	
    
 	
 
    
 
-
    For example:
    
+
    For example:
    
 
 
     <shortcut-list>
-   <shortcut>.....</shortcut>
+   <shortcut>.....</shortcut>
 </shortcut-list>
 
    
 
-
    <shortcut> Element
    
+
    <shortcut> Element
    
 
 
    This element contains the information that indicates the shortcut for the application on the home screen.
    
 
-
    Occurrences:
    
+
    Occurrences:
    
 
 
      
 	
    • 1 (optional)
      • 
 
    
 
-
    Expected children:
    
+
    Expected children:
    
 
 
@@ -560,7 +570,7 @@ The tizen-manifest.xml file must conform to both the stan
 	
    
 	
 
    
 
-
    Attributes:
    
+
    Attributes:
    
 
 
      
 	
    • appid
@@ -572,38 +582,38 @@ The tizen-manifest.xml file must conform to both the stan
 	
    • extra_data
 	
      Data for user content (string)
      
 
-	
      Shortcut element property in the manifest file
      
+	
      Shortcut element property in the manifest file.
      
 	
      • 
 	
    • extra_key
 	
      Key for user content (string)
      
 
-	
      Shortcut element property in the manifest file
      
+	
      Shortcut element property in the manifest file.
      
 	
      • 
 
    
 
-
    For example:
    
+
    For example:
    
 
 
     <shortcut appid="org.example.shortcut" extra_data="data" extra_key="key">
-   <icon>shortcut.png</icon>
-   <label>shortcut</label>
-   <label xml:lang="en-us">short</label>
+   <icon>shortcut.png</icon>
+   <label>shortcut</label>
+   <label xml:lang="en-us">short</label>
 </shortcut>
 
    
 
 
    <account> Element
    
 
-
    This element contains a set of user accounts and account provider-related information in the Tizen application.
    
+
    This element contains a set of user accounts and account provider-related information for a Tizen application.
    
 
-
    For more information on the relationship between the elements, see the element hierarchy.
    
+
    For more information on the relationship between the elements, see the element hierarchy.
    
 
-
    Occurrences:
    
+
    Occurrences:
    
 
 
      
 	
    • 1 (optional)
      • 
 
    
 
-
    Expected children:
    
+
    Expected children:
    
 
 
@@ -618,19 +628,19 @@ The tizen-manifest.xml file must conform to both the stan
 	
    
 	
 
    
 
-
    For example:
    
+
    For example:
    
 
 
     <account>
-   <account-provider>.....</account-provider>
+   <account-provider>.....</account-provider>
 </account>
 
    
 
-
    <account-provider> Element
    
+
    <account-provider> Element
    
 
-
    This element contains a specific service provider or user account protocol-related information.
    
+
    This element contains specific service provider or user account protocol-related information.
    
 
-
    Expected children:
    
+
    Expected children:
    
 
 
@@ -653,7 +663,7 @@ The tizen-manifest.xml file must conform to both the stan
 	
    
 	
 
    
 
-
    Attributes:
    
+
    Attributes:
    
 
 
      
 	
    • appid
@@ -663,60 +673,60 @@ The tizen-manifest.xml file must conform to both the stan
 	
      This can be used for launching or terminating the application explicitly.
      
 	
      • 
 	
    • multiple-accounts-support
-	
      Indicates whether multiple accounts are supported (available values: true, false)
      
+	
      Indicates whether multiple accounts are supported (available values: true, false)
      
 	
      • 
 	
    • providerid
 	
      ID of the account provider (string)
      
 	
      • 
 
    
 
-
    For example:
    
+
    For example:
    
 
 
     <account-provider appid="org.tizen.uiapp" multiple-accounts-support="false" providerid="org.tizen.uiapp">
-   <icon>.....</icon>
-   <label>.....</label>
-   <capability>.....</capability>
+   <icon>.....</icon>
+   <label>.....</label>
+   <capability>.....</capability>
 </account-provider>
 
    
 
-
    <icon> Element
    
+
    <icon> Element
    
 
-
    This element contains the account provider icon image. Since the icons are used in the device under settings, the account icons are placed in a shared directory.
    
+
    This element contains the account provider icon image. Since the icons are used on the device under Settings > Accounts, place them in a shared directory.
    
 
-
    Attributes:
    
+
    Attributes:
    
 
 
      
 	
    • section
 
-	
      Usage information of the icon image (available values: account (image size: 72 x 72 for density xhigh and 48 x 48 for density high), account-small (image size: 45 x 45 for density xhigh and 30 x 30 for density high))
      
+	
      Usage information for the icon image (available values: account (image size: 72 x 72 for density xhigh and 48 x 48 for density high), account-small (image size: 45 x 45 for density xhigh and 30 x 30 for density high))
      
 	
      • 
 
    
 
-
    Expected value:
    
+
    Expected value:
    
 
 
      
 	
    • Icon file name
      • 
 
    
 
-
    For example:
    
+
    For example:
    
 
 
     <icon section="account">uiapp.png</icon>
 <icon section="account-small">uiapp.png</icon>
 
    
 
-
    <capability> Element
    
+
    <capability> Element
    
 
-
    This element contains the account provider capability. The capabilities are defined as http://<VENDOR_INFORMATION>/account/capability/<NAME>.
    
+
    This element contains the account provider capability. The capabilities are defined as http://<VENDOR_INFORMATION>/account/capability/<NAME>.
    
 
-
    Expected value:
    
+
    Expected value:
    
 
 
      
 	
    • IRI string
      • 
 
    
 
-
    For example:
    
+
    For example:
    
 
 
     <capability>http://tizen.org/account/capability/calendar</capability>
@@ -724,25 +734,25 @@ The tizen-manifest.xml file must conform to both the stan
 
 
    <privileges> Element
    
 
-
    This element contains a set of required privileges for the Tizen application.
    
+
    This element contains the set of required privileges for a Tizen application.
    
 
-
    Applications that use sensitive APIs must declare the required privileges in the tizen-manifest.xml file.
    
+
    Applications that use sensitive APIs must declare the required privileges in the tizen-manifest.xml file.
    
 
-
    Click Add to open the Add Privilege dialog.
    
+
    Click Add to open the Privileges dialog.
    
 
-
    Figure: Editing the <privileges> element in the manifest editor
    
+
    Figure: Editing the <privileges> element in the manifest editor
    
 
-
    
+
    
 
-
    For more information on the relationship between the elements, see the element hierarchy.
    
+
    For more information on the relationship between the elements, see the element hierarchy.
    
 
-
    Occurrences:
    
+
    Occurrences:
    
 
 
      
 	
    • 1 (optional)
      • 
 
    
 
-
    Expected children:
    
+
    Expected children:
    
 
 
@@ -757,25 +767,25 @@ The tizen-manifest.xml file must conform to both the stan
 	
    
 	
 
    
 
-
    For example:
    
+
    For example:
    
 
 
     <privileges>
-   <privilege>.....</privilege>
+   <privilege>.....</privilege>
 </privileges>
 
    
 
-
    <privilege> Element
    
+
    <privilege> Element
    
 
-
    This element contains the required privileges for the Tizen application.
    
+
    This element contains a required privilege for a Tizen application.
    
 
-
    Occurrences:
    
+
    Occurrences:
    
 
 
      
 	
    • 1 or more (optional)
      • 
 
    
 
-
    Expected value:
    
+
    Expected value:
    
 
 
    Name (mandatory, the URI of the Device API privilege)
    
 
@@ -787,7 +797,7 @@ The tizen-manifest.xml file must conform to both the stan
 	
  • http://tizen.org/privilege/account.read
    • 
 
 
-
    For example:
    
+
    For example:
    
 
 
     <privilege>http://tizen.org/privilege/application.admin</privilege>
@@ -801,41 +811,39 @@ The tizen-manifest.xml file must conform to both the stan
 
 
    The element is used to define the hardware and software components for the Tizen application. In order to use or access an API that is specialized for each vendor or platform, the feature must be declared. This element has no child elements.
    
 
-
    Figure: Editing the <feature> element in the manifest editor
    
+
    Figure: Editing the <feature> element in the manifest editor
    
 
-
    
+
    Editing the feature element in the manifest editor
    
 
-
    For more information on the relationship between the elements, see the element hierarchy.
    
+
    For more information on the relationship between the elements, see the element hierarchy.
    
 
-
    Occurrences:
    
+
    Occurrences:
    
 
 
      
 	
    • 1 or more (optional)
      • 
 
    
 
-
    Attributes:
    
+
    Attributes:
    
 
 
      
-	
    • name (mandatory, a feature key URI)
+	
    • name (mandatory, a feature key URI)
 
-	
      Item name used in feature-based filtering in the Tizen Store, for example, "http://tizen.org/feature/camera", "http://tizen.org/feature/fmradio"
      
+	
      Item name used in feature-based filtering in the Tizen Store, for example, "http://tizen.org/feature/camera" or "http://tizen.org/feature/fmradio"
      
 	
      • 
 
    
 
-
    Expected value:
    
+
    Expected value:
    
 
 
      
 	
    • true
      • 
 
    
 
-
    For example:
    
+
    For example:
    
 
 
     <feature name="http://tizen.org/feature/camera">true</privilege>
-<feature name="http://tizen.org/feature/fmradio">true</privilege>
    
-
-
-
+<feature name="http://tizen.org/feature/fmradio">true</privilege>
+
    
 
 
 
diff --git a/preview/html/tools/manifest_elements.htm b/preview/html/tools/manifest_elements.htm
index e2638d8..56ce5bb 100644
--- a/preview/html/tools/manifest_elements.htm
+++ b/preview/html/tools/manifest_elements.htm
@@ -15,30 +15,42 @@
     Using Additional Manifest Elements
 
 
-
+
 
 
 
 
    
 
   
    Using Additional Manifest Elements
    
 
-
    The following sections summarize some of the common child elements used in the tizen-manifest.xml file of the .Net application.
    
+
    The following sections summarize some of the common child elements used in the tizen-manifest.xml file of a Tizen .NET application.
    
 
-
    <app-control> Element
    
+
    <app-control> Element
    
 
 
    This element represents Tizen application control configuration information.
    
 
-
    For more information on the relationship between the elements, see the element hierarchy.
    
+
    For more information on the relationship between the elements, see the element hierarchy.
    
 
-
    Occurrences:
    
+
    Occurrences:
    
 
 
      
 	
    • 1 or more (optional)
      • 
 
    
 
-
    Expected children:
    
+
    Expected children:
    
 
 
@@ -61,13 +73,13 @@
 	
    
 	
 
    
 
-
    For example:
    
+
    For example:
    
 
 
     <app-control>
-   <operation name="http://tizen.org/appcontrol/operation/compose"/>
-   <uri name="testuristring"/>
-   <mime name="application/pdf"/>
+   <operation name="http://tizen.org/appcontrol/operation/compose"/>
+   <uri name="testuristring"/>
+   <mime name="application/pdf"/>
 </app-control>
 
    
 
@@ -75,16 +87,16 @@
 
 
    This element represents the operation type of the application control.
    
 
-
    Attributes:
    
+
    Attributes:
    
 
 
      
 	
    • name
 
-	
      Name of the application control, for example, http://tizen.org/appcontrol/operation/compose
      
+	
      Name of the application control, for example, http://tizen.org/appcontrol/operation/compose
      
 	
      • 
 
    
 
-
    For example:
    
+
    For example:
    
 
 
     <operation name="http://tizen.org/appcontrol/operation/compose"/>
@@ -94,7 +106,7 @@
 
 
    This element represents the URI scheme of the application control.
    
 
-
    Attributes:
    
+
    Attributes:
    
 
 
      
 	
    • name
@@ -103,7 +115,7 @@
 	
      • 
 
    
 
-
    For example:
    
+
    For example:
    
 
 
     <uri name="testuristring"/>
@@ -113,7 +125,7 @@
 
 
    This element represents the MIME type of the application control.
    
 
-
    Attributes:
    
+
    Attributes:
    
 
 
      
 	
    • name
@@ -122,25 +134,25 @@
 	
      • 
 
    
 
-
    For example:
    
+
    For example:
    
 
 
     <mime name="application/pdf"/>
 
    
 
-
    <background-category> Element
    
+
    <background-category> Element
    
 
-
    This element represents the category of the application running on the background.
    
+
    This element represents the category of an application that runs in the background.
    
 
-
    For more information on the relationship between the elements, see the element hierarchy.
    
+
    For more information on the relationship between the elements, see the element hierarchy.
    
 
-
    Occurrences:
    
+
    Occurrences:
    
 
 
      
 	
    • 1 or more (optional)
      • 
 
    
 
-
    Attributes:
    
+
    Attributes:
    
 
 
      
 	
    • value
@@ -149,25 +161,25 @@
 	
      • 
 
    
 
-
    For example:
    
+
    For example:
    
 
 
     <background-category value="download"/>
 
    
 
-
    <datacontrol> Element
    
+
    <datacontrol> Element
    
 
 
    This element represents configuration information for the Tizen data controls.
    
 
-
    For more information on the relationship between the elements, see the element hierarchy.
    
+
    For more information on the relationship between the elements, see the element hierarchy.
    
 
-
    Occurrences:
    
+
    Occurrences:
    
 
 
      
 	
    • 1 or more (optional)
      • 
 
    
 
-
    Attributes:
    
+
    Attributes:
    
 
 
      
 	
    • access
@@ -182,49 +194,49 @@
 	
      • 
 
    
 
-
    For example:
    
+
    For example:
    
 
 
     <datacontrol access="WriteOnly" providerid="http://uiapp.com/datacontrol/provider/uiapp" type="Sql"/>
 
    
 
-
    <icon> Element
    
+
    <icon> Element
    
 
 
    This element represents the icon relative or absolute file path for the Tizen application.
    
 
-
    For more information on the relationship between the elements, see the element hierarchy.
    
+
    For more information on the relationship between the elements, see the element hierarchy.
    
 
-
    Occurrences:
    
+
    Occurrences:
    
 
 
      
 	
    • 1 (optional)
      • 
 
    
 
-
    Expected value:
    
+
    Expected value:
    
 
 
      
 	
    • Icon path
      • 
 
    
 
-
    For example:
    
+
    For example:
    
 
 
     <icon>testicon.png</icon>
 
    
 
-
    <label> Element
    
+
    <label> Element
    
 
 
    This element represents the label value for the Tizen application. It is a set of human readable names for the Tizen application according to the language.
    
 
-
    For more information on the relationship between the elements, see the element hierarchy.
    
+
    For more information on the relationship between the elements, see the element hierarchy.
    
 
-
    Occurrences:
    
+
    Occurrences:
    
 
 
      
 	
    • 1 or more (optional)
      • 
 
    
 
-
    Attributes:
    
+
    Attributes:
    
 
 
      
 	
    • xml:lang
@@ -233,32 +245,32 @@
 	
      • 
 
    
 
-
    Expected value:
    
+
    Expected value:
    
 
 
      
 	
    • Label value in string
      • 
 
    
 
-
    For example:
    
+
    For example:
    
 
 
     <label>testlabel</label>
 <label xml:lang="en-gb">testlabel</label>
 
    
 
-
    <metadata> Element
    
+
    <metadata> Element
    
 
 
    This element represents user-defined key-value pairs for the application.
    
 
-
    For more information on the relationship between the elements, see the element hierarchy.
    
+
    For more information on the relationship between the elements, see the element hierarchy.
    
 
-
    Occurrences:
    
+
    Occurrences:
    
 
 
      
 	
    • 1 or more (optional)
      • 
 
    
 
-
    Attributes:
    
+
    Attributes:
    
 
 
      
 	
    • key
@@ -270,10 +282,11 @@
 	
      • 
 
    
 
-
    For example:
    
+
    For example:
    
 
 
    -<metadata key="testkey" value="testvalue"/>
    
+<metadata key="testkey" value="testvalue"/>
+
    
 
 
 
diff --git a/preview/html/tools/project_wizard.htm b/preview/html/tools/project_wizard.htm
index 222feea..af0c950 100644
--- a/preview/html/tools/project_wizard.htm
+++ b/preview/html/tools/project_wizard.htm
@@ -15,80 +15,48 @@
     Project Wizard
 
 
-
+
 
 
    
-
    
-
    
-
    Content
    
-
-
-
    
-
    
 
    
 
 
    
 
   
    Project Wizard
    
-
    The Project Wizard of Visual Studio Tools for Tizen is a tool that is used to create a Tizen .Net application project.
    
-
-
    The Visual Studio Tools for Tizen provides 3 project templates. When you create a new project, you can select a specific template, which the Project Wizard uses to automatically create basic functionalities for the application. The default project files and folders are also created.
    
-
-
    In the Project Wizard, you can select a templates and profile to create the project. In addition, you can set basic project properties, such as the project name, package name and location.
    
+
    The Project Wizard in Visual Studio Tools for Tizen is used to create a Tizen .NET application project.
    
 
-
    To open the Project Wizard, select File > New > Project > Templates > Visual C# > Tizen.
    
+
    In the Project Wizard, you can select a template and profile to create the project. In addition, you can set basic project properties, such as the project name, package name, and location.
    
 
-
    Template
    
-
-
    You can select a template for your project. The Project Wizard creates the project based on the selected template.
    
-
-
    Figure: Selecting the template
    
-
-
    
-
-
    Visual Studio Tools for Tizen provides 3 templates with a basic structure where you can start the native application project:
    
+
    The Project Wizard provides 3 project templates:
    
 
 
      
-	
    • Blank App (Tizen Xamarin.Forms Portable)
-
-	
        
-		
      • Use this template for creating a Tizen Xamarin Application (mobile and TV)
        • 
-		
      • Also use this template in case of adding Tizen Project to Xamarin Forms solution.
        • 
-	
      
-	
      • 
-	
    • Blank App (Tizen Xamarin.Forms Single)
-	
        
-		
      • Use this for creating a Tizen Xamarin Application in a single project without PCL (Portable Class Library).
        • 
-	
      
-	
      • 
-	
    • Class Library (Tizen)
-	
        
-		
      • Use this for creating a blank class library.
        • 
-	
      
-	
      • 
+
    • Blank App (Tizen Xamarin.Forms Portable): Template project for creating a Tizen Xamarin Application (for mobile and TV devices). Also use this template for adding a Tizen project to a Xamarin.Forms solution.
      • 
+
    • Blank App (Tizen Xamarin.Forms Single): Template project for creating a Tizen Xamarin Application in a single project without PCL (Portable Class Library).
      • 
+
    • Class Library (Tizen): Template project for creating a blank class library.
      • 
 
    
 
-
    After selecting a template and setting the location in your local repository, Click OK.
    
-
-
    Profile
    
-
-
    In case of Blank App (Tizen Xamarin.Forms Portable), the Tizen Project Wizard is shown for setting the project name and selecting the profile that you want to add in your solution.
    
-
-
    Figure: Selecting the profile
    
+
    When you create a new project with a specific template, the Project Wizard  automatically creates basic functionalities for the application based on the template. The default project files and folders are also created.
    
 
-
    
-
-
    To move to the next step, select the profile, and click OK.
    
-
-
    The solution illustrated in the following figure contains both profiles (mobile and TV).
    
-
-
    Figure: Solution containing mobile and TV profiles
    
-
-
    
+
    To create a Tizen .NET application project:
    
 
+
      
+	
    1. To open the Project Wizard:
+		
        
+		
      1. In the Visual Studio menu, go to File > New > Project > Templates > Visual C# > Tizen.
        2. 
+		
      2. Select a template for your project.
+		
        The Project Wizard creates the project based on the selected template.
        3. 
+		
      3. Set the basic project properties, such as the project name and its location in your local repository, and click OK.
        4. 
+		
      
+		
      Selecting the template
      
+	
      2. 
+	
    2. If you selected the Blank App (Tizen Xamarin.Forms Portable) template, the Tizen Project Wizard dialog opens.
+	
      Define the package name, select the profiles that you want to add to your solution, and click OK.
      
+	
      Tizen Project Wizard dialog
      3. 
+
    
+
+
    The following figure shows a new .NET application project solution that contains both mobile and TV profiles.
    
+
    Figure: Solution with mobile and TV profiles
    
+
    Solution with mobile and TV profiles
    
 
 
 
diff --git a/preview/html/tools/tools_overview.htm b/preview/html/tools/tools_overview.htm
index 37d3148..3c092d6 100644
--- a/preview/html/tools/tools_overview.htm
+++ b/preview/html/tools/tools_overview.htm
@@ -12,7 +12,7 @@
     
     
     
-    Overview
+    Visual Studio Tools for Tizen
 
 
 
@@ -22,28 +22,26 @@
 
 
    
 
- 
    Overview
    
-
-
    Visual Studio Tools for Tizen Preview provides Tizen-specific tools to improve your productivity:
    
+ 
    Visual Studio Tools for Tizen
    
 
+
    Visual Studio Tools for Tizen Preview provides Tizen-specific tools to improve your productivity:
    
 
      
-	
    • Project Wizard
      
-	The Project Wizard is a tool that is used to create a Tizen .NET application project.
      • 
-	
    • Certificate Registration
      
-	The certificates can be created, edited, removed, and set as active in the Certificate Manager. The active certificates are used when packaging your application.
      • 
-	
    • Tizen Manifest Editor
      
-	The Tizen Manifest Editor is a tool that is used to edit Tizen manifest file, called tizen-manifest.xml, which is used to describe the application information. 
      • 
-	
    • Emulator Manager
      
-	The Emulator Manager provides emulators to run your application in a virtual environment.
      • 
-	
    • Emulator Control Panel
      
-	The Emulator Control panel allows you to run the application in the emulator, and test a variety of user scenarios, such as network access, audio input and out, and text messages. 
      • 
-	
    • Device Manager
      
-	The Device Manager is a standalone tool that provides information of connected Tizen devices or emulators for application debugging.
      • 
-	
    • Log Viewer
      
-	The Log Viewer helps you debug your application by capturing all the events logged by the platform and your application.
      • 
-	
-	
    • API and Privilege Checker
      
-	The API Checker tool checks for API and privilege usage violations in the application code. It helps you to identify and fix potential problems in the application code related to API and privilege use.
      • 
+	
    • Project Wizard
+	
      The Project Wizard is used to create a Tizen .NET application project. You can select from various project templates that make it easier for you to start coding your application. When you create a new project with a specific template, the Project Wizard uses it to automatically create basic functionalities and default project files and folders for the application.
      • 
+	
    • Certificate Manager
+	
      The Certificate Manager is used to create a certificate profile and register author and distributor certificates. Before installing your application on a device or submitting it to the Tizen Store, you must sign it with a certificate profile while packaging your application.
      • 
+	
    • Tizen Manifest Editor
+	
      The manifest editor allows you to edit the Tizen application manifest with a text or form editor. The application manifest contains the application configuration, including specific features and more general runtime settings.
      • 
+	
    • Emulator Manager
+	
      The Emulator Manager allows you to create multiple Tizen emulator instances, for testing your application in an environment similar to a real device.
      • 
+	
    • Emulator Control Panel
+	
      The emulator controls allow you to control the emulator instance and test a variety of user scenarios, such as network access, audio input and output, and text messaging.
      • 
+	
    • API and Privilege Checker
+	
      The API Checker tool checks for API and privilege usage violations in the application code. It helps you to identify and fix potential problems in the application code related to API and privilege use.
      • 
+	
    • Device Manager
+	
      The Tizen Device Manager is used to manage connected Tizen devices and emulator instances. You can also browse files on the device, and transfer files between it and the host computer.
      • 
+	
    • Log Viewer
+	
      The log viewer allows you to check the logs of your application based on the logging methods you have inserted into your code. It helps you to debug your application by capturing all the events logged by the platform and your application.
      • 
 
    
 
 
diff --git a/preview/index.xml b/preview/index.xml
index 4da14ea..2e13d15 100644
--- a/preview/index.xml
+++ b/preview/index.xml
@@ -4,19 +4,17 @@
 
 
 
-
-	
-	
+
+	
 	
 
-
-	
+
 	
 	
-	
+	
+	
 
 
-	
 	
 	
 	
@@ -24,8 +22,8 @@
 	
 	
 	
+	
 	
 	
-	
 
 
-- 
2.7.4