On Fri, Mar 20, 2009 at 5:42 AM, Mariano Kamp <mariano.k...@gmail.com>wrote:
> Yes, it is huge, complex and contains a WebView component. I attached two > pngs to show you that. The one ending in graph is the hierarchy graph as > exported by the hierarchyviewer tool. The one ending in grid is the view you > get when you click on the grid icon in the hierarchy viewer. It shows the > hierarchy as a tree and also show what the screen looks like. It is not > totally completer though as it doesn't show the navigation and zoom > controls. I can't view the picture you attached but "huge" and "complex" are at least bad signs. :) You should never -need- to have a huge and complex view hierarchy, and this is one of the first things you will fix because it impacts performance all over the place. A couple things you can do: - If you have things that aren't always shown, don't include them in the default view hierarchy. Inflate and show them as needed, possibly removing other things that are no longer shown. - If you are using complicated hierarchies of layout managers, consider just writing your own layout manager that does the placement you want. This can tremendously improve performance. -- Dianne Hackborn Android framework engineer hack...@android.com 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 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 -~----------~----~----~----~------~----~------~--~---
