Lines Matching refs:that
26 application correctly, so it is highly recommended that you create them with Eclipse and ADT or
35 …of project and the contents are eventually built into an <code>.apk</code> file that you install o…
41 applications that run on a device.</dd>
45 <dd>These projects contain shareable Android source code and resources that you can reference
46 in Android projects. This is useful when you have common code that you want to reuse.
59 …<p>Android projects are the projects that eventually get built into an <code>.apk</code> file that…
88 <dd>This is empty. You can use it to store raw asset files. Files that you save here are
104 <dd>For XML files that are compiled into animation objects. See the <a href=
110 <dd>For XML files that describe colors. See the <a href=
116 <dd>For bitmap files (PNG, JPEG, or GIF), 9-Patch image files, and XML files that describe
117 Drawable shapes or Drawable objects that contain multiple states (normal, pressed, or
123 <dd>XML files that are compiled into screen layouts (or part of a screen). See the <a href=
128 <dd>For XML files that define application menus.
135 <code>assets/</code> directory only differs in the way that you access them. These files
142 <dd>For XML files that are compiled into many kinds of resource. Unlike other resources in
149 <dd>For miscellaneous XML files that configure application components. For example, an XML
150 file that defines a {@link android.preference.PreferenceScreen}, {@link
164 <dd>The control file that describes the nature of the application and each of its components.
189 build settings used by Ant and also provide the location of your keystore and key alias so that
196 <dd>The Ant build file for your project. This is only applicable for projects that
207 …<p>The SDK includes an example application called <code>TicTacToeMain</code> that shows how a depe…
221 <p>An Android <em>library project</em> is a development project that holds shared Android
228 project feature that generates each library project into its own JAR file.
233 <p>If you have source code and resources that are common to multiple Android projects, you
234 can move them to a library project so that it is easier to maintain across applications and
238 <li>If you are developing multiple related applications that use some of the same components,
242 <li>If you are creating an application that exists in both free and paid versions. You move
243 the part of the application that is common to both versions into a library project. The two
254 <p>However, a library project differs from a standard Android application project in that you
258 library in the dependent application and building that application.</p>
260 <p>When you build an application that depends on a library project, the SDK tools compile the
263 application and the library, the tools ensure that the resource declared in the application gets
264 priority and that the resource in the library project is not compiled into the application
266 resource behaviors or values that are defined in any library.</p>
292 resource. As you develop your applications, be aware that common resource IDs are likely to be
300 …consistent naming scheme that is unique to the project (or is unique across all projects).</p></li>
310 <p>You can develop a library project that itself includes a JAR library, however you need to
315 <p>You can develop a library project that depends on an external library (for example, the Maps
316 external library). In this case, the dependent application must build against a target that
317 includes the external library (for example, the Google APIs Add-On). Note also that both the
336 …"{@docRoot}guide/topics/manifest/uses-sdk-element.html#ApiLevels">API level</a> that is the same a…
337 than — that used by the application. If the library project uses an API level that is
338 higher than that of the application, the application project will not compile. It is
339 perfectly acceptable to have a library that uses the Android 1.5 API (API level 3) and that is
344 <p>There is no requirement for the package name of a library to be the same as that of
345 applications that use it.</p></li>
352 project and the library project is created in all the packages that are needed including the main
359 project by a relative link. What is important is that the main
365 <p>Test projects contain Android applications that you write using the
399 element that connects the test project with the application project.</dd>
418 build settings used by Ant and provide the location to your keystore and key alias, so that the
425 <dd>The Ant build file for your project. This is only applicable for projects that
440 project</a> that instruments an application project that depends on the library project. You
443 <li>You can set up a standard application project that depends on the library and put
444 the instrumentation in that project. This lets you create a self-contained project that