| /frameworks/base/tools/apilint/ |
| D | apilint.py | 119 self.methods = []
180 clazz.methods.append(Method(clazz, raw, blame))
248 for m in clazz.methods:
270 for m in clazz.methods:
286 for m in clazz.methods:
290 if len(clazz.methods) == 1 and clazz.name.startswith("On"):
291 m = clazz.methods[0]
358 methods = [ m.name for m in clazz.methods ]
359 eq = "equals" in methods
360 hc = "hashCode" in methods
[all …]
|
| /frameworks/base/core/jni/android/graphics/ |
| D | PorterDuff.cpp | 41 static JNINativeMethod methods[] = { variable
47 "android/graphics/PorterDuffXfermode", methods, in register_android_graphics_PorterDuff()
48 sizeof(methods) / sizeof(methods[0])); in register_android_graphics_PorterDuff()
|
| D | PathMeasure.cpp | 146 static JNINativeMethod methods[] = { variable
159 int result = AndroidRuntime::registerNativeMethods(env, "android/graphics/PathMeasure", methods, in register_android_graphics_PathMeasure()
160 sizeof(methods) / sizeof(methods[0])); in register_android_graphics_PathMeasure()
|
| /frameworks/volley/src/com/android/volley/toolbox/ |
| D | HttpClientStack.java | 27 import org.apache.http.client.methods.HttpDelete;
28 import org.apache.http.client.methods.HttpEntityEnclosingRequestBase;
29 import org.apache.http.client.methods.HttpGet;
30 import org.apache.http.client.methods.HttpHead;
31 import org.apache.http.client.methods.HttpOptions;
32 import org.apache.http.client.methods.HttpPost;
33 import org.apache.http.client.methods.HttpPut;
34 import org.apache.http.client.methods.HttpTrace;
35 import org.apache.http.client.methods.HttpUriRequest;
|
| /frameworks/volley/tests/src/com/android/volley/toolbox/ |
| D | HttpClientStackTest.java | 23 import org.apache.http.client.methods.HttpDelete;
24 import org.apache.http.client.methods.HttpGet;
25 import org.apache.http.client.methods.HttpHead;
26 import org.apache.http.client.methods.HttpOptions;
27 import org.apache.http.client.methods.HttpPost;
28 import org.apache.http.client.methods.HttpPut;
29 import org.apache.http.client.methods.HttpTrace;
30 import org.apache.http.client.methods.HttpUriRequest;
|
| /frameworks/base/core/tests/hosttests/test-apps/SharedUid/32/jni/ |
| D | native.cpp | 33 static JNINativeMethod methods[] = { variable
66 methods, sizeof(methods) / sizeof(methods[0]))) { in registerNatives()
|
| /frameworks/base/core/tests/hosttests/test-apps/SharedUid/64/jni/ |
| D | native.cpp | 33 static JNINativeMethod methods[] = { variable
66 methods, sizeof(methods) / sizeof(methods[0]))) { in registerNatives()
|
| /frameworks/base/core/tests/hosttests/test-apps/SharedUid/dual/jni/ |
| D | native.cpp | 33 static JNINativeMethod methods[] = { variable
66 methods, sizeof(methods) / sizeof(methods[0]))) { in registerNatives()
|
| /frameworks/webview/chromium/ |
| D | proguard.flags | 12 # Keep the native methods bound to plat_support.
14 native <methods>;
22 @**.CalledByNative <methods>;
25 @**.CalledByNativeUnchecked <methods>;
28 native <methods>;
31 # Keep methods which get bound to JS interfaces via reflection.
33 @**.JavascriptInterface <methods>;
57 # We need to keep these explicitly as they are parameters to methods which
66 # Keep these classes as they are parameters to methods that are native entry points.
|
| /frameworks/base/tools/layoutlib/create/src/com/android/tools/layoutlib/create/ |
| D | AsmGenerator.java | 98 Set<String> methods = mDelegateMethods.get(className); in AsmGenerator() local
99 if (methods == null) { in AsmGenerator()
100 methods = new HashSet<String>(); in AsmGenerator()
101 mDelegateMethods.put(className, methods); in AsmGenerator()
103 methods.add(methodName); in AsmGenerator()
107 Set<String> methods = mDelegateMethods.get(className); in AsmGenerator() local
108 if (methods == null) { in AsmGenerator()
109 methods = new HashSet<String>(); in AsmGenerator()
110 mDelegateMethods.put(className, methods); in AsmGenerator()
112 methods.add(DelegateClassAdapter.ALL_NATIVES); in AsmGenerator()
|
| /frameworks/base/cmds/ime/src/com/android/commands/ime/ |
| D | Ime.java | 105 List<InputMethodInfo> methods; in runList() local
108 methods = mImm.getEnabledInputMethodList(); in runList()
116 methods = mImm.getInputMethodList(); in runList()
124 if (methods != null) { in runList()
126 for (int i=0; i<methods.size(); i++) { in runList()
127 InputMethodInfo imi = methods.get(i); in runList()
|
| /frameworks/base/docs/html/tools/help/uiautomator/ |
| D | UiObjectNotFoundException.jd | 112 …<a href="#" onclick="return toggleInherited(this, null)" id="inherited-methods-java.lang.Throwable…
113 ><img id="inherited-methods-java.lang.Throwable-trigger"
120 <div id="inherited-methods-java.lang.Throwable">
121 <div id="inherited-methods-java.lang.Throwable-list"
124 <div id="inherited-methods-java.lang.Throwable-summary" style="display: none;">
314 …<a href="#" onclick="return toggleInherited(this, null)" id="inherited-methods-java.lang.Object" c…
315 ><img id="inherited-methods-java.lang.Object-trigger"
322 <div id="inherited-methods-java.lang.Object">
323 <div id="inherited-methods-java.lang.Object-list"
326 <div id="inherited-methods-java.lang.Object-summary" style="display: none;">
|
| D | UiAutomatorTestCase.jd | 167 …<a href="#" onclick="return toggleInherited(this, null)" id="inherited-methods-junit.framework.Tes…
168 ><img id="inherited-methods-junit.framework.TestCase-trigger"
175 <div id="inherited-methods-junit.framework.TestCase">
176 <div id="inherited-methods-junit.framework.TestCase-list"
179 <div id="inherited-methods-junit.framework.TestCase-summary" style="display: none;">
305 …<a href="#" onclick="return toggleInherited(this, null)" id="inherited-methods-junit.framework.Ass…
306 ><img id="inherited-methods-junit.framework.Assert-trigger"
313 <div id="inherited-methods-junit.framework.Assert">
314 <div id="inherited-methods-junit.framework.Assert-list"
317 <div id="inherited-methods-junit.framework.Assert-summary" style="display: none;">
[all …]
|
| /frameworks/base/core/java/android/view/ |
| D | ViewDebug.java | 1046 Method[] methods = map.get(klass); in getExportedPropertyMethods() local
1047 if (methods != null) { in getExportedPropertyMethods()
1048 return methods; in getExportedPropertyMethods()
1076 methods = foundMethods.toArray(new Method[foundMethods.size()]); in getExportedPropertyMethods()
1077 map.put(klass, methods); in getExportedPropertyMethods()
1079 return methods; in getExportedPropertyMethods()
1153 final Method[] methods = getExportedPropertyMethods(klass); in exportMethods() local
1154 int count = methods.length; in exportMethods()
1156 final Method method = methods[i]; in exportMethods()
1473 Method[] methods = map.get(klass); in capturedViewGetPropertyMethods() local
[all …]
|
| /frameworks/base/tools/layoutlib/create/ |
| D | README.txt | 92 - specific methods to override (see method stubs details below).
93 - specific methods for which to delegate calls.
94 - specific methods to remove based on their return type.
110 changed from protected/private to public. The code of the methods is then kept as-is, except for
111 native methods which are replaced by a stub. Methods that are to be overridden are also replaced by
118 methods and types. Note that other classes are not transformed and keep referencing the original
134 ReplaceMethodCallsAdapter replaces calls to certain methods. This is different from the
137 This is useful for methods in the Java namespace where we cannot add delegates. The configuration
149 As indicated above, all native and overridden methods are replaced by a stub. We don't have the
173 some specific methods that are stubbed out and change their return value.
[all …]
|
| /frameworks/base/core/jni/ |
| D | android_os_MemoryFile.cpp | 140 static const JNINativeMethod methods[] = { variable
156 methods, NELEM(methods)); in register_android_os_MemoryFile()
|
| D | android_opengl_EGLExt.cpp | 152 static JNINativeMethod methods[] = { variable
160 …err = android::AndroidRuntime::registerNativeMethods(_env, classPathName, methods, NELEM(methods)); in register_android_opengl_jni_EGLExt()
|
| /frameworks/base/docs/html/training/activity-testing/ |
| D | activity-basic-testing.jd | 35 test methods. You can then run your test to get a test report. If any test
72 {@link junit.framework.TestCase#tearDown()} methods in your test. The
74 running any other test methods, and {@link junit.framework.TestCase#tearDown()}
75 at the end of each test method execution. You can use these methods to keep
76 the code for test initialization and clean up separate from the tests methods.
90 methods to your test case, and add variable declarations for the
157 <p>The assertion methods are from the JUnit {@link junit.framework.Assert}
167 <p>In both cases, the test runner proceeds to run the other test methods in the
171 <p>Next, add one or more test methods to verify the layout and functional
188 <p class="note"><strong>Note:</strong> When naming test methods, you can use
[all …]
|
| D | activity-ui-testing.jd | 63 {@link android.app.Activity} or run test methods on the UI thread, you can
65 To learn more about how to run test methods on the UI thread, see
109 <p>The following section demonstrates how you can implement test methods
137 object, then call assertion methods to verify that the
182 helper class provides convenience methods for simulating touch interactions
183 with your application. You can use these methods to simulate clicking, tapping,
186 methods are designed to send events to the UI thread safely from the test thread.
210 <p>You can mark up your test methods with other test annotations to control
|
| /frameworks/base/docs/html/training/basics/activity-lifecycle/ |
| D | index.jd | 43 focus. During this process, the Android system calls a series of lifecycle methods on the
46 lifecycle methods on your activity as it moves into the background (where the activity is no
49 <p>Within the lifecycle callback methods, you can declare how your activity behaves when the
55 <p>This class explains important lifecycle callback methods that each {@link
|
| D | starting.jd | 39 callback methods that correspond to specific stages of its
40 lifecycle. There is a sequence of callback methods that start up an activity and a sequence of
41 callback methods that tear down an activity.</p>
43 <p>This lesson provides an overview of the most important lifecycle methods and shows you how to
50 <p>During the life of an activity, the system calls a core set of lifecycle methods in
56 <p>As the user begins to leave the activity, the system calls other methods that move the activity
72 lifecycle methods. However, it's important that you understand each one and implement those that
73 ensure your app behaves the way users expect. Implementing your activity lifecycle methods properly
88 methods.</p>
225 calls the {@link android.app.Activity#onStart()} and {@link android.app.Activity#onResume()} methods
[all …]
|
| /frameworks/base/docs/html/training/keyboard-input/ |
| D | commands.jd | 23 or directly handle the keyboard input yourself, you can do so by implementing callback methods
31 should generally override the callback methods in your extension of these classes as
77 query the {@link android.view.KeyEvent} that's passed to the callback method. Several methods
80 the exact modifier key you care about is being pressed with methods such as
|
| /frameworks/base/cmds/uiautomator/library/testrunner-src/com/android/uiautomator/testrunner/ |
| D | TestCaseCollector.java | 88 Method[] methods = clazz.getMethods(); in addTestClass() local
89 for (Method method : methods) { in addTestClass()
|
| /frameworks/base/docs/html/tools/testing/ |
| D | testing_android.jd | 105 provide helper methods for creating mock objects and methods that help you control the
148 statements test a part of the application under test. You organize test methods into classes
150 the application under test. Each class is a container for related test methods, although it
151 often provides helper methods as well.
227 teardown, and helper methods.
231 The assert methods compare values you expect from a test to the actual results and
247 … Android instrumentation is a set of control methods or "hooks" in the Android system. These hooks
258 methods directly, but you can do so using instrumentation.
267 With Android instrumentation, though, you can invoke callback methods in your test code.
305 tests can invoke methods in the components, and modify and examine fields in the components.
[all …]
|
| D | service_testing.jd | 65 of the Service lifecycle. If the lifecycle methods that start up your Service, such as
72 Most other testing is facilitated by the methods in the {@link android.test.ServiceTestCase}
80 with with methods for testing application permissions and for controlling the application and
101 Context before any test methods touch it. You can retrieve this Context by calling
106 The methods {@link android.test.ServiceTestCase#setApplication(Application) setApplication()}
128 {@link android.app.Application} in which all the methods throw an Exception, so to use it
129 effectively you subclass it and override the methods you need. You then inject it into the
|