On Wed, May 11, 2011 at 1:08 PM, Cory Kaufman <[email protected]>wrote:
> It's worked out well for me to create a base class that extends Activity > that all of my other activities extend, so I have a central > place to put common functionality. > What happens when you need a MapActivity? Or ListActivity? Or ExpandableListActivity? Or ... ? > When should strings be listed in values/strings.xml and when should they > be hard coded? > Does it need to be localized? Yes -> strings.xml. No? -> Hard code or (preferably) some configuration file. > What kind of conventions should be used when giving views ids? > Whatever makes sense to you. I go with tv_name for TextViews, rb_name for Radio Buttons, etc, etc. Makes them easy to find by what type you're looking for. > Should there not be views in different layouts with the same name? > Not if you're using those layouts together within the same parent(s). Then you might run into issues. ------------------------------------------------------------------------------------------------- TreKing <http://sites.google.com/site/rezmobileapps/treking> - Chicago transit tracking app for Android-powered devices -- 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
