On Tue, Nov 23, 2010 at 5:18 PM, Derek <gamesb...@gmail.com> wrote: > In the last Django advent, Zain Memon said: > > "A lot of implemented features missed the cut for Django 1.2, like > drag-and-drop reordering of inlines for models with an ordering field, and > an autocomplete widget for Foreign Key and M2M relations to be used instead > of the select drop-down (or raw_id_fields). Those features (and others) will > most likely land in Django 1.3." > > Is this still the plan? I think autocomplete is one of the features that is > sorely missing from Django (working with lookups numbering in the tens of > thousands is virtually impossible). All of the third party apps have various > quirks and shortcomings - great in some areas and poor in others. An > official, full-featured solution would be ideal.
Plans in an open source project are only as good as somebody willing to implement them. Zain's branch hasn't seen any activity since the 1.2 features landed. There have been some recent discussion about an autocomplete widget (#14370), but looking at the discussion on the ticket, it's still a work in progress. The problem is that we're about a week or so away from the 1.3 feature freeze, so if any of these UI improvements were to be included in 1.3, they would need to be ready pretty soon -- and you need to find a core developer who isn't already booked with other work they want to get into trunk. I can't speak for anyone else on the core team, but as much as I would love to see autocomplete in admin, my plate is fairly full at the moment. Yours, Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
