I think it's in the other thread, but what's the reason for wanting to
decouple forms from templates? I can think of 2 reasons:
1) Decoupling means you can change the way templates work and not have
to update the forms code. Counter argument: If you change the way
templates work you'd break a lot more than forms so this will likely be
a non-BC thing to do anyway. In and of itself, this isn't a great
argument against keeping things decoupled.
2) Allow the form widgets to be used outside of Django. If this is the
case, could it be that Django defaults to importing django.templates.
If that errors out, use standard Python Template Strings as a fall
back?
Another question. What would it look like if form HTML output type was
a config setting?
DEFAULT_HTML_DOCTYPE = "HTML4"
Then Django supports the common ones: XHTML and HTML4 (and others when
they come along). It's extra code for every HTML type but it keeps
things decoupled.
This still doesn't accomplish letting designers design forms by
changing templates, which I think is a good argument for widget
templates.
-Rob
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django developers" 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-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
