khose wrote: > Any idea?? Frankly, I have yet to see a good reason to use Intents to populate tabs, particularly since you are limited to your own activities.
If this were my code, I would: 1. Move the UI logic for each of the activities to be put into tabs into custom View classes rather than activity classes. 2. For those where I need the UI logic to appear both in a tab and in a standalone activity, create a trivial activity wrapper around the view. 3. Use the custom View classes from step #1 in the TabActivity instead of Intents. 4. Put the option menus in the TabActivity. But, hey, that's just me. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://twitter.com/commonsguy Android App Developer Training: http://commonsware.com/training.html --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
