> > For *my* (completely unilateral) point of view, this is very important and > I'd love to have a place to just flip a switch and change them all; well, > I'd even prefer for it to be the default behavior, but I know selects look > cool too. >
How many projects do you need this on? I think the example snippet is good enough for most cases, you could always wrap it up and put it on PyPI if you find yourself doing it across many projects (and maybe there's other stuff you do too) On Sat, 19 Jan 2019 at 10:48, Santiago Basulto <santiago.basu...@gmail.com> wrote: > Haha, sorry, got overly excited. What's the usual process to make these > sort of decisions in these cases? Should we ask the users list? > > The setting proposal is purely from my perspective as a user. For *my* > (completely unilateral) point of view, this is very important and I'd love > to have a place to just flip a switch and change them all; well, I'd even > prefer for it to be the default behavior, but I know selects look cool too. > > Now, from a "development" perspective, I do understand that it might be a > big change. > > On Saturday, January 19, 2019 at 4:57:21 AM UTC-3, Carlton Gibson wrote: >> >> >> >> On 18 Jan 2019, at 17:20, Santiago Basulto <santiago...@gmail.com> wrote: >> >> Seems like everybody agrees that for large sites, it's necessary. >> >> >> Hang on, slow down. 🙂 >> >> Personally, I’m not sure it’s too onerous as-is. I’ve not yet seen >> exactly why subclassing ModelAdmin in one’s project isn’t good enough. It >> really depends on with the “it” is “it’s necessary” is taken to mean… >> >> - Better examples in docs: Great, no problem. >> - **More** API on ModelAdmin: OK, maybe, but what does that look like >> exactly? >> - A setting: Really? Do we have to? Can we explore other options first? >> >> Both the docs and adjustments to ModelAdmin options could be pushed >> forward with a PR. “Better handling of FK widgets for fields with large >> counts” — sounds great, but what does that involve? >> >> Kind Regards, >> >> Carlton >> >> -- > You received this message because you are subscribed to the Google Groups > "Django developers (Contributions to Django itself)" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-developers+unsubscr...@googlegroups.com. > To post to this group, send email to django-developers@googlegroups.com. > Visit this group at https://groups.google.com/group/django-developers. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/e18c8811-35ae-4607-b9bb-7bb826e8389c%40googlegroups.com > <https://groups.google.com/d/msgid/django-developers/e18c8811-35ae-4607-b9bb-7bb826e8389c%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- Adam -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAMyDDM2Gg%3DQPo6mNksDDnTD%3DkO-DyByaVWwBmTwBnPEGRQkasA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
