johannilsson/android-actionbar — comment on commit 48b124725a6364861b5f78fe40a883d345ec7032
File:  line 0
By rfgamaral:

I think I understand what you're saying now...

My mistake was thinking that the behavior you just described, "this technique allows for a single theme body yet still having different platform themes as your base", would also happen the way I was suggesting.

You are sure it won't work the way I suggested though? You tested it or are just assuming because it what makes sense? Cause I agree with you, it makes sense, but in my head, it also makes sense the way I described it. Maybe not as much sense, but it does a little lol...

For instance, let's assume the library has 2 definitions for ```Theme.ActionBar``` on ```values/themes.xml``` and ```values-v11/themes.xml```. On my app, I create a custom theme inheriting from ```Theme.ActionBar```. If I run the app on a API below 11, I'll see my custom theme, no arguing there. But if I run it on Honeycomb (v11), I won't, unless I "remember to make it to the other", correct?

Sorry if I'm being annoying, but are you really sure this is how it will play out? Don't take this the wrong way, it's not like I don't believe you but I'll have to test this for myself...

I mean, when Android goes to look for my custom theme, it will only find one available on ```values/themes.xml```, no matter the Android version. And the parent will be ```Theme.ActionBar```, which will redirect to the library code. On the library code, ```Theme.ActionBar``` will have 2 definitions, one in ```values/themes.xml``` and the other in ```values-v11/themes.xml```. **Isn't Android going to pick the one corresponding the Android version running?** Just because there was no ```v11``` folder on my app, doesn't mean it shouldn't look for one in the library if needed...