OpenGrok
Home
Sort by relevance
Sort by last modified time
Full Search
Definition
Symbol
File Path
History
|
|
Help
Searched
full:how
(Results
1 - 25
of
4379
) sorted by null
1
2
3
4
5
6
7
8
9
10
11
>>
/external/zlib/contrib/infback9/
README
1
See infback9.h for what this is and
how
to use it.
/system/media/opensles/tools/permute/
readme.txt
1
See comments at top of permute.c for information on
how
to build and use.
/external/netperf/
nettest_sdp.h
16
int recv_buf_size; /*
how
big does the client want it - the */
18
int receive_size; /*
how
many bytes do we want to receive at one */
27
float cpu_rate; /* do we know
how
fast the cpu is already? */
28
int test_length; /*
how
long is the test? */
32
int dirty_count; /*
how
many integers in the receive buffer */
34
int clean_count; /*
how
many integers should be read from the */
43
int recv_buf_size; /*
how
big does the client want it */
47
int test_length; /*
how
long is the test? */
59
float elapsed_time; /*
how
long the test ran */
62
int cpu_method; /*
how
was cpu util measured? *
[
all
...]
nettest_sctp.h
11
int recv_buf_size; /*
how
big does the client want it - the */
13
int receive_size; /*
how
many bytes do we want to receive at one */
22
float cpu_rate; /* do we know
how
fast the cpu is already? */
23
int test_length; /*
how
long is the test? */
27
int dirty_count; /*
how
many integers in the receive buffer */
29
int clean_count; /*
how
many integers should be read from the */
38
int recv_buf_size; /*
how
big does the client want it */
42
int test_length; /*
how
long is the test? */
54
float elapsed_time; /*
how
long the test ran */
57
int cpu_method; /*
how
was cpu util measured? *
[
all
...]
nettest_xti.h
10
int recv_buf_size; /*
how
big does the client want it - the */
12
int receive_size; /*
how
many bytes do we want to receive at one */
21
float cpu_rate; /* do we know
how
fast the cpu is already? */
22
int test_length; /*
how
long is the test? */
26
int dirty_count; /*
how
many integers in the receive buffer */
28
int clean_count; /*
how
many integers should be read from the */
37
int recv_buf_size; /*
how
big does the client want it */
41
int test_length; /*
how
long is the test? */
52
float elapsed_time; /*
how
long the test ran */
55
int cpu_method; /*
how
was cpu util measured? *
[
all
...]
nettest_bsd.h
20
int recv_buf_size; /*
how
big does the client want it - the */
22
int receive_size; /*
how
many bytes do we want to receive at one */
31
float cpu_rate; /* do we know
how
fast the cpu is already? */
32
int test_length; /*
how
long is the test? */
36
int dirty_count; /*
how
many integers in the receive buffer */
38
int clean_count; /*
how
many integers should be read from the */
47
int recv_buf_size; /*
how
big does the client want it */
51
int test_length; /*
how
long is the test? */
62
float elapsed_time; /*
how
long the test ran */
65
int cpu_method; /*
how
was cpu util measured? *
[
all
...]
nettest_unix.h
11
int receive_size; /*
how
many bytes do we want to */
21
float cpu_rate; /* do we know
how
fast the cpu is */
23
int test_length; /*
how
long is the test? */
24
int dirty_count; /*
how
many integers in the receive buffer */
26
int clean_count; /*
how
many integers should be read from the */
35
int recv_buf_size; /*
how
big does the client want it */
41
int test_length; /*
how
long is the test? */
53
float elapsed_time; /*
how
long the test ran */
60
int recv_buf_size; /*
how
big does the client want it */
71
float cpu_rate; /* do we know
how
fast the cpu is? *
[
all
...]
nettest_dlpi.h
12
int receive_size; /*
how
many bytes do we want to */
20
float cpu_rate; /* do we know
how
fast the cpu is */
22
int test_length; /*
how
long is the test? */
26
int dirty_count; /*
how
many integers in the receive buffer */
28
int clean_count; /*
how
many integers should be read from the */
39
int recv_win_size; /*
how
big does the client want it */
43
int test_length; /*
how
long is the test? */
56
float elapsed_time; /*
how
long the test ran */
59
int cpu_method; /*
how
was CPU util measured? */
60
int num_cpus; /*
how
many CPUs were there? *
[
all
...]
/dalvik/dx/src/junit/runner/
TestSuiteLoader.java
4
* An interface to define
how
a test suite should be loaded.
/dalvik/tests/081-hot-exceptions/
info.txt
1
Make a hot exception-throwing path to stress test
how
the trace builder handles
/development/pdk/pndk/samples/sample/
use_hellolibrary.c
1
/* use_hellolibrary.c -- used to show
how
to link to the hellolibrary */
/external/junit/src/junit/runner/
TestSuiteLoader.java
4
* An interface to define
how
a test suite should be loaded.
/external/protobuf/editors/
README.txt
4
See each file's header comment for directions on
how
to use it with the
/frameworks/base/test-runner/src/junit/runner/
TestSuiteLoader.java
4
* An interface to define
how
a test suite should be loaded.
/libcore/junit/src/test/java/junit/runner/
TestSuiteLoader.java
4
* An interface to define
how
a test suite should be loaded.
/frameworks/base/docs/html/guide/appendix/faq/
index.jd
1
page.title=FAQs, Tips, and
How
-to
5
<dt><a href="commontasks.html">Common Development Tasks and
How
To Do Them</a></dt>
6
<dd>Quick and to the point —
how
-to's for a variety of development tasks you are likely to use.</dd>
/frameworks/base/docs/html/guide/practices/design/
index.jd
4
<p>When learning
how
to build applications on a new platform, you first learn what APIs are available and
how
to use them. Later, you learn the nuances of the platform. Put another way: first you learn
how
you <em>can</em> build applications; later, you learn
how
you <em>should</em> build them, to ensure that your applications offer outstanding performance and a great user experience. </p>
8
<p>Successful mobile applications offer an outstanding user experience, in addition to a compelling technical feature set. The user experience is more than just its visual design or UI flow. It is also influenced by
how
well the application responds to the user's keypresses and other actions,
how
it well it interacts with other applications, and
how
fully and efficiently it uses device and system capabilities.</p>
14
different ways; the documents below explain
how
you can build Android
/development/samples/CrossCompatibility/
_index.html
1
<p>This sample demonstrates
how
to design an application that is compatible across different Android versions. Applications
5
<p>In this case, the CrossCompatibility application shows
how
to use APIs that are not available in all Android versions and
19
<p> For more information on
how
to make your applications cross-compatible, please check out the original
20
blogpost <a href="http://android-developers.blogspot.com/2010/07/
how
-to-have-your-cupcake-and-eat-it-too.html">here</a>.</p>
/development/samples/TicTacToeLib/
README.txt
3
These two projects work together. They demonstrate
how
to use the ability to
/external/chromium/third_party/libevent/test/
regress.rpc
17
string
how
= 1;
/frameworks/base/core/java/android/content/res/
package.html
6
(orientation, input types, etc.) that affect
how
the application may behave.
/external/kernel-headers/original/linux/
ncp_mount.h
33
unsigned int time_out; /*
How
long should I wait after
35
unsigned int retry_count; /* And
how
often should I retry? */
56
unsigned int time_out; /*
How
long should I wait after
58
unsigned int retry_count; /* And
how
often should I retry? */
80
unsigned int time_out; /*
How
long should I wait after
82
unsigned int retry_count; /* And
how
often should I retry? */
/frameworks/base/docs/html/guide/appendix/
index.jd
9
<dt><a href="faq/index.html">FAQs, Tips, and
How
-to</a></dt>
10
<dd>
How
to get things done in Android.</dd>
/development/samples/SoftKeyboard/
_index.html
4
a basic example for
how
you would get started writing an input method, to
/external/openssl/apps/
dh2048.pem
12
See there for
how
they were generated.
Completed in 430 milliseconds
1
2
3
4
5
6
7
8
9
10
11
>>