Yup, If the individual activities would maintain their own activity stack, then it would have been good. I mean, from inside a tab, you launch another activity, and the new activity should be displayed inside the tab, that would have been a better use.
Perhaps, the only one advantage that I can see here is that, if an Activity is being used somewhere else, other than the TabActivity, then you can write a separate Activity and then just include this activity inside a tab whenever you want. Morever, writing code for all the views for the tab inside a single Java file is too complex. Apart from this, there's no reason I can see. Thanks and Regards, Kumar Bibek On Mar 18, 6:30 am, Mark Murphy <[email protected]> wrote: > Biosopher wrote: > > I've been programming in Android for two years now and just joined an > > Android project where they are using a TabActivity to host multiple > > Activities. It's unclear why this is better than rewriting the > > TabActivity to simply use Views instead. > > IMHO, it's not. > > -- > Mark Murphy (a Commons > Guy)http://commonsware.com|http://twitter.com/commonsguy > > Android Training in US: 14-18 June 2010:http://bignerdranch.com -- 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
