diff options
| author | Scott Main <smain@google.com> | 2011-06-22 17:45:13 -0700 |
|---|---|---|
| committer | Android (Google) Code Review <android-gerrit@google.com> | 2011-06-22 17:45:13 -0700 |
| commit | 138836adc7e28e66984fdc20d22688d4da561c15 (patch) | |
| tree | af9785b150468aa6d5ebc019e6a35bf8168eca24 /docs/html/guide/topics/fundamentals | |
| parent | 850aaaeff6df3c1c6e9cec5ae67225bb57728e0e (diff) | |
| parent | 9fc3579cabfd71fba8b34dfca6b7e1cf4175b845 (diff) | |
| download | frameworks_base-138836adc7e28e66984fdc20d22688d4da561c15.zip frameworks_base-138836adc7e28e66984fdc20d22688d4da561c15.tar.gz frameworks_base-138836adc7e28e66984fdc20d22688d4da561c15.tar.bz2 | |
Merge "docs: add info about manifest attributes that should not change" into honeycomb-mr2
Diffstat (limited to 'docs/html/guide/topics/fundamentals')
| -rw-r--r-- | docs/html/guide/topics/fundamentals/activities.jd | 13 | ||||
| -rw-r--r-- | docs/html/guide/topics/fundamentals/services.jd | 14 |
2 files changed, 21 insertions, 6 deletions
diff --git a/docs/html/guide/topics/fundamentals/activities.jd b/docs/html/guide/topics/fundamentals/activities.jd index 5cc1b45..cb453da 100644 --- a/docs/html/guide/topics/fundamentals/activities.jd +++ b/docs/html/guide/topics/fundamentals/activities.jd @@ -145,7 +145,7 @@ href="{@docRoot}guide/topics/ui/index.html">User Interface</a> documentation.</p <h3 id="Declaring">Declaring the activity in the manifest</h3> <p>You must declare your activity in the manifest file in order for it to -be accessible to the system. To decalare your activity, open your manifest file and add an <a +be accessible to the system. To declare your activity, open your manifest file and add an <a href="{@docRoot}guide/topics/manifest/activity-element.html">{@code <activity>}</a> element as a child of the <a href="{@docRoot}guide/topics/manifest/application-element.html">{@code <application>}</a> @@ -163,9 +163,16 @@ element. For example:</p> <p>There are several other attributes that you can include in this element, to define properties such as the label for the activity, an icon for the activity, or a theme to style the activity's -UI. See the <a +UI. The <a href="{@docRoot}guide/topics/manifest/activity-element.html#nm">{@code android:name}</a> +attribute is the only required attribute—it specifies the class name of the activity. Once +you publish your application, you should not change this name, because if you do, you might break +some functionality, such as application shortcuts (read the blog post, <a +href="http://android-developers.blogspot.com/2011/06/things-that-cannot-change.html">Things +That Cannot Change</a>).</p> + +<p>See the <a href="{@docRoot}guide/topics/manifest/activity-element.html">{@code <activity>}</a> element -reference for more information about available attributes.</p> +reference for more information about declaring your activity in the manifest.</p> <h4>Using intent filters</h4> diff --git a/docs/html/guide/topics/fundamentals/services.jd b/docs/html/guide/topics/fundamentals/services.jd index d3ef70a..9c38897 100644 --- a/docs/html/guide/topics/fundamentals/services.jd +++ b/docs/html/guide/topics/fundamentals/services.jd @@ -203,7 +203,7 @@ it from other application components.</p> <p>Like activities (and other components), you must declare all services in your application's manifest file.</p> -<p>To decalare your service, add a <a +<p>To declare your service, add a <a href="{@docRoot}guide/topics/manifest/service-element.html">{@code <service>}</a> element as a child of the <a href="{@docRoot}guide/topics/manifest/application-element.html">{@code <application>}</a> @@ -222,9 +222,17 @@ element. For example:</p> <p>There are other attributes you can include in the <a href="{@docRoot}guide/topics/manifest/service-element.html">{@code <service>}</a> element to define properties such as permissions required to start the service and the process in -which the service should run. See the <a +which the service should run. The <a +href="{@docRoot}guide/topics/manifest/service-element.html#nm">{@code android:name}</a> +attribute is the only required attribute—it specifies the class name of the service. Once +you publish your application, you should not change this name, because if you do, you might break +some functionality where explicit intents are used to reference your service (read the blog post, <a +href="http://android-developers.blogspot.com/2011/06/things-that-cannot-change.html">Things +That Cannot Change</a>). + +<p>See the <a href="{@docRoot}guide/topics/manifest/service-element.html">{@code <service>}</a> element -reference for more information.</p> +reference for more information about declaring your service in the manifest.</p> <p>Just like an activity, a service can define intent filters that allow other components to invoke the service using implicit intents. By declaring intent filters, components |
