Brian Beck wrote: > I think your model_field helper being built-in (short for > x._meta.get_field(y).formfield(**params), which is not very pretty) > would be the best solution here. In my experience, customizing just > the widget for a model field is just as common as changing just the > label, just the help text, or just the 'required' status. Using your > helper one could override any number of these, the rest being taken > from the defaults.
May be... I just don't like how it looks. Apart from repeating model name for each field and field's own name twice it is not as readable as a couple of params in Meta that clearly show in what the form is different from default state. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
