I can't really say, we need some tests to analyze the effects of this. I am thinking of a way that might not include any extra overhead at all.
-- Thadeus On Wed, May 5, 2010 at 10:02 PM, mdipierro <[email protected]> wrote: > Before you go and implement this can you assess if this will affect > the speed of template processing? > > On May 5, 9:57 pm, Thadeus Burgess <[email protected]> wrote: >> It might be possible for the parent to look into its children, and >> analyze the child blocks, and if a block in the child contains a >> {{super <me>}} it can then take its own value and replace it into the >> {{super me}}. >> >> -- >> Thadeus >> >> On Wed, May 5, 2010 at 9:56 PM, Thadeus Burgess <[email protected]> >> wrote: >> > 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 >
