Jump to Navigation

Me on Twitter

  • #GooglePlay policy has changed "Ads must not simulate or impersonate system notifications or warnings." Cool ! http://t.co/Pyp1RgSk 11 years 39 weeks ago
  • IOS leads over Android as far as which 1 will win in enterprise marketplace - according to Appcelerator's may report http://t.co/zytDfOEF 11 years 39 weeks ago
  • Cannot simply ignore a file that's already in SVN control. Never bothered looking why. Old tool SVN... http://t.co/dkKO3eiP 11 years 39 weeks ago
  • "Good grammar is credibility, especially on the internet. [...] They are a projection of you in your physical absence." http://t.co/mJv0dUtb 11 years 39 weeks ago
  • @TheBrousse ok. Chapeau bas ! Cc @CedN 11 years 39 weeks ago
  • @TheBrousse au fait on peut savoir ce que fera cette appli ? cc @CedN 11 years 39 weeks ago
  • Tonight's @ParisAndroidUG : apps gain permissions of other apps in the same process 11 years 40 weeks ago
  • @TheBrousse ok. Bon a savoir ! 11 years 40 weeks ago
  • @TheBrousse bien dormi ? :-) c'est fait avec les api android ou titanium ? 11 years 40 weeks ago
  • #AddThis widget in #Firefox3D : #Google+ has a bigger one ;-) http://t.co/3eISv0rv 11 years 40 weeks ago

XML resources

android How to organise XML resources

The first time I read Android developer docs, there was something that was unclear to me : what resource to put in which XML file.

In this article, I will focus on resources in res/values and give some hints about how to name your XML resource files and what kind of resource to put inside.

...

In my case I had only one or two arrays of strings so it was overwhelming to put them in a separate file just because they were of a different type.

Another problem was accessing constant values from both XML layout and Java code. They are constant strings for internal use only, but in order to avoid duplicate declarations I decided to make them available as XML resources. I wanted those resources to be clearly separated from other, 'user visible', resources like GUI labels.

Another thing adding to the fog was the fact that, in derivate files (e.g. strings-fr.xml is derivated from strings.xml), you only want to find values relevant for the given file.
For instance, if you put all values of type 'string' in the same file but only a part of them should be internationalized, you would have a gap between the original and derivated files not only by the translated values but also by the list of values they declare. When coming back to the project after a long time, you might have a hard time remembering why there is this gap.

...

Syndicate content