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

Because the actual public theme is only specified in one place rather then
in both files as it is now. If you make a change to one you have to
remember to make it to the other which isn't very DRY. This technique
allows for a single theme body yet still having different platform themes
as your base.
On Jan 10, 2012 5:22 PM, "Ricardo Amaral" <
reply@reply.github.com>
wrote:

> In your example they also have different parents, the difference is that
> you're talking about ```Theme.ActionBar.InternalBase``` instead of
> ```Theme.ActionBar```. But why do that? Why create
> ```Theme.ActionBar.InternalBase``` and then a "new theme" and inherit from
> that ```InternalBase```? What's the purpose of that?
>
> My point is, the InternalBase is redundant. I can't see the benefit in
> that and that's what I'm trying to understand...
>
> ---
> Reply to this email directly or view it on GitHub:
>
> https://github.com/johannilsson/android-actionbar/commit/48b124725a6364861b5f78fe40a883d345ec7032#commitcomment-855006
>