> To me that would be a nice feature addition. It does, however, bring > into question the fact that a widget, intending to be used on the > public side, would depend on jQuery for its UI. Is Django ready to go > there? Or would an admin-only autocomplete widget be preferred?
The jQuery based ForeignKey widget was part of the adminui refactor and only for this use case discussed. It did have a bunch of side effects that prevented a timely merge before the 1.2 feature freeze, but we should now restart the efforts in my opinion. > Also, at the time, many of the jQuery autocomplete widgets were in a > state of flux or had some warts. Our (Jannis and my) idea at the time > was to write our own from scratch, custom and optimized for Django. > That looks to be about a year ago so the state of things is probably > much different today. (Or not?) At the time we hadn't a good (or 'stable') autocompletion plugin that would fit our needs. Now that the autocomplete feature is part of jQuery UI, maby we should review it again and see if it'd help us. In any case, there is of course the issue of an admin ManyToMany widget that should be dealt with at the same time. Jannis > On Wed, Jun 2, 2010 at 7:13 AM, Sergej dergatsjev eecho > <sergej.dergats...@gmail.com> wrote: >> Current Admin Extensions >> >> ForeignKeyAutocompleteAdmin - ForeignKeyAutocompleteAdmin will enable >> the admin app to show ForeignKey fields with an search input field. >> The search field is rendered by the ForeignKeySearchInput form widget >> and uses jQuery to do configureable autocompletion. >> >> http://code.google.com/p/django-command-extensions/ >> >> >> 2010/6/2 bydesign <jleinewe...@gmail.com>: >>> I second the vote to add the GSoC '09 Admin UI foreign key >>> autocomplete! It's actually somewhat embarrassing that this >>> functionality hasn't made it in yet. Foreign keys in the admin >>> interface become unusable if you have more than 50 or so rows in the >>> table. I hope that since this code has already been written and >>> tested, it can be included very soon! >>> >>> >>> On Jun 1, 9:30 am, Russell Keith-Magee <russ...@keith-magee.com> >>> wrote: >>>> On Thu, May 27, 2010 at 8:26 PM, Philipp Metzler <p...@goli.at> wrote: >>>>> hello, >>>> >>>>> i'm looking for exactely the same solution for an "Ajax foreign key >>>>> filter in the Django admin interface" and hoped it would be integrated >>>>> into the admin interface. I think it should be standard behaviour and >>>>> could be configurable in the admin.py Is the development of the admin >>>>> interface going in that direction or is it not planned at all? >>>> >>>> We're at the start of a development cycle, so the plans for the next >>>> release haven't been finalised yet (beyond the broad guideline that it >>>> will be a feature-light, bugfix heavy release). If this is an area >>>> where you would like to see improvements, feel free to make a specific >>>> proposal (preferably one accompanied by sample code :-) >>>> >>>> Yours, >>>> Russ Magee %-) >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "Django developers" group. >>> To post to this group, send email to django-develop...@googlegroups.com. >>> To unsubscribe from this group, send email to >>> django-developers+unsubscr...@googlegroups.com. >>> For more options, visit this group at >>> http://groups.google.com/group/django-developers?hl=en. >>> >>> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Django developers" group. >> To post to this group, send email to django-develop...@googlegroups.com. >> To unsubscribe from this group, send email to >> django-developers+unsubscr...@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/django-developers?hl=en. >> >> > > > > -- > -Rob > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To post to this group, send email to django-develop...@googlegroups.com. > To unsubscribe from this group, send email to > django-developers+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/django-developers?hl=en. > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
