Actually, you can't have it both ways *AT THE SAME TIME*. Having platform-defined strings only make sense for platform-defined things. Like platform-defined widgets, where you can have platform- defined constants for the platform-defined default values. The roles have to be tightly defined to have any benefit.
Or platform-defined names for platform-defined things, like the audio streams, or other hardware bits and pieces, like "camera", "headphone", etc. Maybe a few key concepts, like "Account", referring specifically to the account manager concept. If Android phones had important buttons with text labels, you'd want to capture that label as a resource, and localize that to the hardware! All the rest -- you manage yourself. On Jan 22, 2:34 pm, Brill Pappin <[email protected]> wrote: > There is that problem Bob, but you can't have it both ways. > Ether you depend on standards and consistency from the platform itself or > you manage it yourself. > Most advice regarding resources are to manage them yourself (your argument > applies to images as well as strings). so that your not surprised > when something changes or goes missing. > > I think there is legitimacy to both ideologies. > For the moment I don't have a lot of confidence in the ability of Goole not > to keep the platform from fragmenting even further, so I'm going to do with > the locale resource model. > > It's somewhat mute anyway, because most of those already translated string > resources are hidden from the public API. Ther is no choice but to extract > them. > > - Brill Pappin -- 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
