Such an approach would be very inefficient for several reasons. First of all it requires to inflate many resources that won't be needed right away, which will slow down your application startup time. It will also increase memory usage. Then you will defeat the history mechanism built in Android, thus forcing you to implement the back yourself, and everything it entails. It's a lot more work for you, and you will probably end up having a user experience that feels like other Android apps but not quite.
What performance issue are you trying to solve? On Tue, Dec 16, 2008 at 6:01 PM, Mark <[email protected]> wrote: > > Would there be an advantage of using multiple Activity classes each > with their own primary layout as opposed to creating multiple layout > views and stacking them into FrameLayout? One of the things I > currently do in my WM development that has worked very well in terms > of performance is to create multiple layers for a form and then show > or hide the layers based on what the user is doing. I could see using > the FrameLayout class to stack multiple other layouts that would > provide the same capabilities. This would allow me to use a single > Activity to wrap what I need rather than creating multiple Activities. > > thanks, > Mark > > > -- Romain Guy Android framework engineer [email protected] Note: please don't send private questions to me, as I don't have time to provide private support. All such questions should be posted on public forums, where I and others can see and answer them --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
