#7028 Pledge not to deprecate raw_id_fields

[mrts]

Tim Graham writes in https://code.djangoproject.com/ticket/7028:

I think it doesn't make sense to add this enhancement while also adding a new autocomplete widget (#14370). After the autocomplete widget is added, we might deprecate raw_id_fields in some later release.

Adding autocomplete support is great news, but I'm unsure whether this fully covers the flexibility that the magnifying glass + related object lookup popup provides. The good thing about the popup is that you can use all the power of Django admin, not only search - filtering, sorting, date filters, limiting the related object queryset by user rights, adding new objects etc.

Regarding the latter, is it planned to support adding new objects in the autocomplete implementation?

Here's a 3-minute video that demonstrates how the patch provided in #7028 can bring additional usability, power and flexibility to raw_id_fields:

http://www.vimeo.com/9322083

This has been in use in an actual project for years with great success and it also works for less-experienced users.

Thus, I propose not to deprecate raw_id_fields (unless autocomplete provides equivalently powerful functionality).

Also, I propose to re-consider #7028 if raw_id_fields are not deprecated. Besides the points above, there are numerous 'this looks really good' comments in the ticket.

Please feel free to disagree :).

Best regards,

Mart

[Aymeric Augustin]

Hello,

This is the first time I hear about the idea to deprecate raw_id_fields. Given how long it’s been the only workaround for Django’s lack of a built-in autocomplete, I’d rather exercise caution here. Also I’m pretty sure there are use cases where raw_id_fields are a better way to select a related element than an autocomplete.

I see that the discussion on the ticket is very long. Perhaps there are other reasons why this feature isn’t desirable (e.g. no obvious and robust way to implement it). However I’m not convinced by the current motivation.

Best regards,

-- 

Aymeric.

--
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-develop...@googlegroups.com.
To post to this group, send email to django-d...@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/062f49f6-afae-48f9-a34d-1cecd5f748f0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Florian Apolloner]

On Sunday, November 27, 2016 at 5:42:10 PM UTC+1, mrts wrote:

Regarding the latter, is it planned to support adding new objects in the autocomplete implementation?

It does support that like it is now (ie with a plus icon next to the input)