On Thu, Feb 11, 2010 at 11:01 AM, Bob Kerns <[email protected]> wrote: > Yeah, it's a good idea to leave R completely untouched. That includes R > $string, R$drawable, R$id, etc. etc. There are things look at that > those via reflection, so the names matter, and there's no significant > bytecodes to optimize anyway. >
For what it's worth, nothing in the platform cares about the R classes. Those are only generated for the application's convenience; the platform doesn't touch them, and will run happily if they even disappear completely. > But I would definitely NOT say you should avoid obfuscation -- though > you should consider that option. If you use it, you do have to > understand it. But you also have to understand the same issues for > shrinking. You have to enumerate all the "seeds" from which its > analysis needs to start. This includes every class name in > AndroidManifest.xml The aapt tool in an upcoming version of the platform should be able to generate all of the symbols needed from the manifest (and layout files, which can also reference Java class names). -- Dianne Hackborn Android framework engineer [email protected] Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
