On Tue, May 11, 2010 at 1:31 AM, EnnaN <[email protected]> wrote: > It is in this case easiest to make a separate activity for each type of > page, but this means that while 'browsing' you're making a new activity for > each click and that feels a bit redundant, expensive or.. well, something > like that? I was wondering if it would be wise to make an effort to keep > both pages in the same activity. >
If you're dealing with actual links and web pages, then yeah, it makes more sense to have a WebView or something where only the current page changes and not create a new activity. If you're using buttons or something else and building a "standalone" app that pulls in data, then rethink having a button on the details page of comment that takes you back to other entries. Or, again, playing with the flags that you use to launch the activities (like using singleTask) will force them to be re-used instead of creating new ones. That also involves more work in handling the update intent information, so it's up to you which you prefer. ------------------------------------------------------------------------------------------------- TreKing - Chicago transit tracking app for Android-powered devices http://sites.google.com/site/rezmobileapps/treking -- 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
