| /frameworks/base/docs/html/guide/topics/manifest/ |
| D | supports-screens-element.jd | 27 <dd>Lets you specify the screen sizes your application supports and enable <a
28 href="{@docRoot}guide/practices/screen-compat-mode.html">screen compatibility mode</a> for screens
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.
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
44 href="{@docRoot}guide/practices/screen-compat-mode.html">screen compatibility mode</a>. When you
45 have not designed for larger screen sizes and the normal resizing does not achieve the appropriate
46 results, screen compatibility mode will scale your UI by emulating a <em>normal</em> size
47 screen and medium density, then zooming in so that it fills the entire screen. Beware that this
[all …]
|
| D | compatible-screens-element.jd | 11 …<<a href="#screen">screen</a> android:<a href="#screenSize">screenSize</a>=["small" | "normal" …
23 <dd>Specifies each screen configuration with which the application is compatible. Only one instance
25 contain multiple <code><screen></code> elements. Each <code><screen></code> element
26 specifies a specific screen size-density combination with which the application is compatible.
31 with specific screen configurations and enable filtering for users. Any screen configuration that is
32 <em>not</em> declared in this element is a screen with which the application is <em>not</em>
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 all screen configurations. Instead of using this element,
43 alternative resources for different screen sizes and densities.</p>
45 <p>If you want to set only a minimum screen <em>size</em> for your your application, then you
[all …]
|
| /frameworks/native/opengl/tests/testViewport/ |
| D | README | 7 The program clears the screen to blue, then draws a full screen white quad that
8 is alligned to the screen.
9 (Therefore the whole screen should appear to be white.)
12 Note that screen is all white.
14 Rotate screen 90 degrees.
16 Expected: screen is still all white.
18 Actual: screen is blue with offset white rectangle.
|
| /frameworks/base/docs/html/guide/practices/ |
| D | screens-distribution.jd | 14 screen configuration</li>
38 configurations of screen size and density, you can instead choose to limit the distribution of your
41 Google Play by adding elements to your manifest file that specify the screen configurations your
44 <p>However, before you decide to restrict your application to certain screen configurations, you
56 href="{@docRoot}guide/practices/screens_support.html#screen-independence">Best Practices for Screen
59 versions of your application for different screen configurations. In such a case, you can use the <a
62 combinations of screen size and density. External services such as Google Play use this
63 information to apply filtering to your application, so that only devices that have a screen
67 <compatible-screens>}</a> element must contain one or more {@code <screen>} elements. Each
68 {@code <screen>} element specifies a screen configuration with which your application is
[all …]
|
| D | screens_support.jd | 9 <li>Android runs on devices that have different screen sizes and densities.</li>
10 <li>The screen on which your application is displayed can affect its user interface.</li>
11 <li>The system handles most of the work of adapting your app to the current screen.</li>
12 <li>You should create screen-specific resources for precise control of your UI. </li>
33 <li><a href="#DeclaringScreenSizeSupport">Declaring screen size support</a></li>
35 <li><a href="#screen-independence">Best Practices</a></li>
66 <p>Android runs on a variety of devices that offer different screen sizes and densities. For
68 handles most of the work to adjust each application's user interface to the screen on which it is
70 application's UI for specific screen sizes and densities, in order to optimize your UI
71 design for different screen configurations. For example, you might want a UI for tablets
[all …]
|
| D | screen-compat-mode.jd | 44 should disable screen compatibility mode in order to maintain the best user experience. To learn how
50 variety of screen sizes and does most of the work to resize application layouts so that they
51 properly fit each screen. However, if your application does not successfully follow the guide to
54 problem, screen compatibility mode can make the application a little more usable on larger
57 <p>There are two versions of screen compatibility mode with slightly different behaviors:</p>
62 normal size handset (emulating a 320dp x 480dp screen), with a black border that fills
63 the remaining area of the screen.
66 original screen size of 320dp x 480dp. Because there are so few active devices remaining that run
68 should not have version 1 of screen compatibility mode enabled for larger screens. This version
70 <p>To disable this version of screen compatibility mode, you simply need to set <a
[all …]
|
| D | screens-support-1.5.jd | 13 <li>Apps developed for Android 1.5 and below support only the baseline screen
35 baseline HVGA screen used on the T-Mobile G1 and similar devices, which is <em>normal</em> screen
36 size and medium density (<em>mdpi</em>). Android 1.6 introduced support for different screen
38 screens, using alternative resources for different screen configurations.</p>
50 href="screen-compat-mode.html">screen compatibility mode</a> when on a device with a screen larger …
52 <em>normal</em> screen size (basically, the system displays the application in a small window
53 that is roughly the size of the normal screen size).</p>
56 href="screen-compat-mode.html">screen compatibility
74 different screen configurations. You should be able to make these changes to your application such
111 that use the screen sizes and densities that you want to support. When you create the AVDs, make
[all …]
|
| D | optimizing-for-3.0.jd | 68 public and provide users a new Android experience on a larger screen, so you should make sure
97 application based on screen configuration</a>.</li>
130 the Android emulator must simulate the ARM instruction set on your computer and the WXGA screen is
138 and wait until you see the home screen (or lock screen) appear. </p>
244 qualifier, but if you want alternative resources for an extra large landscape screen, you
256 best judgment of proportions for each screen size—you don't want the buttons to be too big,
260 scale-independent pixel unit, which will resize as appropriate for the current screen configuration.
265 href="{@docRoot}guide/practices/screens_support.html#screen-independence">Best Practices
330 the screen. By default, the Action Bar includes the application logo on the left side, followed by
396 screen and interact with ongoing services (such as preview their email and control music playback).
[all …]
|
| /frameworks/base/docs/html/tools/revisions/ |
| D | platforms.jd | 90 Nexus 7 (7.3", 800 x 1280, Large tvdpi screen)
93 Galaxy Nexus (4.7", 720 x 1280, Normal xhdpi screen)
96 Nexus S (4.0", 480 x 800, Normal hdpi screen)
99 Nexus One (3.7", 480 x 720, Normal hdpi screen)
102 10.1" WXGA Tablet (1280 x 800, X-Large mdpi screen)
105 7.0" WSVGA Tablet (1024 x 600, Large mdpi screen)
108 5.4" FWVGA (480 x 854, Large mdpi screen)
111 5.1" WVGA (480 x 800, Large mdpi screen)
114 4.7" WXGA (1280 x 720, Normal xhdpi screen)
117 4.65" 720p (720 x 1280, Normal xhdpi screen)
[all …]
|
| /frameworks/base/docs/html/training/design-navigation/ |
| D | ancestral-temporal.jd | 33 screen hierarchy, we need to provide a method for navigating up the hierarchy, to parent and
46 system. All Android users expect the <em>Back</em> button to take them to the previous screen,
48 application (the phone's "home" screen). That is, pressing <em>Back</em> enough times should land
63 button by default simply traverses this list of screens, removing the current screen from the list
67 example, if your screen contains an embedded web browser where users can interact with page elements
78 button, or a <em>Home</em> button at the top-left of the screen, usually as a component of the
80 Upon selecting <em>Home</em>, the user would be taken to the screen at the top of the screen
81 hierarchy, generally known as the application's home screen.</p>
83 …screen can give the user a sense of comfort and security. Regardless of where they are in the appl…
87 be taken to the parent screen in the hierarchy. This navigation step is usually the previous screen
[all …]
|
| D | screen-planning.jd | 16 <li><a href="#screen-list">Create a Screen List</a></li>
30 <img src="{@docRoot}images/training/app-navigation-screen-planning-erd.png"
36 <h2 id="screen-list">Create a Screen List</h2>
43 <li>Home or "launchpad" screen for accessing stories and photos</li>
57 …screen <em>A</em> to another screen <em>B</em> implies that screen <em>B</em> should be directly r…
60 <img src="{@docRoot}images/training/app-navigation-screen-planning-exhaustive-map.png"
61 alt="Exhaustive screen map for the example news application" id="figure-exhaustive-map">
63 <p class="img-caption"><strong>Figure 2.</strong> Exhaustive screen map for the example news applic…
70 …sible to design a completely functional application from this exhaustive screen map. A simplistic …
75 <li>Detail information (e.g., story view, full-screen photo view, etc.)</li>
[all …]
|
| D | wireframing.jd | 25 …screen grouping techniques, it's time to apply them to our screens. Let's take another look at our…
28 <img src="{@docRoot}images/training/app-navigation-screen-planning-exhaustive-map.png"
29 alt="Exhaustive screen map for the example news application" id="figure-exhaustive-map">
31 <p class="img-caption"><strong>Figure 1.</strong> Exhaustive screen map for the example news applic…
34 … and apply navigation patterns discussed in the previous lessons to this screen map, maximizing na…
41 …t the horizontally-pageable <em>Story List</em> screen as a left pane, and the <em>Story View</em>…
43 <p>Below are diagrams representing the new screen maps for handsets and tablets after applying thes…
47 alt="Final screen map for the example news application on handsets" id="figure-map-example-phone">
49 <p class="img-caption"><strong>Figure 2.</strong> Final screen map for the example news application…
53 …alt="Final screen map for the example news application on tablets, in landscape" id="figure-map-ex…
[all …]
|
| D | multiple-sizes.jd | 7 previous.link=screen-planning.html
33 <p>The exhaustive screen map from the previous lesson isn't tied to a particular device form factor…
35 … other factors, including interaction methods (i.e., the lack of a touch screen), legibility of te…
47 …n tablets and TVs, on the other hand, generally have much more available screen space and are able…
66 …screen size at which to draw the line between single-pane and multi-pane layouts, you can provide …
68 <p class="note"><strong>Implementation Note:</strong> While a single screen is implemented as an {@…
81 … Panes could have fixed widths or take a certain percentage of the available screen width.</p></li>
91 …portrait mode. However, <em>to ensure the functional parity</em> of your screen in portrait and la…
103 …ulti-pane layouts on larger-screen devices, let's apply this technique to our exhaustive screen ma…
106 <img src="{@docRoot}images/training/app-navigation-multiple-sizes-multipane-screen-map.png"
[all …]
|
| D | descendant-lateral.jd | 37 …ndant navigation</em>, allowing users to descend 'down' a screen hierarchy into a child screen, an…
66 …. Upon selecting one of these targets, the child screen is opened, replacing the current context (…
70 …alt="Example button-based navigation interface with relevant screen map excerpt. Also shows dashbo…
72 …gure 3.</strong> Example button-based navigation interface with relevant screen map excerpt. Also …
75 …ge, iconic buttons that constitutes the entirety, or most of, the parent screen. The grid generall…
93 …alt="Example list-, grid-, and carousel-based navigation interfaces with relevant screen map excer…
95 …xample list-, grid-, and carousel-based navigation interfaces with relevant screen map excerpt.</p>
100 … on larger screens, as list items generally span the entire width of the screen yet have a fixed h…
111 …ping of sibling screens, in that the tab content container in the parent screen can embed child sc…
115 …alt="Example phone and tablet tab-based navigation interfaces with relevant screen map excerpt" id…
[all …]
|
| /frameworks/base/docs/html/design/patterns/ |
| D | navigation.jd | 25 between screens. For instance, if screen A displays a list of items, and selecting an item leads to
26 screen B (which presents that item in more detail), then screen B should offer an Up button that
27 returns to screen A.</p>
28 <p>If a screen is the topmost one in an app (that is, the app's home), it should not present an Up
35 <p>When the previously viewed screen is also the hierarchical parent of the current screen, pressing
38 button can return the user to the Home screen, or even to a different app.</p>
42 <p>The Back button also supports a few behaviors not directly tied to screen-to-screen navigation:
52 <p>Sometimes a screen doesn't have a strict position within the app's hierarchy, and can be reached
53 from multiple entry points—such as a settings screen that can be reached from any other screen
54 in your app. In this case, the Up button should choose to return to the referring screen, behaving
[all …]
|
| D | multi-pane-layouts.jd | 13 <p>When writing an app for Android, keep in mind that Android devices come in many different screen
15 layout by adjusting its content to varying screen sizes and orientations.</p>
17 one compound view when a lot of horizontal screen real estate is available and by splitting them up
22 view. Touching an item in the master view opens a different screen showing that item's detail
27 <p>Because tablets have more screen real estate than phones, you can use panels to combine the rela…
39 one orientation, try not to split it up when the user rotates the screen. There are several techniq…
65 <p>Rearrange the panels on your screen to match the orientation.</p>
93 …screen cannot accommodate the compound view on rotation show the right pane in full screen view on…
105 <p>Plan in advance on how your app scales to different screen sizes and screen orientations.</p>
109 themselves when screen orientation changes.</p>
[all …]
|
| /frameworks/base/docs/html/guide/webapps/ |
| D | targeting.jd | 40 controlling the viewport size and screen densities.</p>
59 <dt>The device's screen density</dt>
60 <dd>The screen density (the number of pixels per inch) on an Android-powered device affects
61 the resolution and size at which a web page is displayed. (There are three screen density
63 compensate for variations in the screen
65 as a medium-density screen. If graphics are an important element of your web design, you
69 screen densities, you should control how scaling occurs by providing viewport metadata about
70 your web page's target screen density and providing alternative graphics for different screen
82 matches the size of the screen,
84 That is, the number of pixels available to a web page before it exceeds the screen area is
[all …]
|
| /frameworks/base/docs/html/about/versions/ |
| D | android-3.2.jd | 57 designed to run on larger screen sizes, such as on tablets. The new mode is
73 <p>Android 3.2 introduces extensions to the platform's screen support API to
81 support for various screen sizes, the platform also provides a new zoom
82 compatibility mode that renders the UI on a smaller screen area, then scales it
84 screen support API and the controls it provides, see the sections below. </p></li>
93 control over how their applications are displayed across different screen sizes.
95 generalized screen density model, but extends it with the ability to precisely
96 target specific screen ranges by their dimensions, measured in
98 by their generalized screen sizes (such as large or xlarge)</p>
109 <li>A screen's <em>smallestWidth</em> is its fundamental minimum size,
[all …]
|
| /frameworks/base/docs/html/training/implementing-navigation/ |
| D | descendant.jd | 45 …screen contains a list of items in a collection, and a <em>detail</em> screen shows detailed infor…
47 …screen at a time (either the master or the detail screen); this concern is further discussed in <a…
53 …For example, when viewing the contact details screen for an entry in the phone address book, a chi…
55 …cher (the device home screen). It would be confusing if touching your application icon brought the…
|
| /frameworks/base/docs/html/training/multiscreen/ |
| D | index.jd | 42 <p>Android powers hundreds of device types with several different screen sizes,
44 that you design your application to be compatible with all screen sizes so it’s available to as many
47 <p>But being compatible with different device types is not enough. Each screen
51 experience for each screen configuration.</p>
54 optimized for several screen configurations.</p>
71 several different screen sizes (using flexible dimensions for
72 views, {@link android.widget.RelativeLayout}, screen size and orientation qualifiers,
83 that adapts to several screen size/density combinations
85 current layout, handling screen configuration changes).</dd>
|
| /frameworks/base/docs/html/guide/topics/resources/ |
| D | index.jd | 14 href="http://android-developers.blogspot.com/2011/07/new-tools-for-managing-screen-sizes.html">
16 <p>Android 3.2 includes new tools for supporting devices with a wide range of screen sizes.
17 One important result is better support for a new size of screen; what is typically called a ?7-inch?
19 different screen sizes.</p>
34 frustrating users with awkward-looking apps on their tablets, Android 3.2 introduces a screen
51 <p>This class shows you how to implement a user interface that's optimized for several screen
|
| /frameworks/base/docs/html/design/get-started/ |
| D | ui-overview.jd | 5 include the Home screen experience, global device navigation, and notifications.</p>
20 <h4>Home screen</h4>
22 different home screen panels by swiping left and right.</p>
33 <h4>All apps screen</h4>
34 <p>The All Apps screen lets you browse the entire set of apps and widgets that are installed on your
36 <p>Users can drag an app or widget icon from the All Apps screen and place it in any empty location…
37 any Home screen.</p>
44 <h4>Recents screen</h4>
57 <p>The system bars are screen areas dedicated to the display of notifications, communication of dev…
60 to allow the user to enjoy full screen content without distraction.</p>
[all …]
|
| /frameworks/base/docs/html/training/basics/supporting-devices/ |
| D | screens.jd | 36 appearance for different screen sizes and densities.</p>
49 screen size, so many apps should revise the layout to optimize the user experience in each
55 <p>To optimize your user experience on different screen sizes, you should create a unique layout XML
56 file for each screen size you want to support. Each layout should be
62 properly fit the screen. Thus, your layouts for different screen sizes don't
80 an optimized UI for the corresponding screen size.</p>
92 <p>The system loads the layout file from the appropriate layout directory based on screen size of
128 defining screen sizes that allows you to specify resources for screen sizes based on
140 quality and performance on all screen densities.</p>
170 appropriate bitmap based on the screen's density.</p>
|
| /frameworks/base/docs/html/training/animation/ |
| D | screen-slide.jd | 28 Screen slides are transitions between one entire screen to another and are common with UIs
29 like setup wizards or slideshows. This lesson shows you how to do screen slides with
32 {@link android.support.v4.view.ViewPager}s can animate screen slides
33 automatically. Here's what a screen slide looks like that transitions from
34 one screen of content to the next:
106 …through pages, and they display screen slide animations by default, so you don't need to create an…
201 <p>To display a different animation from the default screen slide animation, implement the
203 …screen's transition, this method is called once for each visible page (generally there's only one …
211 position of the page on the screen, which is obtained from the <code>position</code> parameter
214 …ion</code> parameter indicates where a given page is located relative to the center of the screen.
[all …]
|
| /frameworks/base/docs/html/design/style/ |
| D | devices-displays.jd | 4 <p>Android powers millions of phones, tablets, and other devices in a wide variety of screen sizes …
22 <p>On larger devices, take advantage of extra screen real estate. Create compound views that combine
29 <p>Provide resources for different screen densities (<acronym title="Dots per inch">DPI</acronym>) …
40 down for the other buckets. Another approach is to start with the device with the largest screen
48 <p>For information about how to build flexible layouts for multiple screen sizes and densities,
|