| /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
|
| /external/chromium_org/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.
|
| /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...] |
| /frameworks/base/docs/html/guide/topics/manifest/ |
| uses-configuration-element.jd | 30 <dd>Indicates what hardware and software features the application requires.
31 For example, an application might specify that it requires a physical keyboard
33 used to avoid installing the application on devices where it will not work.
36 If an application can work with different device configurations, it
38 each one. Each declaration must be complete. For example, if an application
53 <dd>Whether or not the application requires a five-way navigation control
60 If an application requires a directional control, but not a control of a
68 <dd>Whether or not the application requires a hardware keyboard —
72 <dd>The type of keyboard the application requires, if any at all.
88 <td>The application does not require a keyboard.
[all...] |
| manifest-element.jd | 25 <dd><code><a href="{@docRoot}guide/topics/manifest/application-element.html"><application></a></code></dd>
39 contain an <code><a href="{@docRoot}guide/topics/manifest/application-element.html"><application></a></code> element
50 <dd>A full Java-language-style package name for the application. The name should
61 The package name serves as a unique identifier for the application.
62 It's also the default name for the application process (see the
63 <code><a href="{@docRoot}guide/topics/manifest/application-element.html"><application></a></code>
65 <code><a href="{@docRoot}guide/topics/manifest/application-element.html#aff">process</a></code
[all...] |
| /external/chromium_org/chrome/renderer/plugins/ |
| plugin_uma_unittest.cc | 23 "application/x-mplayer2",
26 "application/x-mplayer2-some_sufix",
29 "some-prefix-application/x-mplayer2",
35 "application/x-silverlight",
38 "application/x-silverlight-some-sufix",
41 "some-prefix-application/x-silverlight",
58 PluginUMAReporter::JAVA, "application/x-java-applet", GURL("some url"));
60 "application/x-java-applet-some-sufix",
63 "some-prefix-application/x-java-applet-sufix",
80 "application/browser-plugin"
[all...] |
| /frameworks/base/docs/html/training/in-app-billing/ |
| test-iab-app.jd | 1 page.title=Testing Your In-app Billing Application
29 <p>To ensure that In-app Billing is functioning correctly in your application, you should test the test the application before you publish it on Google Play. Early testing also helps to ensure that the user flow for purchasing in-app items is not confusing or slow, and that users can see their newly purchased items in a timely way.</p>
32 Test your In-app Billing application with static responses by using Google Play?s reserved product IDs.By using reserved product IDs instead of actual product IDs, you can test the purchase flow without specifying an actual payment method or transferring money. To learn more about the reserved product IDs, see <a href="{@docRoot}google/play/billing/billing_testing.html">Testing In-app Billing</a>.
36 <p>To test your In-app Billing Version 3 application using your own product IDs:
38 <li>In the Developer Console, add one or more tester accounts to the developer account that you are using to publish your application.
43 <li>Build a signed APK file for your In-app Billing application. To learn how to build and sign your APK, see <a href="{@docRoot}tools/publishing/preparing.html#publishing-build">Building Your Application for Release</a>. Make sure that you are using your final (not debug) certificate and private key to sign your application.
45 <li>Make sure that you have uploaded the signed APK for your application to the Developer Console, and associated one or more in-app products with your application. You do (…)
[all...] |
| /frameworks/base/docs/html/google/play/billing/v2/ |
| api.jd | 62 items such as game levels or application features. These items are not transient
63 and usually need to be restored whenever a user reinstalls your application,
64 wipes the data on their device, or installs your application on a new
76 such as fuel or magic spells. These items are consumed within your application
100 application and the Google Play server. In practice, your application never
102 application sends billing requests to the Google Play application over
104 Play application in the form of asynchronous broadcast intents. Your application
[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...] |
| /external/chromium_org/chrome/android/java/src/org/chromium/chrome/browser/sync/ |
| ChromiumSyncAdapterService.java | 7 import android.app.Application;
35 Application application);
|
| /external/chromium_org/content/public/android/java/src/org/chromium/content/browser/ |
| ContentViewDownloadDelegate.java | 12 * Notify the host application that a file should be downloaded. Replaces
19 * Notify the host application that a download is started.
26 * Notify the host application that a download has an extension indicating
|
| /external/chromium_org/net/socket/ |
| next_proto.h | 11 // application-level string that specifies the application level protocol to
12 // use over the TLS connection. NextProto enumerates the application level
|
| /external/qemu/distrib/sdl-1.2.15/Xcode/SDL/pkg-support/devel-resources/ |
| install.sh | 37 if [ -e "/Library/Application Support/Apple/Developer Tools" ] ; then
39 PBXDIR="/Library/Application Support/Apple/Developer Tools"
46 mkdir -p "$PBXDIR/Project Templates/Application"
49 cp -r "$ROOT/Project Stationary/SDL Application" "$PBXDIR/Project Templates/Application/"
50 cp -r "$ROOT/Project Stationary/SDL Cocoa Application" "$PBXDIR/Project Templates/Application/"
51 cp -r "$ROOT/Project Stationary/SDL Custom Cocoa Application" "$PBXDIR/Project Templates/Application/"
52 cp -r "$ROOT/Project Stationary/SDL OpenGL Application" "$PBXDIR/Project Templates/Application/
[all...] |
| /external/robolectric/src/test/java/com/xtremelabs/robolectric/shadows/ |
| LayoutInflaterTest.java | 20 layoutInflater = LayoutInflater.from(Robolectric.application);
26 assertSame(LayoutInflater.from(Robolectric.application), layoutInflater);
27 assertSame(LayoutInflater.from(new ContextWrapper(Robolectric.application)), layoutInflater);
|
| PendingIntentTest.java | 38 PendingIntent pendingIntent = PendingIntent.getBroadcast(Robolectric.application, 99, intent, 100);
44 assertThat(Robolectric.application, equalTo(shadow.getSavedContext()));
50 PendingIntent pendingIntent = PendingIntent.getActivity(Robolectric.application, 99, intent, 100);
56 assertThat(Robolectric.application, equalTo(shadow.getSavedContext()));
62 PendingIntent pendingIntent = PendingIntent.getService(Robolectric.application, 99, intent, 100);
68 assertThat(Robolectric.application, equalTo(shadow.getSavedContext()));
89 PendingIntent pi1 = PendingIntent.getActivity(Robolectric.application, 99,
92 PendingIntent pi3 = PendingIntent.getService(Robolectric.application, 99,
106 .getBroadcast(Robolectric.application, 99, null, 100));
112 .getBroadcast(Robolectric.application, 99, new Intent(), 100))
[all...] |
| WifiInfoTest.java | 10 import static com.xtremelabs.robolectric.Robolectric.application;
20 WifiManager wifiManager = (WifiManager) application.getSystemService(WIFI_SERVICE);
24 wifiManager = (WifiManager) application.getSystemService(WIFI_SERVICE);
|
| /frameworks/base/docs/html/tools/debugging/ |
| debugging-devtools.jd | 6 <p>The Dev Tools application is installed by default on all system images included with the SDK,
7 so you can use it with the Android Emulator. With the Dev Tools application, you can enable a
10 <p> The Dev Tools application relies on a number of permissions that are not available for
11 third party applications. If you'd like to install the Dev Tools application
13 the Dev Tools application with the same key as used for the system image.</p>
15 <p>To get started, launch the Dev Tools application and select <strong>Development Settings</strong>. This will
22 Lets you select the application to debug. You do not need to set this to attach a debugger,
29 <li>It will enable you to select the <em>Wait for Debugger</em> option to pause application
36 <dd>Blocks the selected application from loading until a debugger attaches. This way you can
39 When you change this option, any currently running instances of the selected application wil
[all...] |
| /sdk/eclipse/plugins/com.android.ide.eclipse.tests/unittests/com/android/ide/eclipse/adt/internal/editors/manifest/model/ |
| UiElementNodeTest.java | 47 mAppDesc = new ElementDescriptor("application", new ElementDescriptor[] {
85 * We declared the descriptors as having a "mandatory last" application element
87 * UiModel, we should get these two created, with the application element after
103 new MockXmlNode(null /* namespace */, "application", Node.ELEMENT_NODE, null)
109 // before application since it's a mandatory-last so it "moves" to the end if possible.
134 new MockXmlNode(null /* namespace */, "application", Node.ELEMENT_NODE, null)
143 // get /manifest/application
145 UiElementNode application = ui_child_it.next(); local
146 assertEquals("application", application.getDescriptor().getXmlName())
167 UiElementNode application = ui_child_it.next(); local
212 UiElementNode application = ui_child_it.next(); local
[all...] |
