Lines Matching full:application
74 give developers additional ways to manage application UI across the range of
100 <p>When designing an application's UI, you can still rely on the platform to
103 can design the application UI according to the amount of horizontal or vertical
116 in which the application UI will need to be drawn, not including screen areas
121 current horizontal or vertical space available for application layout, measured
128 <p>The new screens support API is designed to let you manage application UI
248 manifest attributes specify the range of screens that the application supports,
255 attribute lets you specify the maximum smallestWidth on which the application
257 the value specified, the system displays the application in normal mode but
262 attribute lets you specify the maximum smallestWidth on which the application
264 the system forces the application into screen compatibility mode, to ensure best
268 attribute lets you specify the minimum smallestWidth on which the application
270 considers the application incompatible with the device, but does not prevent it
288 renders the application in a smaller screen area and then scales the pixels to
296 applications, the platform allows the application to disable it using manifest
343 methods let an application re-attach or detach fragments in the UI.</li>
361 in the application manifest file.</li>
455 the application to receive the ClassLoader in which the object is being created.</li>
480 in their application manifests, to inform external entities such as Google
491 <p>Android 3.2 introduces new feature constants that let applications specify whether they require display in landscape orientation, portrait orientation, or both. Declaring these constants indicates that the application must not be installed on a device that doesn't offer the associated orientation. Conversely, if one or both of the constants are not declared, it indicates that the application does not have a preference for the undeclared orientations and may be installed on a device that doesn't offer them. </p>
495 android.hardware.screen.landscape} — The application requires display in
498 android.hardware.screen.portrait} — The application requires display in
502 <p>A typical application that functions properly in both landscape and portrait orientations would not normally need to declare an orientation requirement. Rather, an application designed primarily for one orientation, such as an app designed for a television, could declare one of the constants to ensure that it isn't available to devices that don't provide that orientation.</p>
506 android:screenOrientation}</a> attribute, then this also declares that the application
514 android.hardware.faketouch.multitouch.distinct} — The application requires support for emulated mulitouch input with distinct tracking of two or more points.</li>
517 android.hardware.faketouch.multitouch.jazzhand} — The application requires support for emulated mulitouch input with distinct tracking of five or more points.</li>
543 system to correctly determine whether an application is compatible with
544 the system, prior to installing the application. </p>
546 <p>To use APIs introduced in Android {@sdkPlatformVersion} in your application,
547 you need compile the application against the Android library that is provided in
551 attribute to the <code><uses-sdk></code> element in the application's
