On Sat, Apr 25, 2009 at 9:57 AM, Al Sutton <[email protected]> wrote: > > Dianne has already pointed out that even the guys at Google consider it a > less than optimal, lets hope a 1.6 or whatever brings some improvements.
To be clear, the main improvement I expect is a very clear delineation of the maximum stack depth, that will be consistently reported to developers and enforced in the SDK, which the framework will guarantee to support. View hierarchies of the depth we are talking about are just too inefficient to manage on G1 class of hardware; it is something people should just be avoiding. I do think we should look at what we can do in the platform about the situation where an activity is embedded inside of another activity to reduce the amount of nesting the system imposes there, but I don't know how much can/will be done. -- Dianne Hackborn Android framework engineer [email protected] Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. 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 -~----------~----~----~----~------~----~------~--~---
