1 Activity Fragment Intent Filters EventHandling

Activity / Fragments
Intent / Filters
Event Handling: Manual Reference
www.issacitlabs.com
www.facebook.com/issaclabs
www.linkedin.com/in/issacitlabs
Android Activity
 An activity represents a single screen with a user interface just like

window or frame of Java. Android activity is the subclass of
ContextThemeWrapper class.
 If you have worked with C, C++ or Java programming language then
you must have seen that your program starts from main() function.
Very similar way, Android system initiates its program with in
anActivity starting with a call on onCreate() callback method. There
is a sequence of callback methods that start up an activity and a
sequence of callback methods that tear down an activity as shown in
the Activity life cycle diagram: (image courtesy : android.com )
2
Activity Class Inheritance Hierarchy
3
Android Activity Lifecycle
 Android Activity Lifecycle is controlled by 7 methods of

android.app.Activity class. The android Activity is the subclass of
ContextThemeWrapper class.
 An activity is the single screen in android. It is like window or frame of

Java.
 By the help of activity, you can place all your UI components or

widgets in a single screen.
4
 The 7 lifecycle method of Activity describes how activity will behave at

different states.
 Android Activity Lifecycle methods
Let's see the 7 lifecycle methods of android activity.

Method Description
 onCreate called when activity is first created.
 onStart called when activity is becoming visible to the user.
 onResume called when activity will start interacting with the user.
5
 onPause called when activity is not visible to the user.

 onStop called when activity is no longer visible to the user.
 onRestart called after your activity is stopped, prior to start.
 onDestroy called before the activity is destroyed.
6
7
 An activity class loads all the UI component using the XML file
available in res/layout folder of the project. Following statement loads
UI components from res/layout/activity_main.xml file:
setContentView(R.layout.activity_main);
 An application can have one or more activities without any restrictions.
Every activity you define for your application must be declared in your
AndroidManifest.xml file and the main activity for your app must be
declared in the manifest with an <intent-filter> that includes the MAIN
action and LAUNCHER category as follows:
8
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="com.example.helloworld“ android:versionCode="1“ android:versionName="1.0" >
<uses-sdk android:minSdkVersion="8“ android:targetSdkVersion="22" />
<application android:icon="@drawable/ic_launcher“ android:label="@string/app_name"

android:theme="@style/AppTheme" >
<activity android:name=".MainActivity“ android:label="@string/title_activity_main" >
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.LAUNCHER"/>
</intent-filter>
</activity>
</application>
</manifest>
If either the MAIN action or LAUNCHER category are not declared for one of your activities,
then your app icon will not appear in the Home screen's list of apps.
9
Android Activity Lifecycle Example
It provides the details about the invocation of life cycle methods of

activity. In this example, we are displaying the content on the logcat.
File: MainActivity.java
package com.example.activitylifecycle;
import android.os.Bundle;
import android.app.Activity;
import android.util.Log;
import android.view.Menu;
public class MainActivity extends Activity {
@Override
protected void onCreate(Bundle savedInstanceState) {
10
super.onCreate(savedInstanceState);
Log.d("lifecycle","onCreate invoked");
}
@Override
protected void onStart() {
super.onStart();
Log.d("lifecycle","onStart invoked");
}
11
@Override
protected void onResume() {
super.onResume();
Log.d("lifecycle","onResume invoked");
}
@Override
protected void onPause() {
super.onPause();
Log.d("lifecycle","onPause invoked");
}
12
@Override
protected void onStop() {
super.onStop();
Log.d("lifecycle","onStop invoked");
}
@Override
protected void onRestart() {
super.onRestart();
Log.d("lifecycle","onRestart invoked");
}
13
@Override
protected void onDestroy() {
super.onDestroy();
Log.d("lifecycle","onDestroy invoked");
}
}
Output:
You will not see any output on the emulator or device. You need to open
logcat.
Now see on the logcat: onCreate, onStart and onResume methods are
invoked.
14
Android Fragments
 Android Fragment is the part of activity, it is also known as sub-

activity. There can be more than one fragment in an activity.
Fragments represent multiple screen inside one activity.
 Android fragment lifecycle is affected by activity lifecycle because
fragments are included in activity.
 Each fragment has its own life cycle methods that is affected by
activity life cycle because fragments are embedded in activity.
 The FragmentManager class is responsible to make interaction
between fragment objects.
15
Following are important points about fragment −
 A fragment has its own layout and its own behaviour with its own life
cycle callbacks.
 You can add or remove fragments in an activity while the activity is

running.
 You can combine multiple fragments in a single activity to build a

multi-plane UI.
16
 A fragment can be used in multiple activities.
 Fragment life cycle is closely related to the life cycle of its host activity
which means when the activity is paused, all the fragments available
in the activity will also be stopped.
 A fragment can implement a behaviour that has no user interface

component.
 Fragments were added to the Android API in Honeycomb version of

Android which API version 11.
17
 You create fragments by extending Fragment class and You can
insert a fragment into your activity layout by declaring the fragment in
the activity's layout file, as a <fragment> element.
 Prior to fragment introduction, we had a limitation because we can
show only a single activity on the screen at one given point in time. So
we were not able to divide device screen and control different parts
separately. But with the introduction of fragment we got more flexibility
and removed the limitation of having a single activity on the screen at
a time. Now we can have a single activity but each activity can
comprise of multiple fragments which will have their own layout,
events and complete life cycle..
18
 Following is a typical example of how two UI modules defined by
fragments can be combined into one activity for a tablet design, but
separated for a handset design
19
The application can embed two fragments in Activity A, when running on
a tablet-sized device. However, on a handset-sized screen, there's not
enough room for both fragments, so Activity A includes only the fragment
for the list of articles, and when the user selects an article, it starts Activity
B, which includes the second fragment to read the article.
20
Fragment Life Cycle
 Android fragments have their own life cycle very similar to an android
activity. This section briefs different stages of its life cycle.
21
Here is the list of methods which you can to override in your fragment
class −
 onAttach()The fragment instance is associated with an activity

instance.The fragment and the activity is not fully initialized. Typically
you get in this method a reference to the activity which uses the
fragment for further initialization work.
 onCreate() The system calls this method when creating the fragment.
You should initialize essential components of the fragment that you
want to retain when the fragment is paused or stopped, then resumed.
22
 onCreateView() The system calls this callback when it's time for the
fragment to draw its user interface for the first time. To draw a UI for
your fragment, you must return a View component from this method
that is the root of your fragment's layout. You can return null if the
fragment does not provide a UI.
 onActivityCreated()The onActivityCreated() is called after the

onCreateView() method when the host activity is created. Activity and
fragment instance have been created as well as the view hierarchy of
the activity. At this point, view can be accessed with the
findViewById() method. example. In this method you can instantiate
objects which require a Context object
23
 onStart()The onStart() method is called once the fragment gets visible.
 onResume()Fragment becomes active.
 onPause() The system calls this method as the first indication that the
user is leaving the fragment. This is usually where you should commit
any changes that should be persisted beyond the current user
session.
 onStop()Fragment going to be stopped by calling onStop()
24
 onDestroyView()Fragment view will destroy after call this method
 onDestroy()onDestroy() called to do final clean up of the fragment's

state but Not guaranteed to be called by the Android platform.
25
How to use Fragments?
This involves number of simple steps to create Fragments.
 First of all decide how many fragments you want to use in an activity.
For example let's we want to use two fragments to handle landscape
and portrait modes of the device.
 Next based on number of fragments, create classes which will extend

the Fragment class. The Fragment class has above mentioned
callback functions. You can override any of the functions based on
your requirements.
26
 Corresponding to each fragment, you will need to create layout files in
XML file. These files will have layout for the defined fragments.
 Finally modify activity file to define the actual logic of replacing

fragments based on your requirement.
27
Types of Fragments
Basically fragments are divided as three stages as shown below.
 Single frame fragments − Single frame fragments are using for hand
hold devices like mobiles, here we can show only one fragment as a
view.
 List fragments − fragments having special list view is called as list

fragment
 Fragments transaction − Using with fragment transaction. we can

move one fragment to another fragment.
28
1. Single Frame Fragment
 Single frame fragment is designed for small screen devices such as
hand hold devices(mobiles) and it should be above android 3.0
version.
2. Android - list FragmentAndroid - list Fragment

Static library support version of the framework's ListFragment. Used to
write apps that run on platforms prior to Android 3.0. When running on
Android 3.0 or above, this implementation is still used.
The basic implementation of list fragment is for creating list of items in
fragments
29
LIST IN FRAGMENTS
30
3. Android Fragment Transition
What is a Transition?
Activity and Fragment transitions in Lollipop are built on top of a relatively
new feature in Android called Transitions. Introduced in KitKat, the
transition framework provides a convenient API for animating between
different UI states in an application. The framework is built around two
key concepts: scenes and transitions. A scene defines a given state of an
application's UI, whereas a transition defines the animated change
between two scenes.
31
When a scene changes, a Transition has two main responsibilities −
1. Capture the state of each view in both the start and end scenes.
2. Create an Animator based on the differences that will animate the
views from one scene to the other.
If click on new fragment, it going to be changed the first fragment to

second fragment as shown in next slide.
32
33
Android Fragment Example
Let's have a look at the simple example of android fragment.

activity_main.xml
File: activity_main.xml
<LinearLayout xmlns:android="http://schemas.android.com/apk/res/andr
oid"
android:layout_width="fill_parent"
android:layout_height="fill_parent" >
<fragment
android:id="@+id/fragment2"
android:name="com.example.fragmentexample.Fragment2"
34
android:layout_width="0px"
android:layout_height="match_parent"
android:layout_weight="1"
/>
<fragment
android:id="@+id/fragment1"
android:name="com.example.fragmentexample.Fragment1"
android:layout_width="0px" android:layout_height="match_parent"
android:layout_weight="1"
/>
</LinearLayout>
35
File: fragment1.xml
<?xml version="1.0" encoding="utf-8"?>
oid"
android:layout_width="match_parent"
android:orientation="vertical"
android:background="#00ff00"
>
36
<TextView
android:id="@+id/textView1"
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:text="fragment frist"
android:textAppearance="?android:attr/textAppearanceLarge" />
</LinearLayout>
37
File: fragment2.xml
<?xml version="1.0" encoding="utf-8"?>
oid"
android:orientation="vertical"
android:background="#0000ff"
>
38
<TextView
android:text="Second Fragment"
android:textAppearance="?android:attr/textAppearanceLarge" />
</LinearLayout>
39
MainActivity class
package com.example.fragmentexample;
import android.os.Bundle; import android.app.Activity;
@Override
} }
40
File: Fragment1.java
import android.app.Fragment; import android.os.Bundle;
import android.view.LayoutInflater; import android.view.View;
import android.view.ViewGroup;
public class Fragment1 extends Fragment {
@Override
public View onCreateView(LayoutInflater inflater, ViewGroup container,
Bundle savedInstanceState) {
return inflater.inflate(R.layout.fragment1,container, false);
}
41
File: Fragment2.java
import android.app.Fragment; import android.os.Bundle;
import android.view.LayoutInflater; import android.view.View;
import android.view.ViewGroup;
public class Fragment2 extends Fragment { public View onCreateVi
ew(LayoutInflater inflater, ViewGroup container,
Bundle savedInstanceState) {
// TODO Auto-generated method stub
return inflater.inflate(R.layout.fragment2,container, false);
}
42
Output:
43
Android - Intents and Filters
An Android Intent is an abstract description of an operation to be

performed. It can be used with startActivity to launch an Activity,
broadcastIntent to send it to any interested BroadcastReceiver
components, and startService(Intent) or bindService(Intent,
ServiceConnection, int) to communicate with a background Service.
The intent itself, an Intent object, is a passive data structure holding an

abstract description of an operation to be performed.
44
For example, let's assume that you have an Activity that needs to launch
an email client and sends an email using your Android device. For this
purpose, your Activity would send an ACTION_SEND along with
appropriate chooser, to the Android Intent Resolver. The specified
chooser gives the proper interface for the user to pick how to send your
email data.
Intent email = new Intent(Intent.ACTION_SEND, Uri.parse("mailto:"));
email.putExtra(Intent.EXTRA_EMAIL, recipients);
email.putExtra(Intent.EXTRA_SUBJECT, subject.getText().toString());
email.putExtra(Intent.EXTRA_TEXT, body.getText().toString());
startActivity(Intent.createChooser(email, "Choose an email client
from..."));
45
Previous syntax is calling startActivity method to start an email activity
and result should be as shown below :
46
For example, assume that you have an Activity that needs to open URL in a web
browser on your Android device. For this purpose, your Activity will send
ACTION_WEB_SEARCH Intent to the Android Intent Resolver to open given URL
in the web browser. The Intent Resolver parses through a list of Activities and
chooses the one that would best match your Intent, in this case, the Web Browser
Activity. The Intent Resolver then passes your web page to the web browser and
starts the Web Browser Activity.
String q = “issacitlabs.com";
Intent intent = new Intent(Intent.ACTION_WEB_SEARCH );
intent.putExtra(SearchManager.QUERY, q);
startActivity(intent);
Above example will search as issacitlabs on android search engine and it gives
the result of tutorialspoint in your an activity
47
Thus, Android Intent is the message that is passed between components
such as activities, content providers, broadcast receivers, services etc.
It is generally used with startActivity() method to invoke activity,

broadcast receivers etc.
The dictionary meaning of intent is intention or purpose. So, it can be

described as the intention to do action.
48
The LabeledIntent is the subclass of android.content.Intent class.
Android intents are mainly used to:
1. Start the service

2. Launch an activity
3. Display a web page
4. Display a list of contacts
5. Broadcast a message
6. Dial a phone call etc.
49
There are separate mechanisms for delivering intents to each type of component
- activities, services, and broadcast receivers.
Sr.No Method & Description
1 Context.startActivity()
The Intent object is passed to this method to launch a new activity or get an
existing activity to do something new.
2 Context.startService()
The Intent object is passed to this method to initiate a service or deliver new
instructions to an ongoing service.
3 Context.sendBroadcast()
The Intent object is passed to this method to deliver the message to all interested
broadcast receivers.
50
Intent Objects
An Intent object is a bundle of information which is used by the

component that receives the intent as well as information used by the
Android system.
An Intent object can contain the following components based on what it is

communicating or going to perform −
51
Action
This is mandatory part of the Intent object and is a string naming the
action to be performed — or, in the case of broadcast intents, the action
that took place and is being reported. The action largely determines how
the rest of the intent object is structured . The Intent class defines a
number of action constants corresponding to different intents. Here is a
list of Android Intent Standard Actions
The action in an Intent object can be set by the setAction() method and
read by getAction().
52
Data
Adds a data specification to an intent filter. The specification can be just a
data type (the mimeType attribute), just a URI, or both a data type and a
URI. A URI is specified by separate attributes for each of its parts −
These attributes that specify the URL format are optional, but also
mutually dependent −
If a scheme is not specified for the intent filter, all the other URI attributes
are ignored.
If a host is not specified for the filter, the port attribute and all the path
attributes are ignored.
53
The setData() method specifies data only as a URI, setType() specifies it
only as a MIME type, and setDataAndType() specifies it as both a URI
and a MIME type. The URI is read by getData() and the type by
getType().
54
Some examples of action/data pairs are −
S.N. Action/Data Pair & Description
1 ACTION_VIEW content://contacts/people/1
Display information about the person whose identifier is "1".
2 ACTION_DIAL content://contacts/people/1
Display the phone dialer with the person filled in.
3 ACTION_VIEW tel:123
Display the phone dialer with the given number filled in.
55
4 ACTION_DIAL tel:123
Display the phone dialer with the given number filled in.
5 ACTION_EDIT content://contacts/people/1
Edit information about the person whose identifier is "1".
6 ACTION_VIEW content://contacts/people/
Display a list of people, which the user can browse through.
7 ACTION_SET_WALLPAPER
Show settings for choosing wallpaper
56
8 ACTION_SYNC
It going to be synchronous the data,Constant Value is
android.intent.action.SYNC
9 ACTION_SYSTEM_TUTORIAL
It will start the platform-defined tutorial(Default tutorial or start up tutorial)
10 ACTION_TIMEZONE_CHANGED
It intimates when time zone has changed
11 ACTION_UNINSTALL_PACKAGE
It is used to run default uninstaller
57
Category
The category is an optional part of Intent object and it's a string
containing additional information about the kind of component that should
handle the intent. The addCategory() method places a category in an
Intent object, removeCategory() deletes a category previously added, and
getCategories() gets the set of all categories currently in the object. Here
is a list of Android Intent Standard Categories.
You can check detail on Intent Filters in below section to understand how
do we use categories to choose appropriate activity corresponding to an
Intent.
58
Extras
his will be in key-value pairs for additional information that should be
delivered to the component handling the intent. The extras can be set
and read using the putExtras() and getExtras() methods respectively.
59
Flags
These flags are optional part of Intent object and instruct the Android
system how to launch an activity, and how to treat it after it's launched
etc.
Sr.No Flags & Description
1 FLAG_ACTIVITY_CLEAR_TASK
If set in an Intent passed to Context.startActivity(), this flag will cause any
existing task that would be associated with the activity to be cleared
before the activity is started. That is, the activity becomes the new root of
an otherwise empty task, and any old activities are finished. This can only
be used in conjunction with FLAG_ACTIVITY_NEW_TASK.
60
2 FLAG_ACTIVITY_CLEAR_TOP
If set, and the activity being launched is already running in the current
task, then instead of launching a new instance of that activity, all of the
other activities on top of it will be closed and this Intent will be delivered
to the (now on top) old activity as a new Intent.
3 FLAG_ACTIVITY_NEW_TASK
This flag is generally used by activities that want to present a "launcher"
style behavior: they give the user a list of separate things that can be
done, which otherwise run completely independently of the activity
launching them.
61
Component Name
This optional field is an android ComponentName object representing
either Activity, Service or BroadcastReceiver class. If it is set, the Intent
object is delivered to an instance of the designated class otherwise
Android uses other information in the Intent object to locate a suitable
target.
The component name is set by setComponent(), setClass(), or

setClassName() and read by getComponent().
62
Types of Android Intents
There are two types of intents in android: implicit and explicit.
1) Implicit Intent
Implicit Intent doesn't specifiy the component. In such case, intent
provides information of available components provided by the system that
is to be invoked.
For example, you may write the following code to view the webpage.
Intent intent=new Intent(Intent.ACTION_VIEW);
intent.setData(Uri.parse("http://www.issacitlabs.com"));
63
2) Explicit Intent
Explicit Intent specifies the component. In such case, intent provides the
external class to be invoked.
Intent i = new Intent(getApplicationContext(), ActivityTwo.class);
startActivity(i);
64
65
Explicit Intents : Explicit intent going to be connected internal world of
application,suppose if you wants to connect one activity to another
activity, we can do this quote by explicit intent, below image is connecting
first activity to second activity by clicking button.
66
These intents designate the target component by its name and they are
typically used for application-internal messages - such as an activity
starting a subordinate service or launching a sister activity. For example −
// Explicit Intent by specifying its class name

Intent i = new Intent(FirstActivity.this, SecondActivity.class);
// Starts TargetActivity
startActivity(i);
67
Implicit Intents
These intents do not name a target and the field for the component name
is left blank. Implicit intents are often used to activate components in
other applications. For example −
Intent read1=new Intent();

read1.setAction(android.content.Intent.ACTION_VIEW);
read1.setData(ContactsContract.Contacts.CONTENT_URI);
startActivity(read1);
Above code will give result as shown in next slide :

68
The target component which receives the
intent can use the getExtras() method to
get the extra data sent by the source
component.
For example −
// Get bundle object at appropriate place in your code
Bundle extras = getIntent().getExtras();
// Extract data using passed keys

String value1 = extras.getString("Key1");
String value2 = extras.getString("Key2");
69
Intent Filters
Intent Filters
You have seen how an Intent has been used to call an another activity.
Android OS uses filters to pinpoint the set of Activities, Services, and
Broadcast receivers that can handle the Intent with help of specified set
of action, categories, data scheme associated with an Intent. You will use
<intent-filter> element in the manifest file to list down actions, categories
and data types associated with any activity, service, or broadcast
receiver.
70
Following is an example of a part of AndroidManifest.xml file to specify an
activity com.example.My Application.CustomActivity which can be
invoked by either of the two mentioned actions, one category, and one
data −
<activity android:name=".CustomActivity"
android:label="@string/app_name">
<intent-filter>
<action android:name="android.intent.action.VIEW" />
<action android:name="com.example.My Application.LAUNCH" />
<category android:name="android.intent.category.DEFAULT" />
<data android:scheme="http" />
</intent-filter></activity>
71
Once this activity is defined along with above mentioned filters, other
activities will be able to invoke this activity using either the
android.intent.action.VIEW, or using the com.example.My
Application.LAUNCH action provided their category is
android.intent.category.DEFAULT.
The <data> element specifies the data type expected by the activity to be
called and for above example our custom activity expects the data to start
with the "http://"
72
There may be a situation that an intent can pass through the filters of
more than one activity or service, the user may be asked which
component to activate. An exception is raised if no target can be found.
There are following test Android checks before invoking an activity −
A filter <intent-filter> may list more than one action as shown above but
this list cannot be empty; a filter must contain at least one <action>
element, otherwise it will block all intents. If more than one actions are
mentioned then Android tries to match one of the mentioned actions
before invoking the activity.
73
A filter <intent-filter> may list zero, one or more than one categories. if
there is no category mentioned then Android always pass this test but if
more than one categories are mentioned then for an intent to pass the
category test, every category in the Intent object must match a category
in the filter.
Each <data> element can specify a URI and a data type (MIME media
type). There are separate attributes like scheme, host, port, and path for
each part of the URI. An Intent object that contains both a URI and a data
type passes the data type part of the test only if its type matches a type
listed in the filter.
74
Android Implicit Intent Example
Let's see the simple example of implicit intent that displays a web page.
activity_main.xml
<RelativeLayout xmlns:androclass="http://schemas.android.com/apk/res
/android"
xmlns:tools="http://schemas.android.com/tools"
tools:context=".MainActivity" >
75
<EditText
android:id="@+id/editText1"
android:layout_alignParentTop="true"
android:layout_centerHorizontal="true"
android:layout_marginTop="44dp"
android:ems="10" />
76
<Button
android:id="@+id/button1"
android:layout_below="@+id/editText1"
android:text="Visit" />
</RelativeLayout>
77
Activity class
package org.sssit.implicitintent;
import android.net.Uri;
import android.content.Intent;
import android.view.View;
import android.view.View.OnClickListener;
import android.widget.Button;
import android.widget.EditText;
78
@Override
final EditText editText1=(EditText)findViewById(R.id.editText1);
Button button1=(Button)findViewById(R.id.button1);
79
button1.setOnClickListener(new OnClickListener() {
@Override
public void onClick(View arg0) {
String url=editText1.getText().toString();
Intent intent=new Intent(Intent.ACTION_VIEW,Uri.parse(url));
}
});
}
}
80
Output
81
Android Explicit Intent Example
Android Explicit intent specifies the component to be invoked from

activity. In other words, we can call another activity in android by explicit
intent.
We can also pass the information from one activity to another using
explicit intent.
Here, we are going to see an example to call one activity from another
and vice-versa.
Android calling one activity from another activity example
Let's see the simple example of android explicit example that calls one
activity from another and vice versa.
82
activity_main.xml
/android"
83
<Button
android:id="@+id/Button01"
android:layout_alignParentLeft="true"
android:layout_below="@+id/TextView01"
android:layout_marginLeft="65dp"
android:onClick="onClick"
android:text="Call second activity" />
84
<TextView
android:id="@+id/TextView01"
android:layout_alignLeft="@+id/Button01"
android:minHeight="60dip"
android:text="First Activity"
android:textSize="20sp" /> </RelativeLayout>
85
activitytwo_main.xml
File: activitytwo_main.xml
/android"
86
<Button
android:id="@+id/Button01"
android:layout_below="@+id/TextView01"
android:onClick="onClick"
android:text="Call First activity" />
87
<TextView
android:id="@+id/TextView01"
android:layout_alignLeft="@+id/Button01"
android:minHeight="60dip"
android:text="Second Activity"
android:textSize="20sp" /> </RelativeLayout>
88
ActivityOne class
File: MainActivityOne.java
package com.example.explicitintent2;
import android.widget.Toast;
89
public class ActivityOne extends Activity {
/** Called when the activity is first created. */
@Override
public void onCreate(Bundle savedInstanceState) {
Button button1=(Button)findViewById(R.id.Button01);
button1.setOnClickListener(new OnClickListener(){
public void onClick(View view) {
Intent i = new Intent(getApplicationContext(), ActivityTwo.class);
i.putExtra("Value1", “IssacITLabs");
i.putExtra("Value2", “Adnroid Begins");
// Set the request code to any code you like, you can identify the
// callback via this code
startActivity(i);
} });
} }
90
ActivityTwo class
File: MainActivityTwo.java
package com.example.explicitintent2;
import android.widget.EditText; import android.widget.TextView;
import android.widget.Toast;
91
public class ActivityTwo extends Activity {
/** Called when the activity is first created. */
@Override
public void onCreate(Bundle bundle) {
super.onCreate(bundle);
TextView tv=new TextView(this);
tv.setText("second activity");
setContentView(R.layout.activity_two);
Bundle extras = getIntent().getExtras();
String value1 = extras.getString("Value1");
String value2 = extras.getString("Value2");
Toast.makeText(getApplicationContext(),"Values are:\n First value: "+value1+
"\n Second Value: "+value2,Toast.LENGTH_LONG).show();
Button button1=(Button)findViewById(R.id.Button01);
button1.setOnClickListener(new OnClickListener(){
public void onClick(View view) {
Intent i = new Intent(getApplicationContext(), ActivityOne.class); startActivity(i); } });
} }
92
Output
93
Android StartActivityForResult Example
By the help of android startActivityForResult() method, we can get result

from another activity. By the help of android startActivityForResult()
method, we can send information from one activity to another and vice-
versa. The android startActivityForResult method, requires a result
from the second activity (activity to be invoked). In such case, we need to
override the onActivityResult method that is invoked automatically when
second activity returns result. Method Signature are as follows
There are two variants of startActivityForResult() method.
public void startActivityForResult (Intent intent, int requestCode)
public void startActivityForResult (Intent intent, int requestCode, Bundle
options)
94
Let's see the simple example of android startActivityForResult method.
activity_main.xml
Drag one textview and one button from the pallete, now the xml file will
look like this.
/android"
android:paddingBottom="@dimen/activity_vertical_margin"
95
android:paddingLeft="@dimen/activity_horizontal_margin"
android:paddingRight="@dimen/activity_horizontal_margin"
android:paddingTop="@dimen/activity_vertical_margin"
<TextView
android:layout_alignLeft="@+id/button1"
96
android:text="Default Message" />
<Button
android:layout_below="@+id/textView1"
android:text="GetMessage" /> </RelativeLayout>
97
second_main.xml
This xml file is created automatically when you create another activity. To
create new activity Right click on the package inside the src -> New
-> Other ->Android Activity.
Now drag one editText, one textView and one button from the pallete,
now the xml file will look like this:
File: second_main.xml
/android"
98
android:paddingBottom="@dimen/activity_vertical_margin"
android:paddingLeft="@dimen/activity_horizontal_margin"
android:paddingRight="@dimen/activity_horizontal_margin"
android:paddingTop="@dimen/activity_vertical_margin"
tools:context=".SecondActivity" >
99
<EditText
android:id="@+id/editText1"
android:layout_toRightOf="@+id/textView1"
android:ems="10" />
100
<TextView
android:layout_alignBaseline="@+id/editText1"
android:layout_alignBottom="@+id/editText1"
android:text="Enter Message:" />
101
<Button
android:layout_below="@+id/editText1"
android:text="Submit" />
 </RelativeLayout>
102
Activity class
Now let's write the code that invokes another activity and get result from that
activity.
package com.issac.startactivityforresult;
import android.view.View; import android.view.View.OnClickListener;
import android.widget.Button; import android.widget.TextView;
103
TextView textView1;
Button button1;
@Override
textView1=(TextView)findViewById(R.id.textView1);
button1=(Button)findViewById(R.id.button1);
104
@Override
Intent intent=new Intent(MainActivity.this,SecondActivity.class);
startActivityForResult(intent, 2);// Activity is started with requestCod
e2
}
});
}
105
// Call Back method to get the Message form other Activity
@Override
protected void onActivityResult(int requestCode, int resultCode, Intent d
ata)
{ super.onActivityResult(requestCode, resultCode, data);
// check if the request code is same as what is passed here it is 2
if(requestCode==2)
{
String message=data.getStringExtra("MESSAGE");
textView1.setText(message);
} }
106
@Override
public boolean onCreateOptionsMenu(Menu menu) {
// Inflate the menu; this adds items to the action bar if it is present.
getMenuInflater().inflate(R.menu.main, menu);
return true;
}
}
107
SecondActivity class
Let's write the code that displays the content of second activity layout file.
File: SecondActivity.java
package com.issac.startactivityforresult;
import android.view.View; import android.view.View.OnClickListener;
import android.widget.Button; import android.widget.EditText;
import android.widget.TextView;
108
public class SecondActivity extends Activity {
EditText editText1;
Button button1;
@Override
setContentView(R.layout.activity_second);
editText1=(EditText)findViewById(R.id.editText1);
button1=(Button)findViewById(R.id.button1);
109
@Override
String message=editText1.getText().toString();
Intent intent=new Intent();
intent.putExtra("MESSAGE",message);
setResult(2,intent);
finish();//finishing activity
}
});
}
110
@Override
public boolean onCreateOptionsMenu(Menu menu) {
// Inflate the menu; this adds items to the action bar if it is present.
getMenuInflater().inflate(R.menu.second, menu);
return true;
}
}
111
Output
112
Android - Event Handling
Events are a useful way to collect data about a user's interaction with
interactive components of Applications. Like button presses or screen touch
etc. The Android framework maintains an event queue as first-in, first-out
(FIFO) basis. You can capture these events in your program and take
appropriate action as per requirements.
There are following three concepts related to Android Event Management −
 Event Listeners − An event listener is an interface in the View class that

contains a single callback method. These methods will be called by the
Android framework when the View to which the listener has been
registered is triggered by user interaction with the item in the UI.
113
 Event Listeners Registration − Event Registration is the process by which
an Event Handler gets registered with an Event Listener so that the handler
is called when the Event Listener fires the event.
 Event Handlers − When an event happens and we have registered an

event listener for the event, the event listener calls the Event Handlers,
which is the method that actually handles the event.
114
Event Listeners & Event Handlers
Event Handler Event Listener & Description

 onClick() OnClickListener()
This is called when the user either clicks or touches or focuses upon any
widget like button, text, image etc. You will use onClick() event handler to
handle such event.
 onLongClick() OnLongClickListener()
This is called when the user either clicks or touches or focuses upon any
widget like button, text, image etc. for one or more seconds. You will use
onLongClick() event handler to handle such event.
 onFocusChange() OnFocusChangeListener()
This is called when the widget looses its focus ie. user goes away from the
view item. You will use onFocusChange() event handler to handle such event.
115
 onKey() OnFocusChangeListener()
This is called when the user is focused on the item and presses or releases a
hardware key on the device. You will use onKey() event handler to handle
such event.
 onTouch() OnTouchListener()
This is called when the user presses the key, releases the key, or any
movement gesture on the screen. You will use onTouch() event handler to
handle such event.
 onMenuItemClick() OnMenuItemClickListener()
This is called when the user selects a menu item. You will use
onMenuItemClick() event handler to handle such event.
116
 onCreateContextMenu() onCreateContextMenuItemListener()
This is called when the context menu is being built(as the result of a sustained
"long click)
There are many more event listeners available as a part of View class like
OnHoverListener, OnDragListener etc which may be needed for your
application. So I recommend to refer official documentation for Android
application development in case you are going to develop a sophisticated
apps.
117
Event Listeners Registration
Event Registration is the process by which an Event Handler gets registered
with an Event Listener so that the handler is called when the Event Listener
fires the event. Though there are several tricky ways to register your event
listener for any event, but I'm going to list down only top 3 ways, out of which
you can use any of them based on the situation.
1. Using an Anonymous Inner Class
2. Activity class implements the Listener interface.
3. Using Layout file activity_main.xml to specify event handler directly.
118

1 Activity Fragment Intent Filters EventHandling

Uploaded by

Copyright:

Available Formats

1 Activity Fragment Intent Filters EventHandling

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

1 Activity Fragment Intent Filters EventHandling

Uploaded by

Copyright:

Available Formats

Activity / Fragments

 An activity represents a single screen with a user interface just like

 Android Activity Lifecycle is controlled by 7 methods of

 An activity is the single screen in android. It is like window or frame of

 By the help of activity, you can place all your UI components or

 The 7 lifecycle method of Activity describes how activity will behave at

 Android Activity Lifecycle methods

Let's see the 7 lifecycle methods of android activity.

 onPause called when activity is not visible to the user.

<uses-sdk android:minSdkVersion="8“ android:targetSdkVersion="22" />

<application android:icon="@drawable/ic_launcher“ android:label="@string/app_name"

<activity android:name=".MainActivity“ android:label="@string/title_activity_main" >

It provides the details about the invocation of life cycle methods of

 Android Fragment is the part of activity, it is also known as sub-

 You can add or remove fragments in an activity while the activity is

 You can combine multiple fragments in a single activity to build a

 A fragment can implement a behaviour that has no user interface

 Fragments were added to the Android API in Honeycomb version of

 onAttach()The fragment instance is associated with an activity

 onActivityCreated()The onActivityCreated() is called after the

 onResume()Fragment becomes active.

 onStop()Fragment going to be stopped by calling onStop()

 onDestroyView()Fragment view will destroy after call this method

 onDestroy()onDestroy() called to do final clean up of the fragment's

This involves number of simple steps to create Fragments.

 Next based on number of fragments, create classes which will extend

 Finally modify activity file to define the actual logic of replacing

Basically fragments are divided as three stages as shown below.

 List fragments − fragments having special list view is called as list

 Fragments transaction − Using with fragment transaction. we can

2. Android - list FragmentAndroid - list Fragment

If click on new fragment, it going to be changed the first fragment to

Let's have a look at the simple example of android fragment.

An Android Intent is an abstract description of an operation to be

The intent itself, an Intent object, is a passive data structure holding an

It is generally used with startActivity() method to invoke activity,

The dictionary meaning of intent is intention or purpose. So, it can be

Android intents are mainly used to:

1. Start the service

An Intent object is a bundle of information which is used by the

An Intent object can contain the following components based on what it is

The component name is set by setComponent(), setClass(), or

// Explicit Intent by specifying its class name

Intent read1=new Intent();

Above code will give result as shown in next slide :

// Extract data using passed keys

There are following test Android checks before invoking an activity −

Android Explicit intent specifies the component to be invoked from

By the help of android startActivityForResult() method, we can get result

There are following three concepts related to Android Event Management −

 Event Listeners − An event listener is an interface in the View class that

 Event Handlers − When an event happens and we have registered an

Event Handler Event Listener & Description

You might also like