Carl Meyer skrev 2013-05-17 5:03 PM:
Hi Emil,
On May 16, 2013, at 5:21 PM, Emil Stenström <e...@kth.se> wrote:
Any feedback on how I was thinking? Does it make sense?
Based on the feedback so far I gather that changing the block tag
is a bad idea. I'd love to continue working on this, because I've
felt this need in lots of different projects. A new proposal could
be in terms of a new pair of tags, maybe "layout" and "content".
But before going further I would love some thoughts on the area,
and if you think it's a worthwhile problem to solve.
My feeling is that the existing tools are adequate, using wrapper
blocks as I outlined earlier in the thread, so I don't see this as a
problem that needs solving in the core template language.
I agree that a wrapper is an OK workaround, but I think it feels ugly, a
little bit like adding a wrapper div to do something in CSS.
If you're thinking of using new tag names anyway, you could certainly
experiment with options in a third-party project and bring it back
for consideration in the future if it's demonstrated usefulness and
wide use.
Agreed. Since changing the block tag is probably out of question I'll
play with this as an external package instead.
Thanks for listening in giving me feedback!
/Emil
--
You received this message because you are subscribed to the Google Groups "Django
developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
