Lines Matching full:application
26 application correctly, so it is highly recommended that you create them with Eclipse and ADT or
33 <dd>An Android project is the container for your application's source code, resource files, and
34 files such as the Ant build and Android Manifest file. An application project is the main type
40 <dd>These projects contain code to test your application projects and are built into
54 generate your project. As your application grows in complexity, you might require new kinds of
60 onto a device. They contain things such as application source code and resource files.
97 Contains application resources, such as drawable files, layout files, and string values. See
98 <a href="{@docRoot}guide/topics/resources/index.html">Application Resources</a> for more
128 <dd>For XML files that define application menus.
136 are processed by aapt and must be referenced from the application using a resource
149 <dd>For miscellaneous XML files that configure application components. For example, an XML
153 Metadata</a>. See <a href="{@docRoot}guide/topics/resources/index.html">Application Resources</a>
154 for more information about configuring these application components.</dd>
164 <dd>The control file that describes the nature of the application and each of its components.
190 the build tools can sign your application when building in release mode. This file is integral
207 <p>The SDK includes an example application called <code>TicTacToeMain</code> that shows how a dependent
208 application can use code and resources from an Android Library project. The TicTacToeMain
209 application uses code and resources from an example library project called TicTacToeLib.</p>
217 application</a>.</p>
222 source code and resources. Other Android application projects can reference the library project
224 application projects can reference the same library project and any single application project
239 you move the redundant components out of their respective application projects and create a
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
245 and provide only the difference between the two application versions.</li>
248 <p>Structurally, a library project is similar to a standard Android application project. For
254 <p>However, a library project differs from an 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
265 <code>.apk</code>. This gives your application the flexibility to either use or redefine any
268 <p>To organize your code further, your application can add references to multiple library
270 build up the resources actually used in your application in a cumulative manner. When two
271 libraries referenced from an application define the same resource ID, the tools select the
276 libraries are merged with the application one at a time, starting from the lowest priority to
289 <p>Since the tools merge the resources of a library project with those of a dependent application
291 the resource from the application, or the library with highest priority, and discard the other
293 defined in more than one project and will be merged, with the resource from the application or
311 manually edit the dependent application project's build path and add a path to the JAR file.</p></li>
316 external library). In this case, the dependent application must build against a target that
318 library project and the dependent application must declare the external library in their manifest
327 used by an application must be stored in the <code>assets/</code> directory of the application
333 <p>A library is compiled as part of the dependent application project, so the API used in the
335 application project. In general, the library project should use an <a href=
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
349 <p>When you build the dependent application project, library projects are compiled and
350 merged with the application project. Each library has its own <code>R</code> class, named according
358 dependent application project, as long as the application project can reference the library
388 <dd>A folder for your application resources, such as drawable files, layout files, string
389 values, etc. See <a href="{@docRoot}guide/topics/resources/index.html">Application
399 element that connects the test project with the application project.</dd>
419 build tools can sign your application when building in release mode. This file is integral to
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
