Yes, this approach is also good. Besides, I have no problem in letting the
html tags remain in header and footer.
Thanks :)
On Tue, May 21, 2013 at 3:58 AM, Sam Solomon wrote:
> If you are mainly using this for splitting stuff into multiple files, here
> is what we do to accomplish the same thi
If you are mainly using this for splitting stuff into multiple files, here
is what we do to accomplish the same thing but keep it so that templates
always inherit base.html instead of sidebar.html:
base.html:
{% extends 'header.html' %}
{% block main %}
{% endblock main %}
header.html:
{%
Dow,
I am using the chained approach which you suggested ( base -> topbar ->
sidebar -> view1 ). It works perfectly as i wanted :)
Thanks!
On Sun, May 19, 2013 at 10:50 PM, Dow Street wrote:
> Hi. I'm not sure, but we may be using the terms 'parent' and 'child'
> differently (i.e. what you're
Hi. I'm not sure, but we may be using the terms 'parent' and 'child'
differently (i.e. what you're calling a child I'm calling a parent?). I have
only used django template inheritance where a given template file has at most
one {% extends %} tag in it - that is what I am referring to when I sa
4 matches
Mail list logo
