Home	Sort by relevance Sort by last modified time

Full Search Definition Symbol File Path History   | | Help

    Searched full:users (Results 501 - 525 of 5734) sorted by null

<<21222324252627282930>>

/external/chromium_org/sandbox/win/src/
security_level.h	36 // USER_LIMITED | Users | All except: | Traverse | 37 // | Everyone | Users | | 41 // USER_INTERACTIVE | Users | All except: | Traverse | 42 // | Everyone | Users | | 46 // | | Authent-users | | 50 // | | Users | | 54 // | | Authent-users | | 71 // or power users groups.
/external/chromium_org/third_party/mesa/src/docs/
perf.html	27 buffered mode. (X users only) 56 <li> XFree86 users: if you want to use 24-bit color try starting your
/external/chromium_org/ui/webui/resources/css/
tabs.css	18 /* New users of tabs.css should add 'new-style-tabs' to the class list of any 21 * TODO(rfevang): Remove when all users are converted to the new style.
/external/clang/include/clang/Basic/
Sanitizers.def	11 // enable. Users of this file must define the SANITIZER macro to make use of 12 // this information. Users of this file can also define the SANITIZER_GROUP
/external/clang/www/
menu.html.incl	35 <a href="http://lists.cs.uiuc.edu/mailman/listinfo/cfe-users">cfe-users List</a>
/external/eigen/Eigen/src/Core/products/
Parallelizer.h	76 GemmParallelInfo() : sync(-1), users(0), rhs_start(0), rhs_length(0) {} 79 int volatile users; member in struct:Eigen::internal::GemmParallelInfo
/external/llvm/lib/Support/
COPYRIGHT.regex	15 explicit claim or by omission. Since few users ever read sources, 19 misrepresented as being the original software. Since few users
/external/mdnsresponder/mDNSShared/
dnsextd.conf	30 // you'll want to limit updates to only users with keys. For example, 42 // You could use a single key which you give to all authorized users, but
mDNSResponder.8	49 has no user-specifiable command-line argument, and users should not run 70 Once this logging is enabled, users can additionally use syslog(1)
/external/mesa3d/docs/
perf.html	27 buffered mode. (X users only) 56 <li> XFree86 users: if you want to use 24-bit color try starting your
/frameworks/base/core/java/android/content/pm/
UserInfo.java	46 * delete users. 56 * Indicates the user has restrictions in privileges, in addition to those for normal users.
/frameworks/base/docs/html/design/building-blocks/
text-fields.jd	45 <p>Use auto-complete text fields to present real-time completions or search results in popups, so users 53 <p>Users can select any word in a text field with a long press. This action triggers a text selection
/frameworks/base/docs/html/design/patterns/
app-structure.jd	13 <p>Your app's structure depends largely on the content and tasks you want to surface for your users.</p> 48 <p>Ask yourself: "What are my typical users most likely going to want to do in my app?", and structure 110 <li>You expect your app's users to switch views frequently.</li> 130 <p>A <em>spinner</em> is a drop-down menu that allows users to switch between views of your app. </p> 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> 172 <p>After choosing the best top-level navigation for your app, don't mix and match patterns. For example, if you decide to use tabs for top-level switching, don't add a drawer, even if your navigation branches are deep. In this case, the navigation drawer would simply duplicate the information on the tabs, confusing your users.</p> 200 between categories, users can swipe left/right on the content. 273 <p>If your users are likely to want to look at multiple items in sequence, allow them to navigate
/frameworks/base/docs/html/design/style/
typography.jd	20 users quickly understand a screen of information. To support such use of typography, Ice Cream 61 <p>Users can select a system-wide scaling factor for text in the Settings app. In order to support
/frameworks/base/docs/html/guide/topics/ui/
index.jd	26 <p>By using the Action Bar in your Honeycomb-targeted apps, you'll give your users a familiar 42 and then choose appropriate forms of navigation to allow users to effectively and intuitively
/frameworks/base/docs/html/training/custom-views/
index.jd	58 <dd>Users expect a view to react smoothly and naturally to input gestures. 64 <dd>No matter how beautiful your UI is, users won't love it if it
/frameworks/base/docs/html/training/design-navigation/
descendant-lateral.jd	37 <p>One way of providing access to the full range of an application's screens is to expose hierarchical navigation. In this lesson we discuss <em>descendant navigation</em>, allowing users to descend 'down' a screen hierarchy into a child screen, and <em>lateral navigation</em>, allowing users to access sibling screens.</p> 75 <p>A common, button-based pattern for accessing different top-level application sections, is the dashboard pattern. A <em>dashboard</em> is a grid of large, iconic buttons that constitutes the entirety, or most of, the parent screen. The grid generally has either 2 or 3 rows and columns, depending on the number of top-level sections in the app. This pattern is a great way to present all the sections of the app in a visually rich way. The large touch targets also make this UI very easy to use. Dashboards are best used when each section is equally important, as determined by product decisions or better yet, real-world usage. However, this pattern doesn't visually work well on larger screens, and requires users to take an extra step to jump directly into the app's content.</p> 98 <p>There are several issues with this pattern. Deep, list-based navigation, known as <em>drill-down list navigation</em>, where lists lead to more lists which lead to even more lists, is often inefficient and cumbersome. The number of touches required to access a piece of content with this kind of navigation is generally very high, leading to a poor user experience&mdash;especially for users on-the-go.</p> 134 <li>Since there is a single, initially-selected tab, users have immediate access to that tab's content from the parent screen.</li> 135 <li>Users can navigate quickly between related screens, without needing to first revisit the parent. <p class="note"><strong>Note</strong>: when switching tabs, it is important to maintain this tab-switching immediacy; do not block access to tab indicators by showing modal dialogs while loading content.</p></li> 158 <p>In a horizontal paging UI, a single child screen (referred to as a <em>page</em> here) is presented one at a time. Users are able to navigate to sibling screens by touching and dragging the screen horizontally in the direction of the desired adjacent page. This gestural interaction is often complemented by another UI element indicating the current page and available pages, to aid discoverability and provide more context to the user. This practice is especially necessary when using this pattern for lateral navigation of section-related sibling screens. Examples of such elements include tick marks, scrolling labels, and tabs.</p> 171 <p>In the next lesson, we discuss mechanisms for allowing users to navigate up our information hierarchy and back, to previously visited screens.</p
/frameworks/base/docs/html/training/in-app-billing/
index.jd	29 <p>In-app billing is a service hosted on Google Play that lets you charge for digital content or for upgrades in your app. The In-app Billing API makes it easy for you to integrate In-app Billing into your applications. You can request product details from Google Play, issue orders for in-app products, and quickly retrieve ownership information based on users' purchase history. You can also query the Google Play service for details about in-app products, such as local pricing and availability. Google Play provides a checkout interface that makes user interactions with the In-app Billing service seamless, and provides a more intuitive experience to your users.</p>
/frameworks/base/docs/html/training/location/
index.jd	32 One of the unique features of mobile applications is location awareness. Mobile users bring 33 their devices with them everywhere, and adding location awareness to your app offers users a
/frameworks/base/docs/html/training/multiscreen/
index.jd	45 users as possible.</p> 49 order to truly satisfy and impress your users, your application must go beyond merely
/frameworks/base/docs/html/training/system-ui/
index.jd	52 guidelines and usage patterns. You should carefully consider your users' 53 needs and expectations before modifying the system bars, since they give users a
/frameworks/base/test-runner/src/android/test/mock/
MockContentResolver.java	37 * authority. To have access to a provider based on its authority, users of 43 * Users can also set an authority's entry in the map to null, so that a provider is completely
/ndk/tests/device/issue42891-boost-1_52/jni/boost/boost/config/
select_stdlib_config.hpp	15 // (do not rely on this header being included since users can short-circuit this header 35 // (again do not rely on this header being included since users can short-circuit this
/packages/apps/Settings/src/com/android/settings/deviceinfo/
StorageMeasurement.java	140 * Total disk usage for users, which is only meaningful for emulated 270 // Include cache for all users 407 final List<UserInfo> users = userManager.getUsers(); local 431 // Measure total emulated storage of all users; internal apps data 433 for (UserInfo user : users) { 439 // Measure all apps for all users 446 final int count = users.size() * apps.size(); 450 for (UserInfo user : users) {
/frameworks/base/docs/html/guide/topics/ui/accessibility/
apps.jd	52 <p>Applications built for Android are more accessible to users with visual, physical or age-related 53 limitations when those users activate accessibility services and features on a device. These 56 application and ensure a pleasant experience for all your users.</p> 58 <p>Making sure your application is accessible to all users requires only a few steps, particularly 73 to assist users who are deaf or hard of hearing.</li> 88 making your application accessible for users with blindness or low-vision. Be sure to review the 89 requirements for serving users who are deaf and hard of hearing in the 114 require additional information for users who are not able to see it.</p> 132 attribute <em>instead</em> of a content description, to help users understand what content is 139 <p>Focus navigation allows users with disabilities to step through user interface controls using     [all...]

Completed in 322 milliseconds

<<21222324252627282930>>