On Mon, May 5, 2008 at 2:46 AM, Michael Irani <[EMAIL PROTECTED]> wrote:
> > Hello, > I'm trying to manipulate the rendering for RadioSelect so that the > form element shows up within my form differently than a <UL>. So far > I've come across two options... Use straight form tags in my view, or > to rework RadioFieldRenderer and RadioInput from widgets.py locally so > that I can have a custom renderer. And then use that custom renderer > as the renderer for RadioSelect > > I was wondering if there was a way to bipass these options and just > get at the independant radio buttons that make up the RadioSelect. > Meaning to be able to get all the 2-tuple key-value pairs that makeup > the RadioSelect widget. > RadioSelect allows for you to provide a custom rendering object. See: http://code.djangoproject.com/ticket/4228 Does that not let you do what you want without changing your Django source locally? Karen --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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-users?hl=en -~----------~----~----~----~------~----~------~--~---
