| /frameworks/base/docs/html/google/play/billing/ |
| billing_overview.jd | 32 <li><a href="{@docRoot}training/in-app-billing/preparing-iab-app.html#GetSample">Sample Application (V3)</a></li>
39 Billing features into your application.</p>
52 <p>Your application accesses the In-app Billing service using an API that is
55 application and the Google Play server. In practice, your application never
56 directly communicates with the Google Play server. Instead, your application
57 sends billing requests to the Google Play application over interprocess
59 Your application does not manage any network connections between itself and
90 application to users. Examples of digital goods includes in-game currency,
91 application feature upgrades that enhance the user experience, and new conten
[all...] |
| /frameworks/base/tests/AccessoryDisplay/ |
| README | 9 1. Sink Application
15 The sink application uses the UsbDevice APIs to receive connections
19 The sink application decodes encoded video from the source and
23 2. Source Application
30 The source application uses the UsbAccessory APIs to connect
34 The source application uses the DisplayManager APIs to create
37 the application opens a Presentation on the new virtual display
|
| /frameworks/base/tests/Camera2Tests/SmartCamera/ |
| README.txt | 20 How to build the application:
22 Otherwise, to build the application for a specific device, lunch to that device
25 and run adb install out/target/.../SmartCamera.apk. The application should
35 How to run the application:
36 On a Nexus 7, open up the application from the launcher, and the camera preview
42 The application tries to take good pictures for you automatically when in the
43 start mode. On stop, the application will capture whatever images are in the
|
| /development/samples/Alarm/tests/ |
| _index.html | 2 This sample is the test application for the <a href="../Alarm/index.html">Alarm</a>
3 sample application. It tests the application's <code>AlarmService</code> service.
6 The test application uses the
15 The application shows how to set up a test application project,
17 file for a test application, and how to set up a test case class for a service. The
35 element that links the test application with the application under test. Specifically, the
48 Android package name for the test application (specified in the manifest file), i
[all...] |
| /docs/source.android.com/src/devices/tech/datausage/ |
| kernel-overview.jd | 19 <p>The per-application/delegated data usage monitoring and tracking
30 restrict background data traffic for an application (refer to
36 per-socket basis for every application using the unique UID of the
37 owning application. There are two tag components associated with any
39 the application which is responsible for the data transfer (Linux
41 the UID of the calling application). The second tag component is used
42 to support additional characterization of the traffic into application
43 developer specified categories. Using these application level tags, an
44 application can profile the traffic into several sub-categories.</p>
48 to the UID of the requesting application using th
[all...] |
| /external/chromium_org/tools/telemetry/telemetry/core/platform/ |
| linux_platform_backend.py | 66 def CanLaunchApplication(self, application):
67 if application == 'ipfw' and not self._IsIpfwKernelModuleInstalled():
69 return super(LinuxPlatformBackend, self).CanLaunchApplication(application)
71 def InstallApplication(self, application):
72 if application == 'ipfw':
74 elif application == 'avconv':
75 self._InstallBinary(application, 'libav-tools')
76 elif application == 'perfhost':
77 self._InstallBinary(application, 'linux-tools')
80 'Please teach Telemetry how to install ' + application)
[all...] |
| /external/owasp/sanitizer/tools/findbugs/doc/manual/ |
| building.html | 3 <title>Chapter 3. Building FindBugs™ from Source</title><meta name="generator" content="DocBook XSL Stylesheets V1.76.1"><link rel="home" href="index.html" title="FindBugs™ Manual"><link rel="up" href="index.html" title="FindBugs™ Manual"><link rel="prev" href="installing.html" title="Chapter 2. Installing FindBugs™"><link rel="next" href="running.html" title="Chapter 4. Running FindBugs™"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 3. Building <span class="application">FindBugs</span>™ from Source</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="installing.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="running.html">Next</a></td></tr></table><hr></div><div class="chapter" title="Chapter 3. Building FindBugs™ from Source"><div class="titlepage"><div><div><h2 class="title"><a name="building"></a>Chapter 3. Building <span class="application">FindBugs</span>™ from Source</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="building.html#d0e173">1. Prerequisites</a></span></dt><dt><span class="sect1"><a href="building.html#d0e262">2. Extracting the Source Distribution</a></span></dt><dt><span class="sect1"><a href="building.html#d0e275">3. Modifying <code class="filename">local.properties</code></a></span></dt><dt><span class="sect1"><a href="building.html#d0e333">4. Running <span class="application">Ant</span></a></span></dt><dt><span class="sect1"><a href="building.html#d0e427">5. Running <span class="application">FindBugs</span>™ from a source directory</a></span></dt></dl></div><p>
4 This chapter describes how to build <span class="application">FindBugs</span> from source code. Unless you are
5 interesting in modifying <span class="application">FindBugs</span>, you will probably want to skip to the
8 To compile <span class="application">FindBugs</span> from source, you will need the following:
10 The <a class="ulink" href="http://prdownloads.sourceforge.net/findbugs/findbugs-2.0.3-source.zip?download" target="_top"><span class="application">FindBugs</span> source distribution</a>
14 <a class="ulink" href="http://ant.apache.org/" target="_top">Apache <span class="application">Ant</span></a>, version 1.6.3 or later
17 The version of <span class="application">Ant</span> included as <code class="filename">/usr/bin/ant</code> o
[all...] |
| /frameworks/base/core/java/android/bluetooth/ |
| BluetoothHealthAppConfiguration.java | 24 * The Bluetooth Health Application Configuration that is used in conjunction with
25 * the {@link BluetoothHealth} class. This class represents an application configuration
26 * that the Bluetooth Health third party application will register to communicate with the
39 * @param name Friendly name associated with the application configuration
51 * Constructor to register the application configuration.
53 * @param name Friendly name associated with the application configuration
102 * Return the data type associated with this application configuration.
111 * Return the name of the application configuration.
120 * Return the role associated with this application configuration.
130 * Return the channel type associated with this application configuration
[all...] |
| /frameworks/base/docs/html/google/play/billing/v2/ |
| billing_integrate.jd | 37 <li><a href="#billing-implement">Modifying Your Application Code</a></li>
41 <li><a href="#billing-download">Sample Application (V2)</a></li>
47 implementation tasks, using the sample application as an example.</p>
49 <p>Before you implement in-app billing in your own application, be sure that you read <a
55 <p>To implement in-app billing in your application, you need to do the following:</p>
57 <li><a href="#billing-download">Download the in-app billing sample application</a>.</li>
61 <code>MarketBillingService</code> so your application can send billing requests and receive
67 <li><a href="#billing-implement">Modify your application code</a> to support in-app billing.</li>
70 <h2 id="billing-download">Downloading the Sample Application</h2>
72 <p>The in-app billing sample application shows you how to perform several tasks that are common t
[all...] |
| /frameworks/base/docs/html/guide/practices/app-design/ |
| seamlessness.jd | 24 <p>Even if your application is fast and responsive, certain design decisions can
29 application. In short, you should strive to develop an application that
32 <p>A common seamlessness problem is when an application's background process
35 you are building and testing your application in isolation, on the emulator.
36 However, when your application is run on an actual device, your application may
38 it could end up that your application would display it's dialog behind the
39 active application, or it could take focus from the current application an
[all...] |
| /frameworks/base/docs/html/guide/practices/ |
| seamlessness.jd | 25 <p>Even if your application is fast and responsive, certain design decisions can
30 application. In short, you should strive to develop an application that
33 <p>A common seamlessness problem is when an application's background process
36 you are building and testing your application in isolation, on the emulator.
37 However, when your application is run on an actual device, your application may
39 it could end up that your application would display it's dialog behind the
40 active application, or it could take focus from the current application an
[all...] |
| /frameworks/base/docs/html/guide/topics/manifest/ |
| supports-screens-element.jd | 27 <dd itemprop="description">Lets you specify the screen sizes your application supports and enable <a
29 larger than what your application supports. It's important that you always use this element in your
30 application to specify the screen sizes your application supports.
32 <p>An application "supports" a given screen size if it resizes properly to fill the entire screen.
34 extra work to make your application work on screens larger than a handset device. However, it's
35 often important that you optimize your application's UI for different screen sizes by providing <a
40 <p>However, if your application does not work well when resized to fit different screen sizes, you
42 application should be distributed to smaller screens or have its UI scaled up ("zoomed") to fit
53 android:largestWidthLimitDp}. If you're developing your application for Android 3.2 and higher
[all...] |
| /frameworks/base/docs/html/guide/webapps/ |
| index.jd | 8 users in two ways: in a traditional web browser and in an Android application, by
12 <p>There are essentially two ways to deliver an application on Android: as a
13 client-side application (developed using the Android SDK and installed on user devices in an APK)
14 or as a web application (developed using web standards and accessed through a web
26 interface between your Android application and your web pages that allows JavaScript in the web
27 pages to call upon APIs in your Android application—providing Android APIs to your web-based
28 application.</p>
37 application that you at least expect to be available on Android-powered devices (which you should
42 <dd>How to embed web pages into your Android application using {@link
48 <dd>A list of practices you should follow, in order to provide an effective web application o
[all...] |
| /frameworks/base/docs/html/tools/projects/ |
| index.jd | 26 application correctly, so it is highly recommended that you create them with Eclipse and ADT or
33 <dd>An Android project is the container for your application's source code, resource files, and
34 files such as the Ant build and Android Manifest file. An application project is the main type
40 <dd>These projects contain code to test your application projects and are built into
54 generate your project. As your application grows in complexity, you might require new kinds of
60 onto a device. They contain things such as application source code and resource files.
97 Contains application resources, such as drawable files, layout files, and string values. See
98 <a href="{@docRoot}guide/topics/resources/index.html">Application Resources</a> for more
128 <dd>For XML files that define application menus.
136 are processed by aapt and must be referenced from the application using a resourc
[all...] |
| /development/samples/AliasActivity/ |
| 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:hasCode="false" android:label="@string/app_label">
33 </application>
|
| /development/samples/LunarLander/ |
| 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.*"
27 <application android:icon="@drawable/app_lunar_lander" android:label="@string/app_name">
34 </application>
|
| /development/samples/RSSReader/ |
| 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.*"
25 <application android:label="RSS Reader">
34 </application>
|
| /development/samples/Snake/ |
| AndroidManifest.xml | 17 <!-- Declare the contents of this Android application. The namespace attribute
19 name for the application. When writing your own application, the package
33 <application android:icon="@drawable/ic_launcher" android:label="@string/app_name">
42 </application>
|
| /development/samples/StackWidget/ |
| 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.*"
26 <application android:label="StackWidget">
38 </application>
|
| /development/samples/VoicemailProviderDemo/ |
| AndroidManifest.xml | 18 <!-- Declare the contents of this Android application. The namespace
20 supplies a unique name for the application. When writing your
21 own application, the package name must be changed from "com.example.*"
32 <application android:icon="@drawable/icon" android:label="@string/app_name">
39 </application>
|
| /external/chromium_org/mojo/examples/compositor_app/ |
| compositor_app.cc | 10 #include "mojo/public/cpp/application/application.h"
21 class SampleApp : public Application, public NativeViewportClient {
65 Application* Application::Create() {
|
| /external/chromium_org/mojo/examples/sample_app/ |
| sample_app.cc | 9 #include "mojo/public/cpp/application/application.h"
20 class SampleApp : public Application, public NativeViewportClient {
80 Application* Application::Create() {
|
| /external/chromium_org/third_party/libjingle/source/talk/examples/objc/AppRTCDemo/ios/ |
| APPRTCAppDelegate.m | 39 - (BOOL)application:(UIApplication*)application
51 - (void)applicationWillResignActive:(UIApplication*)application {
52 [[self appRTCViewController] applicationWillResignActive:application];
55 - (void)applicationWillTerminate:(UIApplication*)application {
|
| /external/nist-sip/java/gov/nist/javax/sip/ |
| DialogExt.java | 41 * application layer including those that arrive out of order. This is good for testing
42 * purposes. Validation is delegated to the application and the stack will not attempt to
43 * block requests arriving out of sequence from reaching the application. In particular, the
44 * validation of CSeq and the ACK retransmission recognition are delegated to the application.
45 * Your application will be responsible for error handling of these cases.
|
| /external/qemu/distrib/sdl-1.2.15/include/ |
| SDL_active.h | 25 * Include file for SDL application focus event handling
40 /** @name The available application states */
44 #define SDL_APPACTIVE 0x04 /**< The application is active */
49 * This function returns the current state of the application, which is a
52 * see your application, otherwise it has been iconified or disabled.
|
