| /developers/samples/android/wearable/wear/Timer/ |
| LICENSE | 237 permission to use material in ways otherwise restricted by
348 available to the public including in ways that members of the
|
| /developers/samples/android/wearable/wear/WatchFace/ |
| LICENSE | 237 permission to use material in ways otherwise restricted by
348 available to the public including in ways that members of the
|
| /developers/samples/android/wearable/wear/WatchViewStub/ |
| LICENSE | 237 permission to use material in ways otherwise restricted by
348 available to the public including in ways that members of the
|
| /docs/source.android.com/src/source/ |
| faqs.jd | 165 <p>There are a number of ways you can contribute to Android. You can report
318 ways to help out Android.</p>
|
| /external/ceres-solver/docs/source/ |
| building.rst | 285 of unofficial ways of building these libraries. Building on Windows
532 scripts shipped with Ceres support two ways for you to do this:
|
| /external/clang/docs/ |
| InternalsManual.rst | 56 driver, but diagnostics can be :ref:`rendered in many different ways
116 Diagnostic mappings are used in many ways. For example, if the user specifies
190 the class of the argument, it can be optionally formatted in different ways.
435 It is possible to implement this interface in many different ways. For
607 some tokens can be spelled multiple ways. For example, C++ supports
[all...] |
| /external/libxml2/doc/ |
| FAQ.html | 135 <p>There are many different ways to accomplish this. Here is one way to
294 You need to convert strings encoded in different ways to utf-8 before
|
| /external/llvm/docs/ |
| FAQ.rst | 94 grabbing the wrong linker/assembler/etc, there are two ways to fix it:
228 major ways to tackle generating LLVM IR from a front-end:
|
| CodeGenerator.rst | 620 is *implemented* in different ways (e.g. to output a .s file, output an ELF .o
725 well-known ways to do this in the literature. LLVM uses a SelectionDAG based
[all...] |
| /external/llvm/docs/tutorial/ |
| LangImpl2.rst | 332 There are many ways to handle this, but an elegant and efficient way is
673 extend the language in many ways, etc. In the `next
|
| LangImpl3.rst | 83 variables in a chunk of code. In many ways, it is the top-level
437 actually delete a forward declaration. There are a number of ways to fix
|
| /external/proguard/docs/manual/ |
| ant.html | 44 There are three ways to configure the ProGuard task:
50 These three ways can be combined, depending on practical circumstances and
|
| /external/skia/src/utils/ |
| SkTextureCompressor_Blitter.h | 150 // This function will be most easily implemented in one of two ways:
379 * weird ways...
|
| /external/valgrind/VEX/priv/ |
| host_arm_defs.h | 820 /* Convert between 32-bit and 64-bit FP values (both ways).
840 /* Convert between 32-bit ints and 64-bit FP values (both ways
[all...] |
| /external/vboot_reference/firmware/include/ |
| vboot_api.h | 561 * Disks are used in two ways:
820 * the following ways:
[all...] |
| /frameworks/base/docs/html/guide/components/ |
| bound-services.jd | 111 different ways you can define your service's {@link android.os.IBinder} interface and the following
120 are three ways you can define the interface:</p>
|
| /frameworks/base/docs/html/guide/topics/graphics/ |
| hardware-accel.jd | 140 <p>There are two different ways to check whether the application is hardware accelerated:</p>
646 rendering pipeline as well. Reducing views is one of the easiest ways to optimize your UI.</dd>
|
| /frameworks/base/docs/html/preview/testing/ |
| performance.jd | 350 You can use this data in different ways. One simple but useful visualization is a
424 performance problems, and find appropriate ways to fix them. For that, it?s highly
|
| /prebuilts/tools/common/proguard/proguard4.7/docs/manual/ |
| ant.html | 42 There are three ways to configure the ProGuard task: using an external
44 the equivalent XML configuration tags. These three ways can be combined,
|
| /frameworks/base/docs/html/training/articles/ |
| smp.jd | 333 CPU optimization, but creates more opportunities for code to behave in ways the
[all...] |
| /docs/source.android.com/src/devices/input/ |
| touch-devices.jd | 206 in different ways.</p>
[all...] |
| /external/libxml2/result/valid/ |
| xlink.xml | 119 <p>While this set of characteristics is already very powerful and obviously has proven itself highly useful and effective, each of these assumptions also limits the range of hypertext functionality. The linking model defined here provides ways to create links that go beyond each of these specific characteristics, thus providing features previously available mostly in dedicated hypermedia systems.
302 <p>The existence of a <termref def="dt-link">link</termref> is asserted by a <termref def="dt-linkel">linking element</termref>. Linking elements must be recognized reliably by application software in order to provide appropriate display and behavior. There are several ways link recognition could be accomplished: for example, reserving element type names, reserving attributes names, leaving the matter of recognition entirely up to stylesheets and application software, or using the XLink <xtermref href="http://www.w3.org/TR/REC-xml-names/">namespace</xtermref> to specify element names and attribute names that would be recognized by namespace and XLink-aware processors. Using element and attribute names within the XLink namespace provides a balance between giving users control of their own markup language design and keeping the identification of linking elements simple and unambiguous.</p>
326 <p>The application may use this information in a number of ways, especially in a complex hypertext system, but it is mainly useful in providing context for application behavior.</p>
[all...] |
| /external/libxml2/test/valid/ |
| xlink.xml | 120 <p>While this set of characteristics is already very powerful and obviously has proven itself highly useful and effective, each of these assumptions also limits the range of hypertext functionality. The linking model defined here provides ways to create links that go beyond each of these specific characteristics, thus providing features previously available mostly in dedicated hypermedia systems.
303 <p>The existence of a <termref def="dt-link">link</termref> is asserted by a <termref def="dt-linkel">linking element</termref>. Linking elements must be recognized reliably by application software in order to provide appropriate display and behavior. There are several ways link recognition could be accomplished: for example, reserving element type names, reserving attributes names, leaving the matter of recognition entirely up to stylesheets and application software, or using the XLink <xtermref href="http://www.w3.org/TR/REC-xml-names/">namespace</xtermref> to specify element names and attribute names that would be recognized by namespace and XLink-aware processors. Using element and attribute names within the XLink namespace provides a balance between giving users control of their own markup language design and keeping the identification of linking elements simple and unambiguous.</p>
327 <p>The application may use this information in a number of ways, especially in a complex hypertext system, but it is mainly useful in providing context for application behavior.</p>
[all...] |
| /external/pcre/dist/ |
| README | 98 in various ways, and rooted in a file called index.html, is distributed in
148 file for ways of building PCRE without using autotools.
300 cause programs to crash in strange ways. There is a discussion about stack
[all...] |
| /external/pcre/dist/doc/html/ |
| README.txt | 98 in various ways, and rooted in a file called index.html, is distributed in
148 file for ways of building PCRE without using autotools.
300 cause programs to crash in strange ways. There is a discussion about stack
[all...] |
