A reply by John Shaffer posted on django-developers (didn't realize it
was for "developing django" not "developing with django"):
"We use this in Satchmo:
<form method="post" action=".">
<table>
<tr><td><h4>Discounts</h4></td></tr>
<tr><td><label for="id_discount">Discount code</label></td><td>
{{
form.discount }}</td></tr>
<tr><td></td><td>{% if form.discount.errors %}*** {{
form.discount.errors|join:", " }}{% endif %}</td></tr>
</table>
<input type="submit" value="Confirm"/>
</form>
Does that give you enough control?"
No, that's exactly the type of problem I'm having, with the
{{ form.discount }} shortcut rather than it being an <input/> or
<textarea/> element. The only control that offers me as a designer is
knowing that the id in this case would be "id_discount" as a matter of
convention and that's it - I can't stick a class on it or add any
other attributes, like onFocus or an initial value or all the other
range of stuff I'd be able to monkey with if it was a plain old html
element rather than something auto-generated.
Does using a newform shortcut make things that much easier from a
programmatic standpoint? Or to ask the opposite, is using <input/> and
<textarea/> elements in a template make things that much harder for
things like data validation?
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
