文章出处：https://blog.csdn.net/shift_wwx/article/details/38706147
前言：
一般应用开发的时候，都会通过getResources().getXXX()来获取资源信息，例如getDrawable、getDimension、getString等，这里我小结了资源加载的机制以及加载过程的实现。
获取Resources一般有两种方式：Context、PackageManager。
一、通过Context获取Resource
1、getResources()
Context类中：
public abstract Resources getResources(); @Override
public Resources getResources() {
return mResources;
}private Resources mResources;可以看到这个是个Resources对象，即不同的context对应不同的Resources对象。
而这个对象的赋值是在init()中，在创建ContextImpl的时候，会调用init()对内部的变量进行初始化。其中就包括Resources：
final void init(LoadedApk packageInfo, IBinder activityToken, ActivityThread mainThread,
Resources container, String basePackageName, UserHandle user) {
mPackageInfo = packageInfo;
if (basePackageName != null) {
mBasePackageName = mOpPackageName = basePackageName;
} else {
mBasePackageName = packageInfo.mPackageName;
ApplicationInfo ainfo = packageInfo.getApplicationInfo();
if (ainfo.uid == Process.SYSTEM_UID && ainfo.uid != Process.myUid()) {
// Special case: system components allow themselves to be loaded in to other
// processes. For purposes of app ops, we must then consider the context as
// belonging to the package of this process, not the system itself, otherwise
// the package+uid verifications in app ops will fail.
mOpPackageName = ActivityThread.currentPackageName();
} else {
mOpPackageName = mBasePackageName;
}
}
mResources = mPackageInfo.getResources(mainThread);
mResourcesManager = ResourcesManager.getInstance();2、从代码中可以看出mResources = mPackageInfo.getResources(mainThread)
public Resources getResources(ActivityThread mainThread) {
if (mResources == null) {
mResources = mainThread.getTopLevelResources(mResDir,
Display.DEFAULT_DISPLAY, null, this);
}
return mResources;
} /**
* Creates the top level resources for the given package.
*/
Resources getTopLevelResources(String resDir,
int displayId, Configuration overrideConfiguration,
LoadedApk pkgInfo) {
return mResourcesManager.getTopLevelResources(resDir, displayId, overrideConfiguration,
pkgInfo.getCompatibilityInfo(), null);
}注意这里的mResourcesManager：
ActivityThread() {
mResourcesManager = ResourcesManager.getInstance();
} public static ResourcesManager getInstance() {
synchronized (ResourcesManager.class) {
if (sResourcesManager == null) {
sResourcesManager = new ResourcesManager();
}
return sResourcesManager;
}
}接着：
/**
* Creates the top level Resources for applications with the given compatibility info.
*
* @param resDir the resource directory.
* @param compatInfo the compability info. Must not be null.
* @param token the application token for determining stack bounds.
*/
public Resources getTopLevelResources(String resDir, int displayId,
Configuration overrideConfiguration, CompatibilityInfo compatInfo, IBinder token) {
final float scale = compatInfo.applicationScale;
ResourcesKey key = new ResourcesKey(resDir, displayId, overrideConfiguration, scale,
token);
Resources r;
synchronized (this) {
// Resources is app scale dependent.
if (false) {
Slog.w(TAG, "getTopLevelResources: " + resDir + " / " + scale);
}
WeakReference<Resources> wr = mActiveResources.get(key);
r = wr != null ? wr.get() : null;
//if (r != null) Slog.i(TAG, "isUpToDate " + resDir + ": " + r.getAssets().isUpToDate());
if (r != null && r.getAssets().isUpToDate()) {
if (false) {
Slog.w(TAG, "Returning cached resources " + r + " " + resDir
+ ": appScale=" + r.getCompatibilityInfo().applicationScale);
}
return r;
}
}
//if (r != null) {
// Slog.w(TAG, "Throwing away out-of-date resources!!!! "
// + r + " " + resDir);
//}
AssetManager assets = new AssetManager();
if (assets.addAssetPath(resDir) == 0) {
return null;
}
//Slog.i(TAG, "Resource: key=" + key + ", display metrics=" + metrics);
DisplayMetrics dm = getDisplayMetricsLocked(displayId);
Configuration config;
boolean isDefaultDisplay = (displayId == Display.DEFAULT_DISPLAY);
final boolean hasOverrideConfig = key.hasOverrideConfiguration();
if (!isDefaultDisplay || hasOverrideConfig) {
config = new Configuration(getConfiguration());
if (!isDefaultDisplay) {
applyNonDefaultDisplayMetricsToConfigurationLocked(dm, config);
}
if (hasOverrideConfig) {
config.updateFrom(key.mOverrideConfiguration);
}
} else {
config = getConfiguration();
}
r = new Resources(assets, dm, config, compatInfo, token);
if (false) {
Slog.i(TAG, "Created app resources " + resDir + " " + r + ": "
+ r.getConfiguration() + " appScale="
+ r.getCompatibilityInfo().applicationScale);
}
synchronized (this) {
WeakReference<Resources> wr = mActiveResources.get(key);
Resources existing = wr != null ? wr.get() : null;
if (existing != null && existing.getAssets().isUpToDate()) {
// Someone else already created the resources while we were
// unlocked; go ahead and use theirs.
r.getAssets().close();
return existing;
}
// XXX need to remove entries when weak references go away
mActiveResources.put(key, new WeakReference<Resources>(r));
return r;
}
}以上代码中，mActiveResources对象内部保存了该应用程序所使用到的所有Resources对象，其类型为Hash<ResourcesKey,WeakReference<Resourcces>>，可以看出这些Resources对象都是以一个弱引用的方式保存，以便在内存紧张时可以释放Resources所占内存。
ResourcesKey的构造需要resDir和compInfo.applicationScale。resdDir变量的含义是资源文件所在路径，实际指的是APK程序所在路径，比如可以是：/data/app/com.haii.android.xxx-1.apk，该apk会对应/data/dalvik-cache目录下的：data@app@com.haii.android.xxx-1.apk@classes.dex文件。
所以，如果一个应用程序没有访问该程序以外的资源，那么mActiveResources变量中就仅有一个Resources对象。这也从侧面说明，mActiveResources内部可能包含多个Resources对象，条件是必须有不同的ResourceKey，也就是必须有不同的resDir，这就意味着一个应用程序可以访问另外的APK文件，并从中读取读取其资源。（PS：其实目前的“换肤”就是采用加载不同的资源apk实现主题切换的）
WeakReference<Resources> wr = mActiveResources.get(key);
r = wr != null ? wr.get() : null;
//if (r != null) Slog.i(TAG, "isUpToDate " + resDir + ": " + r.getAssets().isUpToDate());
if (r != null && r.getAssets().isUpToDate()) {
if (false) {
Slog.w(TAG, "Returning cached resources " + r + " " + resDir
+ ": appScale=" + r.getCompatibilityInfo().applicationScale);
}
return r;
} AssetManager assets = new AssetManager();
if (assets.addAssetPath(resDir) == 0) {
return null;
}
//Slog.i(TAG, "Resource: key=" + key + ", display metrics=" + metrics);
DisplayMetrics dm = getDisplayMetricsLocked(displayId);
Configuration config;
boolean isDefaultDisplay = (displayId == Display.DEFAULT_DISPLAY);
final boolean hasOverrideConfig = key.hasOverrideConfiguration();
if (!isDefaultDisplay || hasOverrideConfig) {
config = new Configuration(getConfiguration());
if (!isDefaultDisplay) {
applyNonDefaultDisplayMetricsToConfigurationLocked(dm, config);
}
if (hasOverrideConfig) {
config.updateFrom(key.mOverrideConfiguration);
}
} else {
config = getConfiguration();
}
r = new Resources(assets, dm, config, compatInfo, token);AssetManager的构造函数如下：
public AssetManager() {
synchronized (this) {
if (DEBUG_REFS) {
mNumRefs = 0;
incRefsLocked(this.hashCode());
}
init();
if (localLOGV) Log.v(TAG, "New asset manager: " + this);
ensureSystemAssets();
}
}static void android_content_AssetManager_init(JNIEnv* env, jobject clazz)
{
AssetManager* am = new AssetManager();
if (am == NULL) {
jniThrowException(env, "java/lang/OutOfMemoryError", "");
return;
}
am->addDefaultAssets();
ALOGV("Created AssetManager %p for Java object %p\n", am, clazz);
env->SetIntField(clazz, gAssetManagerOffsets.mObject, (jint)am);
}看一下addDefaultAssets()
bool AssetManager::addDefaultAssets()
{
const char* root = getenv("ANDROID_ROOT");
LOG_ALWAYS_FATAL_IF(root == NULL, "ANDROID_ROOT not set");
String8 path(root);
path.appendPath(kSystemAssets);
return addAssetPath(path, NULL);
}
获得根目录后，再与kSystemAssets路径进行组合，该变量的定义如下：
static const char* kSystemAssets = "framework/framework-res.apk";所以最终获得的路径文件名称为/system/framework/framework-res.apk，这正式framework对应的资源文件。
分析完了AssetManager的init方法，再来看一下ensureSystemAssets方法。
private static void ensureSystemAssets() {
synchronized (sSync) {
if (sSystem == null) {
AssetManager system = new AssetManager(true);
system.makeStringBlocks(false);
sSystem = system;
}
}
}/*package*/ static AssetManager sSystem = null;根据以上AssetManager构造函数分析可知：
Resources对象内部的AssetManager对象除了包含应用程序本身的资源路径外，还包含了framework的资源路径，这就是为什么应用程序仅使用Resources对象就可以访问应用资源和系统资源的原因。如
Resources res = getResources();
Drawable btnPic = res.getDrawable(android.R.drawable.btn_default_small);那么如何AssetManager如何区分访问的是系统资源还是应用资源呢？当使用getXXX(int id)访问资源时，如果id值小于0x10000000时，AssetManager会认为要访问的是系统资源。因为aapt在对系统资源进行编译时，所有的资源id都被编译为小于该值的一个int值，而当访问应用资源时，id值都大于0x70000000。
创建好了Resources对象后，就把该变量缓存到mActiveResources中，以便以后继续使用。 synchronized (this) {
WeakReference<Resources> wr = mActiveResources.get(key);
Resources existing = wr != null ? wr.get() : null;
if (existing != null && existing.getAssets().isUpToDate()) {
// Someone else already created the resources while we were
// unlocked; go ahead and use theirs.
r.getAssets().close();
return existing;
}
// XXX need to remove entries when weak references go away
mActiveResources.put(key, new WeakReference<Resources>(r));
return r;
}
二、通过PackageManager获取Resources
该方法主要用于访问其他程序中的资源，其典型应用就是切换主题，但这种切换仅限于一个程序内部，而不是整个系统。比如市面上aHome桌面，其工作原理如下图：
PackageManager获得资源的代码如下：
PackageManager pm = mContext.getPackageManager();
pm.getResourcesForApplication("com.android.hiii.client");代码如下：
@Override
public PackageManager getPackageManager() {
if (mPackageManager != null) {
return mPackageManager;
}
IPackageManager pm = ActivityThread.getPackageManager();
if (pm != null) {
// Doesn't matter if we make more than one instance.
return (mPackageManager = new ApplicationPackageManager(this, pm));
}
return null;
}public abstract class PackageManager {通过code可以看出
return (mPackageManager = new ApplicationPackageManager(this, pm)); ApplicationPackageManager(ContextImpl context,
IPackageManager pm) {
mContext = context;
mPM = pm;
} public static IPackageManager getPackageManager() {
if (sPackageManager != null) {
//Slog.v("PackageManager", "returning cur default = " + sPackageManager);
return sPackageManager;
}
IBinder b = ServiceManager.getService("package");
//Slog.v("PackageManager", "default service binder = " + b);
sPackageManager = IPackageManager.Stub.asInterface(b);
//Slog.v("PackageManager", "default service = " + sPackageManager);
return sPackageManager;
}pm获取之后，通过接口getResourcesForApplication获得Resources对象：
@Override public Resources getResourcesForApplication(
String appPackageName) throws NameNotFoundException {
return getResourcesForApplication(
getApplicationInfo(appPackageName, 0));
} @Override public Resources getResourcesForApplication(
ApplicationInfo app) throws NameNotFoundException {
if (app.packageName.equals("system")) {
return mContext.mMainThread.getSystemContext().getResources();
}
Resources r = mContext.mMainThread.getTopLevelResources(
app.uid == Process.myUid() ? app.sourceDir : app.publicSourceDir,
Display.DEFAULT_DISPLAY, null, mContext.mPackageInfo);
if (r != null) {
return r;
}
throw new NameNotFoundException("Unable to open " + app.publicSourceDir);
}if (app.packageName.equals("system")) {
return mContext.mMainThread.getSystemContext().getResources();
}Resources r = mContext.mMainThread.getTopLevelResources(
app.uid == Process.myUid() ? app.sourceDir : app.publicSourceDir,
Display.DEFAULT_DISPLAY, null, mContext.mPackageInfo);
if (r != null) {
return r;
}第二种，是当前应用context 调用getTopLevelResources，含义是如果目标资源程序和当前成的uid是一样的话，就用目标程序的sourceDir作为路径，反之则用目标程序的publicSourceDir目录，该目录可以在目标程序的AndroidManifest.xml中设定。
到了getTopLevelResources就跟之前context中说的一样了，会在mActiveResources中添加一个新创建的Resources对象，这个Resources就是对应目标程序的包名。到这里会发现不但可以获取framework-res.apk中的资源、程序本身的资源，其他程序的资源也是可以获取的。
资源加载和获取请看另一篇博文：《android 系统资源的加载和获取》
扫一扫
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
