Android Applications Tutorial
13. Intent

13.0 Intent


API calls aresynchronouswhile intent-based invocations areasynchronous.Intentis basically a message that is passed betweencomponents(such asActivities,Services,Broadcast Receivers, andContent Providers). So, it is almost equivalent to parameters passed to API calls. The fundamental differences between API calls and intents' way of invoking components are:

  • API calls arecompile timebinding while intent-based calls arerun-time binding.
  • API calls aresynchronouswhile intent-based invocations areasynchronous.

Of course, Intents can be made to work exactly like API calls by using what are calledexplicit intents, which will be explained later. But more often than not,implicitintents are the way to go and that is what is explained here.

One component that wants to invoke another has to only express its'intentto do a job. And any other component that exists and has claimed that it can do such a job throughintent-filters, is invoked by the android platform to accomplish the job. This means, both the components are not aware of each other's existence and can still work together to give the desired result for the end-user.

This invisible connection between components is achieved through the combination of intents, intent-filters and the android platform.

This leads to huge possibilities like:

  • Mix and match or rather plug and play of components at runtime.
  • Replacing the inbuilt android applications with custom developed applications.
  • Component level reuse within and across applications.
  • Service orientation to the most granular level, if I may say.

Here is additional description about intent, almost formal.

An intent is an abstract description of an operation to be performed. It can be used withstartActivityto launch anActivity,broadcastIntentto send it to any interestedBroadcastReceivercomponents, andstartService(Intent)orbindService(Intent, ServiceConnection, int)to communicate with a background Service.

An Intent provides a facility for performing late runtime binding between the code in different applications. Its most significant use is in the launching of activities, where it can be thought of as the glue between activities. It is basically a passive data structure holding an abstract description of an action to be performed. The primary pieces of information in an intent are:

  • action
    The general action to be performed, such as ACTION_VIEW, ACTION_EDIT, ACTION_MAIN, etc.
  • data
    The data to operate on, such as a person record in the contacts database, expressed as a Uri.

All Android components that wish to be notified via intents should declare intent filters so that Android knows which intents should go to that component. So, we need to add intent-filter elements to ourAndroidManifest.xmlfile. It looks something like this:

<?xml version="1.0" encoding="utf-8"?> <manifest xmlns:android= "http://schemas.android.com/apk/res/android" package="com.bogotobogo.myContacts" android:versionCode="1" android:versionName="1.0"> <application android:icon="@drawable/icon" android:label="@string/app_name"> <activity android:name=".myContacts" android:label="@string/app_name"> <intent-filter> <action android:name= "android.intent.action.MAIN" /> <category android:name="android.intent.category.LAUNCHER" /> </intent-filter> </activity> </application> <uses-sdk android:minSdkVersion="7" /> <uses-permission android:name= "android.permission.READ_CONTACTS"/> </manifest> 

Note thatintent-filterelement is under theactivityelement. In the file, we are declaring that this activity is (1) the main activity for this application and (2) the activity is in the LAUNCHER category, meaning it gets an icon in the Android menu. Because this activity is the main one for the application, Android knows this is the component it should launch when someone chooses the application from the main menu.

Once we have our intent, we need to pass it to Android and get the child activity to launch. Here, we have two options:

  • CallstartActivity()with the Intent. This will cause Android to find the best matching activity and pass the intent to the activity for handling. The activity will not be informed when the child activity is complete.
  • CallstartActivityForResult(), passing it the intent and a number which is unique to the calling activity. Android will find the best matching activity and pass the intent over to the activity. The activity will be notified when the child activity is complete viaonActivityResult()callback.


13.1 Explicit Intent

In anexplicit intent, we actually specify the activity that is required to respond to the intent. In other words, we explicitly designate the target component. This is typically used for application internal messages.

In animplicit intent, the main power of the android design, we just declare an intent and leave it to the platform to find an activity that can respond to the intent. Here, we do not declare the target component and hence is typically used for activating components of other applications seamlessly

Let's look at our example:

This example has 2 activities:

  • InvokingActivity
  • InvokedActivity

    TheInvokingActivityhas a button "Invoke Next Activity" which when clicked explicitly calls theInvokedActivityclass. The relevant part of the code is here:

            Button invokingButton = (Button)findViewById(R.id.invokebutton);        invokingButton.setOnClickListener(new OnClickListener() {                public void onClick(View v) {        Intent explicitIntent = new Intent(InvokingActivity.this,InvokedActivity.class);        startActivity(explicitIntent);        }        });

    The layout forInvokingActivityis defined in/res/main.xml:

    and forInvokedActivityin/res/invokedactivity.xml.

    Here are our java code,InvokingActivity.java:

    package com.bogotobogo.explicitintent;import android.app.Activity;import android.content.Intent;import android.os.Bundle;import android.view.View;import android.view.View.OnClickListener;import android.widget.Button;public class InvokingActivity extends Activity {@Override    public void onCreate(Bundle savedInstanceState) {        super.onCreate(savedInstanceState);        setContentView(R.layout.main);                Button invokingButton = (Button)findViewById(R.id.invokebutton);        invokingButton.setOnClickListener(new OnClickListener() {                public void onClick(View v) {        Intent explicitIntent = new Intent(InvokingActivity.this,InvokedActivity.class);        startActivity(explicitIntent);        }        });    }}

    andInvokedActivity.java:

    package com.bogotobogo.explicitintent;import android.app.Activity;import android.os.Bundle;public class InvokedActivity extends Activity {@Overridepublic void onCreate(Bundle savedInstanceState) {super.onCreate(savedInstanceState);setContentView(R.layout.invokedactivity);}}



    Files used in this Explicit Intent example,ExplicitIntent.zip

    In the next section, we will see how to work with implicit intents which also needs us to understandintent-filters.



    13.2 Implicit Intent

    In the previous section, we learned how to useExplicit Intentsto invoke activities through a very simple example. Now, we will move on to a more interesting concept ofImplicit IntentsandIntent Filters.

    As described earlier, animplicit intentdoesnotname atarget componentthat should act upon the intent. Android resolves as to which component is best suited to respond to anImplicit Intent. How does this happen?

    Basically, anIntent objecthas the following information (among other things like Component name, extras and flags) which is of interest for implicit intents:

    • Action
    • Category
    • Data

    So, Android compares the three (action, category and data) to something calledIntent Filtersthat are declared by probable target components who are willing to accept Implicit Intent calls. i.e. Intent Filters are the way of any component toadvertiseits own capabilities to the Android system. This is done declaratively in the AndroidManifest.xml file.

    So here are some important points to remember:

    1. Implicit Intents do not specify a target component.
    2. Components willing to receive implicit intents have to declare their ability to handle a specific intent by declaring intent filters.
    3. A component can declare any number of Intent Filters.
    4. There can be more than one component that declares the same Intent Filters and hence can respond to the same implicit intent. In that case, the user is presented both the component options and he can choose which one he wants to continue with.
    5. We can set priorities for the intent filters to ensure the order of responses.

    There are 3 tests conducted in order to match an intent with intent filters:

    1. Action Test
    2. Category Test
    3. Data Test

    Finally, we'll look at declaring an implicit intent in one activity which will invoke one of the native activities of the platform by matching the intent filters declared by the same.

    TheImplicitIntentActivity creates an implicit intent objectcontacts. This intent object's component is not set. However, the action is set toandroid.content.intent.ACTION_VIEWand the data's URI is set toPeople.CONTENT_URI.

    Such an intent matches with the intent filter declared by the view contacts native activity.

    So, when we run this application, it displays the native UI for viewing the existing contacts on the phone!

    Here is the relevant piece of code for the same:

     Button viewContacts = (Button)findViewById(R.id.ViewContacts); viewContacts.setOnClickListener(new OnClickListener() { public void onClick(View v) { Intent contacts = new Intent(); contacts.setAction(android.content.Intent.ACTION_VIEW); contacts.setData(People.CONTENT_URI); startActivity(contacts); } }); 

    In this manner many of the native applications can be seamlessly invoked as one of the activities in our applications through implicit intents.

    Here are our Java code,ImplicitIntent.java:

    package com.bogotobogo.implicitintent; import android.app.Activity; import android.content.ActivityNotFoundException; import android.content.Intent; import android.os.Bundle; import android.provider.Contacts.People; import android.util.Log; import android.view.View; import android.view.View.OnClickListener; import android.widget.Button; public class ImplicitIntent extends Activity { /** Called when the activity is first created. */ @Override public void onCreate(Bundle savedInstanceState) { super.onCreate(savedInstanceState); setContentView(R.layout.main); ViewContacts(); } private void ViewContacts() { try { Button viewContacts = (Button)findViewById(R.id.ViewContacts); viewContacts.setOnClickListener(new OnClickListener() { public void onClick(View v) { Intent contacts = new Intent(); contacts.setAction(android.content.Intent.ACTION_VIEW); contacts.setData(People.CONTENT_URI); startActivity(contacts); } });  }catch (ActivityNotFoundException anfe) { Log.e("ViewContacts","Viewing of Contacts failed", anfe); } } } 



    Files used in this Implicit Intent example,ImplicitIntent.zip


    13.3 Launching a Peer Activity

    In this example, we'll have two fields for the latitude and longitude, and a button asking a map for the location.

    Here is the layout:

    <?xml version="1.0" encoding="utf-8"?><LinearLayout xmlns:android="http://schemas.android.com/apk/res/android"android:orientation="vertical"android:layout_width="fill_parent"android:layout_height="fill_parent"><TableLayoutandroid:layout_width="fill_parent" android:layout_height="wrap_content"android:stretchColumns="1,2"><TableRow><TextViewandroid:layout_width="wrap_content" android:layout_height="wrap_content"android:paddingLeft="2dip"android:paddingRight="4dip"android:text="Location:"/><EditText android:id="@+id/lat"android:layout_width="fill_parent" android:layout_height="wrap_content"android:cursorVisible="true"android:editable="true"android:singleLine="true"android:layout_weight="1"/><EditText android:id="@+id/lon"android:layout_width="fill_parent" android:layout_height="wrap_content"android:cursorVisible="true"android:editable="true"android:singleLine="true"android:layout_weight="1"/></TableRow></TableLayout><Button android:id="@+id/map"android:layout_width="fill_parent" android:layout_height="wrap_content"android:text="Show me the map!"/></LinearLayout>

    Our Java code:

    package com.bogotobogo.Launch;import android.app.Activity;import android.content.Intent;import android.net.Uri;import android.os.Bundle;import android.view.View;import android.widget.Button;import android.widget.EditText;public class Launch extends Activity {private EditText lat;private EditText lon;@Overridepublic void onCreate(Bundle icicle) {super.onCreate(icicle);setContentView(R.layout.main);Button btn=(Button)findViewById(R.id.map);lat=(EditText)findViewById(R.id.lat);lon=(EditText)findViewById(R.id.lon);btn.setOnClickListener(new View.OnClickListener() {public void onClick(View view) {String _lat=lat.getText().toString();String _lon=lon.getText().toString();Uri uri=Uri.parse("geo:"+_lat+","+_lon);startActivity(new Intent(Intent.ACTION_VIEW, uri));}});}}

    The button'sOnClickListenertakes the latitude and longitude, put them into geo scheme Uri.

    Uri uri=Uri.parse("geo:"+_lat+","+_lon);

    Then, starts the activity after creating an intent requesting to view this Uri (ACTION_VIEW)

    startActivity(new Intent(Intent.ACTION_VIEW, uri));



    13.4 Intent Tabs

    In this section, we'll have a tab browser using an Intent. Each tab will launch its own browser Activity. Actually Android's tab-management framework the Activity's UI into each tab.

    Here is the source for our main activity which is hosting theTabView, IntentTab.java:

    package com.bogotobogo.intenttab;import android.app.TabActivity;import android.content.Intent;import android.os.Bundle;import android.widget.TabHost;public class IntentTab extends TabActivity {@Overridepublic void onCreate(Bundle savedInstanceState) {super.onCreate(savedInstanceState);TabHost host=getTabHost();host.addTab(host.newTabSpec("one").setIndicator("BoGoToBoGo").setContent(new Intent(this, BoGoBrowser.class)));host.addTab(host.newTabSpec("two").setIndicator("Android").setContent(new Intent(this, AndroidBrowser.class)));}}

    Here, we are usingTabActivityas the base class, and so we don't have to use our own layout for the view sinceTabActivitysupplies it for us. So, we just get access to theTabHostand add two tabs. Each tab specifies an Intent that directly refers to another class: BoGoBrowser and AndroidBrowser, respectively.


    Other sources we need are:

    BoGoBrowser.java:

    package com.bogotobogo.intenttab;import android.app.Activity;import android.os.Bundle;import android.webkit.WebView;public class BoGoBrowser extends Activity {WebView browser;@Overridepublic void onCreate(Bundle icicle) {super.onCreate(icicle);browser=new WebView(this);setContentView(browser);browser.loadUrl("http://bogotobogo.com");}}

    AdroidBrowser.java:

    package com.bogotobogo.intenttab;import android.app.Activity;import android.os.Bundle;import android.webkit.WebView;public class AndroidBrowser extends Activity {WebView browser;@Overridepublic void onCreate(Bundle icicle) {super.onCreate(icicle);browser=new WebView(this);setContentView(browser);browser.loadUrl("http://www.android.com/");}}

    One more thing, we need to add the following lines toAndroidManifest.xml.

    <activity android:name=".BoGoBrowser" /> <activity android:name=".AndroidBrowser" /> <uses-permission android:name="android.permission.INTERNET" /> 

    So, the manifest file should look like this:

    <?xml version="1.0" encoding="utf-8"?><manifest xmlns:android="http://schemas.android.com/apk/res/android"      package="com.bogotobogo.intenttab"      android:versionCode="1"      android:versionName="1.0">    <application android:icon="@drawable/icon" android:label="@string/app_name"><activity android:name=".IntentTab"                  android:label="@string/app_name">            <intent-filter>                <action android:name="android.intent.action.MAIN" />                <category android:name="android.intent.category.LAUNCHER" />            </intent-filter>        </activity><activity android:name=".BoGoBrowser" /> <activity android:name=".AndroidBrowser" />     </application>    <uses-sdk android:minSdkVersion="3" />    <uses-permission android:name="android.permission.INTERNET" /> </manifest> 

  • 更多相关文章

    1. 代码中设置drawableleft
    2. android 3.0 隐藏 系统标题栏
    3. Android开发中activity切换动画的实现
    4. Android(安卓)学习 笔记_05. 文件下载
    5. Android中直播视频技术探究之—摄像头Camera视频源数据采集解析
    6. 技术博客汇总
    7. android 2.3 wifi (一)
    8. AndRoid Notification的清空和修改
    9. Android中的Chronometer

    随机推荐

    1. Linux Centos 7 有关防火墙命令
    2. SELinux简介以及一些常用命令
    3. Linux服务器下用svn创建多个项目
    4. linux文件系统维护(四)
    5. Linux学习之路(1)
    6. 全面解析Linux 内核 3.10.x - 编译前的准
    7. Linux系统Oracle12.2 RAC集群实施维护_Or
    8. 【linux】Centos7 防火墙操作
    9. 鸟哥的Linux私房菜——基础学习篇(第三版)
    10. keepalived for linux(HA 高可用集群)