Re: FK Autocomplete Widget [GSoC '09 Admin UI Improvements]

I agree the jquery ui widget is the rift way to go IMO! On Jun 2, 1:57 pm, Thomas Schreiber wrote: > +1 for JqueryUI, it has come a long way in the last year, and it now has a > nice system for subclassing widgets with the widget >

Re: FK Autocomplete Widget [GSoC '09 Admin UI Improvements]

+1 for JqueryUI, it has come a long way in the last year, and it now has a nice system for subclassing widgets with the widget factory. http://bililite.com/blog/extending-jquery-ui-widgets/ -Thomas On Wed, Jun 2, 2010 at 18:45, Jannis Leidel wrote: > > To me that would be a

Re: FK Autocomplete Widget [GSoC '09 Admin UI Improvements]

> 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

Re: FK Autocomplete Widget [GSoC '09 Admin UI Improvements]

On Wed, Jun 2, 2010 at 11:20 AM, Rob Hudson wrote: > 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

Re: FK Autocomplete Widget [GSoC '09 Admin UI Improvements]

If I recall correctly, there's another branch on the that project that was refactoring the autocomplete widgets so that there were essentially 2 widgets: A widget intended to be used in your own Django code, and an admin widget that was a subclass for use in the admin. To me that would be a nice

Re: FK Autocomplete Widget [GSoC '09 Admin UI Improvements]

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.

Re: FK Autocomplete Widget [GSoC '09 Admin UI Improvements]

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

Re: FK Autocomplete Widget [GSoC '09 Admin UI Improvements]

On Thu, May 27, 2010 at 8:26 PM, Philipp Metzler 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 >

Re: FK Autocomplete Widget [GSoC '09 Admin UI Improvements]

Hi Margie, Not that much hacky. http://code.djangoproject.com/wiki/CookBookThreadlocalsAndUser Store request, user and ModelAdmin dynamic stuff in local storage and you are happy. On Thu, May 28, 2009 at 5:06 AM, Margie wrote: > > Yuri, Thanks for suggesting thread

Re: FK Autocomplete Widget [GSoC '09 Admin UI Improvements]

Yuri, Thanks for suggesting thread local. I didn't know about that. In the end, a think a concise description of my problem is that when I create my own widget for use in the admin change list, it seems that I am unable to identify the instance for which this widget is being rendered. Thus, I

Re: FK Autocomplete Widget [GSoC '09 Admin UI Improvements]

My usual workaround to this is to store object, request and action ("add", "change", "changelist") in thread local storage when add_view, changelist_view or change_view are called, and use it later. I will be happy if a ModelAdmin instance was created for each request, then I'll able to use it

Re: FK Autocomplete Widget [GSoC '09 Admin UI Improvements]

Yes, I like the idea of a callback that can be overridden. Alex - are you saying this is an ajax solution or a solution that takes place at formset creation time? Also, in the rendered output for a field, think it would be nice for non-editable fields to have ids associated with them the same

Re: FK Autocomplete Widget [GSoC '09 Admin UI Improvements]

That is definitely a very interesting and useful example, appreciate you posting it. I just took a quick look at the source for class ModelAdmin and it seems to me that the get_changelist_formset() and get_changelist_form() methods do not have the obj argument, so I don't see how to do the same

Re: FK Autocomplete Widget [GSoC '09 Admin UI Improvements]

On Tue, May 26, 2009 at 7:05 PM, Ulrich Petri wrote: > > > > > I don't know - maybe my needs are unusual. It's definitely not your > > standard blog app ... so if I am too much on the outskirts for this to > > be something that we consider in the development community, I can > >

Re: FK Autocomplete Widget [GSoC '09 Admin UI Improvements]

> > I don't know - maybe my needs are unusual. It's definitely not your > standard blog app ... so if I am too much on the outskirts for this to > be something that we consider in the development community, I can > understand that. But it seems to me that having a dynamic (ie, object > based)

Re: FK Autocomplete Widget [GSoC '09 Admin UI Improvements]

Hey guys, Yes, I must say, in any advanced form there are fields that depends one from another. Country/Region/City, Project/Issue, Project/Owner, User/Account, Group/User... when two selects appear, there's not zero probability they will depend on each other. Also often a checkbox can

Re: FK Autocomplete Widget [GSoC '09 Admin UI Improvements]

Yes, I use that. Inside my formfield_for_foreignkey() method I instantiate my special widget. My widget contains a render() method that generates javascript that makes an ajax request that requests the options for the select. There is no way to prune down the selections with

Re: FK Autocomplete Widget [GSoC '09 Admin UI Improvements]

Not entirely sure if this is what you were referring to, Margie, but you can limit a the queryset used for an admin dropdown (FK). Code for this looks something like: # defined in the ModelAdmin for this class. def formfield_for_foreignkey(self, db_field, request=None, **kwargs):

Re: FK Autocomplete Widget [GSoC '09 Admin UI Improvements]

I think that foreign key selection in the admin interface is a great area to be putting cycles into. I've played around with Jannis Leidel's foreign key autocomlete widget and am familiar with that, I think you are modeling your stuff after that, is that right? While I think that is a cool