HomeSort by relevance Sort by last modified time
    Searched full:screens (Results 276 - 300 of 768) sorted by null

<<11121314151617181920>>

  /external/chromium_org/chrome/browser/chromeos/login/enrollment/
auto_enrollment_check_screen.h 13 #include "chrome/browser/chromeos/login/screens/error_screen.h"
enrollment_screen.h 16 #include "chrome/browser/chromeos/login/screens/wizard_screen.h"
enrollment_screen_browsertest.cc 10 #include "chrome/browser/chromeos/login/screens/mock_screen_observer.h"
  /external/chromium_org/chrome/browser/chromeos/login/screens/
screen_context_unittest.cc 9 #include "chrome/browser/chromeos/login/screens/screen_context.h"
update_screen.cc 5 #include "chrome/browser/chromeos/login/screens/update_screen.h"
15 #include "chrome/browser/chromeos/login/screens/error_screen.h"
16 #include "chrome/browser/chromeos/login/screens/screen_observer.h"
17 #include "chrome/browser/chromeos/login/screens/update_screen_actor.h"
  /external/chromium_org/chrome/browser/media/
native_desktop_media_list.h 21 // Implementation of DesktopMediaList that shows native screens and
  /external/chromium_org/chrome/browser/resources/about_welcome_android/
about_welcome_android.css 105 /* Increase spacing on larger screens. */
  /external/chromium_org/chrome/browser/ui/ash/multi_user/
user_switch_animator_chromeos.h 88 // tested, otherwise all screens.
  /external/chromium_org/chrome/browser/ui/cocoa/autofill/
autofill_popup_base_view_cocoa.mm 142 NSScreen* screen = [[NSScreen screens] objectAtIndex:0];
  /external/chromium_org/chrome/browser/ui/webui/chromeos/login/
core_oobe_handler.h 11 #include "chrome/browser/chromeos/login/screens/core_oobe_actor.h"
signin_userlist_unittest.cc 6 #include "chrome/browser/chromeos/login/screens/user_selection_screen.h"
  /external/chromium_org/chrome/browser/ui/webui/signin/
user_manager_screen_handler.h 69 // all the visible user manager screens can be updated.
  /external/chromium_org/third_party/mesa/src/src/egl/main/
egldisplay.h 151 _EGLArray *Screens;
  /external/chromium_org/third_party/skia/bench/
PicturePlaybackBench.cpp 17 // This is designed to emulate about 4 screens of textual content
  /external/chromium_org/third_party/webrtc/modules/desktop_capture/
screen_capturer_x11.cc 60 virtual bool GetScreenList(ScreenList* screens) OVERRIDE;
315 bool ScreenCapturerLinux::GetScreenList(ScreenList* screens) {
316 DCHECK(screens->size() == 0);
320 screens->push_back(default_screen);
  /external/chromium_org/ui/gfx/
screen.h 27 // Windows 8, two Screens exist: one for Metro UI and another for the desktop.
  /external/chromium_org/ui/snapshot/
snapshot_mac.mm 23 NSScreen* screen = [[NSScreen screens] objectAtIndex:0];
  /external/mesa3d/src/egl/main/
egldisplay.h 151 _EGLArray *Screens;
  /external/skia/bench/
PicturePlaybackBench.cpp 17 // This is designed to emulate about 4 screens of textual content
  /frameworks/base/docs/html/design/patterns/
app-structure.jd 55 <p>Many apps focus on the content display. Avoid navigation-only screens and instead let people get to
77 <p>All screens in your app should display action bars to provide consistent navigation and surface
151 <p>A <em>navigation drawer</em> is a slide-out menu that allows users to switch between views of your app. It can hold a large number of items and is accessible from anywhere in your app. Navigation drawers show your app's top-level views, but can also provide navigation to lower-level screens. This makes them particularly suitable for complex apps.</p>
157 <li>You want to provide direct access to screens on lower levels.</li>
  /frameworks/base/docs/html/design/style/
typography.jd 24 specifically for the requirements of UI and high-resolution screens.</p>
  /frameworks/base/docs/html/guide/practices/app-design/
seamlessness.jd 148 <p>Any application worth using will probably have several different screens.
149 When designing the screens of your UI, be sure to make use of multiple Activity
181 are flexible enough to display properly on a variety of device screens.</p>
222 some devices will have touch-screens, but many won't.
  /frameworks/base/docs/html/guide/practices/
seamlessness.jd 149 <p>Any application worth using will probably have several different screens.
150 When designing the screens of your UI, be sure to make use of multiple Activity
182 are flexible enough to display properly on a variety of device screens.</p>
223 some devices will have touch-screens, but many won't.
  /frameworks/base/docs/html/guide/practices/ui_guidelines/
icon_design.jd 15 <li>You should create separate icon sets for high-, medium-, and low-density screens.</li>
52 Screens</a></li>
147 Screens</a> document, the Android platform makes it straightforward for you to
329 Screens</a>.</p>
  /frameworks/base/docs/html/guide/topics/manifest/
manifest-element.jd 28 <dd><code><a href="{@docRoot}guide/topics/manifest/compatible-screens-element.html">&lt;compatible-screens&gt;</a></code>
34 <br/><code><a href="{@docRoot}guide/topics/manifest/supports-screens-element.html">&lt;supports-screens&gt;</a></code>

Completed in 470 milliseconds

<<11121314151617181920>>