On 8/14/07, eXt <[EMAIL PROTECTED]> wrote:
>
> On 14 Sie, 03:47, "Russell Keith-Magee" <[EMAIL PROTECTED]>
> wrote:
> (...)
> > What you have described is three different pieces of information that
> > are similar in the trivial case, and one that you don't need to
> > manage.
> >
> > - fields in HTML - where you want to put field X. Only required if you
> > don't like the default rendering of {{ form.as_table }}
> It is also possible and very easy to set up custom form and to write
> custom 'as_my_custom_table' function.
>
> > - fields on a form. Doesn't necessarily correspond 1-1 with model
> > fields (consider password entry - two form fields, one database field
> Exactly.
>
> > - fields in a model.
> >
> > For very simple forms, these three are identical. If you only need
> > simple forms, form_for_model will let you define the model once, and
> > get a default form without respecifying anything. If you have more
> > complex requirements, then you will need to specify those
> > requirements.
> And again it is possible to override default form_from_model
> (from_instance) and made it much more flexible. It is what we did
> here.
>
> > The fourth 'duplicate' - the database - is autogenerated, so doesn't
> > require manual interaction.
> >
> > > Before we shout too much about DRY, newforms _for_model needs a tonne
> > > more flexibility, and syncdb needs migration.
> >
> > And I need a pony. :-)
> LOL
>
> > Instead of throwing around blanket statements about what is broken,
> > how about making some concrete suggestions. Saying newforms "needs a
> > tonne more flexibility" doesn't give any hint as to what you think
> > isn't flexible.
> Right. I agree with sime that newforms are not very flexible at the
> moment, but... sime - your criticism should be much more constructive
> than it is.
>
> Regards
> Jakub Wisniowski
>
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to