Searched refs:it (Results 1 – 25 of 29) sorted by relevance
12
| /sdk/apps/SdkController/ |
| D | Implementation.txt | 18 - All the handlers are started when the service starts and shutdown with it.
25 Another way to see it is that the app handles a number of tasks which are
38 - in onResume this will bind to the service, creating and starting it if necessary.
39 - in onPause, this will unbind from the service, but does not stop it.
46 When the activity is connected to the service, it can then use getServiceBinder()
63 - EmulatorListener is a callback: the emulator connection uses it to indicate
|
| /sdk/ |
| D | README.txt | 23 To build it from the command-line, you'd use "gradle" as such:
56 However it does depend on /tools/base/sdklib. Let's say you want to
91 - Without argument, it prints what it would do but does nothing.
92 Use the "-f" argument to make it build/copy stuff.
97 making it smarter because obviously we don't want anyone to just try
|
| /sdk/testapps/aidlTest/libWithAidl/ |
| D | ant.properties | 3 # This file must be checked in Version Control Systems, as it is
12 # You can also use it define how the release builds are signed by declaring
|
| /sdk/testapps/jarCheckTests3/lib1/ |
| D | ant.properties | 3 # This file must be checked in Version Control Systems, as it is
12 # You can also use it define how the release builds are signed by declaring
|
| /sdk/testapps/aidlTest/mainProject/ |
| D | ant.properties | 3 # This file must be checked in Version Control Systems, as it is
12 # You can also use it define how the release builds are signed by declaring
|
| /sdk/testapps/jarCheckTests2/app/ |
| D | ant.properties | 3 # This file must be checked in Version Control Systems, as it is
12 # You can also use it define how the release builds are signed by declaring
|
| /sdk/testapps/gridlayoutTest/app/ |
| D | ant.properties | 3 # This file must be checked into Version Control Systems, as it is
12 # You can also use it define how the release builds are signed by declaring
|
| /sdk/testapps/jarCheckTests3/app/ |
| D | ant.properties | 3 # This file must be checked in Version Control Systems, as it is
12 # You can also use it define how the release builds are signed by declaring
|
| /sdk/testapps/buildConfigTest/app/ |
| D | ant.properties | 3 # This file must be checked into Version Control Systems, as it is
12 # You can also use it define how the release builds are signed by declaring
|
| /sdk/testapps/jarCheckTests1/lib2/ |
| D | ant.properties | 3 # This file must be checked in Version Control Systems, as it is
12 # You can also use it define how the release builds are signed by declaring
|
| /sdk/testapps/jarCheckTests1/app/ |
| D | ant.properties | 3 # This file must be checked in Version Control Systems, as it is
12 # You can also use it define how the release builds are signed by declaring
|
| /sdk/testapps/jarCheckTests2/lib1/ |
| D | ant.properties | 3 # This file must be checked in Version Control Systems, as it is
12 # You can also use it define how the release builds are signed by declaring
|
| /sdk/testapps/customViewTest/libWithCustomView/ |
| D | ant.properties | 3 # This file must be checked in Version Control Systems, as it is
12 # You can also use it define how the release builds are signed by declaring
|
| /sdk/testapps/customViewTest/mainProject/ |
| D | ant.properties | 3 # This file must be checked in Version Control Systems, as it is
12 # You can also use it define how the release builds are signed by declaring
|
| /sdk/testapps/basicProjectWithAidl/ |
| D | ant.properties | 3 # This file must be checked into Version Control Systems, as it is
12 # You can also use it define how the release builds are signed by declaring
|
| /sdk/testapps/jarCheckTests1/lib1/ |
| D | ant.properties | 3 # This file must be checked in Version Control Systems, as it is
12 # You can also use it define how the release builds are signed by declaring
|
| /sdk/testapps/jarCheckTests2/lib2/ |
| D | ant.properties | 3 # This file must be checked in Version Control Systems, as it is
12 # You can also use it define how the release builds are signed by declaring
|
| /sdk/testapps/jarCheckTests3/lib2/ |
| D | ant.properties | 3 # This file must be checked in Version Control Systems, as it is
12 # You can also use it define how the release builds are signed by declaring
|
| /sdk/find_java2/src/ |
| D | JavaFinder.cpp | 566 for (auto it = paths->begin(); it != paths->end(); ) { in findJavaPaths() local
567 if (it->mVersion < mMinVersion) { in findJavaPaths()
568 it = paths->erase(it); // C++11 set.erase returns an iterator to the *next* element in findJavaPaths()
570 ++it; in findJavaPaths()
|
| /sdk/docs/ |
| D | howto_build_SDK.txt | 60 Basically it's not trivial yet when done right it's not that complicated.
115 SDK is build on top of a Linux SDK where a few binaries are replaced. So it
116 cannot be built on Windows, and it cannot be built on Mac, only on Linux.
118 I'll repeat this again because it's important:
178 Eclipse and install it at a special location. That's not needed
182 build script by giving it a destination directory and an optional build number:
199 The second argument is the build "number". The example used "$USER" but it
|
| D | howto_use_cupcake_sdk.txt | 53 First you will need to grab the zip of the SDK for your platform or build it
60 Grab the new ADT Eclipse plugin zip file or build it yourself. Keep it
95 - Using Help > Software Update, add a new "archived site", point it to the new
99 - After it restarts, please use Window > Preferences > Android and select
113 The SDK comes with a 1.5 platform. Select it and close the properties panel.
117 The new plugin creates a "gen" folder in your project where it puts the R.java
138 files for your Android projects. This makes it easier to create a new layout, a
161 First if you had customized your build.xml, make a copy of it:
288 Since it is used as directory name, please avoid using shell or path specific
317 In this mode, when a project is deployed in debug or run, it checks:
[all …]
|
| D | Notes_on_WST_StructuredDocument.txt | 9 this out there, so this is a short explanation of how it works, totally
10 based on _empirical_ evidence. As such, it must be taken with a grain of salt.
149 So for example an outer XML_TAG_NAME region collection is a proper XML tag, and it will contain
158 here, the only case where it matters is in a tag such as <string name="my_string">: for the
162 If you want the text of the inner region, you actually need to query it from the outer region.
|
| /sdk/avdlauncher/ |
| D | build.gradle | 32 def binaries = executables.avdLauncher.binaries.matching { it.name == name }
|
| /sdk/sdklauncher/ |
| D | build.gradle | 32 def binaries = executables.sdkLauncher.binaries.matching { it.name == name }
|
| /sdk/find_java/ |
| D | build.gradle | 43 def binaries = executables.findJava.binaries.matching { it.name == name }
|
12