There is no particular reason why Google needs to write this. Anybody can write this and make it a reusable component. A knee-jerk reaction of "if it's lime green, Google must write it" is a sad statement.
On Wed, Oct 20, 2010 at 8:26 AM, Richard Leggett <[email protected]> wrote: > I've opened a feature request related to this: > > http://code.google.com/p/android/issues/detail?id=12007 > > Again I completely appreciate ListView was designed for efficient scrolling > through large amounts of data and not for what I need, but we do not yet have > a good alternative for short (static) lists inside ScrollView that also lets > us make use of Adapters, selectors, dividers and input device handling, > without having to re-implement all of these things ourselves. > > Example layout: > > ScrollView > Logo > Top 5 items list > Save button > Edit Button > Delete Button > Footer > > Assume the total height of these controls exceed the dimensions of the > screen, and so require scrolling. If I use ListView for the list (as I want > the user to be able to do ListView-like things). Using > addHeaderView/addFooterView() is not an option here as the background must > scroll for the design work. > > Regards, > Richard > > > > On 20 Oct 2010, at 10:40, Richard Leggett wrote: > >> Hi Mark, >> >> Thanks for your advice. I'd really like to do that as I know that will >> simplify things, unfortunately the scrolling nature of the background behind >> the 3 UI widgets is integral to the design (a port of an iPhone app, that >> had the same challenge as it turns out). >> >> Looks like for now I'll have to go one of two routes... >> >> 1. Extend ListView to implement background scrolling and use >> addHeader/FooterView(). >> 2. Extend LinearLayout to work with a ListAdapter (as this UI strategy is >> used in several Activities) >> >> Many thanks again, >> Richard >> >> >> On 19 Oct 2010, at 19:11, Mark Murphy wrote: >> >>> On Tue, Oct 19, 2010 at 11:00 AM, Richard Leggett >>> <[email protected]> wrote: >>>> I'm keen to see if anyone has a better solution to this problem? >>> >>> Get rid of the background. You are taking on a fairly substantial >>> maintenance headache for the sake of a background image. >>> >>> -- >>> Mark Murphy (a Commons Guy) >>> http://commonsware.com | http://github.com/commonsguy >>> http://commonsware.com/blog | http://twitter.com/commonsguy >>> >>> Android App Developer Books: http://commonsware.com/books >>> >>> -- >>> 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 >> > > -- > 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 > -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy _Android Programming Tutorials_ Version 3.0.1 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 at http://groups.google.com/group/android-developers?hl=en
