Here is an accepted ticket for autocomplete: https://code.djangoproject.com/ticket/14370
The "improved search" seems like what we already have when using raw_id_fields so it seems like it should be easy to include as part of the autocomplete UI. I don't see think it needs to be a separate option. On Tuesday, February 2, 2016 at 10:20:07 PM UTC-5, Cristiano Coelho wrote: > > > <https://lh3.googleusercontent.com/-RY84l0o3Ac0/VrFszlul9uI/AAAAAAAAAGg/0SxzpJ86MLs/s1600/improved_search.PNG> > > > <https://lh3.googleusercontent.com/-5tiY0Xk2bkk/VrFsJtgi8WI/AAAAAAAAAGc/lQmYfhzOUAo/s1600/autocomplete.png> > Hello, > > On one of my projects I'm using django-grappelli to improve the admin site > ( https://github.com/sehmaschine/django-grappelli ) which was used before > the very nice face wash the admin interface received on 1.9. So right now > if I were to update to 1.9, the only thing I would use from this library > would be the autocomplete and improved search features for foreign key > models (includes inlines as well) and some other very minor features since > the 1.9 interface is quite nicer. > > What's Autocomplete like? Basically, rather than a standard dropdown for > foreign keys, you have a textfield where you can search and it then > populate, the library implements it adding an additional required static > method to models so you indicate which fields should be searched through > (however in my opinion that should actually go into the ModelAdmin > definition) and then jqueryui autocomplete and some other javascript plus > required urls for this. I think anyone around knows how an auto complete > works. > > Then for the improved search, which is a second option (you may use one, > both or none), the library adds a small search button next to the dropdown > (or textbox) which will open in a pop up (I actually don't like it being a > pop up at all) which simply contains the actual list page for that model > (the one from the FK dropdown/textbox) having all the advantages of the > features you implemented for that model (ie searching, filtering, sorting, > etc) > I have attached some screenshots of these two to help understand it. > > There are other minor feature that are nice also, like the ability to > collapse inline models, or to use dropdowns for the filtering on the right > rather than displaying all values (which makes it really bad for big > tables). > > So these two features are quite nice, but installing a complete external > library that is made for quite more (pretty much change everything on the > admin page) seems like a bad idea. > *Would it be worth it to have these two features implemented into django?* > > There are also other projects just to add the autocomplete feature which I > haven't used nor tested ( > https://django-autocomplete-light.readthedocs.org/en/master/ and > https://github.com/crucialfelix/django-ajax-selects ) so the feature > looks required. > > > > > > > -- 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/2b592a9e-378e-4f41-9380-d72cf00af47f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
