Hi there! Regarding reusing the admin widget: I would advice highly against it. It made for the admin and requires models to be registered there. It would be better to use django-select2, which is where the autocomplete_fields are originating from.
At the current point I don't see how we could add a more generic widget to Django outside of the admin. This would require ether a manual registration of models as autocomplete light does it, or another approach that doesn't rely on Django cache. The only way I see at the moment, is if Widget.render() would be aware of the request. This way one could use the session as a persistent storage. This is a bigger design decision tho. On Tuesday, September 20, 2016 at 12:51:24 PM UTC+2, guettli wrote: > > I am happy that there will be support for autocomplete in the admin in > 1.11, if this issue/pull-request gets resolved: > > https://code.djangoproject.com/ticket/14370 > > https://github.com/django/django/pull/6385/ > > I looked at the changes of the docs of this pull request. > > It seems that only the contrib module "admin" gets improved. > > Is it planed to add an autocomplete widget in the django forms library? > > > > -- 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 https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/5ffe26b8-11d0-47c9-afab-3d7512adc3e5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
