> If NumberPicker would have been provided in the SDK, then, someone would > have asked for an alphabet picker, or symbol picker, etc, and the list goes > on. Then, someone would have asked for a On-Off button pattern.
Of course, DatePicker already contains a symbol picker, for the month. Having implemented a "picker" widget from scratch on another platform I can tell you that once you've got the basic picker mechanism done adding symbols is easy. And an alphabet picker is even simpler than a symbol picker, it's just that an alphabet picker isn't really practical -- once you get over about 15 choices the interface becomes tedious. (In fact, DatePicker schemes that only implement one "wheel" for day of month are pretty tedious.) IMO, not having a decent numeric picker scheme is a serious flaw and symbolic of the apparent arrogance of the Android developers. On Jan 11, 1:36 am, Kumar Bibek <[email protected]> wrote: > Umm, ok, here I go again. > > If NumberPicker would have been provided in the SDK, then, someone would > have asked for an alphabet picker, or symbol picker, etc, and the list goes > on. Then, someone would have asked for a On-Off button pattern. > > There are several things that could have been possible to provide, like > extra widgets which developers might take advantage of, but then, this would > have made the SDK more bulky. > > Kumar Bibekhttp://techdroid.kbeanie.comhttp://www.kbeanie.com > > On Tue, Jan 11, 2011 at 1:02 PM, mort <[email protected]> wrote: > > On 10 Jan., 22:21, Kumar Bibek <[email protected]> wrote: > > > The reason why a NumberPicker is not public or a part of the SDK is > > > perhaps because it's not a widely used widget. If it were, it would > > > have been a part of the SDK, and the widget would have been public. > > > IMO. > > > I think it's more like the other way around: It's not widely used > > because it's not public. Well, and maybe partly because it's not that > > beautiful and somewhat buggy (esp. if you enter numbers with the > > keyboard). Nontheless, I think you'd see it way more often if it was > > easier to use in own apps, and esp. if there would be support in > > preference views - I for one often would prefer a number picker to > > lists of predefined values or SeekBars, which are terribly imprecise. > > (Dear Android developers: if you'd really do that, please also offer > > min and max values) > > > > There might be other reasons as well, but this seems to be the most > > > obvious reason. Remember, the SDK is for a mobile device. > > > I don't see why this should matter. The NumberPicker already is used > > for date and time pickers since several Android versions on as "weak" > > mobile devices as G1 or Tattoo. And I think even those would also cope > > quite fine with somewhat fancier variations like the digit wheels > > shown in the original post. > > > -- > > 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]<android-developers%[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
