For one thing, it allows you to alter the behavior depending on the device characteristics.
It also is also easier to script such changes, via XSLT. And it's one way pulling these configurable pieces into a single location. Of course, a dedicated class accomplishes this. It doesn't sound like he's taking advantage of any of these, but it's worth noting the advantages anyway. I've also done it with an XML resource, for things a bit too complicated to describe with simple strings. On Mar 19, 6:52 am, TreKing <treking...@gmail.com> wrote: > On Fri, Mar 19, 2010 at 3:53 AM, HippoMan <hippo.mail...@gmail.com> wrote: > > I want to change the behavior of my app by means of the presense or > > absence of some items in strings.xml. This allows me to control this > > behavior by simply adding or deleting the items, and then clicking the > > Save icon in Eclipse (which automatically rebuilds). This allows me to > > quickly test certain features during development. > > Interesting. Personally, I would just use static constants ... but that's > just me. Good luck. > > --------------------------------------------------------------------------- > ---------------------- > TreKing - Chicago transit tracking app for Android-powered > deviceshttp://sites.google.com/site/rezmobileapps/treking -- 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 To unsubscribe from this group, send email to android-developers+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
