Name your string array resources appropriately. Define a string array with an item for each string used by your application. String array resources are best stored in the /res/values/arrays.xml file. Instead, your best bet is to create a string array resource that references the individual string resources you’ve already created, tying them together. Sure, you could load them all up individually in the Java code and make a String array in memory, but you would need to know each of the resource’s full id names and reference it in the code. Now let’s say you wanted to create an array of those character race strings. Step 3: Define String Array Resources Using String Resource References No special code is needed for this to work. The handy thing about loading resources this way is that if you’ve provided alternative resources in different languages, the appropriate language version of the string will be loaded based upon the device settings at runtime. The following code can be dropped into your Activity class to load a String resource defined in your application: String sOrc = getResources().getString(R.string.race_orc) You can easily load a string to use in your code using the getString() method of the Resources class. Step 2: Load Your String Resources Programmatically For example, they might be used together an array or displayed as options in a Spinner control. This helps remind team members that these strings may be related somehow. Note the “race_” prefix of each string resource. For example, the following XML excerpt defines a number of game character race types as individual strings: Name your string resources appropriately. Define a string resource entry for each string used by your application. String resources belong in the /res/values/strings.xml file. Step 1: Define String Resources for Individual Strings So let’s talk about how to add strings and more importantly, string array resources to your applications effectively. Strings don’t clutter up your application code, leaving it clear and easy to maintain.Strings can be internationalized easily, allowing your application to support multiple languages with a single application package file (APK).Therefore, it will have consistent spelling, case and punctuation.
There are a number of benefits to including string content as a resource, such as: Sure, there are occasionally good reasons to do this, especially when writing debug code, but generally speaking, if your Android application relies on string content that is displayed on the screen, this data belongs in the Android resources, not in the code itself. One poor coding practice that really gets our blood boiling is when developers include raw string content inline in code.
0 kommentar(er)
