> Of course there are extra complications. For instance, you can't then > refer to string IDs in standard XML layouts item like TextView and > Button. I guess you could define MyTextView and use your internal > lookup in the derived class. And you have to replace e.g. all > getString() etc calls in a service/activity with something like > MyRes.getString( this ).
> Or you can go for a mixed approach where only stuff that doesn't > appear in layouts is offloaded. Fortunately, in my case the strings referred to in layouts make up less than 10% of the full resource texts. So I will do a mixed approach like you suggest. Assuming I don't die of boredom splitting the resource files. What a pain... -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
