When a model field has help_text, that text will be show in the form.
I'm a little bothered by this because effectively the model is doing
something that really belongs in the view, but I understand the point
is to make it easy to create forms based on a model and I can just
live with it.

What bothers me about this is that it seems pointless to have this
shortcut if the help_text isn't identified in some way when it is
output using as_p()  so that I end up with:

<p><label for="id_username">Username:</label> <input id="id_username"
type="text" name="username" maxlength="30" /> Required. 30 characters
or fewer. Alphanumeric characters only (letters, digits and
underscores).</p>

If I have an error I get:

<ul class="errorlist"><li>This field is required.</li></ul>
<p><label for="id_username">Username:</label> <input id="id_username"
name="username" maxlength="30" type="text"> Required. 30 characters or
fewer. Alphanumeric characters only (letters, digits and
underscores).</p>

where the error is styled in such away that I can draw attention to
it.

I could just go in and hand code my forms in the template so I have
TOTAL control over rendering, it just seems strange I have to go from
drop dead easy as_p() to WET (opposite of DRY) to get my forms out, or
I have to go and overload as_p() in all my forms....

Here is to hoping I'm just stupid and don't see the method behind the
madness


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to [email protected]
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