Ah, I see - thanks Karen - your explanation clarifies/(puts to rest) a
number of points I had in my head when experimenting with the
templates! Reading it again now, I think the thing with super, could
do with being explained a bit differently (putting a for loop in was
irrelevant, and misleading). I may try again with it if still I can't
work out the answer, and phrase the question better next time.
I have to say though, having worked with ASP.NET, the templating
system is a much better approach - it's a lot more intuitive, and
certainly more transparent (which is a godsend when trying to add
javascripts and ajax stuff!) I've even got a MochiKit demo working
now :-)
Thanks again,
Mobeus.
On Jan 13, 7:24 pm, "Karen Tracey" <kmtra...@gmail.com> wrote:
> On Tue, Jan 13, 2009 at 12:31 PM, dr.mob...@googlemail.com <
>
> dr.mob...@googlemail.com> wrote:
>
> > Hello,
> > I'm new to DJango, but I'm already lovin' it. I have a few questions
> > however - can someone offer any guidance, please?
>
> > Is the possible following in a template:
> > { inherits ... }
>
> I take it you mean extends, not inherits, here.
>
>
>
> > {% for item in items %}
>
> > {% block A %}
> > some text here
> > {% endblock A %}
>
> > {% block B %}
> > some other text here
> > {% endblock %}
>
> > {% endfor %}
>
> > without there being another block wrapping the for loop?
>
> No.
>
> > I've tried it
> > and I cannot get it working, but I think I remember some an example
> > doing so... I guess the general point of my question is - do all
> > constructs have to be wrapped in a block?
>
> Yes, in a template that is extending another, everything has to be in a
> block. Fromhttp://docs.djangoproject.com/en/dev/topics/templates/#id1:
>
> The {% extends %} tag is the key here. It tells the template engine that
> this template "extends" another template. When the template system evaluates
> this template, first it locates the parent -- in this case, "base.html".
> At that point, the template engine will notice the three {% block %} tags in
> base.html and replace those blocks with the contents of the child template.
>
> Thus, the only thing relevant in a child template is text contained in {%
> block %} elements that were previously defined in a parent template. There
> isn't any place for text outside of such {% block %} tags in a child
> template to go -- where would it be logically placed in a parent template?
>
> I'll leave the block.super question for someone else to answer, as it's not
> immediately obvious to me what you are asking and I've run out of time right
> now.
>
> Karen
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
