| /frameworks/base/docs/html/guide/topics/data/ |
| install-location.jd | 11 <li>You can allow your application to install on the device's external storage.</li>
34 <p>Beginning with API Level 8, you can allow your application to be installed on the
36 for your application with the <a
39 <em>not</em> declare this attribute, your application will be installed on the internal storage
42 <p>To allow the system to install your application on the external storage, modify your
55 <p>If you declare "{@code preferExternal}", you request that your application be installed on the
56 external storage, but the system does not guarantee that your application will be installed on
58 storage. The user can also move your application between the two locations.</p>
60 <p>If you declare "{@code auto}", you indicate that your application may be installed on the
62 decide where to install your application based on several factors. The user can also move you
[all...] |
| /frameworks/base/docs/html/guide/topics/manifest/ |
| service-element.jd | 20 <dd><code><a href="{@docRoot}guide/topics/manifest/application-element.html"><application></a></code></dd>
28 of the application's components. Unlike activities, services lack a
47 The <code><a href="{@docRoot}guide/topics/manifest/application-element.html"><application></a></code> element has its own
48 <code><a href="{@docRoot}guide/topics/manifest/application-element.html#enabled">enabled</a></code> attribute that applies to all
49 application components, including services. The
50 <code><a href="{@docRoot}guide/topics/manifest/application-element.html"><application></a></code> and {@code <service>}
60 components of the same application or applications
[all...] |
| compatible-screens-element.jd | 23 <dd>Specifies each screen configuration with which the application is compatible. Only one instance
26 specifies a specific screen size-density combination with which the application is compatible.
30 by external services (such as Google Play) to better understand the application's compatibility
32 <em>not</em> declared in this element is a screen with which the application is <em>not</em>
33 compatible. Thus, external services (such as Google Play) should not provide the application to
38 application, by not allowing users to install your application if they have a device with a screen
40 application absolutely does not work with specific screen configurations. Instead of using this
46 <p>If you want to set only a minimum screen <em>size</em> for your your application, then you
48 <supports-screens>}</a> element. For example, if you want your application to be availabl
[all...] |
| uses-feature-element.jd | 16 <li><a href="#testing">Testing the features required by your application</a></li>
38 <p style="margin-top:1em;">By specifying the features that your application requires,
39 you enable Google Play to present your application only to users whose
40 devices meet the application's feature requirements, rather than presenting it
66 application.
70 application depends. The element offers a <code>required</code> attribute that
71 lets you specify whether your application requires and cannot function without
75 application describe the device-variable features that it uses.</p>
77 <p>The set of available features that your application declares corresponds to
84 element, so if your application requires multiple features, it would declar
[all...] |
| supports-gl-texture-element.jd | 38 the application.
40 <p>An application "supports" a GL texture compression format if it is capable of
42 application is installed on a device. The application can provide the
48 <code>android:name</code> attribute. If your application supports multiple
58 (such as Google Play) or applications can check your application's
60 interacting with your application. For this reason, it's very important that
62 your application is capable of supporting. </p>
69 <p>Assuming that the application is built with SDK Platform Tools r3 or higher,
79 <dd>Specifies a single GL texture compression format supported by the application,
[all...] |
| /packages/apps/PackageInstaller/res/values-fr-rCA/ |
| strings.xml | 23 <string name="security_settings_desc" msgid="2706691034244052604">"Autoriser cette application à :"</string>
27 <string name="install_done" msgid="3682715442154357097">"Application installée."</string>
28 <string name="install_confirm_question" msgid="7295206719219043890">"Voulez-vous installer cette application? Elle pourra :"</string>
29 <string name="install_confirm_question_no_perms" msgid="5918305641302873520">"Voulez-vous installer cette application? Elle n\'exige aucun accès particulier."</string>
30 <string name="install_confirm_question_update" msgid="4624159567361487964">"Voulez-vous installer une mise à jour pour cette application? Vos données existantes seront conservées. L\'application mise à jour aura accès à :"</string>
31 <string name="install_confirm_question_update_system" msgid="1302330093676416336">"Voulez-vous installer une mise à jour pour cette application intégrée? Vos données existantes seront conservées. L\'application mise à jour aura accès à :"</string>
32 <string name="install_confirm_question_update_no_perms" msgid="4885928136844618944">"Voulez-vous installer une mise à jour pour cette application? Vos données ne seront pas perdues. Aucun droit d\'accès spécial n\'est requis."</string>
33 <string name="install_confirm_question_update_system_no_perms" msgid="7676593512694724374">"Voulez-vous installer une mise à jour pour cette application intégrée? Vos données existantes ne seront pas perdues. Aucun droit d\'accès spécial n\'est requis (…)
[all...] |
| /frameworks/base/docs/html/guide/topics/resources/ |
| localization.jd | 2 parent.title=Application Resources
37 your application should handle text, audio files, numbers, currency, and
38 graphics in ways appropriate to the locales where your application will be used.
42 applications. The principles apply whether you are developing your application
51 localized aspects of your application as much as possible from the core Java
55 <li>You can put most or all of the <em>contents</em> of your application's
73 data that your Android application needs. An application can include multiple
75 user runs the application, Android automatically selects and loads the
87 <strong>When you write your application:</strong>
[all...] |
| /frameworks/base/docs/html/training/notepad/ |
| index.jd | 6 <p>This tutorial on writing a notepad application gives you a "hands-on" introduction
9 developing a simple notepad application and provides concrete examples of how to
10 set up the project, develop the application logic and user interface, and then
11 compile and run the application. </p>
13 <p>The tutorial presents the application development as a set of
16 application. The exercises explain each step in detail and provide all the
17 sample code you need to complete the application. </p>
20 Android application and will have learned many of the most important
22 your application, you can examine the code in an alternative implementation
23 of a Note Pad application, in the
[all...] |
| notepad-index.jd | 8 developing a simple notepad application and provides concrete examples of how to
9 set up the project, develop the application logic and user interface, and then
10 compile and run the application. </p>
12 <p>The tutorial presents the notepad application development as a set of
15 application. The exercises explain each step in detail and provide all the
16 sample code you need to complete the application. </p>
19 Android application and learned in depth about many of the most important
21 your application, you can examine the code in an alternative implementation
22 of a notepad application, in the
35 application concepts and terminology. If you aren't yet familiar with those, yo
[all...] |
| /frameworks/base/docs/html/google/play/billing/ |
| billing_testing.jd | 31 <p>To test In-app Billing in an application you must install the application on an Android-powered
34 the most current version of the Google Play application installed. If a device is not running the
35 most current Google Play application, your application won't be able to send In-app Billing
155 Google Play. This enables you to verify that your application is handling the primary Google
156 Play responses correctly and that your application is able to verify signatures correctly.</p>
170 <p>You do not need to list the reserved products in your application's product list. Google Play
171 already knows about the reserved product IDs. Also, you do not need to upload your application to
173 install your application on a device, log into the device, and make billing requests using th
[all...] |
| /development/samples/SkeletonApp/ |
| 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.*"
30 <!-- This package contains an application... The 'label' is the name
31 to display to the user for the overall application, and provides
34 <application android:label="@string/skeleton_app">
36 <!-- An Activity in the application - this is something the user
57 </application>
|
| /external/chromium/net/base/ |
| mime_util_unittest.cc | 77 EXPECT_TRUE(MatchesMimeType("application/*+xml",
78 "application/html+xml"));
79 EXPECT_TRUE(MatchesMimeType("application/*+xml", "application/+xml"));
85 EXPECT_FALSE(MatchesMimeType("application/*+xml", "application/xml"));
86 EXPECT_FALSE(MatchesMimeType("application/*+xml",
87 "application/html+xmlz"));
88 EXPECT_FALSE(MatchesMimeType("application/*+xml",
|
| /external/jmonkeyengine/engine/src/core/com/jme3/app/ |
| package.html | 10 The <code>com.jme3.application</code> provides a toolset for jME3 applications
12 {@link com.jme3.app.Application} class will be extended and the update() method
15 An <code>Application</code> will typically provide the following services:
18 data assets included with the application, such as models and textures.</li>
25 {@link com.jme3.app.state.AppState}s, which are specific application
33 settings for the application. These settings may be set by the user
34 or the application itself.</li>
40 An example use of the Application class is as follows<br>
44 public class ExampleUse extends Application {<br>
|
| /external/jmonkeyengine/engine/src/core/com/jme3/system/ |
| SystemListener.java | 36 * The <code>ContextListener> provides a means for an application
42 * Callback to indicate the application to initialize. This method
49 * Called to notify the application that the resolution has changed.
56 * Callback to update the application state, and render the scene
62 * Called when the user requests to close the application. This
66 * @param esc If true, the user pressed ESC to close the application.
71 * Called when the application gained focus. The display
78 * Called when the application lost focus. The display
94 * by the user or requested by the application itself). Typically
|
| /external/qemu/android/ |
| multitouch-port.h | 24 * application running on an Android device that provides touch events, and is
31 * NOTE: Application on the device side depends on these values. Any changes
32 * made here must be reflected in the app too. Application location is at
45 * region. This descriptor is also sent to the MT emulation application on the
48 * NOTE: Application on the device side depends on that structure. Any changes
49 * made here must be reflected in the app too. Application location is at
82 * application on the device.
89 /* Sends framebuffer update to the multi-touch emulation application, running on
96 * application on the device.
|
| /frameworks/native/opengl/libs/GLES_trace/ |
| DESIGN.txt | 16 Application runtime:
18 While the application is running, all its GLES calls are directly routed to their corresponding
24 Application shutdown:
26 Currently, the application is killed when the user stops tracing from the frontend GUI. We need
27 to explore if a more graceful method of stopping the application, or detaching tracing from the
28 application is required.
31 Enabling tracing while the application is running:
33 In order to allow tracing of an already running application, we allow DdmServer to enable
34 OpenGL tracing. In such a case, the application already has its GL hooks set up to point to the
|
| /prebuilts/python/darwin-x86/2.7.5/lib/python2.7/plat-mac/lib-scriptpackages/SystemEvents/ |
| Power_Suite.py | 76 class application(aetools.ComponentItem): class in inherits:aetools.ComponentItem
77 """application - The System Events application """
90 """properties - every property of the System Events application """
106 applications = application
107 application._superclassnames = []
113 application._privpropdict = {
118 application._privelemdict = {
136 'capp' : application,
|
| /packages/apps/PackageInstaller/res/values-fr/ |
| strings.xml | 23 <string name="security_settings_desc" msgid="2706691034244052604">"Autoriser cette application à :"</string>
27 <string name="install_done" msgid="3682715442154357097">"Application installée."</string>
28 <string name="install_confirm_question" msgid="7295206719219043890">"Voulez-vous installer cette application ? Elle pourra :"</string>
29 <string name="install_confirm_question_no_perms" msgid="5918305641302873520">"Voulez-vous installer cette application ? Elle n\'exige aucun accès particulier."</string>
30 <string name="install_confirm_question_update" msgid="4624159567361487964">"Voulez-vous installer une mise à jour pour cette application ? Vos données existantes seront conservées. L\'application mise à jour pourra :"</string>
31 <string name="install_confirm_question_update_system" msgid="1302330093676416336">"Voulez-vous installer une mise à jour pour cette application intégrée ? Vos données existantes seront conservées. L\'application mise à jour pourra :"</string>
32 <string name="install_confirm_question_update_no_perms" msgid="4885928136844618944">"Voulez-vous installer une mise à jour pour cette application ? Vos données ne seront pas perdues. Aucun droit d\'accès spécial n\'est requis."</string>
33 <string name="install_confirm_question_update_system_no_perms" msgid="7676593512694724374">"Voulez-vous installer une mise à jour pour cette application intégrée ? Vos données existantes ne seront pas perdues. Aucun droit d\'accès spécial n\'est requi (…)
[all...] |
| /frameworks/base/docs/html/google/backup/ |
| index.jd | 9 higher. The backup service is <em>not</em> designed for synchronizing application data with other
11 application lifecycle.</p>
17 transparent to your application.</p>
23 <p class="note"><strong>Note:</strong> Registering your application with Android Backup
26 data backup in your application, then it will back up using whichever transport is enabled
27 on the device. Registering with Android Backup Service allows your application to back up
42 <application>
46 </application>
51 <code><application></code> element.</p>
53 <p>When a device that uses Android Backup Service runs your application,
[all...] |
| /frameworks/base/docs/html/google/play/licensing/ |
| licensing-reference.jd | 2 parent.title=Application Licensing
54 access to the application, based on the license response. </td>
86 application to a specific device. Called from LicenseValidator. Implementing
124 <td>One-way IPC callback implementation over which the application receives an
135 licensing server. In general, an application should handle all of these response
153 <td>The application is licensed to the user. The user has purchased the
154 application or the application only exists as a draft.</td>
161 <td>The application is licensed to the user, but there is an updated application
[all...] |
| /frameworks/base/docs/html/tools/devices/ |
| index.jd | 39 To thoroughly test your application, you should create an AVD for each general device configuration
40 (for example, different screen sizes and platform versions) with which your application is compatible
41 and test your application on each one.</p>
46 <li>The API Level of the target is important, because your application will not be able to run
47 on a system image whose API Level is less than that required by your application, as specified
49 <code>minSdkVersion</code></a> attribute of the application's manifest file. For more
50 information about the relationship between system API Level and application
55 by your application, because it allows you to test the
56 forward-compatibility of your application. Forward-compatibility testing ensures that, when
57 users who have downloaded your application receive a system update, your application wil
[all...] |
| /frameworks/base/docs/html/tools/testing/ |
| activity_test.jd | 57 <a href="#InstallCompletedTestApp">Installing the Completed Test Application File</a>
82 instrumentation to give you control over your main application while you are testing it. The entire Android testing environment is discussed in the document
86 This tutorial demonstrates the Android testing tools by presenting a simple Android application and then leading you step-by-step through the creation of a test application for it.
87 The test application demonstrates these key points:
91 An Android test is itself an Android application that is linked to the application under test by entries in its <code>AndroidManifest.xml</code> file.
94 Instead of Android components, an Android test application contains one or more test cases. Each of these is a separate class definition.
100 Android test case classes for activities extend JUnit and also connect you to the application under test with instrumentation. You can send keystroke or touch events directly to the UI.
103 You choose an Android test case class based on the type of component (application, activity, content provider, or service) you are testing
[all...] |
| /external/libnfc-nxp/src/ |
| phOsalNfc_Timer.h | 59 * OSAL timer message .This message type will be posted to calling application thread.
104 * When a timer is created, it is not started by default. The application has to
113 * Application,phOsalNfc;
114 * Application=>phOsalNfc [label="phOsalNfc_Timer_Create()",URL="\ref phOsalNfc_Timer_Create"];
115 * Application<<phOsalNfc [label="Returns Valid timer ID"];
136 * \param[in] Application_callback Application Callback interface to be called
140 * Application,phOsalNfc;
141 * Application=>phOsalNfc [label="phOsalNfc_Timer_Create()", URL="\ref phOsalNfc_Timer_Create"];
142 * Application<<phOsalNfc [label="TIMERID"];
143 * Application=>phOsalNfc [label="phOsalNfc_Timer_Start(TIMERID, TIMEOUT, CB)", URL="\ref phOsalNfc_Timer_Start"]
[all...] |
| /frameworks/base/docs/html/guide/practices/ |
| screens-distribution.jd | 13 <li>If necessary, you can control distribution of your application based on the device
37 <p>Although we recommend that you design your application to function properly on multiple
39 application to certain types of screens, such as only tablets and other large devices or only
42 application supports.</p>
44 <p>However, before you decide to restrict your application to certain screen configurations, you
47 them to the best of your ability. By supporting multiple screens, your application can be made
55 need to filter your application from larger screens. As long as you follow the <a
57 Independence</a>, your application should work well on larger screens such as tablets. However, you
58 might discover that your application can't scale up well or perhaps you've decided to publish two
59 versions of your application for different screen configurations. In such a case, you can use the <
[all...] |
| /development/samples/Home/src/com/example/android/home/ |
| ApplicationInfo.java | 24 * Represents a launchable application. An application is made of a name (or title), an intent
29 * The application name.
34 * The intent used to start the application.
39 * The application icon.
49 * Creates the application intent based on a component name and various launch flags.
|
