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

1 2 3 45 6 7 8 91011>>

  /external/chromium_org/chrome/browser/chromeos/login/screens/
error_screen_actor.h 11 #include "chrome/browser/chromeos/login/screens/error_screen.h"
12 #include "chrome/browser/chromeos/login/screens/error_screen_actor_delegate.h"
eula_screen.cc 5 #include "chrome/browser/chromeos/login/screens/eula_screen.h"
10 #include "chrome/browser/chromeos/login/screens/screen_observer.h"
network_screen.h 12 #include "chrome/browser/chromeos/login/screens/network_screen_actor.h"
13 #include "chrome/browser/chromeos/login/screens/wizard_screen.h"
controller_pairing_screen_actor.cc 5 #include "chrome/browser/chromeos/login/screens/controller_pairing_screen_actor.h"
error_screen_actor.cc 5 #include "chrome/browser/chromeos/login/screens/error_screen_actor.h"
  /external/chromium_org/chrome/browser/media/
desktop_media_list_ash.h 30 // Implementation of DesktopMediaList that shows native screens and
35 SCREENS = 1,
desktop_media_picker.h 34 // Shows dialog with list of desktop media sources (screens, windows, tabs)
  /external/kernel-headers/original/uapi/linux/
virtio_console.h 46 /* colums of the screens */
48 /* rows of the screens */
  /frameworks/base/docs/html/training/design-navigation/
wireframing.jd 25 <p>Now that we have a solid understanding of navigation patterns and screen grouping techniques, it's time to apply them to our screens. Let's take another look at our exhaustive screen map for the example news application from the <a href="screen-planning.html">first lesson</a>, below.</p>
39 <p>First, our second-level screens (<em>Story Category List</em>, <em>Photo List</em>, and <em>Saved Item List</em>) can be grouped together using tabs. Note that we don't necessarily have to use horizontally arranged tabs; in some cases a drop-down list UI element can serve as a suitable replacement, especially on devices with narrow screens such as handsets. We can also group the <em>Saved Photo List</em> and <em>Saved Story List</em> screens together using tabs on handsets, or use multiple vertical content panes on tablets.</p>
58 <p>At this point, it's a good idea to think of screen map variations, in case your chosen patterns don't apply well in practice (when you sketch the application's screen layouts). Below is an example screen map variation for tablets that presents story lists for different categories side-by-side, with story view screens remaining independent.</p>
69 <p><em><a href="http://en.wikipedia.org/wiki/Website_wireframe">Wireframing</a></em> is the step in the design process where you begin to lay out your screens. Get creative and begin imagining how to arrange UI elements to allow users to navigate your app. Keep in mind that at this point, pixel-perfect precision (creating high-fidelity mockups) is not important.</p>
71 <p>The easiest and fastest way to get started is to sketch out your screens by hand using paper and pencils. Once you begin sketching, you may uncover practicality issues in your original screen map or decisions on which patterns to use. In some cases, patterns may apply well to a given design problem in theory, but in practice they may break down and cause visual clutter or interactional issues (for example, if there are two rows of tabs on the screen). If that happens, explore other navigation patterns, or variations on chosen patterns, to arrive at a more optimal set of sketches.</p>
77 <li>Is there screen 'master' functionality, allowing re-use of visual elements across different screens? For example, Action Bars should be visible on almost every screen in your application.</li>
  /developers/build/prebuilts/gradle/BasicTransition/Application/src/main/res/values-w820dp/
dimens.xml 19 (such as screen margins) for screens with more than 820dp of available width. This
  /developers/samples/android/ui/transition/BasicTransition/Application/src/main/res/values-w820dp/
dimens.xml 19 (such as screen margins) for screens with more than 820dp of available width. This
  /development/samples/ActionBarCompat/
AndroidManifest.xml 24 <supports-screens android:largeScreens="true"/>
  /development/samples/browseable/BasicTransition/res/values-w820dp/
dimens.xml 19 (such as screen margins) for screens with more than 820dp of available width. This
  /device/asus/flo/
elan-touchscreen.idc 19 # and may not be appropriate for use with other touch screens.
  /device/asus/grouper/
elan-touchscreen.idc 19 # and may not be appropriate for use with other touch screens.
  /device/asus/grouper/overlay/frameworks/base/packages/SystemUI/res/values/
config.xml 20 be 'platform' or 'noisy' (i.e. for noisy touch screens). -->
  /device/asus/tilapia/overlay/frameworks/base/packages/SystemUI/res/values/
config.xml 29 be 'platform' or 'noisy' (i.e. for noisy touch screens). -->
  /external/chromium_org/chrome/browser/chromeos/login/test/
wizard_in_process_browser_test.h 21 // Base class for test related to login wizard and its screens.
  /external/chromium_org/chrome/browser/resources/options/
supervised_user_create_confirm.css 16 /* Omit the image on very small screens. */
supervised_user_learn_more.css 23 /* Omit the image on very small screens. */
  /external/chromium_org/chrome/browser/ui/
user_manager.h 33 // for smaller screens.
  /external/chromium_org/chrome/browser/ui/webui/chromeos/login/
controller_pairing_screen_handler.h 9 #include "chrome/browser/chromeos/login/screens/controller_pairing_screen_actor.h"
eula_screen_handler.h 10 #include "chrome/browser/chromeos/login/screens/eula_screen_actor.h"
kiosk_autolaunch_screen_handler.h 10 #include "chrome/browser/chromeos/login/screens/kiosk_autolaunch_screen_actor.h"
kiosk_enable_screen_handler.h 11 #include "chrome/browser/chromeos/login/screens/kiosk_enable_screen_actor.h"

Completed in 378 milliseconds

1 2 3 45 6 7 8 91011>>