On 10/10/07, Karen Tracey <[EMAIL PROTECTED]> wrote: > > At 05:10 PM 10/10/2007, Joseph Kocherhans wrote: > >On 10/10/07, Karen Tracey <[EMAIL PROTECTED]> wrote: > > > I'm also curious about something not on the to-do list: something to > > > replace the old radio_admin Field attribute. It seems radio_admin is > > > still allowed on fields, but has no effect on the field's display in > > > newforms-admin. Is the plan to remove radio_admin and provide > > > similar functionality in the new scheme (similar to raw_id_fields > > > maybe?). Or...? (I'm asking because I could take a look at doing > > > whatever the plan is, if you're just needing someone with a little > > > time to spend on doing it. It definitely seems that at a minimum > > > radio_admin ought to be disappearing?) > > > >You're probably right. Something like radio_admin_fields on the > >ModelAdmin class sounds reasonable. Could you file a ticket for this > >so we don't lose track? I don't recall seeing one, but I could be > >wrong. > > I couldn't find one either, so I opened one: > > http://code.djangoproject.com/ticket/5731 > > I'll probably take a look at what's involved in doing it, but given > my unfamiliarity with the code it's quite possible someone else could > whip up a patch sooner.
Here's a hint that will hopefully help you (or anyone else really) get started: this should probably happen in the formfield_for_dbfield method of the ModelAdmin class. Joseph --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
