| /external/chromium_org/ui/gfx/mac/ |
| coordinate_conversion.mm | 18 return NSMaxY([[[NSScreen screens] objectAtIndex:0] frame]);
|
| /frameworks/base/docs/html/design/style/ |
| metrics-grids.jd | 3 page.tags="layout","screens"
4 meta.tags="multiple screens, layout, tablets"
9 inch">DPI</acronym>). To simplify the way you design for multiple screens, think of each device as
44 <a href="http://developer.android.com/resources/dashboard/screens.html" target="_blank">
|
| /frameworks/base/docs/html/guide/topics/resources/ |
| index.jd | 32 href="http://android-developers.blogspot.com/2011/07/new-mode-for-apps-on-large-screens.html">
33 <h4>New Mode for Apps on Large Screens</h4>
35 of apps resize to the larger screens just fine. To keep the few apps that don't resize well from
52 <h4>Designing for Multiple Screens</h4>
|
| /frameworks/base/docs/html/wear/design/ |
| user-interface.jd | 22 <img class="wear-bezel-only" src="{@docRoot}wear/images/screens/bezel.png" alt="">
23 <img class="gif" src="{@docRoot}wear/images/screens/stream.gif">
45 <img class="wear-bezel-only" src="{@docRoot}wear/images/screens/bezel.png" alt="">
46 <img class="gif" src="{@docRoot}wear/images/screens/cuecard.gif">
|
| /packages/apps/Protips/res/values/ |
| arrays.xml | 53 <item>Multiple Home screens.\n
54 Swipe left or right to switch. Drag items to other screens.</item>
71 <item>Want some more home screens?
81 \nDragging items twixt Home screens
|
| /developers/samples/android/wearable/wear/WatchViewStub/ |
| template-params.xml | 26 This sample demonstrates how to specify different layouts for round and rectangular screens.
50 This sample demonstrates how to specify different layouts for round and rectangular screens.
|
| /external/chromium_org/chrome/browser/chromeos/login/screens/ |
| terms_of_service_screen.h | 12 #include "chrome/browser/chromeos/login/screens/terms_of_service_screen_actor.h"
13 #include "chrome/browser/chromeos/login/screens/wizard_screen.h"
|
| base_screen.h | 20 // Base class for the all OOBE/login/before-session screens.
21 // Screens are identified by ID, screen and it's JS counterpart must have same
23 // Most of the screens will be re-created for each appearance with Initialize()
|
| network_screen_browsertest.cc | 7 #include "chrome/browser/chromeos/login/screens/mock_screen_observer.h"
8 #include "chrome/browser/chromeos/login/screens/network_screen.h"
9 #include "chrome/browser/chromeos/login/screens/wizard_screen.h"
|
| error_screen.h | 13 #include "chrome/browser/chromeos/login/screens/error_screen_actor_delegate.h"
14 #include "chrome/browser/chromeos/login/screens/wizard_screen.h"
|
| /frameworks/base/docs/html/guide/topics/sensors/ |
| index.jd | 17 that run Android on screens that are naturally landscape in their orientation. That is, when held in
18 the default position, the screens are wider than they are tall. This introduces a few fairly subtle
|
| /packages/apps/Protips/res/values-en-rGB/ |
| arrays.xml | 24 <item msgid="1000948398885889319">"Multiple Home screens.\n Swipe left or right to switch. Drag items to other screens."</item>
|
| /packages/apps/Protips/res/values-en-rIN/ |
| arrays.xml | 24 <item msgid="1000948398885889319">"Multiple Home screens.\n Swipe left or right to switch. Drag items to other screens."</item>
|
| /frameworks/base/docs/html/guide/practices/ |
| optimizing-for-3.0.jd | 45 <li><a href="#Landscape">Adding support for landscape screens</a></li>
86 add extra resources to support extra large screens, as appropriate.</p>
174 larger screens.</p>
232 <li><b>Supply alternative layout resources for xlarge screens</b>
235 resources</a> when running on extra large screens (using the <code>xlarge</code> resource
239 screens:</p>
483 application to certain types of screens, such as only tablets or only mobile devices. To do so, you
489 href="{@docRoot}guide/practices/screens_support.html">supporting multiple screens</a> and employ
490 them to the best of your ability. By supporting multiple screens, your application can be made
497 for smaller screens, you should add <
[all...] |
| screens_support.jd | 1 page.title=Supporting Multiple Screens
3 meta.tags="multiple screens"
23 <li><a href="#range">Range of screens supported</a></li>
26 <li><a href="#support">How to Support Multiple Screens</a>
43 <li><a href="#testing">How to Test Your Application on Multiple Screens</a></li>
77 different screens, you should make the effort to optimize your application for different screen
89 href="{@docRoot}guide/practices/screens-support-1.5.html">Strategies for Android 1.5</a>.
100 <h2 id="overview">Overview of Screens Support</h2>
102 <p>This section provides an overview of Android's support for multiple screens, including: an
132 <dd>The total number of physical pixels on a screen. When adding support for multiple screens,
[all...] |
| /external/chromium_org/chrome/ |
| chrome_browser_chromeos.gypi | [all...] |
| /frameworks/base/core/java/android/util/ |
| DisplayMetrics.java | 31 * Standard quantized DPI for low-density screens.
36 * Standard quantized DPI for medium-density screens.
60 * Standard quantized DPI for high-density screens.
65 * Intermediate density for screens that sit between {@link #DENSITY_HIGH} (240dpi) and
72 * Standard quantized DPI for extra-high-density screens.
77 * Intermediate density for screens that sit somewhere between
85 * Standard quantized DPI for extra-extra-high-density screens.
90 * Intermediate density for screens that sit somewhere between
98 * Standard quantized DPI for extra-extra-extra-high-density screens. Applications
101 * use of this density would be 4K television screens -- 3840x2160, whic
[all...] |
| /external/chromium_org/third_party/webrtc/modules/desktop_capture/mac/ |
| desktop_configuration.mm | 104 NSArray* screens = [NSScreen screens];
105 assert(screens);
109 for (NSUInteger i = 0; i < [screens count]; ++i) {
111 GetConfigurationForScreen([screens objectAtIndex: i]);
|
| /frameworks/base/docs/html/training/multiscreen/ |
| screendensities.jd | 2 page.metaDescription=Providing sets of layouts and drawable resources for specific ranges of device screens.
3 meta.tags="multiple screens"
5 parent.title=Designing for Multiple Screens
30 <li><a href="{@docRoot}guide/practices/screens_support.html">Supporting Multiple Screens</a></li>
54 pixels is a problem because different screens have different pixel densities,
|
| /frameworks/base/docs/html/google/play/ |
| filters.jd | 33 href="{@docRoot}guide/topics/manifest/supports-screens-element.html"><supports-screens></a></code></li>
122 <td valign="top" style="white-space:nowrap;"><code><a href="{@docRoot}guide/topics/manifest/supports-screens-element.html"><supports-screens></a></code>
128 setting attributes of the <code><supports-screens></code> element. When
134 smaller layouts to larger screens, but cannot adapt larger layouts to smaller
135 screens. Thus, if an application declares support for "normal" screen size only,
141 <code><supports-screens></code>, Google Play uses the default values for those
149 targetSdkVersion</a></code> to 3 or lower, the <code><supports-screens></code> element itself
151 the application is designed for normal-size screens and shows the application t
[all...] |
| /frameworks/base/docs/html/google/play/publishing/ |
| multiple-apks.jd | 38 <li><a href="#ScreenOptions">Supporting multiple screens</a></li>
49 <li><a href="{@docRoot}guide/practices/screens_support.html">Supporting Multiple Screens</a></li>
216 href="{@docRoot}guide/topics/manifest/supports-screens-element.html">{@code
217 <supports-screens>}</a> <em>or</em> <a
218 href="{@docRoot}guide/topics/manifest/compatible-screens-element.html">{@code
219 <compatible-screens>}</a> element. You should never use both elements and you should use only
220 <a href="{@docRoot}guide/topics/manifest/supports-screens-element.html">{@code
221 <supports-screens>}</a> when possible.</p>
222 <p>For example, you can provide one APK that supports small and normal size screens and another
223 APK that supports large and xlarge screens.</p
[all...] |
| /external/chromium_org/third_party/mesa/src/src/glx/tests/ |
| clientinfo_unittest.cpp | 54 this->screens = new glx_screen *[dpy->nscreens];
55 memset(this->screens, 0, sizeof(struct glx_screen *) * dpy->nscreens);
61 if (this->screens[i] != NULL)
62 delete this->screens[i];
65 delete [] this->screens;
96 if (this->screens[i] != NULL)
97 delete this->screens[i];
99 this->screens[i] = new fake_glx_screen(this, i, ext);
245 if (this->glx_dpy->screens != NULL) {
247 delete [] this->glx_dpy->screens[i]->serverGLXexts
[all...] |
| /external/mesa3d/src/glx/tests/ |
| clientinfo_unittest.cpp | 54 this->screens = new glx_screen *[dpy->nscreens];
55 memset(this->screens, 0, sizeof(struct glx_screen *) * dpy->nscreens);
61 if (this->screens[i] != NULL)
62 delete this->screens[i];
65 delete [] this->screens;
96 if (this->screens[i] != NULL)
97 delete this->screens[i];
99 this->screens[i] = new fake_glx_screen(this, i, ext);
245 if (this->glx_dpy->screens != NULL) {
247 delete [] this->glx_dpy->screens[i]->serverGLXexts
[all...] |
| /frameworks/base/docs/html/training/design-navigation/ |
| ancestral-temporal.jd | 34 ancestor screens. Additionally, we should ensure that temporal navigation via the <em>Back</em>
45 <p>Temporal navigation, or navigation between historical screens, is deeply rooted in the Android
47 regardless of other state. The set of historical screens is always rooted at the user's Launcher
62 the <em>back stack</em></a>, or the list of previous screens, automatically. The <em>Back</em>
63 button by default simply traverses this list of screens, removing the current screen from the list
102 <em>Home</em> or <em>Up</em>, make sure to clear the back stack of any descendent screens. For
|
| /packages/apps/Launcher2/ |
| print_db.py | 9 SCREENS = 5
185 screens = [] variable
186 for i in range(0,SCREENS):
193 screens.append(screen)
196 screen = screens[row["screen"]]
209 for screen in screens:
|
