/system/core/libutils/ |
README | 136 The resource overlay mechanism aims to (partly) shadow and extend
|
/external/chromium_org/third_party/WebKit/PerformanceTests/Dromaeo/resources/dromaeo/web/tests/ |
cssquery-dojo.html | 259 language for transforming XML trees, uses this mechanism. <a href="#refsSTTS">[STTS]</a></p> [all...] |
cssquery-jquery.html | 258 language for transforming XML trees, uses this mechanism. <a href="#refsSTTS">[STTS]</a></p> [all...] |
cssquery-prototype.html | 258 language for transforming XML trees, uses this mechanism. <a href="#refsSTTS">[STTS]</a></p> [all...] |
dom-attr.html | 139 language for transforming XML trees, uses this mechanism. <a href="#refsSTTS">[STTS]</a></p> 772 The mechanism for declaring a namespace prefix is left up to the 773 language implementing Selectors. In CSS, such a mechanism is defined [all...] |
dom-modify.html | 169 language for transforming XML trees, uses this mechanism. <a href="#refsSTTS">[STTS]</a></p> 802 The mechanism for declaring a namespace prefix is left up to the 803 language implementing Selectors. In CSS, such a mechanism is defined [all...] |
dom-query.html | 196 language for transforming XML trees, uses this mechanism. <a href="#refsSTTS">[STTS]</a></p> [all...] |
dom-traverse.html | 168 language for transforming XML trees, uses this mechanism. <a href="#refsSTTS">[STTS]</a></p> 801 The mechanism for declaring a namespace prefix is left up to the 802 language implementing Selectors. In CSS, such a mechanism is defined [all...] |
jslib-attr-jquery.html | 145 language for transforming XML trees, uses this mechanism. <a href="#refsSTTS">[STTS]</a></p> 778 The mechanism for declaring a namespace prefix is left up to the 779 language implementing Selectors. In CSS, such a mechanism is defined [all...] |
jslib-attr-prototype.html | 145 language for transforming XML trees, uses this mechanism. <a href="#refsSTTS">[STTS]</a></p> 778 The mechanism for declaring a namespace prefix is left up to the 779 language implementing Selectors. In CSS, such a mechanism is defined [all...] |
jslib-event-jquery.html | 132 language for transforming XML trees, uses this mechanism. <a href="#refsSTTS">[STTS]</a></p> 765 The mechanism for declaring a namespace prefix is left up to the 766 language implementing Selectors. In CSS, such a mechanism is defined [all...] |
jslib-event-prototype.html | 132 language for transforming XML trees, uses this mechanism. <a href="#refsSTTS">[STTS]</a></p> 765 The mechanism for declaring a namespace prefix is left up to the 766 language implementing Selectors. In CSS, such a mechanism is defined [all...] |
jslib-modify-jquery.html | 156 language for transforming XML trees, uses this mechanism. <a href="#refsSTTS">[STTS]</a></p> 789 The mechanism for declaring a namespace prefix is left up to the 790 language implementing Selectors. In CSS, such a mechanism is defined [all...] |
jslib-modify-prototype.html | 156 language for transforming XML trees, uses this mechanism. <a href="#refsSTTS">[STTS]</a></p> 789 The mechanism for declaring a namespace prefix is left up to the 790 language implementing Selectors. In CSS, such a mechanism is defined [all...] |
jslib-style-jquery.html | 154 language for transforming XML trees, uses this mechanism. <a href="#refsSTTS">[STTS]</a></p> 787 The mechanism for declaring a namespace prefix is left up to the 788 language implementing Selectors. In CSS, such a mechanism is defined [all...] |
jslib-style-prototype.html | 155 language for transforming XML trees, uses this mechanism. <a href="#refsSTTS">[STTS]</a></p> 788 The mechanism for declaring a namespace prefix is left up to the 789 language implementing Selectors. In CSS, such a mechanism is defined [all...] |
jslib-traverse-jquery.html | 156 language for transforming XML trees, uses this mechanism. <a href="#refsSTTS">[STTS]</a></p> 789 The mechanism for declaring a namespace prefix is left up to the 790 language implementing Selectors. In CSS, such a mechanism is defined [all...] |
jslib-traverse-prototype.html | 156 language for transforming XML trees, uses this mechanism. <a href="#refsSTTS">[STTS]</a></p> 789 The mechanism for declaring a namespace prefix is left up to the 790 language implementing Selectors. In CSS, such a mechanism is defined [all...] |
/development/ndk/platforms/android-4/samples/san-angeles/jni/ |
license-LGPL.txt | 303 b) Use a suitable shared library mechanism for linking with the 304 Library. A suitable mechanism is one that (1) uses at run time a
|
/external/chromium/chrome/common/extensions/docs/ |
autoupdate.html | 4 templating mechanism. 418 <p>The basic autoupdate mechanism is designed to make the server-side work as easy as just dropping a static XML file onto any plain webserver such as apache, and updating that XML file as you release new versions of your extension(s).</p>
|
tut_oauth.html | 4 templating mechanism. 344 <a href="http://oauth.net/">OAuth</a> is an open protocol that aims to standardize the way desktop and web applications access a user's private data. OAuth provides a mechanism for users to grant access to private data without sharing their private credentials (username/password). Many sites have started enabling APIs to use OAuth because of its security and standard set of libraries.
|
/external/chromium_org/native_client_sdk/src/libraries/third_party/pthreads-win32/ |
COPYING.LIB | 303 b) Use a suitable shared library mechanism for linking with the 304 Library. A suitable mechanism is one that (1) uses at run time a
|
/external/chromium_org/third_party/WebKit/Source/bindings/v8/ |
V8Binding.h | 196 // WebCore string. The reference counting mechanism is used to keep the 575 // the mechanism for these relies on data stored in these fields. We should
|
/external/chromium_org/third_party/WebKit/Source/core/ |
LICENSE-LGPL-2.1 | 303 b) Use a suitable shared library mechanism for linking with the 304 Library. A suitable mechanism is one that (1) uses at run time a
|
/external/chromium_org/third_party/freetype/include/freetype/internal/ |
ftobjs.h | [all...] |