Its only available in Developer version! D.
On Jun 15, 1:24 am, handsome greg <[EMAIL PROTECTED]> wrote: > Oh, looks like maybe I can do this with a custom metaclass for my > model. I'll just use it to tack on custom formfield() methods to my > _meta.fields list for the model. Make sense? > > On Jun 14, 9:35 am, handsome greg <[EMAIL PROTECTED]> wrote: > > > Hi guys, quick question: There's no current way to specify how model > > fields are mapped to form fields for a model with > > newforms.form_for_model is there? I know you can change the formfield > > callback but the model doesn't impact that function in any way by > > default. What I'm looking for is a way for a model to define the form/ > > field relationships so form_for_model will return a custom form class > > for the model without me having to know anything about it. Is this in > > newforms at all? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
