Add documentation about hack in commit: f8ea750455 [DO NOT MERGE]

Change-Id: I9ce871a67fb67e02e0c4df1eb5c3261ea52a914b
(cherry picked from commit 6330971ed2)
This commit is contained in:
Deepanshu Gupta
2015-05-21 11:47:36 -07:00
parent b318ff54fc
commit c96ef95285

View File

@@ -464,6 +464,20 @@ public final class BridgeContext extends Context {
@Override @Override
public ClassLoader getClassLoader() { public ClassLoader getClassLoader() {
// The documentation for this method states that it should return a class loader one can
// use to retrieve classes in this package. However, when called by LayoutInflater, we do
// not want the class loader to return app's custom views.
// This is so that the IDE can instantiate the custom views and also generate proper error
// messages in case of failure. This also enables the IDE to fallback to MockView in case
// there's an exception thrown when trying to inflate the custom view.
// To work around this issue, LayoutInflater is modified via LayoutLib Create tool to
// replace invocations of this method to a new method: getFrameworkClassLoader(). Also,
// the method is injected into Context. The implementation of getFrameworkClassLoader() is:
// "return getClass().getClassLoader();". This means that when LayoutInflater asks for
// the context ClassLoader, it gets only LayoutLib's ClassLoader which doesn't have
// access to the apps's custom views.
// This method can now return the right ClassLoader, which CustomViews can use to do the
// right thing.
if (mClassLoader == null) { if (mClassLoader == null) {
mClassLoader = new ClassLoader(getClass().getClassLoader()) { mClassLoader = new ClassLoader(getClass().getClassLoader()) {
@Override @Override