/external/chromium/chrome/browser/ui/cocoa/ |
browser_window_controller.h | 10 // object. Handles interactions between Cocoa and the cross-platform
|
/external/chromium_org/chrome/browser/media_galleries/mac/ |
mtp_device_delegate_impl_mac.mm | 33 // interactions with it are done on the UI thread, but it may be
|
/external/chromium_org/chrome/browser/password_manager/ |
password_form_manager.h | 25 // Per-password-form-{on-page, dialog} class responsible for interactions
|
/external/chromium_org/third_party/angle/extensions/ |
EXT_robustness.txt | 250 Interactions with EGL_EXT_create_context_robustness
|
/external/chromium_org/third_party/icu/source/i18n/unicode/ |
selfmt.h | 108 * <p>Patterns can be nested, so that it's possible to handle interactions of
|
/external/chromium_org/third_party/mesa/src/src/mesa/main/ |
arrayobj.c | 381 /* The "Interactions with APPLE_vertex_array_object" section of the
|
/external/chromium_org/third_party/skia/src/gpu/ |
GrGpu.h | 310 * They have been adjusted to account for any interactions between the
|
/external/clang/lib/Tooling/ |
Tooling.cpp | 305 // abstraction that allows openat() style interactions.
|
/external/icu4c/i18n/unicode/ |
selfmt.h | 121 * <p>Patterns can be nested, so that it's possible to handle interactions of
|
/external/mesa3d/src/mesa/main/ |
arrayobj.c | 381 /* The "Interactions with APPLE_vertex_array_object" section of the
|
/external/skia/src/gpu/ |
GrGpu.h | 310 * They have been adjusted to account for any interactions between the
|
/frameworks/base/core/java/android/view/textservice/ |
SpellCheckerSession.java | 68 * selection and interactions.</p>
|
/frameworks/base/docs/html/distribute/googleplay/strategies/ |
app-quality.jd | 81 In usability and in app design too, you should listen carefully to your users. Ask a handful of real Android device users (friends, family, etc.) to try out your app and observe them as they interact with it. Look for cases where they get confused, are unsure of how to proceed, or are surprised by certain behaviors. Minimize these cases by rethinking some of the interactions in your app, perhaps working in some of the <a href="http://www.youtube.com/watch?v=M1ZBjlCRfz0">user interface patterns</a> the Android UI team discussed at Google I/O.</p>
|
/frameworks/base/docs/html/training/custom-views/ |
making-interactive.jd | 73 <p>Touch events by themselves are not particularly useful. Modern touch UIs define interactions in
|
/frameworks/base/docs/html/training/gestures/ |
detector.jd | 196 data is being generated for even simple interactions.</p>
|
/frameworks/base/packages/WallpaperCropper/src/com/android/photos/ |
BitmapRegionTileSource.java | 393 // loaded, the lifecycle is different and interactions are on a different
|
/frameworks/base/services/java/com/android/server/display/ |
WifiDisplayAdapter.java | 63 * the interactions between Media Server, Surface Flinger and the Display Manager Service.
|
/packages/apps/Contacts/src/com/android/contacts/group/ |
GroupDetailFragment.java | 54 import com.android.contacts.interactions.GroupDeletionDialogFragment;
|
/packages/apps/Dialer/ |
AndroidManifest.xml | 249 <receiver android:name=".interactions.UndemoteOutgoingCallReceiver">
|
/packages/apps/Launcher3/WallpaperPicker/src/com/android/photos/ |
BitmapRegionTileSource.java | 397 // loaded, the lifecycle is different and interactions are on a different
|
/system/core/libutils/ |
Looper.cpp | 10 // Debugs poll and wake interactions.
|
/external/chromium_org/third_party/mesa/src/docs/ |
MESA_texture_array.spec | [all...] |
/external/mesa3d/docs/ |
MESA_texture_array.spec | [all...] |
/frameworks/base/core/java/android/os/ |
ParcelFileDescriptor.java | 99 * mechanism for interactions such as {@link ContentProvider}, 115 * mechanism for interactions such as {@link ContentProvider}, [all...] |
/frameworks/base/services/input/ |
InputDispatcher.h | 570 // a kind of continuation used to postpone sensitive policy interactions to a point [all...] |