From 40678c96046921d00a7dcdaad75400b103bee2fd Mon Sep 17 00:00:00 2001 From: "bg.chun" Date: Mon, 31 Aug 2015 16:05:13 +0900 Subject: [PATCH] [tizen_2.4] Add Tizen Alias ID is deprecated comment Change-Id: Ia01a55cafdbe796fda1cd20788c73c85990a6310 Signed-off-by: bg.chun --- .../html/web/tizen/application/application_w.htm | 25 ++++++++++++++-------- .../web/tizen/application/alarm_tutorial_w.htm | 4 ++-- 2 files changed, 18 insertions(+), 11 deletions(-) diff --git a/org.tizen.guides/html/web/tizen/application/application_w.htm b/org.tizen.guides/html/web/tizen/application/application_w.htm index dfd7b4e..25e4fd5 100644 --- a/org.tizen.guides/html/web/tizen/application/application_w.htm +++ b/org.tizen.guides/html/web/tizen/application/application_w.htm @@ -47,7 +47,8 @@ The Application API is mandatory for both Tizen mobile and wearable profiles, which means that it is supported in all mobile and wearable devices. -

All mandatory APIs are supported on the Tizen Emulators.

+

All mandatory APIs are supported on the Tizen Emulators.

+ @@ -79,7 +80,8 @@

The provider application calls the getRequestedAppControl() method of the Application interface to get the reference of the RequestedApplicationControl object containing the application control passed by the launchAppControl() method from the calling application. Then, the provider application calls either the replyResult() method (in case of success) or the replyFailure() method (in case of failure) of the RequestedApplicationControl interface to return the control back to the requesting application. The result of the provided operation (if any), is delivered as an array of ApplicationControlData objects (in mobile and wearable applications). The result is received in the original calling application through the ApplicationControlDataArrayReplyCallback event handler (in mobile and wearable applications).

The application control uses the following primary information: