And then it was so:
http://code.djangoproject.com/ticket/14370
On Sep 30, 3:54 pm, "subs...@gmail.com" <subs...@gmail.com> wrote:
> Yeah, I think your right. raw_id_fields is a neat idea if you really
> are reluctant to use AJAX. If introducing AJAX into admin is fine,
> dumping these fields altogether seems the best approach.
>
> As for the options given, I've only used ajax-selects. I think its
> implementation is rather cumbersome in situations where I didn't
> really care about what the resulting list looked like (if I just
> wanted a list of the objects represented by whatever is in their
> __unicode__).
>
> So a starting admin equivalent might look like: ajax_fields =
> {'person': ['first_name','last_name']}. The list in this case is the
> search_fields which kind of mirrors admin's current functionality. Or
> maybe I'm getting ahead of myself.
>
> -Steve
>
> On Sep 30, 2:21 pm, "burc...@gmail.com" <burc...@gmail.com> wrote:
>
>
>
> > On Thu, Sep 30, 2010 at 10:27 PM, subs...@gmail.com <subs...@gmail.com>
> > wrote:
> > > At that point its not really raw_id_fields, is it? =)
>
> > After all, what's the purpose of these fields?
>
> > --
> > Best regards, Yuri V. Baburov, ICQ# 99934676, Skype: yuri.baburov,
> > MSN: bu...@live.com
--
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.
