| /prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.7-4.6/sysroot/usr/include/sys/ |
| ioctl.h | 29 /* Define some types used by `ioctl' requests. */
32 /* On a Unix system, the system <sys/ioctl.h> probably defines some of
|
| /external/chromium/net/base/ |
| keygen_handler_unittest.cc | 66 // Challenge String: some challenge
76 KeygenHandler handler(768, "some challenge", GURL("http://www.example.com"));
80 AssertValidSignedPublicKeyAndChallenge(result, "some challenge");
96 KeygenHandler handler(768, "some challenge",
129 new ConcurrencyTestTask(events[i], "some challenge", &results[i]),
141 AssertValidSignedPublicKeyAndChallenge(results[i], "some challenge");
|
| /external/markdown/markdown/extensions/ |
| wikilinks.py | 12 >>> text = "Some text with a [[WikiLink]]."
15 u'<p>Some text with a <a class="wikilink" href="/WikiLink/">WikiLink</a>.</p>'
29 u'<p>Some text with a <a class="foo" href="/wiki/WikiLink.html">WikiLink</a>.</p>'
41 u'<p>Some text with a <a href="http://example.com/WikiLink.html">WikiLink</a>.</p>'
49 ... Some text with a [[WikiLink]]."""
52 u'<p>Some text with a <a href="http://example.com/WikiLink.html">WikiLink</a>.</p>'
|
| /external/stlport/stlport/stl/config/ |
| _como.h | 23 // (and SIMILAR NAMES INVOLVING COMO).... no doubt some of this will
25 // some changes are not really Comeau C++ specific, but required to
30 // (that is, some of the .cxx files cannot compile in strict mode, because they
35 // These changes may also work for some earlier versions of Comeau C++,
60 // Mods for an fpos_t problem for some LINUXes
145 // Some joker #define'd __END_DECLS as };
|
| /external/valgrind/main/docs/xml/ |
| manual-intro.xml | 13 tools. It comes with a set of tools each of which performs some kind of
35 profiler. It has some overlap with Cachegrind, but also gathers some
79 some instrumentation basics; and <command>Nulgrind</command> is the minimal
100 code without worrying about license conflicts. Some of the PThreads
129 <para>Be aware that the core understands some command line options, and
|
| /libcore/luni/src/main/java/javax/xml/transform/sax/ |
| SAXTransformerFactory.java | 72 * @throws TransformerConfigurationException If for some reason the
86 * @throws TransformerConfigurationException If for some reason the
101 * @throws TransformerConfigurationException If for some reason the
114 * @throws TransformerConfigurationException If for some reason the
128 * @throws TransformerConfigurationException If for some reason the
141 * @throws TransformerConfigurationException If for some reason the
|
| /ndk/sources/cxx-stl/stlport/stlport/stl/config/ |
| _como.h | 23 // (and SIMILAR NAMES INVOLVING COMO).... no doubt some of this will
25 // some changes are not really Comeau C++ specific, but required to
30 // (that is, some of the .cxx files cannot compile in strict mode, because they
35 // These changes may also work for some earlier versions of Comeau C++,
60 // Mods for an fpos_t problem for some LINUXes
145 // Some joker #define'd __END_DECLS as };
|
| /prebuilts/ndk/5/sources/cxx-stl/stlport/stlport/stl/config/ |
| _como.h | 23 // (and SIMILAR NAMES INVOLVING COMO).... no doubt some of this will
25 // some changes are not really Comeau C++ specific, but required to
30 // (that is, some of the .cxx files cannot compile in strict mode, because they
35 // These changes may also work for some earlier versions of Comeau C++,
60 // Mods for an fpos_t problem for some LINUXes
145 // Some joker #define'd __END_DECLS as };
|
| /prebuilts/ndk/6/sources/cxx-stl/stlport/stlport/stl/config/ |
| _como.h | 23 // (and SIMILAR NAMES INVOLVING COMO).... no doubt some of this will
25 // some changes are not really Comeau C++ specific, but required to
30 // (that is, some of the .cxx files cannot compile in strict mode, because they
35 // These changes may also work for some earlier versions of Comeau C++,
60 // Mods for an fpos_t problem for some LINUXes
145 // Some joker #define'd __END_DECLS as };
|
| /prebuilts/ndk/7/sources/cxx-stl/stlport/stlport/stl/config/ |
| _como.h | 23 // (and SIMILAR NAMES INVOLVING COMO).... no doubt some of this will
25 // some changes are not really Comeau C++ specific, but required to
30 // (that is, some of the .cxx files cannot compile in strict mode, because they
35 // These changes may also work for some earlier versions of Comeau C++,
60 // Mods for an fpos_t problem for some LINUXes
145 // Some joker #define'd __END_DECLS as };
|
| /prebuilts/ndk/8/sources/cxx-stl/stlport/stlport/stl/config/ |
| _como.h | 23 // (and SIMILAR NAMES INVOLVING COMO).... no doubt some of this will
25 // some changes are not really Comeau C++ specific, but required to
30 // (that is, some of the .cxx files cannot compile in strict mode, because they
35 // These changes may also work for some earlier versions of Comeau C++,
60 // Mods for an fpos_t problem for some LINUXes
145 // Some joker #define'd __END_DECLS as };
|
| /sdk/eclipse/plugins/com.android.ide.eclipse.adt/src/com/android/ide/eclipse/adt/internal/editors/layout/gle2/ |
| Gesture.java | 31 * some gestures don't actually edit anything, such as a selection), and a
63 * <li>Resize (dragging some edge or corner of a widget to change its size, for
64 * example to some new fixed size, or to "attach" it to some other edge.)
65 * <li>Inline Editing (editing the text of some text-oriented widget like a
67 * <li>Link (associate two or more widgets in some way, such as an
|
| /ndk/sources/host-tools/nawk-20071023/ |
| FIXES | 40 fixed some null pointer refs calling adjbuf.
50 removed some no-effect asserts in run.c.
77 removed some #ifdef's in run.c and lex.c that appear to no
97 smaller size, and i think that's right. added some assertions to b.c
116 this one but for providing a fix, in some of the most mysterious
172 added some parens to isblank, in another attempt to make things
192 rolled back -- programs like x = 1.2 don't work in some locales,
217 added some tests for null pointers to debugging printf's, which
271 fixed some nextfile bugs: not handling all cases. thanks to
289 band-aid in b.c (member()), and some (uschar) casts to head
[all...] |
| /prebuilts/gcc/linux-x86/host/i686-linux-glibc2.7-4.6/i686-linux/include/c++/4.6.x-google/ext/pb_ds/ |
| assoc_container.hpp | 59 * to the corresponding containers in std (except for some points
194 // Constructor taking some policy objects. r_hash_fn will be
199 // Constructor taking some policy objects. r_hash_fn will be
206 // Constructor taking some policy objects. r_hash_fn will be
214 // Constructor taking some policy objects. r_hash_fn will be
232 // some policy objects. The value_types between first_it and
240 // some policy objects The value_types between first_it and
251 // some policy objects The value_types between first_it and
264 // some policy objects The value_types between first_it and
333 // Constructor taking some policy objects. r_hash_fn will b
[all...] |
| /prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.7-4.6/x86_64-linux/include/c++/4.6.x-google/ext/pb_ds/ |
| assoc_container.hpp | 59 * to the corresponding containers in std (except for some points
194 // Constructor taking some policy objects. r_hash_fn will be
199 // Constructor taking some policy objects. r_hash_fn will be
206 // Constructor taking some policy objects. r_hash_fn will be
214 // Constructor taking some policy objects. r_hash_fn will be
232 // some policy objects. The value_types between first_it and
240 // some policy objects The value_types between first_it and
251 // some policy objects The value_types between first_it and
264 // some policy objects The value_types between first_it and
333 // Constructor taking some policy objects. r_hash_fn will b
[all...] |
| /prebuilts/ndk/8/sources/cxx-stl/gnu-libstdc++/4.6/include/ext/pb_ds/ |
| assoc_container.hpp | 59 * to the corresponding containers in std (except for some points
194 // Constructor taking some policy objects. r_hash_fn will be
199 // Constructor taking some policy objects. r_hash_fn will be
206 // Constructor taking some policy objects. r_hash_fn will be
214 // Constructor taking some policy objects. r_hash_fn will be
232 // some policy objects. The value_types between first_it and
240 // some policy objects The value_types between first_it and
251 // some policy objects The value_types between first_it and
264 // some policy objects The value_types between first_it and
333 // Constructor taking some policy objects. r_hash_fn will b
[all...] |
| /external/quake/quake/src/WinQuake/ |
| glqnotes.txt | 62 these options on the command line, or they will only take effect on some of
75 there are some additional settings that can drastically lower the amount of
96 and the second for the lightmaps that are blended on the textures. On some
103 This extension will be autodetected and used. If for some reason it is not
119 Sets texture mapping to point sampled, which may be faster on some GL systems
132 some hardware run faster. If this is cleared, the 3dfx will back up a number
138 like normal quake, but it can be a significant speed hit on some systems.
141 Glquake uses a buffering method that avoids clearing the Z buffer, but some
152 These are some rendering tricks that were easy to do in glquake. They aren't
165 chance, I will probably release some maps that have been processed properly
[all...] |
| /external/quake/quake/src/WinQuake/kit/ |
| README.TXT | 62 these options on the command line, or they will only take effect on some of
75 there are some additional settings that can drastically lower the amount of
96 and the second for the lightmaps that are blended on the textures. On some
103 This extension will be autodetected and used. If for some reason it is not
119 Sets texture mapping to point sampled, which may be faster on some GL systems
132 some hardware run faster. If this is cleared, the 3dfx will back up a number
138 like normal quake, but it can be a significant speed hit on some systems.
141 Glquake uses a buffering method that avoids clearing the Z buffer, but some
152 These are some rendering tricks that were easy to do in glquake. They aren't
165 chance, I will probably release some maps that have been processed properly
[all...] |
| /external/valgrind/main/gdbserver_tests/ |
| README_DEVELOPERS | 27 and on some platforms gdb 7.0 and 7.1.
28 Some gdb tests implies a gdb >= 7.2. (these are automatically disabled
30 Test behaviour with gdb < 7.0 is unknown: some might fail,
31 some might block or loop for a very long time.
33 Some tests implies to have a vgdb "ptrace invoker" capable.
121 ... some output
123 ... some other output, filtered by both the first and second push
129 gdbserver, tests can verify specifically some output without being
181 c # continue, some errors will appear
194 wait for some messages from the "big" firefox executable to appear
[all...] |
| /prebuilts/gcc/linux-x86/host/i686-linux-glibc2.7-4.4.3/i686-linux/include/c++/4.4.3/ext/pb_ds/ |
| assoc_container.hpp | 178 // Constructor taking some policy objects. r_hash_fn will be
183 // Constructor taking some policy objects. r_hash_fn will be
190 // Constructor taking some policy objects. r_hash_fn will be
198 // Constructor taking some policy objects. r_hash_fn will be
216 // some policy objects. The value_types between first_it and
224 // some policy objects The value_types between first_it and
235 // some policy objects The value_types between first_it and
248 // some policy objects The value_types between first_it and
317 // Constructor taking some policy objects. r_hash_fn will be
322 // Constructor taking some policy objects. r_hash_fn will b
[all...] |
| /prebuilts/ndk/5/sources/cxx-stl/gnu-libstdc++/include/ext/pb_ds/ |
| assoc_container.hpp | 178 // Constructor taking some policy objects. r_hash_fn will be
183 // Constructor taking some policy objects. r_hash_fn will be
190 // Constructor taking some policy objects. r_hash_fn will be
198 // Constructor taking some policy objects. r_hash_fn will be
216 // some policy objects. The value_types between first_it and
224 // some policy objects The value_types between first_it and
235 // some policy objects The value_types between first_it and
248 // some policy objects The value_types between first_it and
317 // Constructor taking some policy objects. r_hash_fn will be
322 // Constructor taking some policy objects. r_hash_fn will b
[all...] |
| /prebuilts/ndk/6/sources/cxx-stl/gnu-libstdc++/include/ext/pb_ds/ |
| assoc_container.hpp | 178 // Constructor taking some policy objects. r_hash_fn will be
183 // Constructor taking some policy objects. r_hash_fn will be
190 // Constructor taking some policy objects. r_hash_fn will be
198 // Constructor taking some policy objects. r_hash_fn will be
216 // some policy objects. The value_types between first_it and
224 // some policy objects The value_types between first_it and
235 // some policy objects The value_types between first_it and
248 // some policy objects The value_types between first_it and
317 // Constructor taking some policy objects. r_hash_fn will be
322 // Constructor taking some policy objects. r_hash_fn will b
[all...] |
| /prebuilts/ndk/7/sources/cxx-stl/gnu-libstdc++/include/ext/pb_ds/ |
| assoc_container.hpp | 178 // Constructor taking some policy objects. r_hash_fn will be
183 // Constructor taking some policy objects. r_hash_fn will be
190 // Constructor taking some policy objects. r_hash_fn will be
198 // Constructor taking some policy objects. r_hash_fn will be
216 // some policy objects. The value_types between first_it and
224 // some policy objects The value_types between first_it and
235 // some policy objects The value_types between first_it and
248 // some policy objects The value_types between first_it and
317 // Constructor taking some policy objects. r_hash_fn will be
322 // Constructor taking some policy objects. r_hash_fn will b
[all...] |
| /prebuilts/ndk/8/sources/cxx-stl/gnu-libstdc++/4.4.3/include/ext/pb_ds/ |
| assoc_container.hpp | 178 // Constructor taking some policy objects. r_hash_fn will be
183 // Constructor taking some policy objects. r_hash_fn will be
190 // Constructor taking some policy objects. r_hash_fn will be
198 // Constructor taking some policy objects. r_hash_fn will be
216 // some policy objects. The value_types between first_it and
224 // some policy objects The value_types between first_it and
235 // some policy objects The value_types between first_it and
248 // some policy objects The value_types between first_it and
317 // Constructor taking some policy objects. r_hash_fn will be
322 // Constructor taking some policy objects. r_hash_fn will b
[all...] |
| /frameworks/base/docs/html/distribute/googleplay/strategies/ |
| app-quality.jd | 30 A better app can go a very long way: a higher quality app will translate to higher user ratings, generally better rankings, more downloads, and higher retention (longer install periods). High-quality apps also have a much higher likelihood of getting some unanticipated positive publicity such as being featured in Google Play or getting social media buzz.</p>
32 The upside to having a higher-quality app is obvious. However, it's not always clear how to make an app "better". This document looks at some of the key factors in app quality and ways of improving your app over time, after you've launched the app.</p>
38 The most obvious way to listen to users is by reading and addressing comments on your app in Google Play. Although the comments aren't always productive or constructive, some will provide valuable insight on aspects of your app that you may not have consciously considered before. It's important to remember that users have the opportunity to change their ratings and comments about an app as much as they'd like.</p>
40 One way to reach users and help them address their concerns is to set up your own support and discussion destination(s). There are some great support tools out there that can put you in touch with your users directly, from forums such as <a href="http://groups.google.com">Google Groups</a> to comprehensive customer support products and destinations. Once you get set up with such a tool, make sure to fill in the support link in your Google Play product details page — users do click through to these.</p>
42 Another way to better listen to your users is by having a public beta or trusted tester program. It's crucial to have some amount of real user testing before releasing something in Google Play. Fortunately, you can distribute your apps to users outside of Google Play via a website; this website can require a login or be publicly accessible — it's entirely up to you. Take advantage of this opportunity by offering your next planned update to some early adopters, before submitting to Google Play. You'll be surprised by how many little, yet impactful, improvements can come out of crowd-sourced, real-user testing.</p>
54 Last, keep an external bug and feature request tracker and let users know how to find it. This will enable them to engage with the app at a closer level, by following features and bugs that affect them. User frustration with app problems can be effectively managed with diligent issue tracking and communication. Some of the community support tools listed above offer issue tracking features, and if your project is open source, most popular repository hosting sites will offer this as well.</p>
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>
90 In the same vein, two problems that can plague some Android user interfaces are small tap targets and excessively small font sizes. These are generall (…)
[all...] |
