Just playing with optimization after watching this video: http://www.youtube.com/watch?v=UApv-ZMJ51g
(play at about 44:00) He talks about using merge because nested views/layouts are much more expensive than, say, using wider hierarchies. On Apr 17, 3:58 pm, Mark Murphy <[email protected]> wrote: > westmeadboy wrote: > > Yeah, I was wondering whether the Adapter (or whatever) internally > > creates some container to put the item layout into. > > Nope. > > > While using the merge-via-include approach may be useful to some, it > > doesn't help in my particular situation because that RelativeLayout is > > exactly the sort of thing I'm trying to eliminate :( > > Why are you trying to eliminate it? > > -- > Mark Murphy (a Commons > Guy)http://commonsware.com|http://twitter.com/commonsguy > > _Beginning Android 2_ from Apress Now Available! > > -- > 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 > athttp://groups.google.com/group/android-developers?hl=en -- 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
