Il 24/02/2015 20:12, Marc Tamlyn ha scritto:
I would suggest that a good modal implementation for these should still support "open in new tab/window" properly, with control/command click not detected by the overriding JavaScript. It may be possible to do this and keep the popup functionality passing the new id back to the parent window.
uhm, that should be doable [snip]
There are definitely better ways to deal with raw_id_fields than the popup window in my opinion - utilising something like select2 with ajax loading and a hook on the ModelAdmin would be ideal.
Yeah, reusing existing libraries in the admin would be really nice
In any case, it is fairly trivial to add options like this to the modeladmin and make them opt in if that is desired.
Overall, I'm probably -0 on morals, but +1 on supporting an optional alternative way to handle add buttons on related objects.
-0 on morals sounds good :) So i think it'll be better to keep the windows and focus on making experimentation with this widget possible for downstream users.
Thanks to everyone that partecipated in the discussion. -- Riccardo Magliocchetti Software Tinkerer @rmistaken http://menodizero.it -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/54ECF0F1.1070301%40gmail.com. For more options, visit https://groups.google.com/d/optout.
