Thanks for the followup reply, Carl.
Yes, I think I was a bit confused regarding "for". Sounds fine.
Your points about scope creep and keeping the proposal as achievable as
possible is also noted.
If we're going to keep things simple, why are we introducing the idea of
inline "using" templates?
You go a long way of convincing me that the confusion introduced by
'extends' isn't worth it.
You're right, my example suited a separate template file just fine. But do I
really need to create a new template file for all specific cases? It seems
like the following templates would be much better to just be kept inline
with the main template the form is being used in.
"forms/p-custom-help-text-for-displayname.html"
{% extends "forms/p.html" %}
{% block config %}
{% formconfig field using "checkbox-custom-help-text-for-displayname.html" for
form.display_name %}
{% endblock %}
"forms/fields/checkbox-custom-help-text-for-displayname.html"
{% extends "forms/fields/checkbox.html" %}
{% block label %}Show posts by me as from <em>{{ user.username }}</em>
rather than <em>{{ user.get_full_name }}</em>{% endblock %}
Perhaps I'm not quite getting how we'd do this kind of thing with the
current proposal.
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/django-developers/-/6mJiTF2HwK0J.
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.
