On Fri, 2008-07-04 at 12:20 +0200, Florencio Cano wrote:
> I'm trying to understand Django forms and I have a doubt.
> Imagine that you define a Form class called AddressClass.
> You can instantiate it like this:
>
> address_form = AddressClass()
>
> address_form will be an unbound form object and when you if you show
> it in the template all the fields will be blank.
>
> Now with the same class definition, first you declare a dictionary
> with some values:
> aDict = {'street':'somestreet', 'number':3}
> address_form = AddressClass(aDict)
>
> Now address_form is a bound form object and if you show it in a
> template the street field and the number street will be filled.
> form_from_instance work very similar and this is my doubt!
> If you create the form from an address object:
> an_address = Address.objects.all[0]
> AddressForm = form_from_instance(an_address)
> address_form2 = AddressClass()
>
> address_form2 will be a bound object very similar to address_form?
> Because if you show it in the html now you have some values filled,
> haven't you? What differences will exist between them?
The difference is that data passed to a form's constructor is the data
that was submitted to populate the form (typically, request.POST). It's
user-supplied. The data extracted from the instance in a ModelForm or
form_for_instance() is used as initial data to populate the form fields.
It's not bound data or data submitted by the user, it's purely initial
default stuff. It's the way an unbound form can have initial values for
display.
Regards,
Malcolm
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
