On Sat, May 14, 2011 at 4:22 PM, Daniel Roseman <dan...@roseman.org.uk> wrote:
> Which is what Shawn said. If you follow the pattern described in the
> excellent documentation, you'll see that there's no reason to try and
> reference the form's data, as the form will re-render itself anyway if
> validation fails. And there's no reason to have separate templates or views
> for add and edit.
So the fact that form.name.data is set sometimes but not others is not
a bug? Seems like a bug to me. Why is it set at all if accessing it
isn't the preferred way?
So OK, if I do use {{ form.name }} then I have to set CSS attributes
for every field using:
name = forms.CharField( widget=forms.TextInput(attrs={'class':'special'}))
How is that better than just writing a simple <input> field myself?
--
Greg Donald
destiney.com | gregdonald.com
--
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
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
