Jump to Navigation

Me on Twitter

  • @louistouzet @CedN plus de place pour scala. Je suis inscrit pour android ! 11 years 21 weeks ago
  • @louistouzet @twandroid @louistouzet excellent ! De quoi m'inciter a réinstaller #jellybean 11 years 21 weeks ago
  • Just noticed that I've started to drink coffee lately. Wonder why... #Scala 11 years 21 weeks ago
  • #Scala sometimes u just want 2 fix ur code a bit... and u just spend the rest of the evening figuring out how to get back the working code ! 11 years 21 weeks ago
  • RT @Etalab: Encore 1 MOIS pour concourir a #Dataconnexions 2. RDV sur http://t.co/bX6ino3d pour s' inscrire et faire gagner vos applic ... 11 years 22 weeks ago
  • RT @vogella: RT @w1bble The Lance Armstrong bug - when the code never fails a test, but evidence shows it's not behaving as it should. 11 years 22 weeks ago
  • @Viadeo : Un site web à la française http://t.co/AbcWAaQi 11 years 23 weeks ago
  • @agoncal spéciale dédicace à @IBM @IBM_AppServer #websphere 11 years 24 weeks ago
  • @rovio @badpiggies is a game that calls for sharing fun moments! It deserves in-game screenshot & video capture facilities... 11 years 24 weeks ago
  • Like crashing or not crashing... 11 years 24 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