On Fri, Dec 9, 2011 at 7:28 PM, Richard Schilling <[email protected]> wrote: > I see TabActivity is deprecated. > But there are still some examples in the platform of making Activities > children of TabHost.
Examples don't get updated terribly often. Also, while it is deprecated, it is still available. > This is what we are doing: calling TabHost.addTab and passing in a TabSpec > that contains intents which launch activities. > > Do you think that's a bad idea now that TabActivity is deprecated? Well, honestly, I've thought that was a bad idea since sometime in 2008. Putting Views in tabs is fine, but going the Intent route adds layers to your hierarchy, causing the very sort of problem you are experiencing. As I see it, you have four main courses of action: 1. Stick with your current tab setup, and find other ways to simplify your hierarchy. 2. Switch to putting views in tabs instead of activities in tabs via Intents. 3. Switch away from TabHost entirely, moving to ActionBarSherlock and putting your tabs in the action bar. ActionBarSherlock should offer tab support going back to Android 2.1 or earlier. 4. Switch away from the tab metaphor entirely, using some other navigation pattern. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy _The Busy Coder's Guide to *Advanced* Android Development_ Version 2.2 Available! -- 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
