To run aapt2 link we need to provide an AndroidManifest.xml, but a basic and mostly empty manifest seems to be good enough: Īnd while we could run the link command now, it still wouldn’t work. But we still need to package this once more for consumption, but here’s where it gets a little tricky. This will produce compiled/values_ which contains our data. (Note: You can download aapt2 from its documentation page)Īapt2 compile res/values/override.xml -o compiled/ Note that aapt2 requires the path to be the same as it would be in your android directory, so for me I put the overrides in overrides/res/values/override.xml which I then compiled. Then we need to create the same colors for our resource override file. I used some dim, gray colors where I’d notice any change to something more colorful immediately. To test this, I created a very basic app with a theme that uses some primary, primary dark, and accent color with the colors defined in some res/values/colors.xml like we’re used to. We can tell Android to load a separate file which will override any existing resources, so we could for example change our colorPrimary and marvel at how all buttons, colors, etc will just work as if we had switched the color at compile time. You can achieve dynamically colored themes with some libraries that will either use their own View implementations or some amount of workarounds to get it working good enough but not completely.Īndroid 11 added the option to include your own Resource Loaders and with that we finally have a way to dynamically alter our apps themes dynamically.
You can override some values, but you always need to know those colors at compile time and create more themes or theme overlays. Android Theming works great once you really get into it, but one of the biggest limitations is that you can’t modify those themes at runtime.
0 kommentar(er)
