On Oct 16, 2:09 am, Andrew Godwin <and...@aeracode.org> wrote:
> So, from what I can work out, this is a proposal for an {% extends %}
> tag which allows you to extend from the parent template of the same nameJust to chime in, I like this proposal. IMO: If a designer wants to override a third party's template (by altering blocks), they should not have to: 1. copy paste the template 2. touch python code Admin's solution is only works when presented with foreknown hierarchical data. The solution of apps needing to provide a way to override default templates (usually via a view argument) is a cumbersome requirement app developers and requires (2). http://code.djangoproject.com/wiki/ExtendingTemplates doesn't really work for third party apps that well. One downer is that this makes the behaviour of templates with self- extending tags dependent on the order on which the templates are loaded. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
