> > Any thoughts on how "bad" the current behaviour is? > > Not sure what you mean - but if you haven't touched anything else, the > current behavior is the default behavior, which should suffice for most > apps.
My point was, you're basically doing the equivalent of browsing a site. But for each click (as you go from an entry to its comments, to an entry), you start a new activity. Now i can imagine that for a browser you'd have an activity per tab, but not per page (as you have one "super"class here, being "page"). This feels more efficient 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. -- 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
