Right. As much as I would like the functionality... This cannot be done as the system stands. Child templates know nothing of their parent, therefore they are unable to request anything from the parent template.
The way that you effectively override a block is by effort of the parent looking at all its children and going "Hey, you have the same block I do, so I will use yours". So the way to do this, is for the child to know about its parent, and its parents parents, and parents parents parents (etc, depending on the level of hierarchy.) The issue is, how does this element then determine which parent it should pull from, assuming the grandparent defines a block, and the parent overrides the block, what is left is not what is intended. -- Thadeus On Wed, May 5, 2010 at 8:28 PM, Yarko Tymciurak <[email protected]> wrote: > nyway, I don't know what the right syntax / implementation (exactly) > of a template "super" function is - I just know it makes sense, and I > think we should have it (I am certainly investing a lot of effort in > driving exploration of how it would work, look, and w
