On Sat, 2007-04-21 at 23:55 -0700, ~Kender wrote: > Along this same line, there's another issue with the RadioSelect > widget.. It makes use of a rendering (returned by the render method) > but the class is hardcoded in the method, so there's no way to supply > an alternative renderer except to subclass both classes (the renderer, > and the RadioSelect widget). Being able to supply a new rendering > object would allow easier customization of the appearance of the > RadioSelect widget. Then it's just a matter of subclassing > RadioFieldRenderer and overriding the __unicode__ method.
Please open a ticket in Trac for things like this. Bug reports and enhancement requests on the mailing list are very easy to forget about. Items in Trac don't get lost. Thanks, Malcolm --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
