Scribd
Upload
164 views4 pages

Android App Resources: Grouping Resource Types

Android apps can externalize resources like images, layouts, and strings to maintain them independently of code. At runtime, Android selects the appropriate alternative resource based on the device configuration, such as providing different layouts for different screen sizes. Resources are accessed in code via unique IDs generated in the R class.

Uploaded by

lenciadonicka
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
164 views4 pages

Android App Resources: Grouping Resource Types

Android apps can externalize resources like images, layouts, and strings to maintain them independently of code. At runtime, Android selects the appropriate alternative resource based on the device configuration, such as providing different layouts for different screen sizes. Resources are accessed in code via unique IDs generated in the R class.

Uploaded by

lenciadonicka
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

Android App Resources

 These are additional files and static content that your code uses
o Example
 bitmaps,
 layout definitions,
 user interface strings,
 animation instructions
 externalize app resources from your code to maintain them independently
 We must provide alternative resources for specific device configurations
o At runtime, Android uses the appropriate resource based on the current
configuration.
o Example - provide a different UI layout depending on the screen size
 Externalized app resources can be accessed by using resource IDs that are
generated in your project's R class.

 Grouping resource types


o Place each type of resource in a specific subdirectory of your
project's res/ directory.

MyProject/
src/
MyActivity.java
res/
drawable/
graphic.png
layout/
main.xml
info.xml
mipmap/
icon.png
values/
strings.xml
 Resource directories supported inside project res/ directory.

Directory Resource Type

animator/ XML files that define property animations.


color/ XML files that define a state list of colors.
drawable/ Bitmap files (.png, .9.png, .jpg, .gif)

mipmap/ Drawable files for different launcher icon densities.

layout/ XML files that define a user interface layout.


menu/ XML files that define app menus, such as an Options Menu, Context Menu, or Sub
Menu.
raw/ Arbitrary files to save in their raw form. To open these resources with a
raw InputStream, callResources.openRawResource() with the resource ID, which
is R.raw.filename.
values/ XML files that contain simple values, such as strings, integers, and colors.

xml/ Arbitrary XML files that can be read at runtime by calling Resources.getXML().
Various XML configuration files must be saved here.
font/ Font files with extensions such as .ttf, .otf, or .ttc, or XML files that include
a <font-family> element.

Providing alternative resources


 Alternative resources - to support specific device configurations.

 Example:-

o alternative drawable resources for different screen densities and

o Alternative string resources for different languages.

 Note:-

o At runtime, Android detects the current device configuration and loads


the appropriate resources for your app.

Two different devices, each using different layout resources.

To specify configuration-specific alternatives for a set of resources:

Create a new directory in res/ named in the form


<resources_name>-<config_qualifier>.
 <resources_name> - directory name of the corresponding default resources
 <qualifier> - name that specifies an individual configuration for which these
resources are to be used
Accessing your app resources
 Apply/use in code it by referencing its resource ID.
 All resource IDs are defined in your project's R class, which the aapt tool
automatically generates.
 For each type of resource, there is an R subclass
o for example,
 R.drawable for all drawable resources
 a static integer - for each resource (of that type) – Resource ID
o for example,
 R.drawable.icon
A resource ID is always composed of:

 The resource type: (Each resource is grouped into a "type,")

o Ex:- string, drawable, and layout.

 The resource name:


o filename (excluding the extension) or
o the value in the XML android:name attribute, if the resource is a simple value
(such as a string).

 two ways you can access a resource:


o In code: Using a static integer from a sub-class of your R class, such
as:
 R.string.hello
 R – Class name
 string - resource type and

 hello - resource name


o In XML:
 @string/hello

Accessing resources in code


ImageView imageView = (ImageView) findViewById(R.id.myimageview);
Accessing resources from XML

Referencing style attributes

You might also like