On Tue, Apr 26, 2011 at 3:42 PM, Joan Pujol <joanpu...@gmail.com> wrote: > I've read in that message that it was not possible to nest more than one > activity. It's still true?
Yes. > And if it's true what is the recommended workarround? Not doing it. > In my app I've a main TabView and I also need to have a flow inside the tab > child activities. In general, I do not recommend that. I do not even recommend having activities as contents of tabs. TabHost and related classes are being replaced with tabs in the action bar managing fragments. > In the post I read that I can use simply view but if my > program grows I doesn't found it practical. You are welcome to use fragments, with the Android Compatibility Library. You cannot use the action bar except on Android 3.0, at present, unfortunately. You are welcome to not "have a flow inside the tab child activities". For that matter, you are welcome to get rid of the "child activities" and replace them with views. Or, you are welcome to organize your code in other ways. Please bear in mind that object-oriented programming predated Android by decades, and so you are welcome to organize your logic using your own non-View, non-Activity classes if you desire. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy Warescription: Three Android Books, Plus Updates, One Low Price! -- 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
