jarkman wrote: > Scratching about looking for ways to use less stack, > and to avoid complicated view structures, doesn't feel very 2009.
Well, bear in mind, you are far closer to doing embedded systems development than desktop or server development when you write for mobile devices. These sorts of hiccups and optimizations are par for the course when working on embedded systems, as I understand it. My hope is that we can collectively work out a set of design guidelines to help avoid stack issues, while we await more stack space, or more efficient use of existing stack space, or something. Cases in point: Romain Guy wrote a couple of blog posts earlier this year about using RelativeLayout instead of nested LinearLayouts and using <merge> to eliminate redundant layouts needed solely to satisfy XML requirements. I link to them in a blog post I wrote up on this topic earlier today: http://androidguys.com/?p=4688 At the time he wrote those posts, my reaction was "meh", because I didn't see the value. Now, of course, the value is much more obvious and immediate. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://twitter.com/commonsguy Android App Developer Books: http://commonsware.com/books.html --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
