| /frameworks/base/test-runner/src/android/test/ |
| ApplicationTestCase.java | 21 import android.app.Application;
26 * This test case provides a framework in which you can test Application classes in
28 * Application, and hooks by which you can inject various dependencies and control
29 * the environment in which your Application is tested.
32 * Every Application is designed to be accessed within a specific sequence of
33 * method calls (see {@link android.app.Application} for more details).
34 * In order to support the lifecycle of a Application, this test case will make the
42 * automatically called, and it will stop & destroy your application by calling its
47 * Every Application has one inherent dependency, the {@link android.content.Context Context} in
52 * <p>If simply run your tests as-is, your Application will be injected with a fully-functiona
[all...] |
| /development/samples/TicTacToeMain/ |
| _index.html | 1 <p>This sample demonstrates how an application can make use of shared code and
4 <p>In this case, the TicTacToeMain application project includes a reference to
5 the TicTacToeLib library project. When you build the TicTacToeMain application,
7 as part of the main application's <code>.apk</code> file. The main application
14 <li>The main application's <a
18 Currently, an application must declare in its manifest any components or
22 shows how a class in the main application imports and uses
30 <code>GameActivity</code>, that handles most of the application lifecycle.</p>
38 handles most of the application lifecycle and manages general game play.</li
[all...] |
| /frameworks/base/docs/html/guide/google/play/licensing/ |
| overview.jd | 2 parent.title=Application Licensing
29 <p>Google Play Licensing is a network-based service that lets an application query a trusted
30 Google Play licensing server to determine whether the application is licensed to the current
32 to determine whether a given user is licensed to use a given application. Google Play considers a
33 user to be licensed if the user is a recorded purchaser of the application.</p>
35 <p>The request starts when your application makes a request to a service hosted by
36 the Google Play client application. The Google Play application then sends a request to
37 the licensing server and receives the result. The Google Play application sends
38 the result to your application, which can allow or disallow further use of th
[all...] |
| /sdk/eclipse/plugins/com.android.ide.eclipse.ddms/src/com/android/ide/eclipse/ddms/ |
| IDebuggerConnector.java | 25 * Is this application from a project present in the workspace?
26 * @param appName name of the application. This is typically the application's package, but
35 * The given port is tied to the application and should be used if possible. However the
37 * @param appName the name of the application. Usually the application's package but this
40 * @param selectedPort the port value for the selected application
|
| /tools/motodev/src/plugins/android/src/com/motorola/studio/android/adt/ |
| Sample.java | 25 * Bean that represents a sample application
43 * Retrieves the sample application folder
45 * @return the sample application folder
53 * Retrieves the sample application name
55 * @return the sample application name
63 * Retrieves the sample application target SDK
65 * @return the sample application target SDK
|
| /frameworks/base/docs/html/guide/topics/manifest/ |
| receiver-element.jd | 19 <dd><code><a href="{@docRoot}guide/topics/manifest/application-element.html"><application></a></code></dd>
27 subclass) as one of the application's components. Broadcast receivers enable
29 applications, even when other components of the application are not running.
48 The <code><a href="{@docRoot}guide/topics/manifest/application-element.html"><application></a></code> element has its own
49 <code><a href="{@docRoot}guide/topics/manifest/application-element.html#enabled">enabled</a></code> attribute that applies to all
50 application components, including broadcast receivers. The
51 <code><a href="{@docRoot}guide/topics/manifest/application-element.html"><application></a></code> an
[all...] |
| uses-configuration-element.jd | 32 <dd>Indicates what hardware and software features the application requires.
33 For example, an application might specify that it requires a physical keyboard
35 used to avoid installing the application on devices where it will not work.
38 If an application can work with different device configurations, it
40 each one. Each declaration must be complete. For example, if an application
55 <dd>Whether or not the application requires a five-way navigation control
62 If an application requires a directional control, but not a control of a
70 <dd>Whether or not the application requires a hardware keyboard —
74 <dd>The type of keyboard the application requires, if any at all.
90 <td>The application does not require a keyboard.
[all...] |
| /frameworks/base/docs/html/guide/webapps/ |
| overview.jd | 7 users in two ways: in a traditional web browser and in an Android application, by
11 <p>There are essentially two ways to deliver an application on Android: as a
12 client-side application (developed using the Android SDK and installed on user devices as an {@code
13 .apk}) or as a web application (developed using web standards and accessed through a web
16 <p>The approach you choose for your application could depend on several factors, but Android makes
17 the decision to develop a web application easier by providing:</p>
19 <li>Support for viewport properties that allow you to properly size your web application
25 <p>Thus, your decision to develop a web application for Android can exclude consideration for
29 <p>Another great feature of Android is that you don't have to build your application purely on
31 application that embeds some web pages (using a {@link android.webkit.WebView} in your Androi
[all...] |
| /frameworks/base/docs/html/guide/practices/app-design/ |
| responsiveness.jd | 23 but still sends users in a fiery rage when they try to use the application.
30 Application Not Responding (ANR) dialog, shown at right in Figure 1. The user
31 can choose to let the application continue, but the user won't appreciate having
32 to act on this dialog every time he or she uses your application. It's critical
33 to design responsiveness into your application, so that the system never has
36 <p>Generally, the system displays an ANR if an application cannot respond to
37 user input. For example, if an application blocks on some I/O operation
38 (frequently a network access), then the main application thread won't be able to
40 application is frozen, and displays the ANR to give the user the option to kill
43 <p>Similarly, if your application spends too much time building an elaborate in-memor
[all...] |
| /frameworks/base/docs/html/guide/practices/ |
| responsiveness.jd | 23 but still sends users in a fiery rage when they try to use the application.
30 Application Not Responding (ANR) dialog, shown at right in Figure 1. The user
31 can choose to let the application continue, but the user won't appreciate having
32 to act on this dialog every time he or she uses your application. It's critical
33 to design responsiveness into your application, so that the system never has
36 <p>Generally, the system displays an ANR if an application cannot respond to
37 user input. For example, if an application blocks on some I/O operation
38 (frequently a network access), then the main application thread won't be able to
40 application is frozen, and displays the ANR to give the user the option to kill
43 <p>Similarly, if your application spends too much time building an elaborate in-memor
[all...] |
| /development/samples/SpinnerTest/ |
| _index.html | 2 This sample is the test application for the
5 application.
8 The test application uses the
16 The application shows how to set up a test application project,
18 file for a test application, and how to set up a test case class for a test fixture. The
24 Test setup: The <code>setUp()</code> method re-initializes the state of the application under test
29 test that the application under test is properly initialized prior to running the
37 Application control using instrumentation: The <code>testStateDestroy()</code> and <code>testStatePause()</code>
43 that links the test application with the application under test. Specifically, th
[all...] |
| /frameworks/base/core/java/android/provider/ |
| Applications.java | 44 * The content path for application component URIs.
49 * The content path for application search.
53 private static final String APPLICATION_SUB_TYPE = "vnd.android.application";
56 * The MIME type for a single application item.
62 * The MIME type for a list of application items.
73 * Gets a cursor with application search results.
82 * Gets the application component name from an application URI.
86 * @return The component name for the application, or
103 * Gets the URI for an application component
[all...] |
| /development/samples/Compass/ |
| AndroidManifest.xml | 18 used by the system to determine how to start your application and
21 <!-- Declare the contents of this Android application. The namespace
23 supplies a unique name for the application. When writing your
24 own application, the package name must be changed from "com.example.*"
29 <!-- This package contains an application... The 'label' is the name
30 to display to the user for the overall application, and provides
33 <application android:label="@string/compass_app">
35 <!-- An Activity in the application - this is something the user
56 </application>
|
| /development/samples/HeavyWeight/ |
| AndroidManifest.xml | 17 <!-- Declare the contents of this Android application. The namespace
19 supplies a unique name for the application. When writing your
20 own application, the package name must be changed from "com.example.*"
24 <application android:label="Heavy Weight" android:cantSaveState="true">
31 </application>
|
| /development/samples/HelloActivity/ |
| AndroidManifest.xml | 17 <!-- Declare the contents of this Android application. The namespace
19 supplies a unique name for the application. When writing your
20 own application, the package name must be changed from "com.example.*"
24 <application android:label="Hello, Activity!">
31 </application>
|
| /external/chromium/chrome/common/extensions/docs/examples/apps/hello-python/ |
| README | 6 This application implements a sample client for the Chrome Web Store Licensing
18 app.yaml and replace the text INSERT APPLICATION NAME HERE with the application
27 'app_id': 'INSERT APPLICATION ID HERE',
29 Then deploy your application to App Engine, and you will be able to log in
|
| /frameworks/base/core/java/android/preference/ |
| package.html | 3 Provides classes that manage application preferences and implement the preferences UI.
4 Using these ensures that all the preferences within each application are maintained
8 The preferences portion of an application
18 to the application's instance of {@link android.content.SharedPreferences}. Access to the
21 Note that saved preferences are accessible only to the application that created them.</p>
|
| /frameworks/base/services/java/com/android/server/input/ |
| InputApplicationHandle.java | 20 * Functions as a handle for an application that can receive input.
22 * application window token.
26 // Pointer to the native input application handle.
31 // The window manager's application window token.
34 // Application name.
|
| /packages/providers/DrmProvider/ |
| AndroidManifest.xml | 5 <!-- Allows an application to access DRM content -->
18 <application android:process="android.process.media"
30 <data android:mimeType="application/vnd.oma.drm.rights+xml" />
31 <data android:value="application/vnd.oma.drm.rights+wbxml" />
35 </application>
|
| /sdk/avdlauncher/ |
| avdlauncher.exe.manifest | 10 <application>
11 <!--The ID below indicates application support for Windows Vista -->
13 <!--The ID below indicates application support for Windows 7 -->
15 </application>
25 <!-- Identify the application security requirements. -->
|
| /sdk/find_java/ |
| find_java.exe.manifest | 10 <application>
11 <!--The ID below indicates application support for Windows Vista -->
13 <!--The ID below indicates application support for Windows 7 -->
15 </application>
25 <!-- Identify the application security requirements. -->
|
| /sdk/find_lock/ |
| find_lock.exe.manifest | 10 <application>
11 <!--The ID below indicates application support for Windows Vista -->
13 <!--The ID below indicates application support for Windows 7 -->
15 </application>
25 <!-- Identify the application security requirements. -->
|
| /sdk/sdklauncher/ |
| sdklauncher.exe.manifest | 10 <application>
11 <!--The ID below indicates application support for Windows Vista -->
13 <!--The ID below indicates application support for Windows 7 -->
15 </application>
25 <!-- Identify the application security requirements. -->
|
| /frameworks/base/docs/html/tools/building/ |
| building-eclipse.jd | 24 <p>When Eclipse automatically builds your application, it enables debugging and signs the
25 <code>.apk</code> with a debug key, by default. When you run the application,
26 Eclipse invokes ADB and installs your application to a device or emulator, so you do not have to
28 following topics show you how to run an application, which will automatically build your
29 application as well.</p>
31 <p>To distribute your application, however, you must build your application in release mode and sign the
34 <p>This document shows you how to run your application on an emulator or a real device
35 from Eclipse—all of which is done using the debug version of your application.
36 For more information about how to sign your application with a private key for release, see <a href
[all...] |
| /development/samples/SipDemo/ |
| _index.html | 1 <p>This is a demo application highlighting how to make internet-based calls with
2 the SIP API. The application uses a walkie-talkie style interface, allowing you
8 within the application.</p>
11 <p>The application includes:<p>
24 <p>If you are developing an application that uses the SIP API, remember that the
27 not all devices will offer SIP support. To ensure that your application can only
29 following to the application's manifest before publishing to Google Play:</p>
31 indicates to Google Play and the platform that your application requires
36 element.</li> </ul> <p>To control how Google Play filters your application
38 application's manifest <ul> <li><code><uses-featur
[all...] |
