Function	Description
New()	Constructs the Dali::Application class.
GetWindow()	Retrieves the window used by the Dali::Application class.
SetViewMode()	Sets the viewing mode for the application.
Quit()	Quits the application.

Table: Callbacks for basic application event signals
Callback	Description
InitSignal()	Called when the DALi application is ready to start. The signal is emitted when the DALi core components (windows, resource, thread) are ready for use.
ResumeSignal()	Called when the application becomes visible. The signal is most useful when the application is ready to restart from the paused state.
PauseSignal()	Called when the application becomes invisible. The signal is emitted when the application is paused due to another application becoming active (for example, because of a call, alarm, or message alert).
TerminateSignal()	Called when the application is terminated. The signal is useful when the application has resources to release at the end. By releasing those resources, you allow other applications to use them.
ResizeSignal()	Called when the window size is changes. The signal is called when a window is created or resized. You can use the signal to change the UI layout according to the new window size.
AppControlSignal()	Called when an application control signal is emitted from another application. This provides the means to communicate between applications.
LanguageChangedSignal()	Called when the language is changed on the device. You can use the signal to refresh the display with the new language.
RegionChangedSignal()	Called when the region is changed. You can use the signal to refresh any region-specific information on the screen.
BatteryLowSignal()	Called when the battery state is low. You can use the signal to save any crucial information in case the battery state becomes so low that the application is forcefully terminated.
MemoryLowSignal()	Called when the memory state is low. You can use the signal to release any unused memory.

Note
A DALi watch application is implemented similarly to a DALi basic UI application, since the Dali::WatchApplication class inherits from the Dali::Application class. Consequently, make sure you are familiar with the basic UI application details before tackling a watch application.

Function	Description
GetHour()	Get the hour from the WatchTime handle.
GetHour24()	Get the hour from the WatchTime handle in the 24-hour format.
GetMinute()	Get the minute from the WatchTime handle.
GetSecond()	Get the second from the WatchTime handle.

Table: Callbacks for watch application event signals
Callback	Description
TimeTickSignal()	Called every second. You can use the signal to update the time on the screen.
AmbientTickSignal()	Called every minute when the device is in the ambient mode. You can use the signal to update the time on the screen.
AmbientChangedSignal()	Called when the device enters or exits the ambient mode.

+ Table: Application state change events +
Callback	Description
app_create_cb()	Used to take necessary actions before the main event loop starts. Place the UI generation code here to prevent missing any events from your application UI.
app_pause_cb()	Used to take necessary actions when the application becomes invisible. For example, release memory resources so other applications can use them. Do not starve the foreground application that is interacting with the user.
app_resume_cb()	Used to take necessary actions when the application becomes visible. If you relinquish anything in the app_pause_cb() callback, re-allocate those resources here before the application resumes.
app_terminate_cb()	Used to take necessary actions when the application is terminating. Release all resources, especially any allocations and shared resources, so that other running applications can fully use any shared resources.

+ Table: Event types +
Event type	Description
APP_EVENT_LOW_MEMORY	Event type for the callback function that is responsible for saving data in the main memory to a persistent memory or storage to avoid data loss in case the Tizen platform Low Memory Killer kills your application to get more free memory. The callback function must also release any cached data in the main memory to secure more free memory.
APP_EVENT_LOW_BATTERY	Event type for the callback function that is responsible for saving data in the main memory to a persistent memory or storage to avoid data loss in case the power goes off completely. The callback function must also stop heavy CPU consumption or power consumption activities to save the remaining power.
APP_EVENT_DEVICE_ORIENTATION_CHANGED	Event type for the callback function that is responsible for changing the display orientation to match the device orientation.
APP_EVENT_LANGUAGE_CHANGED	Event type for the callback function that is responsible for refreshing the display into the new language.
APP_EVENT_REGION_FORMAT_CHANGED	Event type for the callback function that is responsible for refreshing the display into the new time zone.
APP_EVENT_SUSPENDED_STATE_CHANGED	Event type for the callback function that is responsible for taking necessary actions before entering the suspended state or after exiting from the state. (Supported since Tizen 2.4.)

+ Table: Application states +
State	Description
READY	Application is launched.
CREATED	Application starts the main loop.
RUNNING	Application is running and visible to the user.
PAUSED	Application is running but invisible to the user.
TERMINATED	Application is terminated.

Table: Allowed background application policy
Background category	Description	Related APIs	Manifest file <background-category> element value
Media	Playing audio, recording, and outputting streaming video on the background	Multimedia API (in mobile and wearable applications)	media
Download	Downloading data with the Tizen Download-manager API	Download API (in mobile applications)	download
Background network	Processing general network operations on the background (such as sync-manager, IM, and VOIP)	Sync Manager API (in mobile applications), Socket, and Curl API (in mobile and wearable applications)	background-network
Location	Processing location data on the background	Location API (in mobile and wearable applications)	location
Sensor (context)	Processing context data from the sensors, such as gesture	Sensor API (in mobile and wearable applications)	sensor
IoT Communication/Connectivity	Communicating between external devices on the background (such as Wi-Fi and Bluetooth)	Wi-Fi (in mobile and wearable applications) and Bluetooth API (in mobile and wearable applications)	iot-communication

Note
The <background-category> element is supported since the API version 2.4. An application with a <background-category> element declared can fail to be installed on devices with a Tizen version lower than 2.4. In this case, declare the background category as <metadata key="http://tizen.org/metadata/background-category/<value>"/>.
+ +<?xml version="1.0" encoding="utf-8"?> +<manifest xmlns="http://tizen.org/ns/packages" api-version="2.3" package="org.tizen.test" version="1.0.0"> + <ui-application appid="org.tizen.test" exec="text" type="capp" multiple="false" taskmanage="true" nodisplay="false"> + <icon>rest.png</icon> + <label>rest</label> + <!--For API version lower than 2.4--> + <metadata key="http://tizen.org/metadata/background-category/media"/> + <metadata key="http://tizen.org/metadata/background-category/download"/> + <metadata key="http://tizen.org/metadata/background-category/background-network"/> + </ui-application> + <service-application appid="org.tizen.test-service" exec="test-service" multiple="false" type="capp"> + <metadata key="http://tizen.org/metadata/background-category/background-network"/> + <metadata key="http://tizen.org/metadata/background-category/location"/> + </service-application> +</manifest> + + The <metadata key="http://tizen.org/metadata/bacgkround-category/<value>"/> element has no effect on Tizen 2.3 devices, but, in Tizen 2.4 and higher devices, it has the same effect as the <background-category> element. +

- Table: Application state change events -
Callback	Description
app_create_cb()	Used to take necessary actions before the main event loop starts. Place the UI generation code here to prevent missing any events from your application UI.
app_pause_cb()	Used to take necessary actions when the application becomes invisible. For example, release memory resources so other applications can use them. Do not starve the foreground application that is interacting with the user.
app_resume_cb()	Used to take necessary actions when the application becomes visible. If you relinquish anything in the app_pause_cb() callback, re-allocate those resources here before the application resumes.
app_terminate_cb()	Used to take necessary actions when the application is terminating. Release all resources, especially any allocations and shared resources, so that other running applications can fully use any shared resources.

- Table: Event types -
Event type	Description
APP_EVENT_LOW_MEMORY	Event type for the callback function that is responsible for saving data in the main memory to a persistent memory or storage to avoid data loss in case the Tizen platform Low Memory Killer kills your application to get more free memory. The callback function must also release any cached data in the main memory to secure more free memory.
APP_EVENT_LOW_BATTERY	Event type for the callback function that is responsible for saving data in the main memory to a persistent memory or storage to avoid data loss in case the power goes off completely. The callback function must also stop heavy CPU consumption or power consumption activities to save the remaining power.
APP_EVENT_DEVICE_ORIENTATION_CHANGED	Event type for the callback function that is responsible for changing the display orientation to match the device orientation.
APP_EVENT_LANGUAGE_CHANGED	Event type for the callback function that is responsible for refreshing the display into the new language.
APP_EVENT_REGION_FORMAT_CHANGED	Event type for the callback function that is responsible for refreshing the display into the new time zone.
APP_EVENT_SUSPENDED_STATE_CHANGED	Event type for the callback function that is responsible for taking necessary actions before entering the suspended state or after exiting from the state. (Supported since Tizen 2.4.)

- Table: Application states -
State	Description
READY	Application is launched.
CREATED	Application starts the main loop.
RUNNING	Application is running and visible to the user.
PAUSED	Application is running but invisible to the user.
TERMINATED	Application is terminated.

Table: Allowed background application policy
Background category	Description	Related APIs	Manifest file <background-category> element value
Media	Playing audio, recording, and outputting streaming video on the background	Multimedia API (in mobile and wearable applications)	media
Download	Downloading data with the Tizen Download-manager API	Download API (in mobile applications)	download
Background network	Processing general network operations on the background (such as sync-manager, IM, and VOIP)	Sync Manager API (in mobile applications), Socket, and Curl API (in mobile and wearable applications)	background-network
Location	Processing location data on the background	Location API (in mobile and wearable applications)	location
Sensor (context)	Processing context data from the sensors, such as gesture	Sensor API (in mobile and wearable applications)	sensor
IoT Communication/Connectivity	Communicating between external devices on the background (such as Wi-Fi and Bluetooth)	Wi-Fi (in mobile and wearable applications) and Bluetooth API (in mobile and wearable applications)	iot-communication

Note
The <background-category> element is supported since the API version 2.4. An application with a <background-category> element declared can fail to be installed on devices with a Tizen version lower than 2.4. In this case, declare the background category as <metadata key="http://tizen.org/metadata/background-category/<value>"/>.
- -<?xml version="1.0" encoding="utf-8"?> -<manifest xmlns="http://tizen.org/ns/packages" api-version="2.3" package="org.tizen.test" version="1.0.0"> - <ui-application appid="org.tizen.test" exec="text" type="capp" multiple="false" taskmanage="true" nodisplay="false"> - <icon>rest.png</icon> - <label>rest</label> - <!--For API version lower than 2.4--> - <metadata key="http://tizen.org/metadata/background-category/media"/> - <metadata key="http://tizen.org/metadata/background-category/download"/> - <metadata key="http://tizen.org/metadata/background-category/background-network"/> - </ui-application> - <service-application appid="org.tizen.test-service" exec="test-service" multiple="false" type="capp"> - <metadata key="http://tizen.org/metadata/background-category/background-network"/> - <metadata key="http://tizen.org/metadata/background-category/location"/> - </service-application> -</manifest> - - The <metadata key="http://tizen.org/metadata/bacgkround-category/<value>"/> element has no effect on Tizen 2.3 devices, but, in Tizen 2.4 and higher devices, it has the same effect as the <background-category> element. -

Watch Application

EFL Watch Application

Tizen allows you to create a watch application and manage its life-cycle to retrieve the current date and time and display it accurately on the screen.

This feature is supported in wearable applications only.

diff --git a/org.tizen.guides/html/native/app_management/widget_app_n.htm b/org.tizen.guides/html/native/app_management/widget_app_n.htm index bb03cac..3f731c2 100644 --- a/org.tizen.guides/html/native/app_management/widget_app_n.htm +++ b/org.tizen.guides/html/native/app_management/widget_app_n.htm @@ -10,7 +10,7 @@ - Widget Application + EFL Widget Application @@ -48,7 +48,7 @@

Widget Application

EFL Widget Application

You can create widget applications, which are Tizen native applications shown on the home screen. They are launched by the home screen when the user selects them in the Add Widget menu.

The main features of the Widget Application API include:

diff --git a/org.tizen.guides/html/native/graphics/adv_performance_n.htm b/org.tizen.guides/html/native/graphics/adv_performance_n.htm index 2470695..f386c49 100644 --- a/org.tizen.guides/html/native/graphics/adv_performance_n.htm +++ b/org.tizen.guides/html/native/graphics/adv_performance_n.htm @@ -46,7 +46,7 @@

Try to avoid writing a heavy fragment shader. If the same data apply to all fragments, do not compute the data in the fragment shader but compute them at the CPU side and provide them as uniforms. On the other hand, whenever the data can be computed at the vertex shader, use it.

In general, the glReadPixels() function is quite slow, because it reinforces CPU-GPU synchronization, drastically decreasing the overall performance. In most cases, it is possible to obtain the desired result with the framebuffer object (FBO), avoiding the use of glReadPixels(). With FBO, you can access the pixels of the framebuffer (the output of GPU processing) through a texture object (render-to-texture). Since it uses texture data from a GPU stage to another GPU stage, CPU does not have to be synchronized. If the application must use the glReadPixels()function, use another thread to avoid blocking the main thread.

With FBO, various effects can be made. Consider an application requiring a number of rendering chains for making a complex effect: A framebuffer is mapped to a texture, the texture is used to render another framebuffer, the framebuffer is mapped to another texture, and so on. This enables you to create a very complex scene, but unfortunately the rendering chain cannot be parallelized. Make the rendering chains as small as possible.

According to the application life-cycle, the application gets the app_pause() callback when the application runs at the background. Then, you must stop calling drawcalls during the pause state. +

According to the application life-cycle, the application gets the app_pause() callback when the application runs at the background. Then, you must stop calling drawcalls during the pause state.

As presented in Interactive UI, the application can control the rendering loop by using an animator internally and then stop the animator in the app_pause() callback.

@@ -74,4 +74,4 @@ var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga - \ No newline at end of file + diff --git a/org.tizen.guides/html/native/migration_guide_n.htm b/org.tizen.guides/html/native/migration_guide_n.htm index 874e69c..6674bea 100644 --- a/org.tizen.guides/html/native/migration_guide_n.htm +++ b/org.tizen.guides/html/native/migration_guide_n.htm @@ -48,7 +48,7 @@

New Background Application Policy

Since Tizen 2.4, the application on the background goes into a suspended state.

In the suspended state, the application process is executed with limited CPU resources. In other words, the platform does not allow the running of the background applications, except for some exceptional applications (such as Media and Download) that necessarily work on the background. In this case, the application can designate their background category as an allowed category to avoid going into the suspended state.

For more information, and a list of background categories that allow the application to run on the background, see Allowing Applications to Run on the Background.

You can receive an event when the background application goes to the suspended state. Pass APP_EVENT_SUSPENDED_STATE_CHANGED as event_type to the ui_app_add_event_handler() or service_app_add_event_handler() function to handle the suspended event. You must release the resources properly when your application goes to the suspended state.

@@ -106,4 +106,4 @@ var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga - \ No newline at end of file + diff --git a/org.tizen.guides/html/native/ui/dali/actors_n.htm b/org.tizen.guides/html/native/ui/dali/actors_n.htm index a55d461..8d30b30 100644 --- a/org.tizen.guides/html/native/ui/dali/actors_n.htm +++ b/org.tizen.guides/html/native/ui/dali/actors_n.htm @@ -18,12 +18,13 @@ @@ -58,9 +61,9 @@

UI Components are used to organize the application appearance. For more information, see UI Components.
Camera actor determines which view of the whole virtual 3D world is rendered on the screen. By default, it is best suited for 2D applications, so you do not need to care about it in this case. For more information, see the Dali::CameraActor class.
Camera actor determines which view of the whole virtual 3D world is rendered on the screen. By default, it is best suited for 2D applications, so you do not need to care about it in this case. For more information, see the Dali::CameraActor class (in mobile and wearable applications).
Layer provides a mechanism for overlaying groups of actors on top of each other. For more information, see the Dali::Layer class.
Layer provides a mechanism for overlaying groups of actors on top of each other. For more information, see the Dali::Layer class (in mobile and wearable applications).

diff --git a/org.tizen.guides/html/native/ui/dali/animation_n.htm b/org.tizen.guides/html/native/ui/dali/animation_n.htm index 280faa5..3ce6619 100644 --- a/org.tizen.guides/html/native/ui/dali/animation_n.htm +++ b/org.tizen.guides/html/native/ui/dali/animation_n.htm @@ -18,12 +18,13 @@

Dependencies

Tizen 2.4 and Higher for Mobile
Tizen 3.0 and Higher for Wearable

Content

@@ -136,7 +140,7 @@ void HelloWorldExample::OnFinished( Animation& animation )

Using Alpha Functions

Alpha functions are used in animations to specify the rate of change of the animation parameter over time. This allows the animation to be, for example, accelerated, decelerated, repeated, or bounced. The built-in supported functions can be viewed in the Dali::AlphaFunction::BuiltinFunction enumeration.

 animation.SetDefaultAlphaFunction( Dali::AlphaFunction::EASE_IN );

diff --git a/org.tizen.guides/html/native/ui/dali/animation_types_n.htm b/org.tizen.guides/html/native/ui/dali/animation_types_n.htm index 4595a1b..954aa0e 100644 --- a/org.tizen.guides/html/native/ui/dali/animation_types_n.htm +++ b/org.tizen.guides/html/native/ui/dali/animation_types_n.htm @@ -18,12 +18,13 @@ @@ -79,7 +82,7 @@ path.AddPoint( Vector3( 10.0f, 90.0f, 0.0f ) );

 path.GenerateControlPoints( 0.25f );

Here 0.25f represents the curvature of the path you require. For more information, see the GenerateControlPoints() function in Dali::Path class.

Here 0.25f represents the curvature of the path you require. For more information, see the GenerateControlPoints() function in the Dali::Path class (in mobile and wearable applications).

To animate actor1 along this path, use the following function:

 animation.Animate( actor1, path, Vector3::ZERO );
diff --git a/org.tizen.guides/html/native/ui/dali/background_n.htm b/org.tizen.guides/html/native/ui/dali/background_n.htm
index b052150..ef274b9 100644
--- a/org.tizen.guides/html/native/ui/dali/background_n.htm
+++ b/org.tizen.guides/html/native/ui/dali/background_n.htm
@@ -18,17 +18,20 @@
 
 
 	
-		
+		 
 	
 		
 		Dependencies
 		
 			Tizen 2.4 and Higher for Mobile
+			Tizen 3.0 and Higher for Wearable
 		
 		Related Info
 		
 			Dali::Actor API for Mobile Native
-			Dali::Stage API for Mobile Native			
+			Dali::Stage API for Mobile Native	
+			Dali::Actor API for Wearable Native
+			Dali::Stage API for Wearable Native			
 		
 	
 	
diff --git a/org.tizen.guides/html/native/ui/dali/buttons_n.htm b/org.tizen.guides/html/native/ui/dali/buttons_n.htm
index 8aa372b..f204eb7 100644
--- a/org.tizen.guides/html/native/ui/dali/buttons_n.htm
+++ b/org.tizen.guides/html/native/ui/dali/buttons_n.htm
@@ -18,12 +18,13 @@
 
 
 	
-		
+		 
 	
 		
 		Dependencies
 		
 			Tizen 2.4 and Higher for Mobile
+			Tizen 3.0 and Higher for Wearable
 		
 		Content
 		
@@ -37,6 +38,10 @@
 			Dali::Toolkit::CheckBoxButton API for Mobile Native
 			Dali::Toolkit::PushButton API for Mobile Native
 			Dali::Toolkit::RadioButton API for Mobile Native
+			Dali::Toolkit::Button API for Wearable Native
+			Dali::Toolkit::CheckBoxButton API for Wearable Native
+			Dali::Toolkit::PushButton API for Wearable Native
+			Dali::Toolkit::RadioButton API for Wearable Native
 			(DALi) Button Sample Description			
 		
 	
diff --git a/org.tizen.guides/html/native/ui/dali/constraints_n.htm b/org.tizen.guides/html/native/ui/dali/constraints_n.htm
index 756c8a7..59e3a7c 100644
--- a/org.tizen.guides/html/native/ui/dali/constraints_n.htm
+++ b/org.tizen.guides/html/native/ui/dali/constraints_n.htm
@@ -18,12 +18,13 @@
 
 
 	
-		
+		 
 	
 		
 		Dependencies
 		
 			Tizen 2.4 and Higher for Mobile
+			Tizen 3.0 and Higher for Wearable
 		
 		Content
 		
@@ -35,6 +36,7 @@
 		Related Info
 		
 			DALi::Constraint API for Mobile Native
+			DALi::Constraint API for Wearable Native
 		
 	
 
@@ -169,7 +171,7 @@ void HelloWorldExample::OnPan( Actor actor, const PanGesture& gesture )
 }

For more information, see the New() function in the Dali::Constraint class.

For more information, see the New() function in the Dali::Constraint class (in mobile and wearable applications).

Using Functors as Constraint Functions

@@ -291,12 +293,12 @@ actor.RemoveConstraints( tag ); Need an actor to appear centered around the bottom-right corner of its parent. - Use the Dali::ParentOrigin and Dali::AnchorPoint namespaces. + Use the Dali::ParentOrigin (in mobile and wearable applications) and Dali::AnchorPoint (in mobile and wearable applications) namespaces.

For more information, see Positioning Actors.

Need to lay out a series of controls with various alignment requirements. - Use either ParentOrigin and AnchorPoint settings, or the Dali::Toolkit::TableView class. + Use either ParentOrigin and AnchorPoint settings, or the Dali::Toolkit::TableView class (in mobile and wearable applications). Need to automatically modify the position property of one actor based on the position property of another actor that is neither a parent or a child. diff --git a/org.tizen.guides/html/native/ui/dali/control_base_n.htm b/org.tizen.guides/html/native/ui/dali/control_base_n.htm index 918822b..c658c76 100644 --- a/org.tizen.guides/html/native/ui/dali/control_base_n.htm +++ b/org.tizen.guides/html/native/ui/dali/control_base_n.htm @@ -18,12 +18,13 @@ diff --git a/org.tizen.guides/html/native/ui/dali/dali_n.htm b/org.tizen.guides/html/native/ui/dali/dali_n.htm index d0c3583..b20f7e7 100644 --- a/org.tizen.guides/html/native/ui/dali/dali_n.htm +++ b/org.tizen.guides/html/native/ui/dali/dali_n.htm @@ -18,16 +18,18 @@ @@ -37,8 +39,6 @@

DALi is a cross-platform 3D UI Toolkit for embedded systems. Its 3D user interface engine enables you to create rich and high-performance UI applications. DALi is based on OpenGL ES 2.0, but provides a clean cross-platform C++ framework. This means that you can use high-level DALi APIs instead of accessing low-level OpenGL APIs directly.

This feature is supported in mobile applications only.

When creating a DALi application, make sure you understand the following main features:

To create a 'Hello World' application with Dali:

Create a DALi project: +

Create a DALi project:

In the Tizen Studio menu, go to File > New > Tizen Project. -
Select a template for a mobile native application and create a project using the Basic UI with DALi template. Click Finish, and your project is created at the default location. If you want to change the location, uncheck Use default location and set a new location. For more information, see Creating the Application Project.
+
In the Tizen Studio menu, go to File > New > Tizen Project.
In the Project Wizard, select Template > Mobile or Wearable > Native Application > Basic UI with DALi.
Click Finish, and your project is created at the default location. If you want to change the location, uncheck Use default location and set a new location. For more information, see Creating the Application Project.
The new project is shown in the Project Explorer view of the Tizen Studio. If you open the src/basicdaliapplication.cpp file, you can see the source code of the basic DALi application: +

The new project is shown in the Project Explorer view of the Tizen Studio. If you open the src/basicuiwithdali.cpp file, you can see the source code of the basic DALi application:

 #include <dali-toolkit/dali-toolkit.h>
 
@@ -138,16 +141,18 @@ class HelloWorldExample : public ConnectionTracker
       stage.SetBackgroundColor( Color::WHITE );
 
       TextLabel textLabel = TextLabel::New( "Hello World" );
+      textLabel.SetSize( stage.GetSize() );
       textLabel.SetAnchorPoint( AnchorPoint::TOP_LEFT );
-      textLabel.SetName( "hello-world-label" );
+      textLabel.SetProperty( TextLabel::Property::HORIZONTAL_ALIGNMENT, "CENTER" );
+      textLabel.SetProperty( TextLabel::Property::VERTICAL_ALIGNMENT, "CENTER" );
       stage.Add( textLabel );
 
       // Connect to touch and key event signals
-      stage.GetRootLayer().TouchedSignal().Connect( this, &HelloWorldExample::OnTouch );
+      stage.GetRootLayer().TouchSignal().Connect( this, &HelloWorldExample::OnTouch );
       stage.KeyEventSignal().Connect( this, &HelloWorldExample::OnKeyEvent );
     }
 
-    bool OnTouch( Actor actor, const TouchEvent& event )
+    bool OnTouch( Actor actor, const TouchData& touch )
     {
       // Quit the application
       mApplication.Quit();
@@ -184,7 +189,7 @@ int main( int argc, char **argv )

Initialize the DALi application: +
Initialize the DALi application:
- To use the DALi APIs, you only need to include the dali-toolkit.h file. It includes the header files of DALi Core and DALi Adaptor as well as DALi Toolkit.
  @@ -201,7 +206,7 @@ using namespace Dali::Toolkit;
- -
  The Dali::Application class initializes and sets up DALi.
  +
  The Dali::Application class (in mobile and wearable applications) initializes and sets up DALi.
  
  Create a Dali::Application instance:
  @@ -210,7 +215,7 @@ Application application = Application::New( &argc, &argv );
- Several signals can be connected to keep you informed when certain platform-related activities occur, and ensure that, upon system events, DALi is called in a thread-safe manner.
  -
  To manage signal connection safely, DALi provides the Dali::ConnectionTracker class. A typical way for starting a DALi application is to create a class derived from the Dali::ConnectionTracker class and use its member functions as callback functions for DALi signals (for more information, see Automatic Connection Management). The HelloWorldExample class is used in other code samples in the Tizen DALi documentation.
  +
  To manage signal connection safely, DALi provides the Dali::ConnectionTracker class (in mobile and wearable applications). A typical way for starting a DALi application is to create a class derived from the Dali::ConnectionTracker class and use its member functions as callback functions for DALi signals (for more information, see Automatic Connection Management). The HelloWorldExample class is used in other code samples in the Tizen DALi documentation.
  
  After getting the initialized signal from the Dali::Application instance, you can use the DALi APIs for building the scene graph. Connect the HelloWorldExample::Create() callback to the DALi::Application::InitSignal() function:
  @@ -219,40 +224,42 @@ mApplication.InitSignal().Connect( this, &HelloWorldExample::Create );
Create an actor and add it to the stage: +
Create an actor and add it to the stage: -
The Dali::Toolkit::TextLabel UI component renders a short text string. To display the TextLabel component, add it to a stage. The stage instance is a singleton object (the only instance of its class during the lifetime of the program), so you can get it using a static function.
+
The Dali::Toolkit::TextLabel UI component (in mobile and wearable applications) renders a short text string. To display the TextLabel component, add it to a stage. The stage instance is a singleton object (the only instance of its class during the lifetime of the program), so you can get it using a static function.
```
 Stage stage = Stage::GetCurrent();
 stage.SetBackgroundColor( Color::WHITE );
 
 TextLabel textLabel = TextLabel::New( "Hello World" );
+textLabel.SetSize( stage.GetSize() );
 textLabel.SetAnchorPoint( AnchorPoint::TOP_LEFT );
-textLabel.SetName( "hello-world-label" );
+textLabel.SetProperty( TextLabel::Property::HORIZONTAL_ALIGNMENT, "CENTER" );
+textLabel.SetProperty( TextLabel::Property::VERTICAL_ALIGNMENT, "CENTER" );
 stage.Add( textLabel );
 
```
The above code additionally sets the background color of the stage and the anchor point, a point defining a position of a child actor from its parent, of the textLabel. The application stores the actor and resource handles. DALi objects are reference-counted, which makes sure they exist only as long as they are needed. Even if the TextLabel component is removed from the stage, it remains alive through the reference.
Connect to input signals: +
Connect to input signals:
The application can handle touch and key event signals as follows:
```
-stage.GetRootLayer().TouchedSignal().Connect( this, &HelloWorldExample::OnTouch );
+stage.GetRootLayer().TouchSignal().Connect( this, &HelloWorldExample::OnTouch );
 stage.KeyEventSignal().Connect( this, &HelloWorldExample::OnKeyEvent );
 
```
Any key inputs and touches on the stage are handled by 2 callback functions, HelloWorldExample::OnKeyEvent and HelloWorldExample::OnTouch.
-
Note that the first parameter of the HelloWorldExample::OnTouch callback (actor) is passed by a value, not by a reference or a pointer. You can simply pass instances of most DALi classes by value, when the class inherits from the Dali::BaseHandle class. This is due to the handle/body pattern widely used in DALi.
+
Note that the first parameter of the HelloWorldExample::OnTouch callback (actor) is passed by a value, not by a reference or a pointer. You can simply pass instances of most DALi classes by value, when the class inherits from the Dali::BaseHandle class (in mobile and wearable applications). This is due to the handle/body pattern widely used in DALi.
```
-bool OnTouch( Actor actor, const TouchEvent& event )
+bool OnTouch( Actor actor, const TouchData& touch )
 
```
Start the application main loop: +
Start the application main loop:
To run the application, start its main loop. This ensures that images are displayed, and events as well as signals are dispatched and captured.
```
@@ -261,13 +268,13 @@ application.MainLoop();
 
 
 
```
Build the DALi application: +
Build the DALi application:
To build your application, select Project > Build Project or press F10 in the Tizen Studio.

The Tizen Studio automatically packages the project after building. Note that you need to register your certificate when building for the first time. For more information, see Working with the Certificate Profile and Building Applications.
Run the DALi application: +
Run the DALi application:
To run your application, select Run > Run or press Ctrl+F11 in the Tizen Studio.

For more information, see Running Applications.
diff --git a/org.tizen.guides/html/native/ui/dali/event_handling_n.htm b/org.tizen.guides/html/native/ui/dali/event_handling_n.htm index 9dc10ed..0e1ae10 100644 --- a/org.tizen.guides/html/native/ui/dali/event_handling_n.htm +++ b/org.tizen.guides/html/native/ui/dali/event_handling_n.htm @@ -18,16 +18,17 @@
-
+
Dependencies
- Tizen 2.4 and Higher for Mobile
- Tizen 3.0 and Higher for Wearable
Content
@@ -78,23 +88,23 @@
Many-to-many relationship: 1 slot can connect to many signals and 1 signal can be connected to many slots, for example

Touch Events

The Dali::Actor class provides the TouchedSignal() function to inform the application that a user touches the actor. It is defined as follows:

Touch Data

The Dali::Actor class (in mobile and wearable applications) provides the TouchSignal() function to inform the application that a user touches the actor. It is defined as follows:

-typedef Signal<bool ( Actor, const TouchEvent& )> TouchSignalType;
-TouchSignalType& TouchedSignal();

+typedef Signal<bool ( Actor, const TouchData& )> TouchDataSignalType; +TouchDataSignalType& TouchSignal(); -

This means that a slot of the following type can be connected to the return value of the Actor::TouchedSignal() function:

This means that a slot of the following type can be connected to the return value of the Actor::TouchSignal() function:

-bool YourCallbackName( Actor actor, const TouchEvent& event );
+bool YourCallbackName( Actor actor, const TouchData& data );

The return value true indicates that the touch event must be consumed. Otherwise, the signal is emitted on the next sensitive parent of the actor. Note that a callback function signature varies depending on its corresponding signal type. Some signal types do not have a return value in their callback functions.

Each point on the screen being or having been touched is represented by the Dali::TouchPoint object. This object stores information about the state of the touch point (such as down, up, or motion.) and the coordinates of the touch.

A collection of touch points at a specific moment in time is collated into the Dali::TouchEvent object. When a multi-touch event occurs, each touch point represents the points that are currently being touched or the points where touch has stopped.

A collection of touch points at a specific moment in time is collated into the Dali::TouchData object (in mobile and wearable applications). When a multi-touch event occurs, each touch point represents the points that are currently being touched or the points where touch has stopped.

The following example shows how a connection to a touch event signal can be established:

@@ -111,31 +121,33 @@ void HelloWorldExample::Create( Application& application ) Stage::GetCurrent().Add( control ); // Connect to a touch signal emitted by the control - control.TouchedSignal().Connect( this, &HelloWorldExample::OnTouch ); + control.TouchSignal().Connect( this, &HelloWorldExample::OnTouch ); } -bool HelloWorldExample::OnTouch( Actor actor, const TouchEvent& event ) +bool HelloWorldExample::OnTouch( Actor actor, TouchData& touch ) { - bool handled = false; - unsigned int pointCount = event.GetPointCount(); + const std::size_t pointCount = touch.GetPointCount(); if( pointCount == 1 ) { - if( event.GetPoint( 0 ).state == TouchPoint::Down ) + // Single touch event + + // Get touch state of the primary point + PointState::Type pointState = touch.GetState( 0 ); + if( pointState == PointState::DOWN ) { - // Act on the first touch on screen - handled = true; + // User has just pressed on the device } - } - else if( pointCount > 1 ) - { - if( event.GetPoint( pointCount-1 ).state == TouchPoint::Down ) + else if( pointState == PointState::UP ) { - // Act on a multi-touch on screen - handled = true; + // User has just released their finger from the device } } - // true if the touch has been handled, false otherwise - return handled; + else + { + // Multi-touch event + } + + return true; // Touch handled } @@ -143,6 +155,8 @@ bool HelloWorldExample::OnTouch( Actor actor, const TouchEvent& event )

If a parent and child actor both connect to the touch signal, the touch event is first offered to the child. If it is consumed by the child, the parent is not informed.

For more information on handling touch event data, see Touch Data.

Key Events

The following example shows how to handle key events on the stage:

@@ -315,7 +329,7 @@ void HelloWorldExample::OnKeyEvent( const KeyEvent& event )

The basic DALi input signals are as follows:

Touched signal notifies you of a screen touch or mouse click
Touch signal notifies you of a screen touch or mouse click
Hovered signal notifies you of mouse hovering
Wheel event signal notifies you of wheel rolling (for example, mouse wheel)
Key event signal notifies you of a keyboard input

TouchedSignal()

TouchSignal()

Callback: bool YourCallbackName( Actor actor, const TouchEvent& event );

Callback: bool YourCallbackName( Actor actor, const TouchData& touch );

HoveredSignal()

-Dali::Stage +Dali::Stage (in mobile and wearable applications) - + +

Callback: void YourCallbackName( const TouchData& data )

@@ -391,7 +405,7 @@ void HelloWorldExample::OnKeyEvent( const KeyEvent& event )

-Dali::Toolkit::Control +Dali::Toolkit::Control (in mobile and wearable applications)

@@ -370,9 +384,9 @@ void HelloWorldExample::OnKeyEvent( const KeyEvent& event )
Description
TouchedSignal()	TouchSignal()	Emitted when touch input is received. - Callback: void YourCallbackName( const TouchEvent& event )
HoveredSignal()

- + @@ -432,7 +446,7 @@ void HelloWorldExample::OnKeyEvent( const KeyEvent& event )

-Dali::Toolkit::KeyboardFocusManager +Dali::Toolkit::KeyboardFocusManager (in mobile and wearable applications)

@@ -420,7 +434,7 @@ void HelloWorldExample::OnKeyEvent( const KeyEvent& event )
Callback: bool YourCallbackName( Control control );
TouchedSignal(), HoveredSignal(), KeyEventSignal()	TouchSignal(), HoveredSignal(), KeyEventSignal()	Same as the ones supported by Actor.

Add the background category type (since Tizen 2.4).
You can describe the background category of your Tizen native application.

To add background category types to allow running on the background, click + in the Background Category panel, select the category type, and click OK.
Add the background category type (since Tizen 2.4).
You can describe the background category of your Tizen native application.

To add background category types to allow running on the background, click + in the Background Category panel, select the category type, and click OK.
Add shortcuts.
To add a shortcut for the application, click + in the Shortcut List panel, define the shortcut details, and click OK.