| /external/chromium/chrome/browser/chromeos/cros/ |
| touchpad_library.h | 13 // This interface defines interaction with the ChromeOS synaptics library APIs.
|
| /external/chromium/chrome/browser/extensions/ |
| extension_clipboard_api.h | 13 // Base class for clipboard function APIs.
|
| extension_input_api.h | 15 // Base class for input APIs.
|
| /external/chromium/chrome/browser/ |
| memory_purger.h | 5 // MemoryPurger provides static APIs to purge as much memory as possible from
|
| /external/icu4c/common/unicode/ |
| udeprctd.h | 14 * Contains data for commenting out APIs.
|
| umisc.h | 24 * This file contains miscellaneous definitions for the C APIs.
|
| usystem.h | 14 * Contains data for commenting out APIs.
|
| /external/icu4c/samples/case/ |
| ucase.c | 37 /* uchar.h APIs, single character case mapping */
47 /* ustring.h APIs, UChar * string case mapping with a Turkish locale */
60 /* ustring.h APIs, UChar * string case mapping with a Engish locale */
72 /* ustring.h APIs, UChar * string case folding */
|
| /external/llvm/docs/ |
| doxygen.intro | 8 /// here on how to use LLVM, only the APIs that make up the software. For usage
|
| /external/webkit/LayoutTests/fast/encoding/ |
| euckr-name.html | 6 <p>Test for <a href="http://bugs.webkit.org/show_bug.cgi?id=25487">bug 25487</a>. Even though we treat EUC-KR as windows-949, the name exposed via DOM APIs should still be EUC-KR.</p>
|
| /frameworks/base/docs/html/guide/topics/usb/ |
| accessory.jd | 10 <a href="#choosing">Choosing the Right USB Accessory APIs</a>
13 <li><a href="#installing">Installing the Google APIs add-on library</a></li>
22 APIs</a></li>
63 <h2 id="choosing">Choosing the Right USB Accessory APIs</h2>
65 <p>Although the USB accessory APIs were introduced to the platform in Android 3.1, they are also
66 available in Android 2.3.4 using the Google APIs add-on library. Because these APIs were
73 <a href="http://code.google.com/android/add-ons/google-apis/index.html">Google APIs add-on
74 library</a> includes the backported USB accessory APIs and they are contained in thi
[all...] |
| /frameworks/base/docs/html/sdk/ |
| compatibility-library.jd | 13 <li><a href="#Using">Using the v4 Library APIs</a></li>
31 application in order to use APIs that are either not available for older platform versions or that
32 offer "utility" APIs that aren't a part of the framework APIs. The goal is to simplify your
33 development by offering more APIs that you can bundle with your application so you can
39 support classes to work with v13 APIs). The minimum version is indicated
62 <li>Support for Accessiblity APIs:
100 <li>Changes to Fragment APIs:
102 <li>Added new APIs to control the visibility of new menus.</li>
103 <li>Added custom animation APIs.</li
[all...] |
| /frameworks/base/graphics/java/android/renderscript/ |
| package.html | 3 <p>The Renderscript rendering and computational APIs offer a low-level, high performance means of
17 APIs in the <code><sdk_root>/platforms/android-3.0/renderscript</code> directory.
18 The Android system APIs are broken into a few main groups:</p>
34 are defined by the native Renderscript APIs and used by your Renderscript code. The
|
| /frameworks/base/media/java/android/media/ |
| package.html | 4 <p>The Media APIs are used to play and, in some cases, record media files. This includes
|
| /frameworks/support/v4/froyo/android/support/v4/view/ |
| ViewConfigurationCompatFroyo.java | 22 * Implementation of menu compatibility that can call Honeycomb APIs.
|
| /frameworks/support/v4/honeycomb/android/support/v4/view/ |
| KeyEventCompatHoneycomb.java | 22 * Implementation of key event compatibility that can call Honeycomb APIs.
|
| MenuCompatHoneycomb.java | 22 * Implementation of menu compatibility that can call Honeycomb APIs.
|
| VelocityTrackerCompatHoneycomb.java | 22 * Implementation of velocity tracker compatibility that can call Honeycomb APIs.
|
| /hardware/invensense/mlsdk/mllite/ |
| ml_mputest.h | 34 /* user APIs */
|
| /cts/tools/signature-tools/templates/ |
| ApiOverviewPage.st | 21 <p>The differences described in this report are based a comparison of the APIs
31 No differences were detected between the two provided APIs.
|
| /development/samples/ApiDemos/res/layout/ |
| secure_view_overlay.xml | 19 <com.example.android.apis.view.SecureViewOverlay
50 </com.example.android.apis.view.SecureViewOverlay>
|
| /development/samples/ApiDemos/res/xml/ |
| preference_headers.xml | 22 <header android:fragment="com.example.android.apis.preference.PreferenceWithHeaders$Prefs1Fragment"
27 <header android:fragment="com.example.android.apis.preference.PreferenceWithHeaders$Prefs2Fragment"
|
| /development/samples/ApiDemos/src/com/example/android/apis/accessibility/ |
| TaskListActivity.java | 17 package com.example.android.apis.accessibility;
19 import com.example.android.apis.R;
|
| /development/samples/ApiDemos/src/com/example/android/apis/animation/ |
| LayoutAnimationsByDefault.java | 17 package com.example.android.apis.animation;
21 import com.example.android.apis.R;
|
| /development/samples/ApiDemos/src/com/example/android/apis/app/ |
| CustomDialogActivity.java | 17 package com.example.android.apis.app;
21 import com.example.android.apis.R;
|
