Android/frameworks_base
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge "docs: Clarified purpose of application "name" attr within manifest." into mnc-mr-docs

Browse Source 
am: c3500321cd

* commit 'c3500321cd10300b5dd44330e704fec55d62bce6':
  docs: Clarified purpose of application "name" attr within manifest.

Change-Id: I8d7ed288d4265b28372f09c17ad48d06c2a904c7
This commit is contained in:
Kevin Hufnagle
2016-04-20 00:56:17 +00:00
committed by android-build-merger
parent 86efe4331c c3500321cd
commit c9c3ad8c5e
2 changed files with 21 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files

26
core/java/android/app/Application.java
View File

@@ -28,19 +28,21 @@ import android.content.res.Configuration;
import android.os.Bundle;
/**
* Base class for those who need to maintain global application state. You can
* provide your own implementation by specifying its name in your
* AndroidManifest.xml's <application> tag, which will cause that class
* to be instantiated for you when the process for your application/package is
* created.
* Base class for maintaining global application state. You can provide your own
* implementation by creating a subclass and specifying the fully-qualified name
* of this subclass as the <code>"android:name"</code> attribute in your
* AndroidManifest.xml's <code>&lt;application&gt;</code> tag. The Application
* class, or your subclass of the Application class, is instantiated before any
* other class when the process for your application/package is created.
*
* <p class="note">There is normally no need to subclass Application. In
* most situation, static singletons can provide the same functionality in a
* more modular way. If your singleton needs a global context (for example
* to register broadcast receivers), the function to retrieve it can be
* given a {@link android.content.Context} which internally uses
* <p class="note"><strong>Note: </strong>There is normally no need to subclass
* Application. In most situations, static singletons can provide the same
* functionality in a more modular way. If your singleton needs a global
* context (for example to register broadcast receivers), include
* {@link android.content.Context#getApplicationContext() Context.getApplicationContext()}
* when first constructing the singleton.</p>
* as a {@link android.content.Context} argument when invoking your singleton's
* <code>getInstance()</code> method.
* </p>
*/
public class Application extends ContextWrapper implements ComponentCallbacks2 {
private ArrayList<ComponentCallbacks> mComponentCallbacks =
@@ -287,4 +289,4 @@ public class Application extends ContextWrapper implements ComponentCallbacks2 {
}
}
}
}
}

14
core/res/res/values/attrs_manifest.xml
View File

@@ -1176,14 +1176,14 @@
{@link #AndroidManifestActivity activity},
{@link #AndroidManifestActivityAlias activity-alias}, and
{@link #AndroidManifestUsesLibrary uses-library}. The application tag
appears as a child of the root {@link #AndroidManifest manifest} tag. -->
appears as a child of the root {@link #AndroidManifest manifest} tag in
an application's manifest file. -->
<declare-styleable name="AndroidManifestApplication" parent="AndroidManifest">
<!-- An optional name of a class implementing the overall
{@link android.app.Application} for this package. When the
process for your package is started, this class is instantiated
before any of the other application components. Note that this
is not required, and in fact most applications will probably
not need it. -->
<!-- The (optional) fully-qualified name for a subclass of
{@link android.app.Application} that the system instantiates before
any other class when an app's process starts. Most applications
don't need this attribute. If it's not specified, the system
instantiates the base Application class instead.-->
<attr name="name" />
<attr name="theme" />
<attr name="label" />